Replies: 4 comments
-
Hi. This isn't an issue/bug per se. The OKD Working Group only provides resources for N and N-1 releases at this time. As of last week, that means 4.17 and 4.16 (which are SCOS-based releases). The FCOS Working Group, who was creating and storing the FCOS artifacts, has likely pruned artifacts from 2023. As to whether a newer version of FCOS would work with a 4.14 installer, we have no resources to say one way or the other. |
Beta Was this translation helpful? Give feedback.
-
./openshift-install coreos print-stream-json will tell you the initial image that the installer is using. In the case of 4.14.0-0.okd-2023-11-12-042703 it uses FCOS 38.20230609.3.0. It also gives the URL to download from.
In this case for vmware. The install will upgrade the OS to the appropriate level during the install process |
Beta Was this translation helpful? Give feedback.
-
@fortinj66 The FCOS Working Group asked us if it was okay to prune older artifacts, which we agreed with. While it may be downloadable, we can't guarantee it will be as the pruning process proceeds. So, we'll want to avoid just telling folks without verifying. |
Beta Was this translation helpful? Give feedback.
-
Jaime, I validated the image existed prior to posting. The process is the same regardless of release. Also, by that logic we should prune the releases on github too. |
Beta Was this translation helpful? Give feedback.
-
Hello,
I'm trying to set up OKD 4.14.0-0.okd-2023-11-12-042703 in an air-gapped environment. According to the release notes, this version requires Fedora CoreOS (FCOS) version 38.20231027.3.
I've tried looking for this specific FCOS version through:
However, I cannot locate this specific version. Could you please:
Thank you for your help.
Beta Was this translation helpful? Give feedback.
All reactions