trying to upgrade VCF to 4.2 from 4.1, the SDDC manager upgrade completed but now fails at the next step - 'configuration bundle drift update".
It looks like it's trying to update the cluster HA config and fails with "VSPHERE_HA_UPDATE_ISOLATION_RESPONSE_FAILED Failed to set vSphere HA Isolation Response for VM(s)" error (full log is attached).
Any help would be appreciated.
May I know did you solved the issue? I got exactly the same issue as you.
First the VSPHERE_HA_UPDATE_ISOLATION_RESPONSE_FAILED Failed to set vSphere HA Isolation Response for VM(s)"
Second the error of reconfigure cluster error in vCenter.
It turned out that one of the Edge VMs somehow got removed from the "VM Overrides" configuration section in vCenter (on the cluster level). Once all Edge nodes were added to the "VM Overrides" with "vSphere Restart Priority" set to "high", the upgrade was able to get past this error.
Im hitting the same issue and sure enough, "someone" had messed with the VM Overrides options for the edge VMs. I have corrected these but when trying to retry the upgrade, Im now getting:
Scheduling immediate update of bundle failed. Http failure response for https://sddc-manager.mydomain.example/ui/api/v1/upgrades: 400 Bad Request
Any ideas whats stopping me retrying?
Have a look at the operationsmanager.log to see if you can get any more information.
Only thing i see in that log is:
Can't find resource for bundle java.util.PropertyResourceBundle, key PASSWORD_UPDATE_FETCH_VREALIZE_NODE_DETAILS_FAILED.remedy
But I dont think that is related.
I do have a "Fetching task info... " stuck in pending since. Any easy way to clear this?
You can reboot the service or reboot SDDC Manager, the task should come back as failed upon reboot / service starting fully.
Yeah, reboot didn't clear it.
I think ill pause for the night and rethink this tomorrow by reverting snapshot and trying again with support.
Thanks for the help !
One more way to run the precheck before starting the upgrade . NSX-T affinity rules will not remove automatically , If you do the precheck it will tell u node cannot go into MM mode .
your logs clearly tell Caused by: com.vmware.vim.binding.vim.fault.InvalidDasConfigArgument: The setting of vmConfig is invalid for cluster m01-cl01. something wrong . with setting .