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:
ESXs and vcenter are version 6.0.0
The workaround is to disable caching on the compute resource, clearing the cache does not do anything. Working on getting this in for 6.5 and 6.4.z
Created redmine issue https://projects.theforeman.org/issues/27363 from this bug
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/27363 has been resolved.
Verified with Sat 6.7 snap 8. Tried through WebUI, using steps from OP, both image-based and pxe-based provisioning. Tried with hammer. There are some issues that I will open a separate BZ against but these are not regression, compared to 6.6.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2020:1454