Bug #23580
closed
Non-clustered ESX hosts, no longer appear in host creation
Description
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.
Updated by Jeff Sparrow almost 6 years ago
Work around:
Create a cluster under the datacenter and move the single host into it.
Updated by Ewoud Kohl van Wijngaarden almost 6 years ago
- Project changed from Packaging to Foreman
- Category set to Compute resources - VMware
I'm going to assume this isn't a packaging issue so I'm moving this to the main foreman project.
Updated by Jeff Sparrow almost 6 years ago
Ewoud Kohl van Wijngaarden wrote:
I'm going to assume this isn't a packaging issue so I'm moving this to the main foreman project.
Thanks. I totally missed the category dropdown.
Updated by Jeff Sparrow almost 6 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.
Updated by Anon niem almost 6 years ago
this solved it for me, https://github.com/fog/fog/commit/66e5521 note: file is in /opt/theforeman/
Updated by Chris Roberts almost 6 years ago
- Assignee set to Chris Roberts
- Triaged set to Yes
Can confirm it does not work past 1.15, this looks like the commit that broke it:
Will keep looking further.
Updated by Chris Roberts almost 6 years ago
- Pull request https://github.com/fog/fog-vsphere/pull/149 added
Updated by Chris Roberts almost 6 years ago
- Status changed from New to Ready For Testing
- translation missing: en.field_release set to 370
- Difficulty set to easy
Updated by Nathan Ward almost 6 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.
Updated by Chris Roberts almost 6 years ago
- Target version changed from 1.18.1 to 1.19.0
Hi Nathan,
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.
Updated by Chris Roberts almost 6 years ago
- Status changed from Ready For Testing to Resolved
- Fixed in Releases 1.19.0 added
Updated by Chris Roberts almost 6 years ago
- Pull request https://github.com/theforeman/foreman-packaging/pull/2729 added
Updated by Chris Roberts almost 6 years ago
- Pull request https://github.com/theforeman/foreman-packaging/pull/2731 added
Updated by Ewoud Kohl van Wijngaarden almost 6 years ago
- Related to Bug #23961: Networks in a distributed switch take a long time to load when there is alot added
Updated by Tomer Brisker almost 6 years ago
- Status changed from Resolved to Closed