VROPS Error "vmdir.password is not set; aborting installation" or "Failed to Configure Network"

After I patched VCSA 7.x U2 to VCSA 7.x U3h, I encountered this warning message in the VCSA Console -> "vmdir.password is not set; aborting installation"

To fix please follow below steps

- Login to VCSA SSH

- Delete/move the file /etc/vmware/cap/cap-firstboot.sh (removing this file will prevent the issue from occurring in the future) -> Run this command mv /etc/vmware/cap/cap-firstboot.sh /tmp

- Delete/move the file /var/log/firstboot/failed -> Run this command mv /var/log/firstboot/failed /tmp

- Create a new file "succeeded" under the directory /var/log/firstboot -> Run this command touch /var/log/firstboot/succeeded

- Take a backup of rpmInstall.json file -> cp /var/log/firstboot/rpmInstall.json /var/log/firstboot/rpmInstall.json.BAK

- Replace contents of /var/log/firstboot/rpmInstall.json with the below:

- To update the content of rpmInstall.json

- Run this command vi rpmInstall.json

- Type i to edit the content.

- Delete the original content and replace of the below parameters

{
  "progress": 100,
  "question": null,
  "status": "success",
  "progress_message": {
    "localized": "",
    "translatable": ""
  },
  "error": null,
  "warning": [],
  "start_time": "2021-06-13T14:28:50.278Z",
  "info": [],
  "end_time": "2021-06-13T14:47:07.972Z"
}

Note: Start and End times set to the estimated date the upgrade occurred.

- Press ESC on the keyboard

- To save type w;! and to exit type :q!

- You are all good now.

Note: If the message still shows on the console, execute this /usr/lib/applmgmt/dcui/notify script to immediately remove the message from DCUI.

Note: Reboot is not required

Workaround.

To prevent the issue from occurring:

If planning to update from 70U2 or if already updated but have yet to reboot the vCenter appliance, delete the file /etc/vmware/cap/cap-firstboot.sh following the steps below:

- Login into putty/ssh session to VC

- Delete the file /etc/vmware/cap/cap-firstboot.sh

VMware Reference: https://kb.vmware.com/s/article/84259