vRops environment sync fails after manually changing the root password of vRops node from LCM
book
Article ID: 345989
calendar_today
Updated On:
Products
VMware Aria Suite
Issue/Introduction
- To successfully update the new root password on each node and succeed inventory sync for the vRops environment from LCM
Symptoms:
- vRops environment sync fails after manually changing the root password of vRops node from LCM
- Changing to a new password fails from LCM every time on each node
Environment
VMware vRealize Suite Lifecycle Manager 8.x
Cause
- This can happen if you manually change the vrops node passwords outside of the LCM.
Resolution
Workaround:
- To workaround, follow the steps below :
- ssh as root on vrops node.
- On the vrops node run the below command to remove old password entries so that existing password as per locker can be re-used:
rm /etc/security/opasswd
- Set the same password after viewing the password (existing entry) from locker as new password for the node:
passwd
- From the LCM UI create a new locker entry for your new vrops node password.
- Change the password from LCM UI for the node :

- Repeat the process on each node of the vrops cluster
- Once password successfully changed on all nodes , trigger and inventory sync and it should succeed.
Additional Information
Impact/Risks:
- Inventory sync from LCM will fail unless fixed.
Feedback
thumb_up
Yes
thumb_down
No