Description of problem:
Creation of a second hostedcluster in the same namespace fails with the error "failed to set secret''s owner reference" in the status of the second hostedlcuster's yaml. ~~~ conditions: - lastTransitionTime: "2024-04-02T06:57:18Z" message: 'failed to reconcile the CLI secrets: failed to set secret''s owner reference' observedGeneration: 1 reason: ReconciliationError status: "False" type: ReconciliationSucceeded ~~~ Note that the hosted control plane namespace is still different for both clusters. Customer is just following the doc - https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.9/html/clusters/cluster_mce_overview#creating-a-hosted-cluster-bm for both the clusters and only the hostedcluster CR is created in the same namespace.
Version-Release number of selected component (if applicable):
4.14
How reproducible:
Steps to Reproduce:
1. Create a hostedcluster as per the doc https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.9/html/clusters/cluster_mce_overview#creating-a-hosted-cluster-bm 2. Create another hostedcluster in the same namespace where the first hostedcluster was created. 3. Second hostedcluster fails to proceed with the said error.
Actual results:
The hostedcluster creation fails
Expected results:
The hostedcluster creation should succeed
Additional info:
- is cloned by
-
OCPBUGS-32404 [release-4.15] Creation of second hostedcluster in the same namespace fails with 'failed to set secret''s owner reference'
- Closed
- is depended on by
-
OCPBUGS-32404 [release-4.15] Creation of second hostedcluster in the same namespace fails with 'failed to set secret''s owner reference'
- Closed
- links to
-
RHEA-2024:0041 OpenShift Container Platform 4.16.z bug fix update