Description of problem: During must-gather run, it fails to collect authentication operator information because it refers to the 'authentication-operator' namespace instead of 'openshift-authentication-operator' Version-Release number of selected component (if applicable): 4.1.0 / 4.1.1 How reproducible: 100% Additional info: [ec2-user ca-central-1 ~]$ oc get clusteroperator authentication -o=yaml apiVersion: config.openshift.io/v1 kind: ClusterOperator metadata: creationTimestamp: "2019-06-04T21:18:12Z" generation: 1 name: authentication resourceVersion: "2896029" selfLink: /apis/config.openshift.io/v1/clusteroperators/authentication uid: 427e4171-870e-11e9-9662-0214201dd1d8 spec: {} status: conditions: - lastTransitionTime: "2019-06-11T17:48:01Z" reason: AsExpected status: "False" type: Degraded - lastTransitionTime: "2019-06-11T17:48:01Z" reason: AsExpected status: "False" type: Progressing - lastTransitionTime: "2019-06-04T21:23:15Z" reason: AsExpected status: "True" type: Available - lastTransitionTime: "2019-06-04T21:18:12Z" reason: NoData status: Unknown type: Upgradeable extension: null relatedObjects: - group: operator.openshift.io name: cluster resource: authentications - group: config.openshift.io name: cluster resource: authentications - group: config.openshift.io name: cluster resource: infrastructures - group: config.openshift.io name: cluster resource: oauths - group: "" name: openshift-config resource: namespaces - group: "" name: openshift-config-managed resource: namespaces - group: "" name: openshift-authentication resource: namespaces - group: "" name: authentication-operator resource: namespaces versions: - name: operator version: 4.1.1 - name: oauth-openshift version: 4.1.1_openshift
Upstream PR: https://github.com/openshift/cluster-authentication-operator/pull/135
PR merged
Based on #comment 2, set target release to 4.1.z QE have verified that the issue has been fixed in 4.2, we still need to back-port the fix to 4.1, so moving bug back to assigned. Below result show that the issue has been fixed in 4.2 $ oc get co authentication -o yaml apiVersion: config.openshift.io/v1 kind: ClusterOperator metadata: creationTimestamp: "2019-07-03T03:55:12Z" generation: 1 name: authentication resourceVersion: "16570" selfLink: /apis/config.openshift.io/v1/clusteroperators/authentication uid: 5bfd928e-9d46-11e9-91f9-02a2294f236c spec: {} status: conditions: - lastTransitionTime: "2019-07-03T03:58:58Z" reason: AsExpected status: "False" type: Degraded - lastTransitionTime: "2019-07-03T04:09:43Z" reason: AsExpected status: "False" type: Progressing - lastTransitionTime: "2019-07-03T04:04:39Z" reason: AsExpected status: "True" type: Available - lastTransitionTime: "2019-07-03T03:55:12Z" reason: NoData status: Unknown type: Upgradeable extension: null relatedObjects: - group: operator.openshift.io name: cluster resource: authentications - group: config.openshift.io name: cluster resource: authentications - group: config.openshift.io name: cluster resource: infrastructures - group: config.openshift.io name: cluster resource: oauths - group: "" name: openshift-config resource: namespaces - group: "" name: openshift-config-managed resource: namespaces - group: "" name: openshift-authentication resource: namespaces - group: "" name: openshift-authentication-operator resource: namespaces versions: - name: operator version: 4.2.0-0.nightly-2019-06-30-221852 - name: oauth-openshift version: 4.2.0-0.nightly-2019-06-30-221852_openshift
Please don't set the target milestone to a lower version if you want a backport, create a separate BZ for the backport next time. I'll do that for you now, but just this once.
Please move the BZ to VERIFIED if the solution is satisfactory.
4.1.z is tracked in https://bugzilla.redhat.com/show_bug.cgi?id=1729100. This one is used to track 4.2. According to #comment 5, the issue in 4.2 is fixed. Move bug to verified.
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:2922