I have been trying to update the vCenter server appliance in my lab from 8.0.1.00300 to 8.0.2 but after data migration the appliance restarts and only displays a kernel panic.
I have been able to pin-point this issue to FIPS mode which seems to be enabled in the GRUB boot options. Once I set "fips=0" instead of "fips=1" the VM boots normally but the update still fails according to VAMI.
This also happens when I try to deploy a new VCSA with version 8.0.2.
I haven't had any issues in the past with updating or installing the appliance on older versions. Is there something I could do?
Thank you in advance!
Just curious how you were doing the update?
I did mine by mounting the patch ISO (not the full release) and then SSH to the VCSA. Don't use the bash shell once you connect and run the following commands :
software-packages stage --iso
software-packages install --staged
This ran all the prechecks and updated without any issues. Took about 20 minutes
I have tried multiple methods. Through VAMI (online and patch ISO) and through the CLI (with the patch ISO) as @pmichelli described but had the same outcome every time.
I believe the update process itself isn't the issue as the kernel panic also occurs when I deploy a new VCSA version 8.0.2 using the installer. Installing and updating to VCSA 8.0.0 worked flawlessly.
In my situation (upgrade worked), it was my test vCenter that has no hosts attached to it.
It is a second VM that lives in my DR cluster that I use only to test upgrades before moving to DR then to Prod clusters
The hardware backing it is a PowerEdge FX2 with FC640 Blades and Intel(R) Xeon(R) Gold 6238R CPU @ 2.20GHz for processor
@pmichelli did you ever run into the kernel panic issue or are you just telling us your upgrade worked? I'm sure plenty of people successfully upgraded using the multitude of available methods, but I'd like to hear from somebody who ran into this specific issue and what they did to resolve it.
No kernel panic. I only replied because VMware often wants to know from folks that had problems and those that did not. Perhaps its tied to the AMD chips. My upgrade (in a very scaled down test vCenter with no hosts or VMs attached to it) was successful with the CLI update.
There is no solution for the issue encountered and is limited to certain specific HW listed in the KB.
Only option for now is to deploy vCenter 80U2 on an alternate HW .