Uploaded image for project: 'Red Hat Advanced Cluster Security'
  1. Red Hat Advanced Cluster Security
  2. ROX-29163

Users unable to proceed in the schedules wizard when CO is unhealthy in their clusters

    • Icon: Story Story
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • Compliance Workflows
    • Rox Sprint 4.8H - Global

      Description:

      During the Red Hat Advanced Cluster Security schedule process, users encounter a roadblock between the 3rd and 4th stages. The cause is that Compliance Operator not installed in the clusters OR the compliance operator version installed in the cluster is older than v1.6.
      When this occurs, the installation wizard appears to halt, preventing users from proceeding further in the schedules wizard. 
      We think this is one of the reasons around 50% of the customers drop between 3th and 4th stages (based on telemetry data).

      Steps to Reproduce:

      1. Create a new schedule
      2. Proceed through the initial stages of the wizard. (Step 1- Set parameters)
      3. Reach the point where the wizard attempts to configur the target cluster's compliance settings (Step 2 - Select Clusters). Operator status shows 'Unhealthy', however it allows you to select that cluster and move to 'Next'.
      4. Once you reach to Step 3 - Select profiles, the wizard shows the following error not allowing the customers to continue.

       

      Expected Behaviour:

      The installation wizard must warn users from proceeding if they've chosen an unhealthy cluster or the operator version of any chosen cluster is not fit to run (CO under 1.6 version).
       

        1. image (16).png
          image (16).png
          471 kB
        2. image (17).png
          image (17).png
          553 kB
        3. Screenshot 2025-05-29 at 8.21.30 AM.png
          Screenshot 2025-05-29 at 8.21.30 AM.png
          403 kB

              linsong@redhat.com Linda Song
              rh-ee-masimonm Maria Simon Marcos
              ACS Sensor & Ecosystem
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: