Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-36501

prometheus bound service token causing issues with version skew between mgmt and cluster-under-test

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Major Major
    • 4.13.z
    • 4.14.z, 4.15.z
    • HyperShift
    • Important
    • No
    • Hypershift Sprint 256
    • 1
    • False
    • Hide

      None

      Show
      None
    • Release Note Not Required
    • In Progress

      This is a clone of issue OCPBUGS-36464. The following is the description of the original issue:

      This is a clone of issue OCPBUGS-34949. The following is the description of the original issue:

      hypershift e2e and conformance for 4.15 and 4.14 clusters under tests are failing due to version skew with the mgmt cluster version (4.16).

      As of 4.16.0-rc3, openshift-controller-manager switched to using bound service account tokens in https://issues.redhat.com/browse/API-1644

      Two PRs were made against openshift/origin and openshift/library-go to support this for 4.16.

      https://github.com/openshift/origin/pull/28679
      https://github.com/openshift/library-go/pull/1697

      However, for 4.15 and 4.14 tests, both repos do not have those changes. The changes might not be backward compatible (need feedback from lusanche@redhat.com on this).

      In o/o for example, it is using 4.15 o/o code to do prom operation on a 4.16 mgmt cluster.
      https://github.com/openshift/origin/blob/2320880deab4c456c7d8b157ea7dc91b85c85302/test/extended/etcd/leader_changes.go#L32

            sjenning Seth Jennings
            openshift-crt-jira-prow OpenShift Prow Bot
            Jie Zhao Jie Zhao
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: