Do not rename hosts from VCenter when ESX, NSX upgrade is in progress, orchestrated by SDDC-Manager

Products

• VMware Cloud Foundation
• VMware SDDC Manager

Issue/Introduction

• Upgrade failure could occur at multiple stages depending on when the host rename is attempted.
• To guide on what steps to suggest in case you are seeing a failure in upgrades, immediately after renaming a host when upgrade is in progress. 

Environment

VMware Cloud Foundation 9.0

Cause

Renamed a host in vCenter when SDDC Manager is orchestrating ESX or NSX upgrade and the LCM cache was stale when ESX host name was used to retrieve host details from cache

Resolution

Issue is resolved in VMware Cloud Foundation 9.0

 

Workaround:

• Ensure the host name is updated in SDDC Manager inventory by refreshing the Hosts tab or the using the /v1/hosts API in Developer Center. New host FQDN should be reflected for the updated host.
• The LCM cache refreshes every 5 mins. Wait for 5 mins before retrying the upgrade OR restart LCM service before proceeding with upgrade using `systemctl restart lcm` to ensure the cache is updated.