-
Notifications
You must be signed in to change notification settings - Fork 145
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
fix(manager): fix logic for when RWX workload is restarted after node… #3077
Conversation
185b690
to
3b2090c
Compare
3b2090c
to
d412cef
Compare
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.
Should we remove the code at
longhorn-manager/controller/volume_controller.go
Lines 4524 to 4531 in 69f8cdb
// kill the workload pods, when the share manager goes into error state | |
// easiest approach is to set the RemountRequestedAt variable, | |
// since that is already responsible for killing the workload pods | |
if sm.Status.State == longhorn.ShareManagerStateError || sm.Status.State == longhorn.ShareManagerStateUnknown { | |
volume.Status.RemountRequestedAt = c.nowHandler() | |
msg := fmt.Sprintf("Volume %v requested remount at %v", volume.Name, volume.Status.RemountRequestedAt) | |
c.eventRecorder.Eventf(volume, corev1.EventTypeNormal, constant.EventReasonRemount, msg) | |
} |
d412cef
to
8b1a9cd
Compare
I thought about removing the kick from volume_controller, but it is still necessary in some cases. Comment revised to be more accurate, though. |
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.
LGTM. Thanks!
58505f4
to
78e6299
Compare
This pull request is now in conflict. Could you fix it @james-munson? 🙏 |
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.
LGTM
Could you please help to resolve the conflict for merging @james-munson ?
… failure Signed-off-by: James Munson <james.munson@suse.com>
f2e0773
78e6299
to
f2e0773
Compare
@mergify backport v1.7.x |
✅ Backports have been created
|
… failure
Which issue(s) this PR fixes:
longhorn/longhorn#9095
What this PR does / why we need it:
Special notes for your reviewer:
Additional documentation or context