ARTIFACTORY: How to overcome the error "Can't perform changes when disabled member present. Found disabled member"

ARTIFACTORY: How to overcome the error "Can't perform changes when disabled member present. Found disabled member"

AuthorFullName__c
Elina Floim
articleNumber
000005811
ft:sourceType
Salesforce
FirstPublishedDate
2023-07-12T13:44:38Z
lastModifiedDate
2023-07-11
VersionNumber
1

Under certain circumstances, attempts to delete a federated repository can result in the following error:

"errors" : [ {
    "status" : 500,
    "message" : "Can't perform changes when disabled member present. Found disabled member: https://ART_HOST/artifactory/federated-local."
  } ]

This error may occur even though the federated repository has no associated members and is disabled. This issue has been fixed in Artifactory version 7.59.12.

If this is the case and if an upgrade is not possible right away, it is possible to first remove the federated members (under the “federatedMembers” section of the repository config) of the affected repository from the repository config descriptor (artifactory.repository.config.latest.json for Artifactory versions 7.49.x and above) or from the config descriptor, (artifactory.config.latest.xml for Artifactory versions older than 7.49.x) before being able to delete the repository itself:
"federatedMembers" : [
               {
                  "enabled" : false,
                  "url" : "https://ART_HOST/artifactory/federated-local"
               },
               {
                  "enabled" : false,
                  "url" : "https://ART_HOST/artifactory/federated-local-east"
               },
               {
                  "enabled" : false,
                  "url" : "https://ART_HOST/artifactory/federated-local-west"
               }
            ]

In addition, you may be required to remove the entire repository configuration section of the desired federated repository from the config file. After removing the federated repository section from the config file, the artifactory.repository.config.latest.json (or artifactory.config.latest.xml, depends on the version) file needs to be bootstrapped for the changes to take effect. More information on how to bootstrap the repository or global configuration can be found here and here respectively.