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

Should show information on page if the upgrade to a target version doesn't take effect.

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 4.12.z
    • 4.12
    • Management Console
    • None
    • Moderate
    • None
    • Proposed
    • False
    • Hide

      None

      Show
      None

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

      Description of problem:

      On cluster setting page, it shows available upgrade on page. After user chooses one target version and clicks "Upgrade", wait for a long time, there is no info about upgrade status.

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

      4.12.0-0.nightly-2022-10-25-210451

      How reproducible:

      Always

      Steps to Reproduce:

      1.Login console with available upgrade for the cluster, select a target version in the available version list. Then click "Update". Check the upgrade progress on the cluster setting page.
      2.Check upgrade info from client with "oc adm upgrade".
      3.
      

      Actual results:

      1.There is not any information or upgrade progress shown on the page.
      2.It shows info about retrieving target version failed.
      $ oc adm upgrade 
      Cluster version is 4.12.0-0.nightly-2022-10-25-210451
        ReleaseAccepted=False  
        Reason: RetrievePayload
        Message: Retrieving payload failed version="4.12.0-0.nightly-2022-10-27-053332" image="registry.ci.openshift.org/ocp/release@sha256:fd4e9bec095b845c6f726f9ce17ee70449971b8286bb9b7478c06c5f697f05f1" failure=The update cannot be verified: unable to verify sha256:fd4e9bec095b845c6f726f9ce17ee70449971b8286bb9b7478c06c5f697f05f1 against keyrings: verifier-public-key-redhatUpstream: https://openshift-release.apps.ci.l2s4.p1.openshiftapps.com/graph
      Channel: stable-4.12
      Recommended updates:  
        VERSION                            IMAGE
        4.12.0-0.nightly-2022-11-01-135441 registry.ci.openshift.org/ocp/release@sha256:f79d25c821a73496f4664a81a123925236d0c7818fd6122feb953bc64e91f5d0
        4.12.0-0.nightly-2022-10-31-232349 registry.ci.openshift.org/ocp/release@sha256:cb2d157805abc413394fc579776d3f4406b0a2c2ed03047b6f7958e6f3d92622
        4.12.0-0.nightly-2022-10-28-001703 registry.ci.openshift.org/ocp/release@sha256:c914c11492cf78fb819f4b617544cd299c3a12f400e106355be653c0013c2530
        4.12.0-0.nightly-2022-10-27-053332 registry.ci.openshift.org/ocp/release@sha256:fd4e9bec095b845c6f726f9ce17ee70449971b8286bb9b7478c06c5f697f05f1
      

      Expected results:

      1. It should also show this kind of message on console page if retrieving target payload failed, so that user knows the actual result after try to upgrade.

      Additional info:

       

              jhadvig@redhat.com Jakub Hadvig
              openshift-crt-jira-prow OpenShift Prow Bot
              Yanping Zhang Yanping Zhang
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: