Add operational-mode annotation to resolve VRG state ambiguity during… #1479
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… failover - Problem: During failover, if the primary cluster is inaccessible, the DRPC cannot distinguish between a VRG in its final secondary state and one transitioning to secondary. This ambiguity prevents the user from failing over the application. - Solution: Introduced annotation to indicate the current operational mode of the VRG. This fix allows the DRPC to correctly identify the VRG's state and maintaining the PeerReady condition. Fixes: bz-2264765 Signed-off-by: Benamar Mekhissi <bmekhiss@ibm.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For CephFS PVCs, we need two VRGs: one as primary on the primary cluster and the other as secondary on the failover cluster. If the workload has been relocated from the secondary cluster back to the primary and the primary goes offline, when the DRPC reconciles, it will find the primary inaccessible and will only detect the secondary VRG on the failover cluster. This situation is difficult to resolve because the DRPC can't distinguish between a VRG that is in its final state as secondary and one that is transitioning from primary to secondary. As a result, the PeerReady condition will be turned off, and the user will be unable to failover the application using the UI.
The fix for this is to add a hint so that the DRPC can tell whether the VRG is in its final state or transitioning to primary or secondary. This hint is provided through the use of an annotation.
Fixes: bz-2264765