### Human: Can you tell about One Click Hypervisor (ESXi) Upgrade Caveats and Troubleshooting. ### Assistant: One-Click Hypervisor (ESXi) Upgrade Caveats and Troubleshooting. One Click Hypervisor Upgrade for ESXi has the following caveats that need to be kept in mind should the same fail.

Issue #1

URLDecoder: Illegal hex characters in escape (%) pattern - For input string:



This comes up if:

The Metadata and Binary files are either incorrect; orThe Binary file is chosen in place of the JSON file and vice versa

So once you click on Software Update - Hypervisor:

HYPERVISOR METADATA FILE - this is the JSON fileHYPERVISOR BINARY FILE - this is the ESXi upgrade image

Upgrade will further fail with a size mismatch if:

The JSON file and the ESXi image build numbers do not matchCorrect JSON build number and ESXi build number are chosen but the ESXi ISO image is used. For this to work, you will need the ZIP (Depot)

So essentially, using the below combination will fail either with a size mismatch or "URLDecoder: Illegal hex characters in escape (%) pattern - For input string:"

VMware-VMvisor-Installer-6.0.0-2494585.x86_64.iso6.0.0-2494585.json

Issue #2

URLDecoder: Illegal hex characters in escape (%) pattern - For input string:

URLDecoder: Illegal hex characters in escape (%) pattern - For input string:

Attempted to modify the Hypervisor Upgrade JSON file to add an ISO file.

After realizing the mistake, uploaded the correct zip file, but received the "Bundle integrity verification" error.



Issue #3

URLDecoder: Illegal hex characters in escape (%) pattern - For input string:



Issue #4

Available compatible versions show "not qualified"

 

Issue #5

URLDecoder: Illegal hex characters in escape (%) pattern - For input string:

. Issue #1

To resolve this issue, the correct files needed are:

VMware-ESXi-6.0.0-2494585-depot.zip and6.0.0-2494585.json

Note: For this to work, the Virtual Center Server needs to be upgraded to vSphere 6.0 Build 2494585 or later prior to the ESXi upgrade. Else, the upgrade with fail with:

2015-09-02 00:27:54 INFO cluster_upgrade.py:351 Current host version: 5.1.0-1065491

If you are using the Virtual Center Virtual Appliance (Linux based VCVA), the account that needs to be used is root because administrator@vsphere.local might fail with a username password error.

Logs will show the below:

2015-09-02 00:27:54 INFO cluster_upgrade.py:351 Current host version: 5.1.0-1065491

Should the root account be used and the below messages come up, then the root account does not have access to the Virtual Center Inventory. In such a case, the root account will need to be provided access to the Virtual Center Inventory by using the administrator@vsphere.local and adding the root user to the SSO permissions so it has access to the inventory.

2015-09-02 00:27:54 INFO cluster_upgrade.py:351 Current host version: 5.1.0-1065491

Or:

2015-09-02 00:27:54 INFO cluster_upgrade.py:351 Current host version: 5.1.0-1065491

If the above message is seen, log on with the root user to the Virtual Center Server and confirm you are unable to see the Inventory Objects (ESXi hosts, Virtual Machines, etc.)

To add permission for the root user, log on to the Virtual Center Server using the administrator@vsphere.local

Log in to the Web client “https://client-hostname:9443/vsphere-client” with administrator@vsphere.local using the password of whatever you configured SSO password as. *Note you can only configure SSO using the Web Client*Navigate to vCenter Servers > Manage > Permissions, click on the + to add a userNow add the root (localhost) to vCenter along with the permissions required and click on OK.Try and login with the user you just configured and you should now have access to the Web client or the Windows vSphere UI Inventory

Should the below be seen:

2015-09-02 00:27:54 INFO cluster_upgrade.py:351 Current host version: 5.1.0-1065491

The hosts need to be a part of the vSphere Cluster in vCenter.

Admission control can cause pre-upgrade to fail at 33%.

2015-09-02 00:27:54 INFO cluster_upgrade.py:351 Current host version: 5.1.0-1065491

Should this be the case, go to Cluster Settings on Virtual Center and check the "Disable: Power on VMs that violate availability constraints".



In vCenter 6.5, this is how you disable Admission Control:

In the vSphere Web Client, browse to the vSphere HA cluster.Click the Configure tab.Select vSphere Availability and click Edit.Click Admission Control to display the configuration options.Select a number for the Host failures cluster tolerates. This is the maximum number of host failures that the cluster can recover from or guarantees failover for.Select an option for Define host failover capacity by:
	DisabledSelect this option to disable admission control and allow virtual machine power on that violate availability constraints.

	* Note the original configuration before disabling admission control so that you can put it back post-upgrade.
	Click OK.

For the One-Click to work, the following needs to be configured as these are a part of the Pre-Upgrade Checks and needs to be enabled prior to the upgrade attempt.

root user needs to have access to the Inventory ObjectsvMotion needs to be configured and enabledDRS needs to be enabled

Issue #2

Remove all downloaded files from CVMs:

2015-09-02 00:27:54 INFO cluster_upgrade.py:351 Current host version: 5.1.0-1065491

Issue #3

Most of the time, this issue is because the host SSH is disabled.

Run "ncc health_checks run_all" and if you see below FAIL messages, enable SSH on the hosts and run the pre-upgrade check from Prism one click.

2015-09-02 00:27:54 INFO cluster_upgrade.py:351 Current host version: 5.1.0-1065491

Issue #4

After uploading the files (JSON and ZIP), you see a "(not qualified)" next to the ESXi version in Prism and there is a Retry button instead of Upgrade.

You see the following in the genesis.out:

2015-09-02 00:27:54 INFO cluster_upgrade.py:351 Current host version: 5.1.0-1065491

Do the following:

Check MD5 value of the Hypervisor zip bundle and compare it to the vendor provided value (available from the VMware download or Dell download site in case of customized ISO)Check the MD5 value of the JSON file. Ensure that the latest available version is downloaded from portal.nutanix.com. In this case, the JSON had a different MD5 value, and downloading a fresh JSON should work.

Issue #5

Most of the time, this issue is because of the wrong credentials or wrong vCenter IP addresses.

Make sure credentials are correct and to double-check the correct vCenter IP is provided, run "hostssh grep serverIp /etc/vmware/vpxa/vpxa.cfg" and you will see the IP address of vCenter that host is connected.

2015-09-02 00:27:54 INFO cluster_upgrade.py:351 Current host version: 5.1.0-1065491

Another way to check the vCenter IP address is run "ncli ms list-management-server-info".

2015-09-02 00:27:54 INFO cluster_upgrade.py:351 Current host version: 5.1.0-1065491

Issue #6

The upgrade process may get stuck on a one or multiple ESXi hosts when upgrading from ESXi 6.7 to ESXi 7.0. Customer may report that the upgrade is stuck for a long time at a particular percentage.

Hypervisor logs under /scratch/host-upgrade.log on the ESXi host will show Timeout occurred during entering maintenance modevCenter task "Entering Maintenance mode" for that host will be stuck at ~70% with the message "Waiting for active NFC sessions to terminate". Manually putting the host into maintenance mode will also result in the same issue.Restarting the vpxa service on the affected ESXi host allows the host to enter maintenance mode.

Use the command:

2015-09-02 00:27:54 INFO cluster_upgrade.py:351 Current host version: 5.1.0-1065491
In order to resume the upgrade, restart genesis across the cluster using the below and command and monitor,

2015-09-02 00:27:54 INFO cluster_upgrade.py:351 Current host version: 5.1.0-1065491. ### Human: Now explain this as a Nutanix support agent summarizing the answer step by step. In case, you don't know the answer say - I don't know.