Bug 2067207 - Bare metal asset secrets are not backed up
Summary: Bare metal asset secrets are not backed up
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Advanced Cluster Management for Kubernetes
Classification: Red Hat
Component: DR4Hub
Version: rhacm-2.5
Hardware: x86_64
OS: Unspecified
unspecified
high
Target Milestone: ---
: rhacm-2.5
Assignee: vbirsan
QA Contact: Thuy Nguyen
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-03-23 14:27 UTC by Thuy Nguyen
Modified: 2023-06-07 23:25 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-06-09 02:10:05 UTC
Target Upstream Version:
Embargoed:
bot-tracker-sync: rhacm-2.5+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github stolostron backlog issues 21069 0 None None None 2022-03-23 19:24:01 UTC
Red Hat Product Errata RHSA-2022:4956 0 None None None 2022-06-09 02:10:14 UTC

Description Thuy Nguyen 2022-03-23 14:27:44 UTC 
Description of problem: Bare metal asset secrets are not backed up


Version-Release number of selected component (if applicable):
ACM 2.5.0-DOWNSTREAM-2022-03-17-03-36-41 (Final S4)

How reproducible:


Steps to Reproduce:
1. Primary hub has baremetal spoke provisioned
2. Create backup for primary hub
3. Restore activation on secondary hub

Actual results:
clustersync created for the spoke cluster failed due to no bare metal assets' secrets found

Expected results:


Additional info:

oc get managedcluster
NAME            HUB ACCEPTED   MANAGED CLUSTER URLS                                  JOINED   AVAILABLE   AGE
local-cluster   true           https://api.slot-06.dev09.red-chesterfield.com:6443   True     True        11h
slot-02         true           https://api.slot-02.dev09.red-chesterfield.com:6443   True     True        14m


oc get baremetalassets -n slot-02
NAME                                AGE
fog07.acm.lab.eng.rdu2.redhat.com   17m
fog08.acm.lab.eng.rdu2.redhat.com   17m
fog09.acm.lab.eng.rdu2.redhat.com   17m


oc get clustersync -n slot-02
NAME      STATUS
slot-02   Failure


oc get clustersync -n slot-02 slot-02 -oyaml
apiVersion: hiveinternal.openshift.io/v1alpha1
kind: ClusterSync
metadata:
  creationTimestamp: "2022-03-23T14:10:15Z"
  generation: 1
  name: slot-02
  namespace: slot-02
  ownerReferences:
  - apiVersion: hive.openshift.io/v1
    blockOwnerDeletion: true
    kind: ClusterDeployment
    name: slot-02
    uid: e75d5304-f3ea-4c56-86d0-365018e78c20
  resourceVersion: "151573565"
  uid: 7cce945d-16d1-4a99-8f6d-a89692748d50
spec: {}
status:
  conditions:
  - lastProbeTime: "2022-03-23T14:10:15Z"
    lastTransitionTime: "2022-03-23T14:10:15Z"
    message: SyncSets fog07.acm.lab.eng.rdu2.redhat.com, fog08.acm.lab.eng.rdu2.redhat.com,
      fog09.acm.lab.eng.rdu2.redhat.com are failing
    reason: Failure
    status: "True"
    type: Failed
  syncSets:
  - failureMessage: 'failed to read secret 0: Secret "fog07.acm.lab.eng.rdu2.redhat.com-bmc-secret"
      not found'
    lastTransitionTime: "2022-03-23T14:21:13Z"
    name: fog07.acm.lab.eng.rdu2.redhat.com
    observedGeneration: 1
    result: Failure
  - failureMessage: 'failed to read secret 0: Secret "fog08.acm.lab.eng.rdu2.redhat.com-bmc-secret"
      not found'
    lastTransitionTime: "2022-03-23T14:10:15Z"
    name: fog08.acm.lab.eng.rdu2.redhat.com
    observedGeneration: 1
    result: Failure
  - failureMessage: 'failed to read secret 0: Secret "fog09.acm.lab.eng.rdu2.redhat.com-bmc-secret"
      not found'
    lastTransitionTime: "2022-03-23T14:10:15Z"
    name: fog09.acm.lab.eng.rdu2.redhat.com
    observedGeneration: 1
    result: Failure
Comment 2 Yuanyuan He 2022-04-11 07:40:36 UTC 
@
Comment 3 bot-tracker-sync 2022-04-20 20:55:23 UTC 
G2Bsync 1104289977 comment 
 thuyn-581 Wed, 20 Apr 2022 18:29:00 UTC 
 G2BSync -
Validated on ACM 2.5.0-DOWNSTREAM-2022-04-18-17-36-04.
Comment 6 errata-xmlrpc 2022-06-09 02:10:05 UTC 
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
Comment 7 Eboni Booker 2023-02-16 11:29:13 UTC Comment hidden (spam)
Note You need to log in before you can comment on or make changes to this bug.