Workaround | You need to follow these steps to fix this issue.
- Do test connection for both the broker services and see if it is successful and manually delete the instance of the broker service from UI for which test connection fails. It will remove the entry from the DB as well and show all the correct entries in the UI.
- In this case, test if the connection for both the broker services is successful. Therefore you need to perform the followings.
- Manually delete the first instance of the broker service from UI
- Run the below command after SSH login to the admin node
# orchestration-cli-client --update-admin-node
Once completed, you can see that duplicate broker service is now removed in NW GUI(ADMIN > Services). If you are unsure of any of the steps above or experience any issues, contact RSA Support and quote this article number for further assistance. |