Description:
In some configurations and usage scenarios of Federated Repositories, you may encounter issues where the "Federated Repository" cannot be deleted from "Deployment Bindings".
For example:
After configuring Deployment Bindings between two JPDs (e.g., JPD A and JPD B), if you change the Base URL of JPD A and try to reconfigure the Deployment Bindings with JPD B using the new Base URL, the old Deployment Bindings may become undeletable due to the Base URL has changed. When trying to delete them, the list of relationships for deletion appears empty, as shown below:
This article will guide you through how to solve this issue.
Root Cause:
"Deployment Bindings" depend on the base URL of JPDs. For example, after the base URL of JPD A is changed, JPD B still uses the old address of JPD A; the previous "Deployment Bindings" information may persist and cannot be deleted through the UI.
Solution:
We can remove the old "Deployment Bindings" information using the following steps:
- Back up the Config Descriptor data. Navigate to JPD A UI | Administration | Artifactory Settings | Config Descriptor and back up the data;
- In the "Config Descriptor" on JPD A, find the following section containing the JDP B's address and remove it, and also do it in "Config Descriptor" on JPD B, remove the following section containing the JDP A's address:
- After deleting, return to the UI and check that the old relationship information for "Deployment Bindings" has been cleared:
Now, you can reconfigure the "Deployment Bindings".