mirror of
https://github.com/ceph/ceph-csi.git
synced 2024-11-09 16:00:22 +00:00
8d7b6ee59f
During ResyncVolume we check if the image is in an error state, and we resync. After resync, the image will move to either the `Error` or the `Resyncing` state. And if the image is in the above two conditions, we will return a successful response and Ready=false so that the consumer can wait until the volume is ready to use. If the image is in any other state we return an error message to indicate the syncing is not going on. The whole resync and image state change depends on the rbd mirror daemon. If the mirror daemon is not running, the image can be in Resyncing or Unknown state. The Ramen marks the volume replication as secondary, and once the resync starts, it will delete the volume replication CR as a cleanup process. As we dont have a check for the rbd mirror daemon, we are returning a resync success response and Ready=false. Due to this false response Ramen is assuming the resync started and deleted the volume replication CR, and because of this, the cluster goes into a bad state and needs manual intervention. fixes #3289 Signed-off-by: Madhu Rajanna <madhupr007@gmail.com> |
||
|---|---|---|
| .. | ||
| cephfs | ||
| controller | ||
| csi-addons | ||
| csi-common | ||
| journal | ||
| kms | ||
| liveness | ||
| nfs | ||
| rbd | ||
| util | ||