-
Notifications
You must be signed in to change notification settings - Fork 295
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Iso in machine-os-images references RHCOS in 4.12 instead of FCOS #1506
Comments
The OKD installer from the `origin` namespace has to be used in the build in order to actually pull the FCOS bootimage. Fixes: okd-project/okd#1506
* machine-os-images: Use OKD installer for OKD builds The OKD installer from the `origin` namespace has to be used in the build in order to actually pull the FCOS bootimage. Fixes: okd-project/okd#1506 * machine-os-images: Add OKD/SCOS builds
With 4.12.0-0.okd-2023-03-05-022504, the image now contains FCOS, but it's version 37.20221127.3.0 instead of 37.20230205.3.0 which is actually used by the cluster. It's not that critical, because the upgrade works in this case, but it would still be nice if the correct image would be installed immediately to safe some time and download bandwidth. |
@bernhardloos technically, that is expected right now, as that's the FCOS version that the installer references for bootimages: https://github.com/openshift/installer/blob/44b1b0bf0377270adcbabb34062a76fedb9028ad/data/data/coreos/fcos.json#L37 OKD/FCOS does not currently produce its own bootimages -- vanilla FCOS is always booted first and then rebased. |
This leads to ironic trying to provision a host with RHCOS first.
This was correct in 4.11.
From 4.11.0-0.okd-2023-01-14-152430:
From 4.12.0-0.okd-2023-02-04-212953:
The text was updated successfully, but these errors were encountered: