Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2079500

Summary: okd-baremetal-install uses fcos for bootstrap but rhcos for cluster
Product: OpenShift Container Platform Reporter: Erik Berg <redhat-bugzilla>
Component: InstallerAssignee: Vadim Rutkovsky <vrutkovs>
Installer sub component: OpenShift on Bare Metal IPI QA Contact: Eldar Weiss <eweiss>
Status: CLOSED ERRATA Docs Contact:
Severity: medium    
Priority: medium CC: eweiss, rpittau, vrutkovs
Version: 4.10Keywords: Triaged
Target Milestone: ---   
Target Release: 4.11.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-08-10 11:08:39 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 Flags
.openshift_install.log none

Description Erik Berg 2022-04-27 16:03:17 UTC
Created attachment 1875404 [details]
.openshift_install.log

Thanks for opening a bug report!
Before hitting the button, please fill in as much of the template below as you can.
If you leave out information, it's harder to help you.
Be ready for follow-up questions, and please respond in a timely manner.
If we can't reproduce a bug we might close your issue.
If we're wrong, PLEASE feel free to reopen it and explain why.

Version:

$ openshift-baremetal-install version
openshift-baremetal-install 4.10.0-0.okd-2022-03-07-131213
built from commit 3b701903d96b6375f6c3852a02b4b70fea01d694
release image quay.io/openshift/okd@sha256:2eee0db9818e22deb4fa99737eb87d6e9afcf68b4e455f42bdc3424c0b0d0896
release architecture amd64


Platform:
baremetal

Please specify:
IPI

What happened?

The bootstrap node is running fcos, but the pxe-booted machines are running rhcos.

You can see https://github.com/openshift/okd/discussions/1200 for additional logs and information.

What did you expect to happen?
I expected the pxe-booted machines to run fcos.

How to reproduce it (as minimally and precisely as possible)?

on the provisioner;
$ oc adm release extract --command=openshift-baremetal-install --to ~/.local/bin quay.io/openshift/okd:4.10.0-0.okd-2022-03-07-131213
$ cp working-baremetal-install-config.yaml clusterconfigs/install-config.yaml
$ openshift-baremetal-install --dir clusterconfigs create manifests
$ openshift-baremetal-install --dir clusterconfigs create cluster

Anything else we need to know?

https://github.com/openshift/okd/discussions/1200#discussioncomment-2647764

Comment 1 Vadim Rutkovsky 2022-05-12 17:09:52 UTC
Possibly a dupe of https://bugzilla.redhat.com/show_bug.cgi?id=2082312 - could you check OKD 4.10 nightlies?

Comment 5 Eldar Weiss 2022-06-13 09:16:59 UTC
Issue seems to be resolved.
I've added the log:
(.venv) [kni@provisionhost-0-0 ocp-edge-auto]$ oc get clusterversion
NAME      VERSION                              AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.11.0-0.nightly-2022-06-06-201913   True        False         39m     Cluster version is 4.11.0-0.nightly-2022-06-06-201913

(.venv) [kni@provisionhost-0-0 ocp-edge-auto]$ oc adm release extract --command=openshift-baremetal-install --to ~/.local/bin quay.io/openshift/okd:4.10.0-0.okd-2022-03-07-131213
(.venv) [kni@provisionhost-0-0 ocp-edge-auto]$ cat /home/kni/ocp-edge-auto/install-config.yaml | grep rhcos
    bootstrapOSImage: http://registry.ocp-edge-cluster-0.qe.lab.redhat.com:8080/images/rhcos-411.85.202205101201-0-qemu.x86_64.qcow2.gz?sha256=75ca83efc8c40669631d7367664fd48372c067da5fa448551bc2ab28026b94c4
    clusterOSImage: http://registry.ocp-edge-cluster-0.qe.lab.redhat.com:8080/images/rhcos-411.85.202205101201-0-openstack.x86_64.qcow2.gz?sha256=46278e035367c88349d50cbefb01a9ca73db26808b6dcee8ce58ebf4b52deaf4

Comment 7 errata-xmlrpc 2022-08-10 11:08:39 UTC
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 (Important: OpenShift Container Platform 4.11.0 bug fix and security update), 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-2022:5069