New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
csi: remove cephFs networkFence code temporarily #13806
csi: remove cephFs networkFence code temporarily #13806
Conversation
update go.mod to use csi-addons version v0.8.0. Signed-off-by: subhamkrai <srai@redhat.com>
earlier, we were only checking the specs of networkFence to see if unfencing is done before proceeding with deletion but we should also check the status of networkFence before proceeding with deletion. Signed-off-by: subhamkrai <srai@redhat.com> (cherry picked from commit 0ace7cf)
cephFs fencing needs more testing and bug fixes to make it in production. We tried multiple fixes but still it need more work. So, removing the cephfs networkFence realted code will rever this commit when we start working on this again. Signed-off-by: subhamkrai <srai@redhat.com> (cherry picked from commit bd4250f)
Hi @subhamkrai, this pull request was opened against a release branch, is it expected? Normally patches should go in the master branch first and then be backported to release branches. |
@travisn Manually backport is required as 1.13 branch was using csi-addons 0.7.0 but we 0.8.0 with the latest changes |
@@ -604,8 +449,8 @@ func (c *clientCluster) unfenceAndDeleteNetworkFence(ctx context.Context, node c | |||
return false, err | |||
} | |||
|
|||
if networkFence.Spec.FenceState != addonsv1alpha1.Unfenced { | |||
logger.Infof("waiting for network fence CR %s to get in %s state before deletion", networkFence.Name, addonsv1alpha1.Unfenced) | |||
if networkFence.Status.Message != addonsv1alpha1.UnFenceOperationSuccessfulMessage { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if networkFence.Status.Message != addonsv1alpha1.UnFenceOperationSuccessfulMessage { | |
if networkFence.Status.Message != addonsv1alpha1.UnFenceOperationSuccessfulMessage { |
This check requires csi-addons v0.8.0
Please check individual commit messages
Issue resolved by this Pull Request:
Resolves #13805
Checklist: