Artifactory 7.117

RPG-1841

A common issue has been identified with upgrading existing Artifactory HA installations. The upgrade process might fail because the Router service fails to start, displaying the following error: Could not update configuration for key

7.117.14

Suggested workaround:

To resolve this issue, delete the content of the Router Traefik folder located at /opt/jfrog/artifactory/var/data/router/traefik and then restart Artifactory.

Here is an example command to accomplish this:

rm -rf /opt/jfrog/artifactory/var/data/router/traefik

JFUI-18806

During startup and regular operation, the Artifactory Frontend service attempts to download resources from the public internet endpoint https://grpc.qwak.ai. In disconnected environments where access to this endpoint is blocked, the service may retry multiple times, possibly causing performance degradation of the Frontend service.

7.117.10

JFrog recommends avoiding the upgrade to this version if your organization's environment restricts access to this endpoint.

A fix that removes this request to the external resource will be released soon.

RPG-1831

A common issue has been identified with upgrading existing Artifactory installations that have Router TLS enabled (router.tlsEnabled: true) in the system.yaml file. The upgrade process might fail because the Router service fails to start, displaying the following error: Error during the build of the default TLS configuration: unknown TLS options: default.

7.117.7

Suggested workaround:

To resolve this issue, delete the content of the Router Traefik folder located at /opt/jfrog/artifactory/var/data/router/traefik, and then restart Artifactory.

Here is an example command to accomplish this:

rm -rf /opt/jfrog/artifactory/var/data/router/traefik

RTFS-968

Federation: Rapid delete followed by recreate of the same artifact path (within the same RTFS batch) could cause errors on the target member.

7.117.7

Cloud: Rolled out.

Self-Hosted: TBD

Suggested workaround:

Workaround (until patched): Temporarily reduce the RTFS workers’ batch size (e.g., to 1) to prevent delete+create from landing in the same batch.

Operational tip: Avoid back-to-back delete → recreate on the exact same path where possible.