Bug 1578911
Summary: | VMware resource pools are populated only from first cluster found | |||
---|---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Timur Daianov <tdaianov> | |
Component: | Compute Resources - VMWare | Assignee: | Ondřej Ezr <oezr> | |
Status: | CLOSED ERRATA | QA Contact: | Lukáš Hellebrandt <lhellebr> | |
Severity: | high | Docs Contact: | ||
Priority: | high | |||
Version: | 6.3.1 | CC: | chrobert, lhellebr, mawerner, mcorr, mhulan, mmccune, oezr, pcreech, sjagtap | |
Target Milestone: | 6.7.0 | Keywords: | Triaged | |
Target Release: | Unused | |||
Hardware: | x86_64 | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | foreman-1.23.0 | Doc Type: | Known Issue | |
Doc Text: |
When you provision a host using the VMware compute resource, you can only select the default resource pool. If you try to select a different resource pool, provisioning fails. As a workaround, disable the cache on the compute resource.
|
Story Points: | --- | |
Clone Of: | ||||
: | 1789393 (view as bug list) | Environment: | ||
Last Closed: | 2020-04-14 13:22:58 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | ||||
Bug Blocks: | 1789393 |
Description
Timur Daianov
2018-05-16 15:21:08 UTC
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 |