vRops environment sync fails after manually changing the root password of vRops node 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

Purpose

• To successfully update the new root password on each node and succeed inventory sync for the vRops environment from LCM

Cause

• This can happen if you manually change the vrops node passwords outside of the LCM.

Impact / Risks

• Inventory sync from LCM will fail unless fixed.

Resolution

• There is a workaround.

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.