Description of problem: After launching cluster with payload 4.2.0-0.nightly-2019-08-06-072822, I find that the support operator is in the state DEGRADED. Version-Release number of the following components: openshift-install v4.2.0-201908060219-dirty How reproducible: always Steps to Reproduce: 1. deploy cluster with payload 4.2.0-0.nightly-2019-08-06-072822 2. 3. Actual results: # oc get clusteroperator NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE support 4.2.0-0.nightly-2019-08-06-072822 True False True 27m # oc get co support -oyaml apiVersion: config.openshift.io/v1 kind: ClusterOperator metadata: creationTimestamp: "2019-08-07T07:58:03Z" generation: 1 name: support resourceVersion: "15227" selfLink: /apis/config.openshift.io/v1/clusteroperators/support uid: 14f578b0-b8e9-11e9-afd9-02a2a6b7f4f6 spec: {} status: conditions: - lastTransitionTime: "2019-08-07T08:08:17Z" message: 'Unable to report: Post https://cloud.redhat.com/api/ingress/v1/upload: net/http: invalid header field value "Bearer b3BlbnNoaWZ0LXJlbGVhc2UtZGV2K2ppYWxpdXJlZGhhdGNvbTFjcWdkZm9q\nMmdxenRxdHg1c21lOHI0b3Z2ajpHSzFRQkdORUtJS0JMSzIzRzNWNEpTNVhH\nSlZaU0hJMExQV0I1RkZEVENXNjREUlJKV0RVWUc5VVZaOTVTSlAx\n" for key Authorization' reason: UploadFailed status: "True" type: Degraded - lastTransitionTime: "2019-08-07T07:58:02Z" status: "True" type: Available - lastTransitionTime: "2019-08-07T08:00:03Z" message: An error has occurred status: "False" type: Progressing - lastTransitionTime: "2019-08-07T08:00:03Z" status: "False" type: Disabled extension: lastReportTime: null versions: - name: operator version: 4.2.0-0.nightly-2019-08-06-072822 Expected results: support operator works Additional info: Please attach logs from ansible-playbook with the -vvv flag
Wow, that's awesome. I think your pull secret is broken, but this is a bad message to report.
Workaround to not block upgrade progress: > oc edit clusterversion version ... spec: ... overrides: - group: config.openshift.io/v1 kind: ClusterOperator name: insights namespace: "" unmanaged: true
It is fixed, I verified it with version: 4.2.0-0.nightly-2019-08-13-183722
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