Uploaded image for project: 'OCMUI - OpenShift Cluster Manager UI'
  1. OCMUI - OpenShift Cluster Manager UI
  2. OCMUI-2840

[Cluster details] Two expiration alerts are displayed on the trial cluster page, potentially confusing the user.

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • None
    • False
    • Hide

      None

      Show
      None
    • False

      Steps to Reproduce:

      1. Create an OSD trial cluster and wait for it to be in ready status.
      2. On the cluster details page, notice the alerts.

      Expected Result:

      1. There is a first alert shown to the user which states that 

        "This cluster will be deleted in a day" or 

        "This cluster will be deleted in 13 hours".

       

      1. A second alert, "This cluster will be deleted in 6 months," and below this alert, there is a button titled "Upgrade from trial" is shown to the user. Clicking on that button should show the alert "This cluster will be deleted in 7 days" immediately.

      Actual Result:

      1. Since we are upgrading using the marketplace quota, we want to show the expiration alert immediately to let the user know about the latest expiration time. However, there is some delay in viewing the alert.
      2. Showing two expiration alerts on the details page is misleading the user. Ideally, we would want to show only one expiration time.

       

        1. alerts_expiration_times.mp4
          11.23 MB
          LAKSHMI SHIVANTHI AMARACHINTHA
        2. image-2025-01-03-14-43-49-381.png
          40 kB
          LAKSHMI SHIVANTHI AMARACHINTHA

            [OCMUI-2840] [Cluster details] Two expiration alerts are displayed on the trial cluster page, potentially confusing the user.

            Cool thanks. Lakshmi

            Kim Doberstein added a comment - Cool thanks. Lakshmi

            kdoberst the logic exists in production, but when I verified this scenario in both environments, I did not see two expiration alerts when we upgraded the cluster from trial to a marketplace quota one in the PROD env. So, I thought this might be a regression effect. If you think the changes are unrelated, please feel free to unlink the bug.

            LAKSHMI SHIVANTHI AMARACHINTHA added a comment - kdoberst the logic exists in production, but when I verified this scenario in both environments, I did not see two expiration alerts when we upgraded the cluster from trial to a marketplace quota one in the PROD env. So, I thought this might be a regression effect. If you think the changes are unrelated, please feel free to unlink the bug.

            That makes sense. I think this one should be fixed soon - but since the logic existed in production, I think we can remove it as a blocker from the multiRegion work.  lamarach@redhat.com  thoughts?

            Kim Doberstein added a comment - That makes sense. I think this one should be fixed soon - but since the logic existed in production, I think we can remove it as a blocker from the multiRegion work.   lamarach@redhat.com   thoughts?

            The marketplace cluster will be deleted in 7 days and the trial cluster in 180 days. So, if the user upgrades from a trial one to a marketplace cluster using the marketplace quota, the expiration time will be 7 days. I am providing this information based on the existing testcases  OCP-44780 OCP-41332 

            LAKSHMI SHIVANTHI AMARACHINTHA added a comment - The marketplace cluster will be deleted in 7 days and the trial cluster in 180 days. So, if the user upgrades from a trial one to a marketplace cluster using the marketplace quota, the expiration time will be 7 days. I am providing this information based on the existing testcases   OCP-44780 OCP-41332 

            I'm wondering if the "The cluster will be deleted in 1 day" alert is due to our own internal set-up for dev.  So I'm wondering if both are kind of true.  It will be deleted in a day due to our own internal policy and in 7 days if it still exists due to the subscription end date.   

            I'm comparing code from production and dev and the logic for when the alerts are shown appear to be the same - so I suspect this isn't an issue due to the multiRegion work.  (See: 
            ExpirationAlert in src/components/clusters/ClusterDetailsMultiRegion/components/ClusterDetailsTop/ClusterDetailsTop.jsx)

            So do we know what the rules are if both banners are supposed to be shown which one should be shown and which one should be hidden?  

            Kim Doberstein added a comment - I'm wondering if the "The cluster will be deleted in 1 day" alert is due to our own internal set-up for dev.  So I'm wondering if both are kind of true.  It will be deleted in a day due to our own internal policy and in 7 days if it still exists due to the subscription end date.    I'm comparing code from production and dev and the logic for when the alerts are shown appear to be the same - so I suspect this isn't an issue due to the multiRegion work.  (See:  ExpirationAlert in src/components/clusters/ClusterDetailsMultiRegion/components/ClusterDetailsTop/ClusterDetailsTop.jsx) So do we know what the rules are if both banners are supposed to be shown which one should be shown and which one should be hidden?  

              Unassigned Unassigned
              lamarach@redhat.com LAKSHMI SHIVANTHI AMARACHINTHA
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: