Back to bug 2056871

Who When What Removed Added
James Espy 2022-02-22 18:38:36 UTC CC jespy
Shyamsundar 2022-02-23 15:42:59 UTC CC srangana
Shyamsundar 2022-02-23 15:43:30 UTC QA Contact ebenahar
Assignee mrajanna srangana
Sub Component volume-replication-operator ramen
Shyamsundar 2022-02-23 15:44:26 UTC QA Contact ebenahar
Matthias Muench 2022-02-24 08:47:48 UTC CC mmuench
Mudit Agarwal 2022-03-08 13:45:36 UTC Flags needinfo?(srangana)
Shyamsundar 2022-03-08 17:27:59 UTC Status NEW ASSIGNED
Flags needinfo?(srangana)
Assignee srangana jmishra
RHEL Program Management 2022-03-09 09:34:30 UTC Target Release --- ODF 4.10.0
Raghavendra Talur 2022-03-14 13:10:18 UTC CC rtalur
Link ID Github RamenDR/ramen/pull/403
Status ASSIGNED POST
Mudit Agarwal 2022-03-15 12:12:03 UTC CC jmishra
Flags needinfo?(jmishra)
OpenShift BugZilla Robot 2022-03-15 13:46:07 UTC Link ID Github red-hat-storage/ramen/pull/20
OpenShift BugZilla Robot 2022-03-15 14:02:13 UTC Status POST MODIFIED
Shyamsundar 2022-03-21 13:12:12 UTC Fixed In Version v4.10.0-199
Status MODIFIED ON_QA
Flags needinfo?(jmishra)
Elad 2022-03-22 09:47:34 UTC QA Contact ebenahar amagrawa
Aman Agrawal 2022-04-10 14:24:19 UTC Status ON_QA ASSIGNED
Flags needinfo?(jmishra) needinfo?(srangana)
Benamar Mekhissi 2022-04-11 10:55:10 UTC CC bmekhiss
Sunil Kumar Acharya 2022-04-11 11:38:55 UTC CC sheggodu
Mudit Agarwal 2022-04-11 11:40:31 UTC Target Release ODF 4.10.0 ---
RHEL Program Management 2022-04-11 11:40:40 UTC Target Release --- ODF 4.11.0
Orit Wasserman 2022-04-12 08:08:26 UTC CC owasserm
Mudit Agarwal 2022-06-29 13:30:13 UTC Flags needinfo?(jmishra)
Flags needinfo?(srangana)
Flags needinfo?(amagrawa) needinfo?(bmekhiss)
Aman Agrawal 2022-06-29 13:40:46 UTC Flags needinfo?(amagrawa)
RHEL Program Management 2022-07-05 10:13:20 UTC Target Release ODF 4.11.0 ---
RHEL Program Management 2022-07-13 18:06:04 UTC Target Release --- ODF 4.12.0
Benamar Mekhissi 2022-08-10 09:08:50 UTC Doc Text Cause:
The user starts relocating an application from one cluster to another before the PeerReady Condition Status is TRUE. The Condition Status is seen through the DRPC yaml file or by running the following `oc` command:
`oc get drpc -A -o wide`

Consequence:
If the Relocation is initiated before the peer (target cluster) is in a clean state, then the relocation will stall forever.

Workaround (if any):
Change the DRPC .Spec.Action back to Failover, and wait until the PeerReady condition status is TRUE.

Result:
After applying the workaround, change the Action to Relocate, and the relocation will take effect.
Doc Type If docs needed, set a value Known Issue
Aman Agrawal 2022-08-10 13:46:29 UTC Blocks 2094357
Olive Lakra 2022-08-18 14:44:27 UTC CC olakra
Doc Text Cause:
The user starts relocating an application from one cluster to another before the PeerReady Condition Status is TRUE. The Condition Status is seen through the DRPC yaml file or by running the following `oc` command:
`oc get drpc -A -o wide`

Consequence:
If the Relocation is initiated before the peer (target cluster) is in a clean state, then the relocation will stall forever.

Workaround (if any):
Change the DRPC .Spec.Action back to Failover, and wait until the PeerReady condition status is TRUE.

Result:
After applying the workaround, change the Action to Relocate, and the relocation will take effect.
.Relocation fails when failover and relocate is performed within a few minutes

When the user starts relocating an application from one cluster to another before the `PeerReady` condition status is `TRUE`, the condition status is seen through the DRPC YAML file or by running the following `oc` command: `oc get drpc -A -o wide`

If the Relocation is initiated before the peer (target cluster) is in a clean state, then the relocation will stall forever.

Workaround: Change the DRPC .Spec.Action back to `Failover`, and wait until the `PeerReady` condition status is TRUE. After applying the workaround, change the Action to Relocate, and the relocation will take effect.
Aman Agrawal 2022-08-19 07:29:31 UTC Flags needinfo?(olakra)
Olive Lakra 2022-08-19 08:20:03 UTC Doc Text .Relocation fails when failover and relocate is performed within a few minutes

When the user starts relocating an application from one cluster to another before the `PeerReady` condition status is `TRUE`, the condition status is seen through the DRPC YAML file or by running the following `oc` command: `oc get drpc -A -o wide`

If the Relocation is initiated before the peer (target cluster) is in a clean state, then the relocation will stall forever.

Workaround: Change the DRPC .Spec.Action back to `Failover`, and wait until the `PeerReady` condition status is TRUE. After applying the workaround, change the Action to Relocate, and the relocation will take effect.
.Relocation fails when failover and relocate is performed within a few minutes

When the user starts relocating an application from one cluster to another before the `PeerReady` condition status is `TRUE`, the condition status is seen through the DRPC YAML file or by running the following `oc` command: `oc get drpc -o yaml -n busybox-workloads-1`

where `busybox-workloads-1` is the namespace where the workloads are present for deploying the sample application.

If the Relocation is initiated before the peer (target cluster) is in a clean state, then the relocation will stall forever.

Workaround: Change the DRPC .Spec.Action back to `Failover`, and wait until the `PeerReady` condition status is TRUE. After applying the workaround, change the Action to Relocate, and the relocation will take effect.
Aman Agrawal 2022-08-19 08:28:05 UTC Flags needinfo?(bmekhiss) needinfo?(olakra)
John Call 2022-10-03 16:21:34 UTC CC jcall
Shyamsundar 2022-10-18 11:25:17 UTC Status ASSIGNED MODIFIED
Status MODIFIED ON_QA
Fixed In Version v4.10.0-199 4.12.0-74
Aman Agrawal 2022-12-26 07:47:51 UTC Flags needinfo?(srangana)
Red Hat Bugzilla 2022-12-31 19:00:12 UTC Assignee jmishra srangana
CC jmishra
Red Hat Bugzilla 2022-12-31 19:21:15 UTC CC sagrawal
Red Hat Bugzilla 2022-12-31 19:22:36 UTC CC prsurve
Red Hat Bugzilla 2022-12-31 20:00:26 UTC CC olakra
Red Hat Bugzilla 2022-12-31 20:04:23 UTC QA Contact amagrawa kramdoss
Red Hat Bugzilla 2022-12-31 22:33:46 UTC CC owasserm
Red Hat Bugzilla 2023-01-01 05:47:54 UTC Assignee srangana nobody
CC srangana
Red Hat Bugzilla 2023-01-01 08:30:06 UTC CC bmekhiss
Red Hat Bugzilla 2023-01-01 08:30:29 UTC CC jespy
Red Hat Bugzilla 2023-01-01 08:32:21 UTC QA Contact kramdoss
CC kramdoss
Elad 2023-01-03 08:53:45 UTC CC ebenahar
QA Contact amagrawa
Shyamsundar 2023-01-03 14:10:19 UTC Assignee nobody srangana
Flags needinfo?(srangana)
CC srangana
Alasdair Kergon 2023-01-04 04:42:03 UTC Assignee srangana jmishra
Alasdair Kergon 2023-01-04 04:48:40 UTC CC bmekhiss
Alasdair Kergon 2023-01-04 04:59:56 UTC CC jespy
Alasdair Kergon 2023-01-04 05:00:15 UTC CC jmishra
Alasdair Kergon 2023-01-04 05:07:00 UTC CC kramdoss
Alasdair Kergon 2023-01-04 05:25:54 UTC CC olakra
Alasdair Kergon 2023-01-04 05:26:53 UTC CC owasserm
Alasdair Kergon 2023-01-04 05:33:27 UTC CC prsurve
Alasdair Kergon 2023-01-04 05:39:37 UTC CC sagrawal
Aman Agrawal 2023-01-04 09:16:26 UTC Flags needinfo?(srangana)
Shyamsundar 2023-01-04 12:42:08 UTC Flags needinfo?(srangana)
Aman Agrawal 2023-01-04 12:45:25 UTC Status ON_QA CLOSED
Resolution --- CANTFIX
Last Closed 2023-01-04 12:45:25 UTC
Elad 2023-08-09 17:00:43 UTC CC odf-bz-bot

Back to bug 2056871