MC1903's Accepted Solutions

Tried 'disabling CEIP' as per https://kb.vmware.com/s/article/76053 but the service restart eventually got stuck in a loop waiting longer and longer each time for something to come ready. Gave up and trashed the vRA deployment: SSH'd into the vRA, as root, and confirmed the vco-app pod was in the CrashLoopBackOff state with kubectl -n prelude get pods Crashed out the vRA install (powered the vRA VM off & deleted it). SSH'd into the vRSLCM instance and gracefully restarted it. Deleted the dead vRA environment from within vRSLCM Recreated a new environment for vRA within vRSLCM Added a certificate for vRA into the locker Installed vRA into the newly created environment. SSH'd into the vRA once it was up and monitored the pod install/startup with  watch -n 5 kubectl -n prelude get pods 34 minutes from start to finish. Done!

After much searching through the vCenter Server file system I found what I was looking for. ** Proceed at your own risk - I am sure this is probably NOT SUPPORTED by VMware GSS ** There is a file named com.vmware.usersetting.recenttasks.columns in the VCSA's /storage/vsphere-ui/SerenityDB/serenity/{username}/ directory. Log the user out of all vCenter vSphere Client sessions, delete the file and then log them back in. The Recent Tasks layout has been reset.  

Doh, school boy error... Note to self...Read the prerequisites TWICE, check the system meets them and then RECHECK!.. Turns out that my vDS had NOT been upgraded from 6.5.0.!! I upgraded it to 7.0.0 and the reconfigure task runs as expected. I feel a bit silly, but at the same time I expect the wizard to have checked the prerequisites and this should have been flagged. depping​ TheBobkin​ Would one of you gents be able to flag this to engineering for review in a future release? Thanks. M