Madhu Rajanna 8c5563a9bc rbd: remove checkHealthyPrimary check ... After Failover of workloads to the secondary cluster when the primary cluster is down, RBD Image is not marked healthy, and VR resources are not promoted to the Primary, In VolumeReplication, the `CURRENT STATE` remains Unknown and doesn't change to Primary. This happens because the primary cluster went down, and we have force promoted the image on the secondary cluster. and the image stays in up+stopping_replay or could be any other states. Currently assumption was that the image will always be `up+stopped`. But the image will be in `up+stopped` only for planned failover and it could be in any other state if its a forced failover. For this reason, removing checkHealthyPrimary from the PromoteVolume RPC call. Signed-off-by: Madhu Rajanna <madhupr007@gmail.com>		2022-07-27 09:04:27 +00:00
..
cephfs	cleanup: create k8s.io/mount-utils Mounter only once	2022-07-21 07:14:43 +00:00
controller	cleanup: ReconcilePersistentVolume consider passing it by pointer	2022-06-28 19:12:53 +00:00
csi-addons	ci: fix all linter errors found in golangci-lint	2022-06-03 12:55:54 +00:00
csi-common	cleanup: create k8s.io/mount-utils Mounter only once	2022-07-21 07:14:43 +00:00
journal	cephfs: added support for snapshot-backed volumes	2022-06-16 09:44:27 +00:00
kms	rbd: create token and use it for vault SA	2022-06-17 11:37:59 +00:00
liveness	cleanup: move log functions to new internal/util/log package	2021-08-26 09:34:05 +00:00
nfs	ci: fix all linter errors found in golangci-lint	2022-06-03 12:55:54 +00:00
rbd	rbd: remove checkHealthyPrimary check	2022-07-27 09:04:27 +00:00
util	cleanup: create k8s.io/mount-utils Mounter only once	2022-07-21 07:14:43 +00:00