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

There are no instructions on how to remove, or uninstall all the RDR related bits from the managed and hub clusters. Are these instructions going to be included?

Reported by: dparkes

https://access.redhat.com/documentation/en-us/red_hat_openshift_data_foundation/4.10/html/configuring_openshift_data_foundation_for_regional-dr_with_advanced_cluster_management/index#annotations:b39aa26d-8589-4395-aa0d-e589700c4d28

— Additional comment from RHEL Program Management on 2022-05-19 06:58:19 UTC —

This bug having no release flag set previously, is now set with release flag 'odf‑4.11.0' to '?', and so is being proposed to be fixed at the ODF 4.11.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.

— Additional comment from Bipin Kunal on 2022-05-19 08:55:56 UTC —

Anjana: let's make this a blocker for 4.10.3

— Additional comment from Anjana Suparna Sriram on 2022-06-03 12:15:24 UTC —

@bkunal@redhat.com We do not have the capacity to address this bug for 4.10.3. Moving it to the next release.

— Additional comment from Olive Lakra on 2022-06-03 13:14:43 UTC —

Hi Harish, Talur, Akarsha,

Can you share how to perform DR uninstallation here so that we can add it to the docs as requested by Bipin.

— Additional comment from Shyamsundar on 2022-11-16 15:59:11 UTC —

We need to test some steps detailing uninstall of DR components:

• Disable DR for all workloads
• Delete DR policies
• (Ensure DRClusters and MirrorPeers are also deleted)
• (Ensure DR operators on managed clusters are also uninstalled as a result)
• Uninstall DR and MCO bundles on the hub

I would expect that we write a flow and test the same, before we can document it. This would need to be converted to an Epic as a result in Jira.

— Additional comment from Red Hat Bugzilla on 2022-12-31 19:55:04 UTC —

remove performed by PnT Account Manager <pnt-expunge@redhat.com>

— Additional comment from Red Hat Bugzilla on 2022-12-31 20:00:25 UTC —

remove performed by PnT Account Manager <pnt-expunge@redhat.com>

— Additional comment from Red Hat Bugzilla on 2022-12-31 20:04:23 UTC —

remove performed by PnT Account Manager <pnt-expunge@redhat.com>

— Additional comment from Red Hat Bugzilla on 2022-12-31 20:04:41 UTC —

remove performed by PnT Account Manager <pnt-expunge@redhat.com>

— Additional comment from Red Hat Bugzilla on 2022-12-31 20:04:49 UTC —

remove performed by PnT Account Manager <pnt-expunge@redhat.com>

— Additional comment from Red Hat Bugzilla on 2023-01-01 00:44:37 UTC —

remove performed by PnT Account Manager <pnt-expunge@redhat.com>

— Additional comment from Red Hat Bugzilla on 2023-01-01 05:47:54 UTC —

remove performed by PnT Account Manager <pnt-expunge@redhat.com>

— Additional comment from Red Hat Bugzilla on 2023-01-01 05:48:04 UTC —

remove performed by PnT Account Manager <pnt-expunge@redhat.com>

— Additional comment from Red Hat Bugzilla on 2023-01-01 05:48:14 UTC —

remove performed by PnT Account Manager <pnt-expunge@redhat.com>

— Additional comment from Red Hat Bugzilla on 2023-01-01 08:29:06 UTC —

Account disabled by LDAP Audit

— Additional comment from Red Hat Bugzilla on 2023-01-01 08:29:58 UTC —

Account disabled by LDAP Audit

— Additional comment from Harish NV Rao on 2023-01-06 14:32:17 UTC —

(In reply to Shyamsundar from comment #5)
> We need to test some steps detailing uninstall of DR components:
> - Disable DR for all workloads
> - Delete DR policies
> - (Ensure DRClusters and MirrorPeers are also deleted)
> - (Ensure DR operators on managed clusters are also uninstalled as a result)
> - Uninstall DR and MCO bundles on the hub
>
> I would expect that we write a flow and test the same, before we can
> document it. This would need to be converted to an Epic as a result in Jira.

@shyam and @anjana is there a Jira already created for this? Can you please share the draft document so QE can test the same in 4.12?

— Additional comment from Red Hat Bugzilla on 2023-01-16 05:13:48 UTC —

remove performed by INVALID USER <pnt-expunge@redhat.com>

— Additional comment from Shyamsundar on 2023-01-23 13:56:11 UTC —

(In reply to Harish NV Rao from comment #17)
> (In reply to Shyamsundar from comment #5)
> > We need to test some steps detailing uninstall of DR components:
> > - Disable DR for all workloads
> > - Delete DR policies
> > - (Ensure DRClusters and MirrorPeers are also deleted)
> > - (Ensure DR operators on managed clusters are also uninstalled as a result)
> > - Uninstall DR and MCO bundles on the hub
> >
> > I would expect that we write a flow and test the same, before we can
> > document it. This would need to be converted to an Epic as a result in Jira.
>
> @shyam and @anjana is there a Jira already created for this? Can you please
> share the draft document so QE can test the same in 4.12?

This requires the ability to disable DR for a given workload to start the steps to remove all DR components. This is tracked int he Jira https://issues.redhat.com/browse/RHSTOR-4137 for 4.13 and hence the overall procedure to remove all DR components can be tested with 4.13 as a result.

— Additional comment from Harish NV Rao on 2023-04-04 15:52:24 UTC —

Hi Olive,

since internal whiteboard has 4.13 in it, could you please set target release to 4.13?

— Additional comment from RHEL Program Management on 2023-04-05 04:39:19 UTC —

The 'Target Release' is not to be set manually at the Red Hat OpenShift Data Foundation product.

The 'Target Release' will be auto set appropriately, after the 3 Acks (pm,devel,qa) are set to "" for a specific release flag and that release flag gets auto set to "".

— Additional comment from RHEL Program Management on 2023-04-05 07:34:17 UTC —

This BZ is being approved for ODF 4.13.0 release, upon receipt of the 3 ACKs (PM,Devel,QA) for the release flag 'odf‑4.13.0

— Additional comment from RHEL Program Management on 2023-04-05 07:34:17 UTC —

Since this bug has been approved for ODF 4.13.0 release, through release flag 'odf-4.13.0+', the Target Release is being set to 'ODF 4.13.0

— Additional comment from RHEL Program Management on 2023-04-05 07:34:49 UTC —

This BZ is being approved for ODF 4.13.0 release, upon receipt of the 3 ACKs (PM,Devel,QA) for the release flag 'odf‑4.13.0

— Additional comment from RHEL Program Management on 2023-04-05 07:34:49 UTC —

Since this bug has been approved for ODF 4.13.0 release, through release flag 'odf-4.13.0+', the Target Release is being set to 'ODF 4.13.0

— Additional comment from Harish NV Rao on 2023-05-30 06:00:58 UTC —

(In reply to Shyamsundar from comment #19)
> (In reply to Harish NV Rao from comment #17)
> > (In reply to Shyamsundar from comment #5)
> > > We need to test some steps detailing uninstall of DR components:
> > > - Disable DR for all workloads
> > > - Delete DR policies
> > > - (Ensure DRClusters and MirrorPeers are also deleted)
> > > - (Ensure DR operators on managed clusters are also uninstalled as a result)
> > > - Uninstall DR and MCO bundles on the hub
> > >
> > > I would expect that we write a flow and test the same, before we can
> > > document it. This would need to be converted to an Epic as a result in Jira.
> >
> > @shyam and @anjana is there a Jira already created for this? Can you please
> > share the draft document so QE can test the same in 4.12?
>
> This requires the ability to disable DR for a given workload to start the
> steps to remove all DR components. This is tracked int he Jira
> https://issues.redhat.com/browse/RHSTOR-4137 for 4.13 and hence the overall
> procedure to remove all DR components can be tested with 4.13 as a result.

The jira story https://issues.redhat.com/browse/RHSTOR-4137 is not targeted for 4.13. It is now 4.14 candidate. IIUC, this BZ cannot be tested in 4.13.
Doc team, please check and do the needful

— Additional comment from Olive Lakra on 2023-05-31 13:47:48 UTC —

Moving this jira to 4.14

(In reply to Harish NV Rao from comment #26)
> (In reply to Shyamsundar from comment #19)
> > (In reply to Harish NV Rao from comment #17)
> > > (In reply to Shyamsundar from comment #5)
> > > > We need to test some steps detailing uninstall of DR components:
> > > > - Disable DR for all workloads
> > > > - Delete DR policies
> > > > - (Ensure DRClusters and MirrorPeers are also deleted)
> > > > - (Ensure DR operators on managed clusters are also uninstalled as a result)
> > > > - Uninstall DR and MCO bundles on the hub
> > > >
> > > > I would expect that we write a flow and test the same, before we can
> > > > document it. This would need to be converted to an Epic as a result in Jira.
> > >
> > > @shyam and @anjana is there a Jira already created for this? Can you please
> > > share the draft document so QE can test the same in 4.12?
> >
> > This requires the ability to disable DR for a given workload to start the
> > steps to remove all DR components. This is tracked int he Jira
> > https://issues.redhat.com/browse/RHSTOR-4137 for 4.13 and hence the overall
> > procedure to remove all DR components can be tested with 4.13 as a result.
>
> The jira story https://issues.redhat.com/browse/RHSTOR-4137 is not targeted
> for 4.13. It is now 4.14 candidate. IIUC, this BZ cannot be tested in 4.13.
> Doc team, please check and do the needful

— Additional comment from RHEL Program Management on 2023-05-31 13:47:57 UTC —

The 'Target Release' is not to be set manually at the Red Hat OpenShift Data Foundation product.

The 'Target Release' will be auto set appropriately, after the 3 Acks (pm,devel,qa) are set to "" for a specific release flag and that release flag gets auto set to "".

— Additional comment from RHEL Program Management on 2023-06-16 07:27:56 UTC —

This BZ is being approved for ODF 4.14.0 release, upon receipt of the 3 ACKs (PM,Devel,QA) for the release flag 'odf‑4.14.0

— Additional comment from RHEL Program Management on 2023-06-17 07:28:03 UTC —

Since this bug has been approved for ODF 4.14.0 release, through release flag 'odf-4.14.0+', the Target Release is being set to 'ODF 4.14.0

— Additional comment from Red Hat Bugzilla on 2023-08-03 08:30:26 UTC —

Account disabled by LDAP Audit

— Additional comment from Harish NV Rao on 2023-08-25 15:42:06 UTC —

(In reply to Olive Lakra from comment #27)
> Moving this jira to 4.14
>
> (In reply to Harish NV Rao from comment #26)
> > (In reply to Shyamsundar from comment #19)
> > > (In reply to Harish NV Rao from comment #17)
> > > > (In reply to Shyamsundar from comment #5)
> > > > > We need to test some steps detailing uninstall of DR components:
> > > > > - Disable DR for all workloads
> > > > > - Delete DR policies
> > > > > - (Ensure DRClusters and MirrorPeers are also deleted)
> > > > > - (Ensure DR operators on managed clusters are also uninstalled as a result)
> > > > > - Uninstall DR and MCO bundles on the hub
> > > > >
> > > > > I would expect that we write a flow and test the same, before we can
> > > > > document it. This would need to be converted to an Epic as a result in Jira.
> > > >
> > > > @shyam and @anjana is there a Jira already created for this? Can you please
> > > > share the draft document so QE can test the same in 4.12?
> > >
> > > This requires the ability to disable DR for a given workload to start the
> > > steps to remove all DR components. This is tracked int he Jira
> > > https://issues.redhat.com/browse/RHSTOR-4137 for 4.13 and hence the overall
> > > procedure to remove all DR components can be tested with 4.13 as a result.
> >
> > The jira story https://issues.redhat.com/browse/RHSTOR-4137 is not targeted
> > for 4.13. It is now 4.14 candidate. IIUC, this BZ cannot be tested in 4.13.
> > Doc team, please check and do the needful

https://issues.redhat.com/browse/RHSTOR-4137 is not targeted to 4.14. It's labeled as 4.15 candidate. This BZ cannot be tested in 4.14. Doc team, please check and do the needful.

— Additional comment from RHEL Program Management on 2023-08-30 13:53:19 UTC —

The 'Target Release' is not to be set manually at the Red Hat OpenShift Data Foundation product.

The 'Target Release' will be auto set appropriately, after the 3 Acks (pm,devel,qa) are set to "" for a specific release flag and that release flag gets auto set to "".

— Additional comment from Anjana Suparna Sriram on 2023-08-30 14:22:39 UTC —

(In reply to Harish NV Rao from comment #32)
> (In reply to Olive Lakra from comment #27)
> > Moving this jira to 4.14
> >
> > (In reply to Harish NV Rao from comment #26)
> > > (In reply to Shyamsundar from comment #19)
> > > > (In reply to Harish NV Rao from comment #17)
> > > > > (In reply to Shyamsundar from comment #5)
> > > > > > We need to test some steps detailing uninstall of DR components:
> > > > > > - Disable DR for all workloads
> > > > > > - Delete DR policies
> > > > > > - (Ensure DRClusters and MirrorPeers are also deleted)
> > > > > > - (Ensure DR operators on managed clusters are also uninstalled as a result)
> > > > > > - Uninstall DR and MCO bundles on the hub
> > > > > >
> > > > > > I would expect that we write a flow and test the same, before we can
> > > > > > document it. This would need to be converted to an Epic as a result in Jira.
> > > > >
> > > > > @shyam and @anjana is there a Jira already created for this? Can you please
> > > > > share the draft document so QE can test the same in 4.12?
> > > >
> > > > This requires the ability to disable DR for a given workload to start the
> > > > steps to remove all DR components. This is tracked int he Jira
> > > > https://issues.redhat.com/browse/RHSTOR-4137 for 4.13 and hence the overall
> > > > procedure to remove all DR components can be tested with 4.13 as a result.
> > >
> > > The jira story https://issues.redhat.com/browse/RHSTOR-4137 is not targeted
> > > for 4.13. It is now 4.14 candidate. IIUC, this BZ cannot be tested in 4.13.
> > > Doc team, please check and do the needful
>
> https://issues.redhat.com/browse/RHSTOR-4137 is not targeted to 4.14. It's
> labeled as 4.15 candidate. This BZ cannot be tested in 4.14. Doc team,
> please check and do the needful.

@hnallurv@redhat.com – the bug has been updated and moved to 4.15. Thank you, Harish!

— Additional comment from Erin Donnelly on 2023-10-31 18:58:54 UTC —

Configuring OpenShift Data Foundation for Regional-DR with Advanced Cluster Management, Abstract: "The intent of this solution guide is to detail the steps necessary to deploy OpenShift Data Foundation for disaster recovery with Advanced Cluster Management to achieve a highly available storage infrastructure."

There are no instructions on how to remove, or uninstall all the RDR related bits from the managed and hub clusters. Are these instructions going to be included?

— Additional comment from krishnaram Karthick on 2024-01-22 05:34:57 UTC —

@Karolin - could you pls point to who can provide these steps?

— Additional comment from Karolin Seeger on 2024-01-22 08:09:10 UTC —

@aclewett@redhat.com, can't we use first part (disable DR) of the cluster replacement KCS here?

— Additional comment from Annette Clewett on 2024-01-27 02:15:10 UTC —

@kseeger@redhat.com
Yes we can use replacement cluster process for disable DR and remove DR config from hub and managedclusters. Olive and I discussed this being a new section in the existing DR documentation, Uninstalling MDR or RDR configuration.

Disable DR for cephfs apps is dependent on a fix for https://bugzilla.redhat.com/show_bug.cgi?id=2260130 being backported to ODFo 4.15. I will work with Olive.

— Additional comment from Karolin Seeger on 2024-02-21 16:34:08 UTC —

https://bugzilla.redhat.com/show_bug.cgi?id=2260130 is fixed in 4.15.0-140, so let's move ahead and add the instructions to disable DR. Thanks!

— Additional comment from Olive Lakra on 2024-02-27 09:29:52 UTC —

Here is the draft KCS https://access.redhat.com/articles/7057753 (private)

once approved, we can publish it as active (public)

— Additional comment from Olive Lakra on 2024-03-01 13:48:55 UTC —

I have reviewed the changes made to the KCS by Annette and made one small correction. Also updated the gdoc with the latest content.

https://docs.google.com/document/d/1A_X0xk7uCYbkE3kMzQkx7imMYXEzi7ftuKv16VK-UkA/edit

— Additional comment from avdhoot on 2024-03-12 06:26:40 UTC —

Verified this process as MDR point of view and its look good to me.
Hence marking it as Verified from MDR side.

— Additional comment from Harish NV Rao on 2024-03-12 06:40:41 UTC —

(In reply to avdhoot from comment #42)
> Verified this process as MDR point of view and its look good to me.
> Hence marking it as Verified from MDR side.

Karthick, request you to do the needful from RDR end.