Uploaded image for project: 'Red Hat Advanced Cluster Management'
  1. Red Hat Advanced Cluster Management
  2. ACM-8413

Few components not uninstalled when addon is uninstalled

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Normal Normal
    • None
    • None
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • Submariner Sprint 2023-13, Submariner Sprint 2023-14, Submariner Sprint 2023-15, Submariner Sprint 2024-16, Submariner Sprint 2024-17, Submariner Sprint 2024-18, Submariner Sprint 2024-19, Submariner Sprint 2024-20, Submariner Sprint 2024-21, Submariner Sprint 2024-22, Submariner Sprint 2024-23, Submariner Sprint 2024-24, Submariner Sprint 2024-25, Submariner Sprint 2024-26, Submariner Sprint 2024-27, Submariner Sprint 2024-28, Submariner Sprint 2024-29, Submariner Sprint 2024-30, Submariner Sprint 2024-33, Submariner Sprint 2024-32, Submariner Sprint 2025-34, Submariner Sprint 2025-35
    • Moderate
    • No

      Description of problem:

      When Submariner addon is unistalled, few Submariner components like Broker, roles, role bindings, cluster roles, cluster role bindings are not deleted.

      Various uninstalling scenarios are summarised below:

      Scenario (Hub is also spoke)   Present? Present?
          Hub Spoke
        Broker yes no
        Submariner yes yes
             
      When Submariner addon is uninstalled from a ManagedCluster ensure that Submariner is successfully uninstalled.      
      submariner-addon uninstalled from spoke1 Broker no need to check no
      Submariner no    
      cluster roles and bindings yes    
      SA no    
      role and role bindings no    
             
      When SUbmariner addon is uninstalled from Hub      
      Uninstall addon from Hub after uninstalling from spoke Broker yes  
      Submariner no    
      cluster roles and bindings yes    
      subm config no    
      SA submariner-addon yes    
      broker and addon roles and rolebindings yes    
             
      When a ManagedCluster is removed from the ClusterSet, ensure that Submariner is successfully uninstalled.      
      "detach"ed spoke1 Broker no need to check no
      Submariner no    
      cluster roles and bindings yes    
      subm config no    
      SA submariner-addon no    
      broker and addon roles and rolebindings no    
             
      When a managedClusterSet is deleted (is this allowed?) without removing the ManagedClusters.      
      "Detach"ed "global" clusterset which had hub (acting as spoke as well) and no dedicated spoke Broker no not installed
      Submariner no    
      cluster roles and bindings yes    
      subm config yes    
      SA submariner-addon yes    
      broker and addon roles and rolebindings yes    
             
      When multiple ManagedClusters are selected and Submariner addon is uninstalled, verify that uninstall operation is successful.      
      TO BE TESTED Broker    
      Submariner      
      cluster roles and bindings      
      subm config      
      SA submariner-addon      
      broker and addon roles and rolebindings      

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

      How reproducible:

      Steps to Reproduce:

      1.  Uninstall Submariner-addon from the clusters as per the scenarios defined in the above table.
      2. Check for Broker and RBAC components on Hub and Spoke.

      Actual results:

      Broker and RBAC components were not deleted.

      Expected results:

      Broker and RBAC components to be deleted.

      Additional info:

              tpanteli Thomas Pantelis
              rhn-support-jchhatba Janki Chhatbar
              Prachi Yadav Prachi Yadav
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: