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

ArgoCD Unable to Authenticate to Cluster After ACM Upgrade

XMLWordPrintable

    • 1
    • False
    • Hide

      None

      Show
      None
    • False
    • Workload Mgmt Train 32 - 1
    • Important
    • Customer Facing, Customer Reported
    • None

      Description of problem:

       ArgoCD Unable to Authenticate to Cluster After ACM Upgrade

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

      2.14 and  maybe 2.13

      How reproducible:

      Always on 2.14

      Steps to Reproduce:

      1. Follow the guide to allow for mce import: https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.13/html-single/multicluster_engine_operator_with_red_hat_advanced_cluster_management/index#config-addons-hosted
      2.  Upgrade to 2.14 or install 2.14 before doing the above
      3.  Try to login with token provided by local-cluster-application-manager-cluster-secret

      Actual results:

      The following is shown in argocd:
      Failed to load live state: failed to get cluster info for "https://api.acmnpoce.trusted.visa.com:6443": error synchronizing cache state : the server has asked for the client to provide credentials
      When using the token from local-cluster-application-manager-cluster-secret the following shows:

      You don't have any projects. Contact your system administrator to request a project.

      Expected results:

      It stays synced and the login works through token

      Additional info:

      It appears that the clusterrolebinding attaches to the serviceaccount in the open-cluster-management-agent-addon namespace instead of the open-cluster-management-agent-addon-discovery so the serviceaccount is not getting the appropriate permissions.

              xiangli@redhat.com Xiangjing Li
              rhn-support-dluong David Luong
              Hui Chen Hui Chen
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: