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

Misleading msg in 'oc adm upgrade' output while updating

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Obsolete
    • Icon: Normal Normal
    • None
    • 4.14
    • None
    • No
    • False
    • Hide

      None

      Show
      None

      Description of problem:

        During the upgrade process 4.14.0 -> 4.14.14, a misleading msg of "No updates available" is shown  .   

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

          ocp 4.14.0

      How reproducible:

          100%

      Steps to Reproduce:

      1. trigger an upgrade: 
      [kni@ocp-edge119 ~]$ oc adm upgrade --to=4.14.14 --force
      warning: --force overrides cluster verification of your supplied release image and waives any update precondition failures.
      Requested update to 4.14.14
      2. check upgrade status:
      [kni@ocp-edge119 ~]$ oc adm upgrade
          

      Actual results:

      info: An upgrade is in progress. Working towards 4.14.14: 116 of 860 done (13% complete), waiting on etcd, kube-apiserverUpstream is unset, so the cluster will use an appropriate default. Channel: stable-4.14 (available channels: candidate-4.14, candidate-4.15, eus-4.14, fast-4.14, fast-4.15, stable-4.14) No updates available. You may still upgrade to a specific release image with --to-image or wait for new updates to be available. [kni@ocp-edge119 ~]$      

      Expected results:

      Seems like the "No updates available" refers to the new version "4.14.14", before the upgrade to 4.14.14 was done.
      
      I would expect that while upgrading, no such msg will appear because it is confusing. 
      at least the old "Recommended updates" (of 4.14.0) will remain till the upgrade is finished successfully, or not shown at all while upgrading.     

      Additional info:

          

            trking W. Trevor King
            rhn-support-gamado Gal Amado
            Jia Liu Jia Liu
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: