Distribution Known Issues
Detected Version
To check whether a released version has a known issue detected in it, look for the version number.
Distribution 2.19.1 Known Issues
| Issue ID | Description | Fix Version | Additional Information |
|---|---|---|---|
| JR-7346 | Mission Control is not able to properly identify the home Artifactory in cloud environments. | TBD | |
| JR-7298 | The Export option is displayed in the UI but is not available in the current version to Cloud users. | TBD | |
| JR-7344 | When viewing the Actions Tracking tab for all versions of a Release Bundle, the View Details option does not provide any details about a distribution action. | TBD | The View Details option does work when viewing the actions of a specific Release Bundle version. |
Distribution 2.16.2 Known Issues
| Issue ID | Description | Fix Version | Additional Information |
|---|---|---|---|
| JR-6130 | In some cases of a heavily loaded environment, Release Bundle distribution succeeds and shows in Distribution as COMPLETED, but some of the artifacts are not copied to the target Artifactory. This causes errors when viewing the content of the Release Bundle in the Received tab, or when trying to download Release Bundle artifacts, from the target Artifactory. | Artifactory 7.50.3 | This known Artifactory issue affects all versions of Distribution that were available prior to the release of Artifactory 7.50.3. |
Distribution 2.14.1 Known Issues
| Issue ID | Description | Fix Version | Additional Information |
|---|---|---|---|
| JR-5938 | No signing keys displays for non-admin users. | 2.14.3 |
Distribution 2.13.2 Known Issues
| Issue ID | Description | Fix Version | Additional Information |
|---|---|---|---|
| JR-5569 | API Key is not supported in the Access Client | 2.13.3 |
Distribution 2.12.0 Known Issues
Issue ID | Description | Fix Version | Additional Information |
|---|---|---|---|
Unable to create a release bundle from artifacts in a Project-assigned repository. Related to Artifactory 7.35.1 | 7.37.12 |
Distribution 2.11.0 Known Issues
| Description | Fix Version | Additional Information |
|---|---|---|
| A critical issue causes a distribution process to fail when using older Artifactory versions. | 2.11.1 |
Distribution 2.10.3 Known Issues
| Description | Fix Version | Additional Information |
|---|---|---|
| Unable to perform authentication to SaaS instance using user/password method |
Distribution 2.9.3 (Upgrade from 2.7.2 and 2.9.2) Known Issues
Description | Fix Version | Additional Information |
|---|---|---|
Unable to display distribution targets on UI - missing Mission Control backwards compatibility. Related to Artifactory 7.25.6 &Mission Control 4.7.3 | Workaround: You will need to upgrade Mission Control, preferably to 4.7.16, since 4.7.3 does not return the base URL, so that Distribution sets a null in place of it. | |
Distribution removes the properties that were set on the edge node repository. This means that there is a possibility that all the properties set by customer will be overridden. | 7.31.x | Fixed in Artifactory to resolve known issue. |
Distribution 2.9.2 Known Issues
Issue ID | Description | Fix Version | Additional Information |
|---|---|---|---|
| RTFACT-26363 | The distribution process fails with "Not found 400" errors when release bundles are being distributed after the Incomplete Release Bundles Cleanup Period time period and if the release bundle clean up job is triggered at that corresponding time. Related to Artifactory 7.25.6 &Mission Control 4.7.11 | Suggested Workaround: Increase the Incomplete Release Bundles Cleanup Period | |
| RTFACT-26382 | Edge nodes are not visible if a user has multiple permission targets associated with them. | For the non-admin users that have references in multiple permission targets, make sure to have only one permission target where the user is referred. |
Distribution 2.9.0 Known Issues
| Description | Fix Version | Additional Information |
|---|---|---|
| Conflicting target path for the Docker layers | 2.9.1 |
Updated 3 months ago