vSphere 7.0 Update 2 unable to upgrade

stuartp44phil — Thu, 16 Dec 2021 19:46:14 GMT

Hi All,

I have a large vSphere instance that I struggling to get to upgrade. We are running vmware vSphere version 7.0 Update 2b build 17958471 and have been for awhile. We regular backup this appliance and try to keep it up-to-date, however, we are failing short lately due to a fault we cant seem to shift. When trying to install anything above Update 2b, which includes update 3 and so on we get one of two errors. If we upgrade our solution with Update 2 aka 7.0.2.00200 to 7.0.2.00400, we get asked for the SSO password and then a error that just gets on my wick "Internal error occurs during the execution of the update process". We have tried this by invoking it through the management UI and also via the CDROM (with the patch-fp iso) using the CLI and nothing seems to get it going. Looking through the logs, I cannot see anything that points to bad play (other than a unknown error has occurred), so I am not sure what causes this. If we try and move to the next update version like 7.0.3, we get a pre check failure which again tells us nothing to what its failing on. I have tried a few culprits activities that I have seen, in the past, that have caused issues like removing our internal certificate and resetting it to default vmware one. We have also tried to deploy a new instance and restoring it from backup and then updating that with no success citing the same errors as above. With the security landscape being so bad at this moment, I am keen to get this resolved and really cant allow it to slip. Anyone else have this issue or give me some pointers to where to go/do?

PowerCLI Shortcomings or my lack of knowledge?

stuartp44phil — Wed, 10 Mar 2021 13:20:14 GMT

I am just putting out there and hope that someone can put to rest an issue we seem to face. We have recently converted from the forbidden VMRun to PowerCLI and this has allowed us to upgrade from vSphere/ESXi 6.0 to 7.0. It has been a hard and long process to de-bundle a lot from VMRun as we are a heavy user of the API's of vSphere more than the UI, as we develop software on it and mainly use it to test builds. So far, most things in the migration have gone well. However, there is one item that we have had to put in a large scale waste work around to overcome. It is causing API drama's as we have to do a lot of queries get the information we want. When running program in guest, we used to invoke it and then wait until it's finished and read its exit code all from the command line in one line. PowerCLI seems to behave in fire and forget, so we have to poll the VM running services to wait for our process to exit and then do some magic to pull down the exit code. Is this all there is? Does anyone else know of a hidden secret we dont? Looking at the MOB, I can't see anything we can pass to make it behave any differently. If anyone can help or point me to anything, that would be great.

stuartp44phil Tracker

vSphere 7.0 Update 2 unable to upgrade

PowerCLI Shortcomings or my lack of knowledge?