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

"oc adm upgrade status" and "oc adm upgrade" resulting same output in RHOCP 4.16

XMLWordPrintable

    • Moderate
    • None
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      When clusters are not upgrading -->
      
      In the cluster version 4.16.0 with CLI version 4.16.0 , "oc adm upgrade status" command resulted output "The cluster is not updating" , which is different than "oc adm upgrade" command . [This is an expected behaviour]
      
      However in the cluster version 4.16.1 with CLI version 4.9.23 , "oc adm upgrade status" command gave the exact same result as "oc adm upgrade" command.

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

      4.16.x

      How reproducible:

      100%

      Steps to Reproduce:

      1. Install OCP 4.16 cluster
      2. Check client and server version : $ oc version
      3. View the available updates : `$ oc adm upgrade`
      4. Export environmental variable : $ export OC_ENABLE_CMD_UPGRADE_STATUS=true
      5. Run : $ oc adm upgrade status

      Actual results:

      $ oc adm upgrade and $ oc adm upgrade status commands are showing same output while using 4.9.23 CLI version in OCP 4.16 cluster

      Expected results:

      $ oc adm upgrade and $ oc adm upgrade status should print the different output     

      Additional info:

      In the cluster version 4.16.0 with CLI version 4.16.0 , "oc adm upgrade" command output and "oc adm upgrade status" command output are different:-
      $ oc version
      Client Version: 4.16.0
      Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
      Server Version: 4.16.0
      Kubernetes Version: v1.29.5+29c95f3
      
      $ oc adm upgrade
      Cluster version is 4.16.0Upstream is unset, so the cluster will use an appropriate default.
      Channel: stable-4.16 (available channels: candidate-4.16, candidate-4.17, eus-4.16, fast-4.16, stable-4.16)Recommended updates:  VERSION     IMAGE
        4.16.1      quay.io/openshift-release-dev/ocp-release@sha256:c17d4489c1b283ee71c76dda559e66a546e16b208a57eb156ef38fb30098903a
      
      $ export OC_ENABLE_CMD_UPGRADE_STATUS=true
      $ oc adm upgrade status
      The cluster is not updating.
      
      Also in the cluster version 4.16.0 with CLI version 4.15.0 , "oc adm upgrade" command output and "oc adm upgrade status" command output are different.
      
      However,
      In the cluster version 4.16.1 with CLI version 4.9.23 , "oc adm upgrade status" command gave the same result as "oc adm upgrade" command :-
      $ oc version
      Client Version: 4.9.23
      Server Version: 4.16.1
      Kubernetes Version: v1.29.5+58452d8
      
      $ oc adm upgrade
      Cluster version is 4.16.1Upstream is unset, so the cluster will use an appropriate default.
      Channel: stable-4.16 (available channels: candidate-4.16, candidate-4.17, eus-4.16, fast-4.16, stable-4.16)
      No updates available. You may force an upgrade to a specific release image, but doing so may not be supported and may result in downtime or data loss.
      
      $ export OC_ENABLE_CMD_UPGRADE_STATUS=true
      $ oc adm upgrade status
      Cluster version is 4.16.1Upstream is unset, so the cluster will use an appropriate default.
      Channel: stable-4.16 (available channels: candidate-4.16, candidate-4.17, eus-4.16, fast-4.16, stable-4.16)
      No updates available. You may force an upgrade to a specific release image, but doing so may not be supported and may result in downtime or data loss.
      

              lmohanty@redhat.com Lalatendu Mohanty
              rhn-support-sdharma Suruchi Dharma
              Evgeni Vakhonin Evgeni Vakhonin
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: