Bug 1789309
Summary: | Create host using compute_profile the 'image' field under 'OS' tab remain disabled and host create failed as well | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | vijsingh |
Component: | Compute Resources | Assignee: | Kavita <kgaikwad> |
Status: | CLOSED ERRATA | QA Contact: | vijsingh |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.7.0 | CC: | bkearney, hhudgeon, jyejare, kgaikwad, lhellebr, lvrtelov, mhulan, oprazak, zhunting |
Target Milestone: | 6.7.0 | Keywords: | AutomationBlocker, Triaged |
Target Release: | Unused | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | foreman-1.24.1.4-1 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-04-14 13:28:29 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: |
Description
vijsingh
2020-01-09 10:23:46 UTC
Workaround : Select 'Image' first under 'Operating system' and then select CP during create_host. This bug is also affecting GCE CR, and Host provisioning fails completely. Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/28725 has been resolved. @Satellite 6.7.0 snap 13.0 Verified on AzureRm CR : - Able to provision host using CP with using FT/UD. - Able to provision host using HG+CP and with HG using FT/UD Verified with RHV, Libvirt, EC2. Can't verify with Rackspace due to lack of resources. Verified with OSP. Sorry for being late here !! Verified for GCE! @Satellite 6.7 snap 14 Observation: - During host provisioning, Image selection under the OS tab is available and can switch between a list of images. - Provisioned with an image and the provisioning is successful. 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 |