Bug #23580: Non-clustered ESX hosts, no longer appear in host creation - Foreman

Custom queries

3.12.2 release DONE
3.12.2 release TODO
3.13.1 release DONE
3.13.1 release TODO
3.14.0 release DONE
3.14.0 release TODO
All bugs by votes
All issues closed in the last 3 weeks
Easy and Trivial Issues
Easy Issues (only)
Foreman - new open issues in last 10 days
Good first issues - Foreman core
high prio open bugs
Host registration [open]
Mine
My issues closed in the last 3 weeks
old bugs
Open with target version set (aka blockers)
registration
taken-none
Team Atlas untriaged bugs
templates
Trivial Issues
Untriaged and opened in the past two weeks

Actions

Copy link

Bug #23580

closed

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

Added by Jeff Sparrow almost 7 years ago. Updated over 6 years ago.

Status:

Closed

Priority:

High

Assignee:

Chris Roberts

Category:

Compute resources - VMware

Target version:

1.19.0

Difficulty:

easy

Triaged:

Yes

Bugzilla link:

1596858

Pull request:

https://github.com/fog/fog-vsphere/pull/149, https://github.com/theforeman/foreman-packaging/pull/2729, https://github.com/theforeman/foreman-packaging/pull/2731

Fixed in Releases:

1.19.0

Found in Releases:

1.17.0

Red Hat JIRA:

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 1 (0 open — 1 closed)

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

Closed

Timo Goebel

Actions

Issue # Delay: days Cancel

History
Notes
Property changes

Actions

Copy link

Updated by Jeff Sparrow almost 7 years ago

Work around:

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

Actions

Copy link

Updated by Ewoud Kohl van Wijngaarden almost 7 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.

Actions

Copy link

Updated by Jeff Sparrow almost 7 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.

Actions

Copy link

Updated by Jeff Sparrow almost 7 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.

Actions

Copy link

Updated by Anon niem almost 7 years ago

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

Actions

Copy link

Updated by Chris Roberts almost 7 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:

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

Will keep looking further.

Actions

Copy link

Updated by Chris Roberts almost 7 years ago

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

Actions

Copy link

Updated by Chris Roberts almost 7 years ago

Status changed from New to Ready For Testing
Translation missing: en.field_release set to 370
Difficulty set to easy

Actions

Copy link

Updated by Nathan Ward over 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.

Actions

Copy link

#10

Updated by Chris Roberts over 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.

Actions

Copy link

#11