Non-clustered ESX hosts, no longer appear in host creation
We are seeing a new issue with Foreman 1.17 and ESX 6.5, that previously worked on Foreman 1.16.
ESX hosts that are non clustered, no longer show up as an option in the Virtual Machine tab. It used to be that you could choose any host within an ESX DataCenter, regardless if it was part of a cluster or not.
We have numerous vcenters, many with dozens of hosts that are non-clustered.
It would be nice if the previous methodology worked, as it supported both clustered and non-clustered ESX hosts.
#4 Updated by Jeff Sparrow about 4 years ago
- Priority changed from Normal to High
Bumped this to high as its becoming a nuisance. We would really like the legacy ability from < 1.16 to be able to select individual hosts and not just clustered objects. We have 490+ racks and each one is on its own network. Which means in order to provision to them, we need to create a cluster object for every single host that is in a different rack. The old methodology was much better as it allowed you to choose a cluster AND individual, non-clustered hosts.
#6 Updated by Chris Roberts about 4 years ago
- Triaged set to Yes
- Assignee set to Chris Roberts
Can confirm it does not work past 1.15, this looks like the commit that broke it:
Will keep looking further.
#9 Updated by Nathan Ward almost 4 years ago
Hi - I note that the target release for this is 1.18.1 which is great! However the fix is in fog-vsphere 2.3.0 which is included only in Foreman 1.19.
Does this mean that the target release is incorrect and should be 1.19, or, should we get fog-vsphere 2.3.0 included for Foreman 1.18.1 as well? My preference is for the latter - but not sure the position of the project on updating libraries' minor versions for a patch release.
#10 Updated by Chris Roberts almost 4 years ago
- Target version changed from 1.18.1 to 1.19.0
I have moved it to 1.19 since the new packages are built for that and have not been pulled into 1.18. Since branching is pretty close for 1.19 I feel it is safer to just leave it on that release for now.