Can you include the ClusterVersion YAML?

$ oc get -o yaml clusterversion

[yapei@dhcp-141-192 test-files]$ oc get clusterversion
NAME      VERSION                             AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.2.0-0.nightly-2019-08-08-103722   True        False         26h     Error while reconciling 4.2.0-0.nightly-2019-08-08-103722: the cluster operator insights is degraded
[yapei@dhcp-141-192 test-files]$ oc get clusterversion -o yaml
apiVersion: v1
items:
- apiVersion: config.openshift.io/v1
  kind: ClusterVersion
  metadata:
    creationTimestamp: "2019-08-12T00:52:39Z"
    generation: 1
    name: version
    resourceVersion: "1456431"
    selfLink: /apis/config.openshift.io/v1/clusterversions/version
    uid: 7ba306bb-bc9b-11e9-919a-0235da9abde4
  spec:
    channel: stable-4.2
    clusterID: ec341853-9a12-4023-97d3-21d03748f5c3
    upstream: https://api.openshift.com/api/upgrades_info/v1/graph
  status:
    availableUpdates: null
    conditions:
    - lastTransitionTime: "2019-08-12T01:05:59Z"
      message: Done applying 4.2.0-0.nightly-2019-08-08-103722
      status: "True"
      type: Available
    - lastTransitionTime: "2019-08-13T03:08:52Z"
      message: 'Cluster operator insights is reporting a failure: 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: ClusterOperatorDegraded
      status: "True"
      type: Failing
    - lastTransitionTime: "2019-08-12T01:05:59Z"
      message: 'Error while reconciling 4.2.0-0.nightly-2019-08-08-103722: the cluster
        operator insights is degraded'
      reason: ClusterOperatorDegraded
      status: "False"
      type: Progressing
    - lastTransitionTime: "2019-08-12T00:52:54Z"
      message: 'Unable to retrieve available updates: currently installed version
        4.2.0-0.nightly-2019-08-08-103722 not found in the "stable-4.2" channel'
      reason: RemoteFailed
      status: "False"
      type: RetrievedUpdates
    desired:
      force: false
      image: registry.svc.ci.openshift.org/ocp/release@sha256:82ff0fc8864805b331539540f3d8644f01bd5bf0d1e6ac08a93b57783faeb2b8
      version: 4.2.0-0.nightly-2019-08-08-103722
    history:
    - completionTime: "2019-08-12T01:05:59Z"
      image: registry.svc.ci.openshift.org/ocp/release@sha256:82ff0fc8864805b331539540f3d8644f01bd5bf0d1e6ac08a93b57783faeb2b8
      startedTime: "2019-08-12T00:52:54Z"
      state: Completed
      verified: false
      version: 4.2.0-0.nightly-2019-08-08-103722
    observedGeneration: 1
    versionHash: D2UkUpUJri8=
kind: List
metadata:
  resourceVersion: ""
  selfLink: ""

Also happens when upgrade is in progress

apiVersion: config.openshift.io/v1
kind: ClusterVersion
metadata:
  creationTimestamp: '2019-08-12T07:25:39Z'
  generation: 8
  name: version
  resourceVersion: '494376'
  selfLink: /apis/config.openshift.io/v1/clusterversions/version
  uid: 6254a711-bcd2-11e9-b8a7-ac1f6b92d31c
spec:
  channel: prerelease-4.1
  clusterID: 8064266b-5284-4925-b8cd-193a06f358bb
  desiredUpdate:
    force: true
    image: >-
      registry.svc.ci.openshift.org/ocp/release:4.2.0-0.nightly-2019-08-08-103722
    version: 4.2.0-0.nightly-2019-08-08-103722
  overrides:
    - group: config.openshift.io/v1
      kind: ClusterOperator
      name: insights
      namespace: ''
      unmanaged: true
  upstream: 'https://openshift-release.svc.ci.openshift.org/graph'
status:
  availableUpdates: null
  conditions:
    - lastTransitionTime: '2019-08-12T07:39:29Z'
      message: Done applying 4.1.11
      status: 'True'
      type: Available
    - lastTransitionTime: '2019-08-13T08:30:53Z'
      status: 'False'
      type: Failing
    - lastTransitionTime: '2019-08-13T07:54:47Z'
      message: 'Working towards 4.2.0-0.nightly-2019-08-08-103722: 89% complete'
      status: 'True'
      type: Progressing
    - lastTransitionTime: '2019-08-12T16:08:20Z'
      status: 'True'
      type: RetrievedUpdates
  desired:
    force: true
    image: >-
      registry.svc.ci.openshift.org/ocp/release:4.2.0-0.nightly-2019-08-08-103722
    version: 4.2.0-0.nightly-2019-08-08-103722
  history:
    - completionTime: null
      image: >-
        registry.svc.ci.openshift.org/ocp/release:4.2.0-0.nightly-2019-08-08-103722
      startedTime: '2019-08-13T07:54:47Z'
      state: Partial
      verified: false
      version: 4.2.0-0.nightly-2019-08-08-103722
    - completionTime: '2019-08-13T07:54:47Z'
      image: >-
        registry.svc.ci.openshift.org/ocp/release@sha256:bfca31dbb518b35f312cc67516fa18aa40df9925dc84fdbcd15f8bbca425d7ff
      startedTime: '2019-08-13T03:04:02Z'
      state: Completed
      verified: false
      version: 4.1.11
    - completionTime: '2019-08-13T03:04:02Z'
      image: >-
        quay.io/openshift-release-dev/ocp-release@sha256:b2f03ea1b04edd25bf677aa755450eb0bb55898695b3ec1aa805ae2a97df3b90
      startedTime: '2019-08-12T07:26:00Z'
      state: Completed
      verified: false
      version: 4.1.10
  observedGeneration: 8
  versionHash: vFE4haueOuE=

I happened to notice this in my cluster, so I debugged it while I could reproduce. It turns out to be a simple fix.

This was a little tricky to reproduce since it requires a specific cluster state.

The issue was not reproduced during the upgrade process from 4.2.0-0.nightly-2019-08-20-162755 -> 4.2.0-0.nightly-2019-08-20-213632 -> 4.2.0-0.nightly-2019-08-20-235901

Moving 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