See https://github.com/openshift/okd/issues/783 - newer FCOS don't start networking in some cases. Installer should use older initial FCOS
Hi Vadim, is it possible to catalog those OKD bugs to a specific subcomponent instead of openshift-installer? As you know, we installer QE is responsible for testing all the ON_QA bugs in openshift-installer subcomponent, but for those OKD bugs, I'm afraid they're out of our testing scope. And since we're close to the 4.9 Code Freeze, as QE we have to make sure there's no ON_QA bugs left for 4.9.0 targeted bugs. The proposed fix is for reverting the boot image of OKD to previous version, so I think it's ok to move it to verified directly. Please let me know if you any concerns, thanks.
(In reply to Gaoyun Pei from comment #3) > Hi Vadim, is it possible to catalog those OKD bugs to a specific > subcomponent instead of openshift-installer? I don't think we have a subcomponent for OKD specifically. Do we need one? Most OKD bugs are OCP bugs > As you know, we installer QE is responsible for testing all the ON_QA bugs > in openshift-installer subcomponent, but for those OKD bugs, I'm afraid > they're out of our testing scope. > > And since we're close to the 4.9 Code Freeze, as QE we have to make sure > there's no ON_QA bugs left for 4.9.0 targeted bugs. The proposed fix is for > reverting the boot image of OKD to previous version, so I think it's ok to > move it to verified directly. Feel free to reassign qe contact to me or just close as VERIFIED. We need bugzilla to bypass the openshift-bot mostly
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 (Moderate: OpenShift Container Platform 4.9.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-2021:3759