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

Expired certificate remediation by HyperShift operator should be done via CPO image label check

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Undefined Undefined
    • 4.19.0
    • 4.19.0
    • HyperShift
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • Important
    • None
    • None
    • Rejected
    • None
    • In Progress
    • Release Note Not Required
    • None
    • None
    • None
    • None
    • None

      Description of problem:

         Currently we check for the version number to determine whether we should do automatic restarts for certificate expiration.
https://github.com/openshift/hypershift/blob/6991b4a6bb8ead41e1e5a0843975b7761142514f/hypershift-operator/controllers/hostedcluster/hostedcluster_controller.go#L1978
This should instead use a CPO image label check that is present whenever we move to use CPO v2

      Version-Release number of selected component (if applicable):

          4.19

      How reproducible:

          Always

      Steps to Reproduce:

          1. Create a HostedCluster test cluster with 4.19 nightly and annotations to shorten certificate expiration.
    2. Wait for clusters to expire.
    3.

      Actual results:

          No remediation occurs when certs expire

      Expected results:

          Remediation occurs and cluster continues to function properly

      Additional info:

              cewong@redhat.com Cesar Wong
              cewong@redhat.com Cesar Wong
              None
              None
              Jim Ma Jim Ma
              None
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: