We added a new host to one of our vmware infrastructure providers, updated the ESXi version and build of the current hosts and since this change only one host (which wasn’t updated, or put into maintenance mode and also differe by not being in a cluster) is now being found as an eligible host during the
Note: The host found to be eligible is running ESXi Version: 5.5.0 Build Number: 2068190, where as the upgraded and additional host are ESXi Version: 6.0.0 Build Number: 7967664.
All the hosts are listed via the call to
ems.hosts.each....., but not
prov.eligible_hosts.each...... Using the
ems.hosts.each approach results in an alternative error:
Resource <Host> <22:HOSTNAME> is not an eligible resource for this provisioning instance.
Steps Taken to resolve, to no avail:
The provider and hosts were removed and re-added
Permissions were checked, in vmware and MIQ
Steps listed here: Host Filter in provisioning dialog
After numerous attempts to resolve I ended up standing up a new instance (version gaprindashvili-3 rather than fine-3), configuring this and running a provision which identified all the expected hosts as eligible.
- What is determined as an “eligible host”?
- Why are the hosts no longer eligible? ESXi version and build, possibly?
- Is something cached, something laying around in the DB that’s causing conflict?
Thanks in Advance