Bug 2236387

Summary: [RDR] Volsync secret name is limited to 62chars and blocks intermittent deployments
Product: [Red Hat Storage] Red Hat OpenShift Data Foundation Reporter: Aman Agrawal <amagrawa>
Component: odf-drAssignee: Benamar Mekhissi <bmekhiss>
odf-dr sub component: ramen QA Contact: kmanohar
Status: CLOSED ERRATA Docs Contact:
Severity: medium    
Priority: unspecified CC: bmekhiss, muagarwa, prsurve, rtalur
Version: 4.14   
Target Milestone: ---   
Target Release: ODF 4.14.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 4.14.0-132 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-11-08 18:54:25 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:

Comment 5 Benamar Mekhissi 2023-09-07 19:32:57 UTC
PR: https://github.com/RamenDR/ramen/pull/1060

Comment 10 kmanohar 2023-10-26 17:45:18 UTC
VERIFICATION COMMENTS:
======================

Steps to reproduce
------------------

--> Create an application and its namespace with their names of length of 35 chars, the length of policy.open-cluster-management.io was limited, which led to issues with drpc and vrgs failing the deployment.

Fix is to add `vs-secret` as prefix in the name of policies, in case of application and namespace name exceeds 62 chars.


O/Ps
----

oc get policies.policy.open-cluster-management.io -A
NAMESPACE             NAME                                                            REMEDIATION ACTION   COMPLIANCE STATE   AGE
kmanohar-clu1         openshift-gitops.busybox-1-cephfs-c1-placement-drpc-vs-secret                        Compliant          33h
kmanohar-clu1         openshift-gitops.busybox-1-cephfs-c2-placement-drpc-vs-secret                        Compliant          9h
kmanohar-clu1         openshift-gitops.vs-secret-3316b73f7ab9451db40cd2ef8ce302dc                          Compliant          8h
kmanohar-clu1         openshift-gitops.vs-secret-4010e649d5d5f9738383d493d091f466                          Compliant          158m
kmanohar-clu1         openshift-gitops.vs-secret-c80cbd719af0d3a969735df1b9751592                          Compliant          6h59m
kmanohar-clu1         openshift-gitops.vs-secret-d92652c9d8766d7d0fc77b726e2079cb                          Compliant          8h
kmanohar-clu1         openshift-operators.0eb4d5937ba374896ab0a0f1f8d824acedbecc4     Enforce              Compliant          6d10h
kmanohar-clu1         openshift-operators.b6a6f041c1181265bbc16e669ce8d5201dbd902     Enforce              Compliant          6d10h
kmanohar-clu2         openshift-gitops.busybox-1-cephfs-c1-placement-drpc-vs-secret                        Compliant          33h
kmanohar-clu2         openshift-gitops.busybox-1-cephfs-c2-placement-drpc-vs-secret                        Compliant          9h
kmanohar-clu2         openshift-gitops.vs-secret-3316b73f7ab9451db40cd2ef8ce302dc                          Compliant          8h
kmanohar-clu2         openshift-gitops.vs-secret-4010e649d5d5f9738383d493d091f466                          Compliant          158m
kmanohar-clu2         openshift-gitops.vs-secret-c80cbd719af0d3a969735df1b9751592                          Compliant          6h59m
kmanohar-clu2         openshift-gitops.vs-secret-d92652c9d8766d7d0fc77b726e2079cb                          Compliant          8h
kmanohar-clu2         openshift-operators.0eb4d5937ba374896ab0a0f1f8d824acedbecc4     Enforce              Compliant          6d10h
kmanohar-clu2         openshift-operators.b6a6f041c1181265bbc16e669ce8d5201dbd902     Enforce              Compliant          6d10h
openshift-gitops      busybox-1-cephfs-c1-placement-drpc-vs-secret                                         Compliant          33h
openshift-gitops      busybox-1-cephfs-c2-placement-drpc-vs-secret                                         Compliant          9h
openshift-gitops      vs-secret-3316b73f7ab9451db40cd2ef8ce302dc                                           Compliant          8h           <-------
openshift-gitops      vs-secret-4010e649d5d5f9738383d493d091f466                                           Compliant          158m         <-------
openshift-gitops      vs-secret-c80cbd719af0d3a969735df1b9751592                                           Compliant          6h59m        <-------
openshift-gitops      vs-secret-d92652c9d8766d7d0fc77b726e2079cb                                           Compliant          8h           <-------
openshift-operators   0eb4d5937ba374896ab0a0f1f8d824acedbecc4                         Enforce              Compliant          6d10h
openshift-operators   b6a6f041c1181265bbc16e669ce8d5201dbd902                         Enforce              Compliant          6d10h


Must gather:
------------

c1 - http://rhsqe-repo.lab.eng.blr.redhat.com/OCS/ocs-qe-bugs/keerthana/bz-v/bz-2236387/c1/

c2 - http://rhsqe-repo.lab.eng.blr.redhat.com/OCS/ocs-qe-bugs/keerthana/bz-v/bz-2236387/c2/

hub - http://rhsqe-repo.lab.eng.blr.redhat.com/OCS/ocs-qe-bugs/keerthana/bz-v/bz-2236387/hub/


Verified on:
------------

ODF - 4.14.0-150
OCP - 4.14.0-0.nightly-2023-10-17-113123
MCO - 4.14.0-150
Submariner - 0.16.0(brew.registry.redhat.io/rh-osbs/iib:599799)
ACM - 2.9.0 (2.9.0-DOWNSTREAM-2023-10-03-20-08-35)

Comment 12 errata-xmlrpc 2023-11-08 18:54:25 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 OpenShift Data Foundation 4.14.0 security, enhancement & bug fix update), 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-2023:6832