Bug 1796189
| Summary: | Machine OS image URL should be included in the customized resource definition for consumption by the baremetal operator | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Ian Main <imain> | ||||||
| Component: | Installer | Assignee: | Stephen Benjamin <stbenjam> | ||||||
| Installer sub component: | OpenShift on Bare Metal IPI | QA Contact: | Shelly Miron <smiron> | ||||||
| Status: | CLOSED ERRATA | Docs Contact: | |||||||
| Severity: | high | ||||||||
| Priority: | unspecified | CC: | rbartal | ||||||
| Version: | 4.4 | Flags: | smiron:
needinfo+
|
||||||
| Target Milestone: | --- | ||||||||
| Target Release: | 4.4.0 | ||||||||
| Hardware: | All | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | Telco:Deployment | ||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2020-05-04 11:27:55 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: | |||||||||
| Attachments: |
|
||||||||
|
Description
Ian Main
2020-01-29 19:41:12 UTC
Sorry, hit enter in a field and it submitted the bug. Description of problem: We've created a CRD to supply the MAO and ultimately the BMO with all the information it needs to perform baremetal deployments except the machine OS image. We thought we could get this from elsewhere but it turns out we need it for our downloader container to work. This would involve updating the CRD created by the BMO and the CR created in the installer to include a new MachineOSImageURL field. https://github.com/openshift/machine-api-operator/pull/482 https://github.com/openshift/installer/pull/2987 Hi, We added the 'ProvisioningOSDownloadURL' field in the install_config.yaml file with this image: http://192.168.123.1/rhcos-44.81.202001241431.0-openstack.x86_64.qcow2.gz but after deploying, we ran the following command from the provisionhost: oc describe provisionings.metal3.io, and the image that showed up in 'ProvisioningOSDownloadURL' is this one- https://releases-art-rhcos.svc.ci.openshift.org/art/storage/releases/rhcos-4.4/44.81.202001241431.0/x86_64/rhcos-44.81.202001241431.0-openstack.x86_64.qcow2.gz?sha256=03f713b1a63f942a09e33ef1038368cff40a56f77c71818a1323fc9949dbbffc instead images attached below. Created attachment 1664330 [details]
oc describe metal3provisioning
Created attachment 1664354 [details]
install_config.yaml
ProvisioningOSDownloadURL is only a CR field, it's not something you can put in the install-config.yaml. It is the location of the RHCOS image, which the installer knows but we needed a way to get it into the cluster. So, I would consider your test showing this is validated. The URL in the CR was set. If the user wants to override the images there's other fields in the install-config for that, but it's not part of this feature. Verified. Bug was checked in OCP version 4.4 with ipv4 using 3 workers. Running the following command: oc describe provisionings.metal3.io , to check this image - https://releases-art-rhcos.svc.ci.openshift.org/art/storage/releases/rhcos-4.4/44.81.202001241431.0/x86_64/rhcos-44.81.202001241431.0-openstack.x86_64.qcow2.gz?sha256=03f713b1a63f942a09e33ef1038368cff40a56f77c71818a1323fc9949dbbffc appear in the cluster. 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/RHBA-2020:0581 |