Bug 1699353

Summary: Cannot create featuregate.config.openshift.io
Product: OpenShift Container Platform Reporter: David Eads <deads>
Component: NodeAssignee: Ryan Phillips <rphillips>
Status: CLOSED ERRATA QA Contact: Weinan Liu <weinliu>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.1.0CC: aos-bugs, gblomqui, jokerman, mmccomas, schoudha, sjenning, vlaad
Target Milestone: ---Keywords: BetaBlocker
Target Release: 4.1.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-06-04 10:47:31 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:

Description David Eads 2019-04-12 13:53:57 UTC
We want to create stubs for all *.config.openshift.io resources so that modifications by the user can consistently be `oc edit blah.config.openshift.io`.  Every resource can and has done this except FeatureGate which appears to be stuck on a rendering/MCO-in-cluster mismatch.

Given the area, the most likely culprit is kubelet featuregates.  The fact that there is a mismatch suggests that not all kubelets are running with the same featuregates.

https://github.com/openshift/cluster-config-operator/pull/39 demonstrates the issue

Comment 3 Weinan Liu 2019-04-22 11:14:15 UTC
(In reply to David Eads from comment #0)
> We want to create stubs for all *.config.openshift.io resources so that
> modifications by the user can consistently be `oc edit
> blah.config.openshift.io`.  Every resource can and has done this except
> FeatureGate which appears to be stuck on a rendering/MCO-in-cluster mismatch.
> 
> Given the area, the most likely culprit is kubelet featuregates.  The fact
> that there is a mismatch suggests that not all kubelets are running with the
> same featuregates.
> 
> https://github.com/openshift/cluster-config-operator/pull/39 demonstrates
> the issue

Hi David,
https://github.com/openshift/cluster-config-operator/pull/39 seems to be an empty one, are you sure it's the corrent link to demonstrate the issue?

Could you help to provide more info to get the fix verified?

Thanks!

Comment 4 David Eads 2019-04-22 11:26:51 UTC
Yeah, it's empty and still won't test green.  It suggests that his this problem is not yet solved.

@rphillips, that pull needs to go green and merge.

Comment 5 Ryan Phillips 2019-04-22 17:16:28 UTC
I believe we need this PR [1] to make sure there is not a featuregate change during cluster install.

1. https://github.com/openshift/cluster-config-operator/pull/39

Comment 9 errata-xmlrpc 2019-06-04 10:47:31 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, 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/RHBA-2019:0758