Project

General

Profile

Bug #23580

Non-clustered ESX hosts, no longer appear in host creation

Added by Jeff Sparrow 6 months ago. Updated 4 months ago.

Status:
Closed
Priority:
High
Assignee:
Category:
Compute resources - VMware
Target version:

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.


Related issues

Related to Foreman - Bug #23961: Networks in a distributed switch take a long time to load when there is alotClosed

History

#1 Updated by Jeff Sparrow 6 months ago

Work around:

Create a cluster under the datacenter and move the single host into it.

#2 Updated by Ewoud Kohl van Wijngaarden 6 months ago

  • Category set to Compute resources - VMware
  • Project changed from Packaging to Foreman

I'm going to assume this isn't a packaging issue so I'm moving this to the main foreman project.

#3 Updated by Jeff Sparrow 6 months 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.

#4 Updated by Jeff Sparrow 6 months 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.

#5 Updated by Anon niem 5 months ago

this solved it for me, https://github.com/fog/fog/commit/66e5521 note: file is in /opt/theforeman/

#6 Updated by Chris Roberts 5 months 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:

https://github.com/fog/fog-vsphere/commit/f8b8759de44708a0e4e888da028b6cac6957fd7b#diff-a2a6d7b8a06d68744da04414afb9b591

Will keep looking further.

#7 Updated by Chris Roberts 5 months ago

  • Pull request https://github.com/fog/fog-vsphere/pull/149 added

#8 Updated by Chris Roberts 5 months ago

  • Difficulty set to easy
  • Legacy Backlogs Release (now unused) set to 370
  • Status changed from New to Ready For Testing

#9 Updated by Nathan Ward 4 months 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 4 months 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.

#11 Updated by Chris Roberts 4 months ago

  • Status changed from Ready For Testing to Resolved
  • Fixed in Releases 1.19.0 added

#12 Updated by Chris Roberts 4 months ago

  • Bugzilla link set to 1596858

#13 Updated by Chris Roberts 4 months ago

  • Pull request https://github.com/theforeman/foreman-packaging/pull/2729 added

#14 Updated by Chris Roberts 4 months ago

  • Pull request https://github.com/theforeman/foreman-packaging/pull/2731 added

#15 Updated by Ewoud Kohl van Wijngaarden 4 months ago

  • Related to Bug #23961: Networks in a distributed switch take a long time to load when there is alot added

#16 Updated by Tomer Brisker 4 months ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF