Bug 2138855
Summary: | [RDR] When relocate is performed, Peer Ready isn't marked as False | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat OpenShift Data Foundation | Reporter: | Aman Agrawal <amagrawa> |
Component: | odf-dr | Assignee: | Benamar Mekhissi <bmekhiss> |
odf-dr sub component: | ramen | QA Contact: | Sidhant Agrawal <sagrawal> |
Status: | CLOSED ERRATA | Docs Contact: | |
Severity: | high | ||
Priority: | unspecified | CC: | ebenahar, edonnell, gshanmug, kseeger, muagarwa, odf-bz-bot, sagrawal, sheggodu, srangana |
Version: | 4.12 | ||
Target Milestone: | --- | ||
Target Release: | ODF 4.14.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | 4.14.0-108 | Doc Type: | Bug Fix |
Doc Text: |
.`PeerReady` state is no longer set to `true` when a workload is failed over or relocated to the peer cluster until the cluster from where it was failed over or relocated from is cleaned up*
Previously, after a disaster recovery (DR) action was initiated, the `PeerReady` condition was initially set to `true` for the duration when the workload was failed over or relocated to the peer cluster. After this it was set to `false` until the cluster from where it was failed over or relocated from was cleaned up for future actions. A user looking at `DRPlacementControl` status conditions for future actions may have recognized this intermediate `PeerReady` state as a peer was ready for action and perform the same. This would result in the operation pending or failing and may have required user intervention to recover from.
With this fix, `PeerReady` state is no longer set to `true` on failed or relocated workloads until the cluster is cleaned up, so there is no longer any confusion for the user.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2023-11-08 18:49:51 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 2107226, 2244409 |
Comment 40
Benamar Mekhissi
2023-08-03 17:25:15 UTC
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Important: Red Hat OpenShift Data Foundation 4.14.0 security, enhancement & bug fix update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2023:6832 |