Bug 2017392 - [DR] check local rbd image state for resyncVolume Response
Summary: [DR] check local rbd image state for resyncVolume Response
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: csi-driver
Version: 4.9
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ODF 4.9.0
Assignee: Madhu Rajanna
QA Contact: Sidhant Agrawal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-10-26 12:27 UTC by Madhu Rajanna
Modified: 2023-08-09 16:37 UTC (History)
5 users (show)

Fixed In Version: v4.9.0-210.ci
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-01-07 17:46:31 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github red-hat-storage ceph-csi pull 40 0 None open BUG 2017392: check local image state for resyncing 2021-10-27 04:35:10 UTC
Red Hat Bugzilla 2017392 1 unspecified CLOSED [DR] check local rbd image state for resyncVolume Response 2023-08-09 16:37:41 UTC

Internal Links: 2017392

Description Madhu Rajanna 2021-10-26 12:27:32 UTC
below are the local states of the mirrored image, cephcsi should consider the states to report back the error or the ready state for resyncVolumeResponse so that volume replication operator can update the resync condition in the Volume Replication CR properly.


"unknown" -> If the image is in an error state means data is completely synced
"error" -> If the image is in an error state means it needs resync
"syncing"
"starting_replay"
"replaying" -> If the image is in a replaying state means its replaying from primary source
"stopping_replay"
"stopped"

If the resync is successfully started which means the image will be in a "replaying" state we can consider "replaying" state to report resync successfully going on the state.
we are discarding the intermediate states like "syncing", "starting_replay" and "stopping_replay".

addition details at https://bugzilla.redhat.com/show_bug.cgi?id=2012143#c12


Note You need to log in before you can comment on or make changes to this bug.