VMware Networking Community
willonit
Hot Shot
Hot Shot
Jump to solution

Uninstalling stuck in progress

I went to prepare a cluster but the hosts never fully installed. I figured I'd uninstall and give it another try. Now all the hosts in the cluster report "In Progress" with the cluster status "Uninstalling". It has been like this for over a day now. I've rebooted all hosts multiple times and checked that the VIBs have been removed. The manager and controllers have been rebooted as well. Is there anyway to reset the cluster or end the removal task?

Thanks,

Will

1 Solution

Accepted Solutions
willonit
Hot Shot
Hot Shot
Jump to solution

The vibs had already been uninstalled but the task was still hung. I was able to work around this issue by disconnecting each host and adding back to a different cluster. I deleted the cluster that was stuck and was then able to prepare the hosts in a new cluster. It even kept track of NSX edge gateways that were on the hosts when they moved. The only think I lost was VM folder structure. The hosts installed without issue and have now been added into my transport zone.

View solution in original post

7 Replies
Gaurav_Sangamne
Contributor
Contributor
Jump to solution

Hi ,

You can try to uninstall the VIBs manually using CLI.  The install process typically install 3 VIBs on the ESX hosts, we need to try removing them manually ..

To remove the “esx-vxlan” VIB , execute the below command:

esxcli software vi remove -n esx-vxlan

To remove the “esx-vsip” VIB , execute the below command:

esxcli software vi remove -n esx-vxlan

To remove the “esx-dvfilter-switch-security” VIB , execute the below command:

esxcli software vi remove -n  esx-dvfilter-switch-security

Try refreshing the client after this ..

G

Reply
0 Kudos
willonit
Hot Shot
Hot Shot
Jump to solution

The vibs had already been uninstalled but the task was still hung. I was able to work around this issue by disconnecting each host and adding back to a different cluster. I deleted the cluster that was stuck and was then able to prepare the hosts in a new cluster. It even kept track of NSX edge gateways that were on the hosts when they moved. The only think I lost was VM folder structure. The hosts installed without issue and have now been added into my transport zone.

JayhawkEric
Expert
Expert
Jump to solution

I was having the same problem for the past couple days as well.  This fixed my issue. Thanks for posting.

VCP5-DV twitter - @ericblee6 blog - http://vEric.me
Reply
0 Kudos
lerf2
Contributor
Contributor
Jump to solution

I also found a more easier solution to get rid of hang at "Uninstalling..." in Host Preparation.

You can go to vCenter > Home > vCenter Solutions Manager > vSphere ESX Agent Manager > Management tab.

If the VMware Network Fabric status is "Uninstalled" "Normal" you can try to right click on the item and "Resolve" / "Sync" and "Delete" that agent.

By doing this, we expect the Network Fabric agent being deleted.

Ricktamu
Contributor
Contributor
Jump to solution

This is the correct Answer...Been banging my head against the wall all night.  Thank you!!

Reply
0 Kudos
VMwareGeek_
Enthusiast
Enthusiast
Jump to solution

Not worked for me, for couple of days, I am trying to make two same hosts to success on nsx vib installation. Try to disconnect and add to another cluster, nsx progress always comes at 40% Removing NSX bits and stuck there. This is just a nightmare.

Reply
0 Kudos
cms7
VMware Employee
VMware Employee
Jump to solution

In these sort of situations, you could also try the command line option and the steps as below: -

1. Login to the problematic hosts and check for any NSX vibs present with below command:

'esxcli software vib list | grep nsx'  IF there are any NSX vibs present on host remove then with the below command:-

'esxcli software vib remove -n <vib-name to be removed>' or 'esxcli software vib remove --vibname=<name of vib to be removed>'

Check again with cmd: 'esxcli software vib list | grep nsx' that there are no NSX vibs present on the host.

2.Then reboot the ESXI host after putting it into maintenance mode if its part of a vSphere DRS/HA cluster.

3.Post reboot get the host out of maintenance mode, and retry the NSX installation on the host and it should succeed.

When this works for you, please give a Kudos, and mark this as a correct solution, thanks

Reply
0 Kudos