Bug 2125120

Description of problem (please be detailed as possible and provide log
snippests):
 when DRpolicy created, s3profile secerets are not getting created for managed clusters
Steps Followed:
1. created 3 clusters primary secondary and Hub
2. Followed below document
https://red-hat-storage.github.io/ocs-training/training/ocs4/odf411-metro-ramen.html#_create_data_policy_on_hub_cluster
3. All the steps till chapter 8 were successful
4. After created DR policy. S3 profiles are going to s3ListFailed status

[root@localhost Desktop]# ./oc get drpolicy drpolicy -o jsonpath='{.status.conditions[].reason}{"\n"}'
Succeeded
[root@localhost Desktop]# ./oc get csv,pod -n openshift-dr-system
No resources found in openshift-dr-system namespace.
[root@localhost Desktop]# ./oc get csv,pod -n openshift-dr-system
No resources found in openshift-dr-system namespace.
[root@localhost Desktop]# ./oc get nodes
NAME                                  STATUS   ROLES           AGE   VERSION
cephqe-node4.lab.eng.blr.redhat.com   Ready    master,worker   29h   v1.24.0+b62823b
[root@localhost Desktop]# ./oc get csv,pod -n openshift-dr-system
No resources found in openshift-dr-system namespace.
[root@localhost Desktop]# ./oc get csv,pod -n openshift-dr-system
No resources found in openshift-dr-system namespace.
[root@localhost Desktop]# ./oc get drclusters
NAME            AGE
ocp-mr-2308-1   8h
ocp-mr-2308-2   8h
[root@localhost Desktop]# ./oc get drcluster ocp-mr-2308-1 -o jsonpath='{.status.conditions[2].reason}{"\n"}'
s3ListFailed


 


Version of all relevant components (if applicable):

[root@localhost Desktop]# ./oc version
Client Version: 4.11.0-0.nightly-2022-09-02-184920
Kustomize Version: v4.5.4
Server Version: 4.11.0-0.nightly-2022-09-02-184920
Kubernetes Version: v1.24.0+b62823b

ACM :2.5.1
Ceph : 6.0

Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?


Is there any workaround available to the best of your knowledge?
Earlier we use to create odrbucket.yaml with AWS keys.

Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?


Can this issue reproducible?


Can this issue reproduce from the UI?


If this is a regression, please provide more details to justify this:


Steps to Reproduce:
1.
2.
3.


Actual results:


Expected results:


Additional info: