Bug 2283038
| Summary: | [RDR] [Hub recovery] [Co-situated] Failover never completes when peer ready is true but replication destination is missing | ||
|---|---|---|---|
| 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: | krishnaram Karthick <kramdoss> |
| Status: | ASSIGNED --- | Docs Contact: | |
| Severity: | high | ||
| Priority: | unspecified | CC: | bmekhiss, edonnell, kseeger, muagarwa |
| Version: | 4.16 | Flags: | kseeger:
needinfo?
amagrawa: needinfo? (bmekhiss) amagrawa: needinfo? (edonnell) |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Known Issue | |
| Doc Text: |
.Failover process fails when the `ReplicationDestination` resource has not been created yet
If the user initiates a failover before the `LastGroupSyncTime` is updated, the failover process might fail. This failure is accompanied by an error message indicating that the `ReplicationDestination` does not exist.
Workaround: To mitigate this issue, follow these steps:
. Edit the `ManifestWork` for the VRG on the hub cluster.
. Delete the following section from the manifest:
```
/spec/workload/manifests/0/spec/volsync
```
. Save the changes.
Applying this workaround correctly ensures that the VRG skips attempting to restore the PVC using the `ReplicationDestination` resource. If the PVC already exists, the application uses it as is. If the PVC does not exist, a new PVC is created.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 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: | |||
|
Description
Aman Agrawal
2024-05-23 17:51:02 UTC
Moving the non-blocker BZs out of ODF-4.17.0 as part of Development Freeze. |