Cloud customer?
Start for Free >
Upgrade in MyJFrog >
What's New in Cloud >

Search





Overview

The following document lists the set of known issues in the JFrog Platform, including the version in which they were discovered, and the version in which they were fixed (if relevant). For JFrog Artifactory issues, click the issue ID for the details in JIRA.

Known issues are based on the following criteria:

  • Severity 1 critical issues
  • Breaking changes for upgrades
  • Issues that have caused downtime and restarts

How do Known Issues Affect Your System?

In this document, you will find the issues that met the criteria above and that were detected in a released version (only). When considering an upgrade to your system, we recommend that you review the Known Issues below (including the database schema issues that follow) to help you determine which is the right upgrade for your system.

Page Contents


Known Issues

Issue IDJFrog ProductDescriptionAffected From VersionFix VersionAdditional Information

PipelinesThe runtrigger crashes, which causes the pipeline to get triggered multiple times.1.18.01.18.1

PipelinesThe "Uploading step information' was looped 270 times for a single step that errored out.1.18.01.18.1

PipelinesThe Jenkins Native steps get stuck.1.18.0


DistributionConflicting target path for the Docker layers2.9.02.9.1

XrayThe scan build times out when the build name contains '/'3.27.03.30.2
RTFACT-26250ArtifactoryThe link to the HTTP-SSO does not work after the upgrade and generates an error message.7.24.37.24.6

ArtifactoryArtifactory fails to start due to a circular reference of systemRepoFactory.7.26.07.26.1

ArtifactoryMDS migration causes the distributed_locks table to bloat during a 6.x to 7.x upgrade.7.2.17.24.0

RTFACT-21580

ArtifactoryUsing join key twice (in file and system.yaml) causes startup failures7.2.17.11.1

ArtifactoryThe Conan repositories created in the Free Trial are broken in version 7.9.0:  Free Trial instances do not support Conan repositories; therefore, it is not possible to configure users using Conan repositories. 
7.9.07.10.5

ArtifactorySystem messages do not work in the UI.7.8.27.9.0
RTFACT-23368ArtifactoryWhen an Azure guest user tries to log in to Artifactory, they are not able to log in successfully.7.7.37.10.1

ArtifactoryArtifactory 7.8.0 does not start up after upgrading from Artifactory 6.21.0.7.8.07.8.1

ArtifactoryUnable to run Singleton type tasks, such as garbage collection. Singleton type tasks are marked with markers to decide if they can run and stop other tasks from running.7.6.27.7.0

Artifactory

Because the addition of the "Allow Content browsing" in feature allowed stored XSS and phishing, an addition was made to version 6.23.16 to remove this potential security issue. However, this addition can lead to problems with accessing resources like XML, HTML due to the new CSP header  "Content-Security-Policy: sandbox".

6.23.167.17.2
RTFACT-22591ArtifactoryWhen trying to pull Docker images through mcr.microsoft, the proxy mcr.microsoft no longer works. This is probably due to an upgrade with the HTTP client.6.20.07.6.4, 6.21.0

ArtifactoryPostgreSQL driver should not be bundled in WARs but under tomcat/lib (the Postgres driver is being added twice in Docker containers: both as part of the Artifactory war (artifactory-online-war) and copied during the Docker build (artifactory-pro-docker)).7.6.17.7.0

ArtifactoryArtifactory failed to start after redeployment.7.5.27.6.1

ArtifactoryArtifactory fails to start in Azure SAAS due to "FileNotFoundException: /home/artifactory/.postgresql/root.crt". Consistently affects both AOL and JCR editions in SAAS. This issue occurs when we perform a redeploy of a SaaS customer with a new version, and occurs only on Azure staging environments (as opposed to other cloud providers).7.6.07.6.1
ArtifactorySetting the default system proxy also changes the existing remote repositories definition.7.0.07.27.0
RTFACT-21838ArtifactoryNuget local repository may return an incorrect version when IsLatestVersion=true.6.19.07.5.0, 6.20.0, 6.19.1
RTFACT-21287Artifactory

Re-indexing a path on the metadata server will cause a connection leak and eventually a starvation of connections of the database connection pool, due to a query with a lazy AQL query with an unclosed result set.

7.0.07.2.0
Artifactory

Artifact search performance issue due to case-insensitivity.


7.0.0

From Artifactory 7.0.0, the "artifact search" via UI/API is case-insensitive by default. The case-insensitive search can be disabled by applying the following property:

artifactory.ui.search.artifacts.caseInsensitive=false


Database Schema Known Issues

The JFrog Platform requires a common database upgrade infrastructure for all products. Currently, each product has a different implementation, so the following database schema-related issues are also addressed in this Known Issues document.

Issue IDDescriptionAffected From VersionFix VersionAdditional Information

RTFACT-25637

Problems when upgrading from 6.16.2 to 7.7.8 7.7.8


Artifactory does not cleanly remove deleted configuration import files7.12.67.23.3

RTFACT-22649

The security.<timetstamp>.xml file is being synced between nodes after upgrade upon Artifactory start process 7.5.77.23.3
  • No labels
Copyright © 2021 JFrog Ltd.