Project

General

Profile

Bug #27363

VMware resource pools are populated only from first cluster found

Added by Ondřej Ezr 5 months ago. Updated 5 months ago.

Status:
Closed
Priority:
High
Assignee:
Category:
Compute resources - VMware
Target version:
-
Difficulty:
Triaged:
Yes
Bugzilla link:
Fixed in Releases:
Found in Releases:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1578911

Description of problem:
Customer has multiple vmware clusters under vmware datacenter and each of this clusters has it's own resource pool.
When trying to provision vm under any other than first vm_cluster, resource pools can't be selected and only initial once are displayed.

Version-Release number of selected component (if applicable):
satellite 6.3.1
esx and vcenter components will be updated later

How reproducible:
configure vcenter compute resource on satellite 6.3.1 and make sure that your vmware datacenter has multiple clusters and each has own resource pools
try to provision new vm in any other than first vm_cluster.
If you select resource pool other than generic it will fail.

Steps to Reproduce:
1.see above

Actual results:
resource pool in select field is from first cluster
provision fail if they are selected, or you have to select generic one and than manually change it.

Expected results:
resource pool should be populated each time you select different vmware cluster.

Additional info:

Associated revisions

Revision 4ad299f5 (diff)
Added by Ondřej Ezr 5 months ago

Fixes #27363 - resource_pools cache key with cluster

History

#1 Updated by The Foreman Bot 5 months ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/6924 added

#2 Updated by Ondřej Ezr 5 months ago

  • Triaged changed from No to Yes

#3 Updated by The Foreman Bot 5 months ago

  • Fixed in Releases 1.23.0 added

#4 Updated by Ondřej Ezr 5 months ago

  • Status changed from Ready For Testing to Closed

Also available in: Atom PDF