Bug 1999421 - OKD: revert initial FCOS to 20210626.3.1
Summary: OKD: revert initial FCOS to 20210626.3.1
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 4.9
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: 4.9.0
Assignee: Vadim Rutkovsky
QA Contact: Gaoyun Pei
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-08-31 07:47 UTC by Vadim Rutkovsky
Modified: 2021-10-18 17:50 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-10-18 17:49:59 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift installer pull 5174 0 None None None 2021-08-31 07:47:28 UTC
Red Hat Product Errata RHSA-2021:3759 0 None None None 2021-10-18 17:50:11 UTC

Description Vadim Rutkovsky 2021-08-31 07:47:08 UTC
See https://github.com/openshift/okd/issues/783 - newer FCOS don't start networking in some cases. Installer should use older initial FCOS

Comment 3 Gaoyun Pei 2021-09-04 03:06:19 UTC
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.

Comment 4 Vadim Rutkovsky 2021-09-06 09:09:47 UTC
(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

Comment 7 errata-xmlrpc 2021-10-18 17:49:59 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 (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


Note You need to log in before you can comment on or make changes to this bug.