Back to bug 2081715
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Gopi | 2022-05-04 13:11:19 UTC | Keywords | TestBlocker | |
| QA Contact | vashastr | gpatta | ||
| Red Hat One Jira (issues.redhat.com) | 2022-05-04 13:35:23 UTC | Link ID | Red Hat Issue Tracker RHCEPH-4237 | |
| Deepika Upadhyay | 2022-05-04 14:44:38 UTC | CC | dupadhya | |
| Deepika Upadhyay | 2022-05-05 17:48:33 UTC | Target Release | 5.1z1 | 5.2 |
| Ilya Dryomov | 2022-05-06 10:41:05 UTC | Assignee | idryomov | dupadhya |
| Veera Raghava Reddy | 2022-05-11 15:21:38 UTC | CC | vereddy | |
| Gopi | 2022-05-17 13:40:13 UTC | Blocks | 2085458 | |
| Gopi | 2022-05-17 13:53:41 UTC | Doc Type | If docs needed, set a value | Known Issue |
| Doc Text | Cause: images are reporting as "up+error" and description as "failed to unlink local peer from remote image" after failover operation Consequence: Customer would not able to do failover/failback operations on mirror setup Workaround (if any): Restarting rbd-mirror daemons works sometimes. Result: |
|||
| Mary Frances Hull | 2022-05-17 14:56:25 UTC | Doc Text | Cause: images are reporting as "up+error" and description as "failed to unlink local peer from remote image" after failover operation Consequence: Customer would not able to do failover/failback operations on mirror setup Workaround (if any): Restarting rbd-mirror daemons works sometimes. Result: | .RBD-mirror images are reporting as "up+error" from secondary and "down+replying" from primary after failback operation Users are not able to do failover/failback operations on mirror setup. To work around this issue, you can try restarting the `rbd-mirror` daemons. Restarting the `rbd-mirror` daemons only works sometimes. |
| CC | mhull | |||
| Flags | needinfo?(dupadhya) | |||
| Mary Frances Hull | 2022-05-17 17:02:40 UTC | Docs Contact | mhull | |
| Doc Text | .RBD-mirror images are reporting as "up+error" from secondary and "down+replying" from primary after failback operation Users are not able to do failover/failback operations on mirror setup. To work around this issue, you can try restarting the `rbd-mirror` daemons. Restarting the `rbd-mirror` daemons only works sometimes. | .RBD-mirror images are reporting as "up+error" from secondary and "down+replying" from primary after failback operation Users are not able to do failover/failback operations on mirror setup. To work around this issue, restart the `rbd-mirror` daemons. Restarting the `rbd-mirror` daemons only works sometimes. |
||
| Mary Frances Hull | 2022-05-18 11:56:27 UTC | Blocks | 2085458 | |
| Red Hat Bugzilla | 2022-05-26 08:31:03 UTC | CC | ceph-qe-bugs | |
| Ilya Dryomov | 2022-06-20 08:26:30 UTC | Assignee | dupadhya | idryomov |
| Link ID | Ceph Project Bug Tracker 54448 | |||
| CC | idryomov | |||
| Status | NEW | ASSIGNED | ||
| Ilya Dryomov | 2022-06-20 08:27:34 UTC | Flags | needinfo?(dupadhya) | |
| Doc Text | .RBD-mirror images are reporting as "up+error" from secondary and "down+replying" from primary after failback operation Users are not able to do failover/failback operations on mirror setup. To work around this issue, restart the `rbd-mirror` daemons. Restarting the `rbd-mirror` daemons only works sometimes. | |||
| Doc Type | Known Issue | If docs needed, set a value | ||
| Ilya Dryomov | 2022-06-22 17:08:06 UTC | Status | ASSIGNED | POST |
| Gopi | 2022-06-24 13:09:00 UTC | Status | POST | MODIFIED |
| CC | tserlin | |||
| Fixed In Version | ceph-16.2.8-55.el8cp | |||
| Status | MODIFIED | ON_QA | ||
| Status | ON_QA | VERIFIED | ||
| Mudit Agarwal | 2022-06-29 14:21:59 UTC | Blocks | 2093690 | |
| Akash Raj | 2022-07-29 05:58:20 UTC | Blocks | 2102272 | |
| Akash Raj | 2022-07-29 05:59:20 UTC | CC | akraj | |
| Flags | needinfo?(idryomov) | |||
| Ilya Dryomov | 2022-07-29 09:28:34 UTC | Doc Text | Cause: Due to an implementation defect, replay/resync was attempted even if remote image is not primary (i.e. there is nowhere to replay or resync from). Consequence: Snapshot-based mirroring could run into a livelock and continuously report "failed to unlink local peer from remote image" error. Fix: The implementation defect was fixed. Result: If remote image is not primary, replay/resync is not attempted. No errors are reported. | |
| Doc Type | If docs needed, set a value | Bug Fix | ||
| Flags | needinfo?(idryomov) | |||
| Red Hat Bugzilla | 2022-07-29 18:53:07 UTC | QA Contact | gpatta | vashastr |
| Akash Raj | 2022-08-03 14:18:27 UTC | Flags | needinfo?(idryomov) | |
| Doc Text | Cause: Due to an implementation defect, replay/resync was attempted even if remote image is not primary (i.e. there is nowhere to replay or resync from). Consequence: Snapshot-based mirroring could run into a livelock and continuously report "failed to unlink local peer from remote image" error. Fix: The implementation defect was fixed. Result: If remote image is not primary, replay/resync is not attempted. No errors are reported. | .Replay or resync is no longer attempted if the remote image is not primary Previously, due to an implementation defect, replay or resync would be attempted even if the remote image was not primary, that is, there is nowhere to replay or resync from. This caused the snapshot-based mirroring to run into a livelock and to continuously report "failed to unlink local peer from remote image" error. With this fix, the implementation defect is fixed and replay or resync is not attempted if the remote image is not primary, thereby no errors are reported. | ||
| Docs Contact | mhull | |||
| Ilya Dryomov | 2022-08-04 09:28:31 UTC | Flags | needinfo?(idryomov) | |
| errata-xmlrpc | 2022-08-09 09:59:28 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2022-08-09 17:38:23 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2022-08-09 17:38:23 UTC | |||
| errata-xmlrpc | 2022-08-09 17:39:04 UTC | Link ID | Red Hat Product Errata RHSA-2022:5997 |
Back to bug 2081715