-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
odf-4.18.4
-
None
Description of problem - Provide a detailed description of the issue encountered, including logs/command-output snippets and screenshots if the issue is observed in the UI:
Cannot relocate an application within Openshift Regional-DR after the application was restored with OADP
The ODF deployment type (Internal, External, Internal-Attached (LSO), Multicluster, DR, Provider, etc):
DR
The version of all relevant components (OCP, ODF, RHCS, ACM whichever is applicable):
ODF 4.18.4
Does this issue impact your ability to continue to work with the product?
Yes
Application relocation is failing when trying to relocate the application back to primary datacenter that was previously restored with OADP in primary datacenter.
Is there any workaround available to the best of your knowledge?
delete the uid and resourceVersion fields under pv.spec.claimRef
Can this issue be reproduced? If so, please provide the hit rate
100 %
Steps to Reproduce:
1. Create the application using ACM (Push model).
2. Enable Regional-DR for application (using the policy with enabled: "Advanced Settings -> Enable disaster recovery support for restored and cloned PersistentVolumeClaims").
3. Enable the application backups creating schedule in OADP.
4. Wait few backups.
5. Restore the application:
5a. Disable Regional-DR for application (restoring the app with enabled regional-dr is not possible, so we disable the replication during the restore).
5b. Create restore object in OADP to restore the application and wait to successful restore.
5c. Enable Regional-DR for application (after restoring we want to reprotect the application).
6. Relocate the application to secondary data center (to simulate the maintenance on primary data center).
7. Relocate the application back to primary data center (to simulate the return to standard operation). -> This step is never ends with success, the PVC on secondary data center is never deleted (hanging in Terminating state) hence the application is never started back in primary datacenter.
Logs collected and log location:
supportshell-1 04162774