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

[MultipleHubs] Cannot be triggered to switch hub when modify hubAcceptsClient to false

XMLWordPrintable

    • 1
    • False
    • None
    • False
    • SF Ready/Refined Backlog, SF Train-20
    • Low
    • None

      Description of problem: Cannot be triggered to switch hub when modify hubAcceptsClient to false 

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

      How reproducible:

      Steps to Reproduce:

      1. Create klusterletconfig to have 2 bootstrap kubeconfig. one is for the current one. the other is for the target one. all the kubeconfigs are generated based on managed serviceaccount token
      2. Apply klusterletconfig to the managed cluster via an annotation 
        agent.open-cluster-management.io/klusterlet-config
      3. ensure the klusterlet has such configuration, then modify the hubAcceptsClient to false in the managed cluster
      4. nothing happened. the managed cluster is still connecting to the previous hub cluster. after delete the klusterlet-agent pod, it can start switching to the new hub.

      Actual results: 

      nothing happened.

      Expected results:

      The switch hub should occur when hubAcceptsClient is set as false.

      Additional info:

              zxue@redhat.com ZHAO XUE
              clyang82 Chunlin Yang
              Hui Chen Hui Chen
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: