Uploaded image for project: 'Hybrid Application Console'
  1. Hybrid Application Console
  2. HAC-4122

[Hypershift ROSA] an irrelevant error related to upgrade shown for a hypershift cluster under installation

XMLWordPrintable

    • False
    • False
    • None

      Description of problem:

      Inline error related to upgrade was shown on the HCP cluster's settings tab during the installation.

      Danger alert:Can't schedule upgrade
      CLUSTERS-MGMT-400: Upgrade policies are not supported for this cluster
      Operation ID: 91c50c8b-26b3-4887-beaa-8d0dd14bf5f8 


      The error seems not really relevant in this case, as user never tried to upgrade the cluster or upgrade related action and it is showing by default in settings tab as soon as the cluster installation started from Cluster wizard.

      How reproducible:

       Always

      Steps to reproduce:

      1. Launch OCM Staging.
      2. Open ROSA wizard and select control plane type as "Hosted"
      3. Proceed to next steps by providing all required values in each step.
      4. Reach to "Review and create " step and click "Create cluster" button.
      5. While installation is in progress, Click "settings" tab of the cluster.
      6. See the behavior.

      Actual results:

      Inline error wrongly indicated in settings tab of HCP cluster during the installation.

      Danger alert:Can't schedule upgrade
      CLUSTERS-MGMT-400: Upgrade policies are not supported for this cluster
      Operation ID: 91c50c8b-26b3-4887-beaa-8d0dd14bf5f8 

      Expected results:
      Do not show the error related to upgrade during the cluster installation as the cluster is not ready. 
      If we want to show them as a precaution then it would be good if the message is warning or information alert instead of a error case. 

            zherman Zac Herman
            jmekkatt@redhat.com Jayakrishnan Mekkattillam
            Jayakrishnan Mekkattillam Jayakrishnan Mekkattillam
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: