Bug 2066842
Summary: | cluster pool credentials are not backed up | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Advanced Cluster Management for Kubernetes | Reporter: | Thuy Nguyen <thnguyen> | ||||
Component: | DR4Hub | Assignee: | vbirsan | ||||
Status: | CLOSED ERRATA | QA Contact: | Thuy Nguyen <thnguyen> | ||||
Severity: | high | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | rhacm-2.5 | Flags: | bot-tracker-sync:
rhacm-2.5+
|
||||
Target Milestone: | --- | ||||||
Target Release: | rhacm-2.5 | ||||||
Hardware: | x86_64 | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2022-06-09 02:10:05 UTC | Type: | Bug | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Thuy Nguyen
2022-03-22 15:24:57 UTC
that's because the clusterpool secrets have no hive label annotation .. I expected to see a label annotation `hive.openshift.io/secret-type` as with the cluster deployment secrets oc get secrets -n default az-pool-tn-azure-creds -o yaml kind: Secret metadata: creationTimestamp: "2022-03-18T03:50:39Z" managedFields: - apiVersion: v1 fieldsType: FieldsV1 fieldsV1: f:data: .: {} f:osServicePrincipal.json: {} f:type: {} manager: unknown operation: Update time: "2022-03-18T03:50:39Z" name: az-pool-tn-azure-creds namespace: default resourceVersion: "135499276" uid: 50646ad1-7e30-46fb-8a6a-0910dba2997a type: Opaque The proper fix here is for the team creating the cluster pools to annotate the secrets required to be backed up and used by the cluster pool Can we assign this defect to that team ? I am not sure who that is - apiVersion: hive.openshift.io/v1 kind: ClusterPool The hard way to do this is for the backup component to add those annotations before a backup is executed but I strongly prefer to fix this on the actual resource then me trying to patch G2Bsync 1087625237 comment thuyn-581 Mon, 04 Apr 2022 14:24:11 UTC G2BSync - Validated on ACM 2.5.0-DOWNSTREAM-2022-03-29-05-04-50. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Important: Red Hat Advanced Cluster Management 2.5 security updates, images, and bug fixes), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:4956 |