This is a known issue affecting vRealize Operations Tenant App for vCloud Director 8.6, and is resolved in version 8.6.1.
Workaround:
To workaround the issue:
- Take a snapshot of the vRealize Operations Tenant App for vCloud Director VM through the vSphere Web Client
- SSH to the vRealize Operations Tenant App for vCloud Director as root
- Run the following command
docker images -a
- If "vmware/vrops-vcd-tenant-app-db-cassandra" is missing from the output of the previous step, run the following command
docker load -i /opt/vmware/db/vrops-vcd-tenant-app-db-cassandra.tar.gz
- If "vmware/vrops-vcd-tenant-app-plugin" is missing from the output of step 3, run the following command
docker load -i /opt/vmware/plugin/vrops-vcd-tenant-app-plugin.tar.gz
- If "vmware/vrops-vcd-tenant-app-ui" is missing from the output of the step 3, run the following command
docker load -i /opt/vmware/app/vrops-vcd-tenant-app-ui.tar.gz
- Open /opt/vmware/va/config/subsequentboot.sh using a text editor of your choice
- Comment out (add a # symbol to the beginning of the line) remove_existing_images
- Save the file and exit
- Reboot the vRealize Operations Tenant App for vCloud Director appliance