Artifactory 7.104

RTFS-2128

Failures occur when migrating to the Artifactory Federation Service (rtfs) due to NGINX routing requests to the Artifactory service instead of rtfs.Migrate to the Artifactory Federation ServiceArtifactory Federation Service

TBD

Can affect users in Self-Hosted environments who have a custom NGINX configuration or who use the NGINX configuration created by the JFrog platform UI.

Suggested workaround:

Explicitly add port 8082 to the URL in the /artifactory section of the NGINX configuration file:

if ($request_uri ~ ^/artifactory/service/rtfs/(.*)$ ) {
            proxy_pass       http://localhost:8082/artifactory/service/rtfs/$1;
            break;
}

Where localhost is whatever has been defined for your installation.

INST-10964

Upgrading existing Artifactory installations only for Linux Archive, Debian, and RPM in service mode, where console.log is disabled (shared.logging.consoleLog.enabled: false) in system.yaml may fail because the newly added One Model registry service does not start and results in a "connection refused" error.

7.111.7

Suggested workaround:

Before upgrading, enable console.log in system.yaml.

RTDEV-55119

In certain cases, Artifactory initialization can fail due to delays while waiting for Access to check if the customer has migrated to the Artifactory Federation Service (rtfs).Artifactory Federation Service

7.104.15

This issue is relevant for Self-Hosted customers who have not yet migrated to the Artifactory Federation Service.Artifactory Federation Service

A solution to this issue will be made available in an upcoming patch release.

Suggested workaround:

Run the following commands before starting Artifactory to bypass the check:

sql
INSERT INTO public.configs (config_name, last_modified, data)
VALUES ('rtfs.enabled', EXTRACT(EPOCH FROM NOW())::bigint, 'true'::bytea);

RTFE-2718

In release 7.104.9, an infinite loop occurs when searching for a package by name in the top search bar on the Packages page.

7.104.10

Customers are asked to avoid installing release 7.104.9 and upgrade directly to 7.104.10.

MDL-483

Under certain circumstances, when running an Artifactory instance with the $JFROG_HOME/artifactory/var/data and $JFROG_HOME/artifactory/var/work folders located on different partitions (using mounted volumes), the OneModel Registry service is unable to publish the supergraph. This results in a failure during the Artifactory startup.

7.104.7

RTFACT-31038

An unannounced change was introduced by Conda Forge upstream which impacts Artifactory's ability to resolve package metadata and dependencies with virtual Conda repositories. For more information see this article.

7.104.6

Suggested workaround:

Use the Conda Remote Repository Directly: Instead of relying on the Virtual Conda repository, users can directly use the Conda remote repository (repo.anaconda.com/conda-forge) to download packages.

RTDEV-53914

Release Bundle v2 promotion to a virtual repository fails if the local repository aggregated inside it has been removed manually from the promotion.

7.107.1 (Cloud only)

Promotion to the local repository inside a virtual repository works only when the local repository is included in the promotion.