Uploaded image for project: 'OpenShift Request For Enhancement'
  1. OpenShift Request For Enhancement
  2. RFE-4839

API to monitor cluster upgrade status

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Done
    • Undefined
    • None
    • None
    • API
    • False
    • None
    • False
    • Not Selected
    • 0
    • 0% 0%

    Description

      1. Proposed title of this feature request

      API to monitor cluster upgrade status

      2. What is the nature and description of the request?

      We are looking for all useful information that oc get clusterversion -o yaml provided related to cluster upgrade. Below are some examples. But development team would know much better what all they can expose that is useful to track cluster upgrade status.

      • lastTransitionTime: "2023-10-25T15:01:30Z"
              message: 'Working towards 4.12.30: 245 of 831 done (29% complete), waiting on
                control-plane-machine-set'
              reason: ClusterOperatorUpdating
              status: "True"
              type: Progressing
        history:
            - startedTime: "2023-10-25T15:01:30Z"
              state: Completed
              verified: true
              version: 4.12.30
      • lastTransitionTime: "2023-10-25T06:55:42Z"
              message: 'Retrieving payload failed version="4.12.30" image="ocp.251.mirror.mavdallas.com:8443/openshift/release-images@sha256:86ee723d4dc2a83f836232d1d03f8b4193940c50a2636ee86924acb5d14b0b64"
                failure=The update cannot be verified: unable to verify sha256:86ee723d4dc2a83f836232d1d03f8b4193940c50a2636ee86924acb5d14b0b64
                against keyrings: verifier-public-key-redhat'
              reason: RetrievePayload
              status: "False"
              type: ReleaseAccepted

       

      PS: customer either look for list of possible return values or RFE to provide API that would return for 'upgrade status' something like '245 of 831 done (29% complete)'

      3. Why does the customer need this? (List the business requirements here)

       

      to better monitor cluster upgrade process (as it can get stuck without warning)

      4. List any affected packages or components.

      Attachments

        Issue Links

          Activity

            People

              rh-ee-smodeel Subin MM
              rhn-support-pducai Peter Ducai
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: