+++ This bug was initially created as a clone of Bug #2249012 +++

Describe the issue:

At the point, there is no verification steps for the secret is propagated correctly, if it is not then there is a chance of hitting bz2248723.

To avoid that it is better to add these verification in our doc [1]

And also we need to add that once the application deployed, the ClusterDataProtected is True at once, so that failover of apps not effected

Describe the task you were trying to accomplish:

Suggestions for improvement:
Add the verification step for secret propagation during initial deployment and the verification for the application that are ClusterdataProtected atleast once

Document URL:
[1]: https://access.redhat.com/documentation/en-us/red_hat_openshift_data_foundation/4.12/html/configuring_openshift_data_foundation_disaster_recovery_for_openshift_workloads/index

Chapter/Section Number and Title:

Product Version:

Environment Details:

Any other versions of this document that also needs this update:

Additional information:

— Additional comment from RHEL Program Management on 2023-11-10 07:42:48 UTC —

This bug having no release flag set previously, is now set with release flag 'odf‑4.15.0' to '?', and so is being proposed to be fixed at the ODF 4.15.0 release. Note that the 3 Acks (pm_ack, devel_ack, qa_ack), if any previously set while release flag was missing, have now been reset since the Acks are to be set against a release flag.