Version: HUB: 4.8.0-0.nightly-2021-06-16-020345 SPOKE: 4.8.0-fc.9 ACM: advanced-cluster-management.v2.3.0 Steps to reproduce: Follow the steps to deploy Spoke SNO cluster with ACM and AI/operator. Result: The spoke cluster is deployed successfully, yet the ACM UI still shows the cluster in "creating" status. Expected result: The status should switch from creating to "Ready".
oc get managedcluster elvis -o yaml apiVersion: cluster.open-cluster-management.io/v1 kind: ManagedCluster metadata: creationTimestamp: "2021-06-17T04:50:19Z" finalizers: - agent.open-cluster-management.io/klusterletaddonconfig-cleanup - managedclusterinfo.finalizers.open-cluster-management.io - open-cluster-management.io/managedclusterrole - cluster.open-cluster-management.io/api-resource-cleanup generation: 1 name: elvis resourceVersion: "699671" uid: bef34974-b1c6-4993-bd3f-4598a67ce181 spec: hubAcceptsClient: true leaseDurationSeconds: 60 status: capacity: core_worker: "0" socket_worker: "0" conditions: - lastTransitionTime: "2021-06-17T04:50:20Z" message: Accepted by hub cluster admin reason: HubClusterAdminAccepted status: "True" type: HubAcceptedManagedCluster - lastTransitionTime: "2021-06-17T05:00:20Z" message: Registration agent stopped updating its lease. reason: ManagedClusterLeaseUpdateStopped status: Unknown type: ManagedClusterConditionAvailable version: {} oc get KlusterletAddonConfig elvis -o yaml apiVersion: agent.open-cluster-management.io/v1 kind: KlusterletAddonConfig metadata: creationTimestamp: "2021-06-17T04:50:19Z" finalizers: - agent.open-cluster-management.io/klusterletaddonconfig-cleanup generation: 2 name: elvis namespace: elvis resourceVersion: "687405" uid: 88a7a216-bd96-4b68-a190-ee742d48dee8 spec: applicationManager: argocdCluster: false enabled: true certPolicyController: enabled: true clusterLabels: cloud: auto-detect vendor: auto-detect clusterName: elvis clusterNamespace: elvis iamPolicyController: enabled: true policyController: enabled: true searchCollector: enabled: false version: "" oc get AgentClusterInstall -n elvis -o=custom-columns='STATUS:status.conditions[-3].message' STATUS The installation has completed: Cluster is installed
I checked things with older hub cluser: Version: hub cluster running 4.8.0-fc.7 spoke running 4.8.0-fc.9 quay.io/acm-d/acm-custom-registry:2.3.0-DOWNSTREAM-2021-06-17-01-26-58 Same steps repeated and the spoke cluster became ready automatically, so seems like we have some regression.
Shouldn't it be assigned to ACM? I don't really know what they are looking at in cluster deployment. Can you please attach the output of cluster deployment?
It's a duplicate of other bug in openshift-apiserver that already been handled TL;DR: openshift-apiserver proxies requests to the kube-apiserver, and there are impersonation headers that have not been escaped well. Hive installation uses those headers, and so the installation of Hive operator most probably started but didn't succeed. Make sure to check for a successful installation even on the HiveConfig object (in our automation we forgot it as well). *** This bug has been marked as a duplicate of bug 1972687 ***
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days