-
Notifications
You must be signed in to change notification settings - Fork 39k
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
Automated cherry pick of #67097: Ignore EIO error in unmount path #67443
Automated cherry pick of #67097: Ignore EIO error in unmount path #67443
Conversation
@chakri-nelluri: All 'parent' PRs of a cherry-pick PR must have one of the "release-note" or "release-note-action-required" labels, or this PR must follow the standard/parent release note labeling requirement. The following parent PRs have neither the "release-note" nor the "release-note-action-required" labels: #67097. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@chakri-nelluri: Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
/release-note-none |
|
||
notmnt, err := isNotMounted(d.plugin.host.GetMounter(d.plugin.GetPluginName()), deviceMountPath) | ||
if err != nil { | ||
return err | ||
if util.IsCorruptedMnt(err) { | ||
notmnt = false // Corrupted error is assumed to be mounted. |
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.
Just curious: not sure why is assumed to be mounted if the error can be ENOTCONN, for example
But this is identical to the original, so the same should be here in the cherry-pick :)
/lgtm |
Can you add release note to #67097? Ideally release notes for patch release should mention every non-trivial change in the release, so the users know what to expect when they upgrade. Release notes are generated from original PRs to master, not cherry-picks, so adding the note just to this PR won't make it show up in release notes. |
Also: I've approved cherry-pick, but this needs to be approved by an owner of pkg/volume/util today to make it to 1.10.7. |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: chakri-nelluri, gnufied, rata The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/test all [submit-queue is verifying that this PR is safe to merge] |
Automatic merge from submit-queue. |
Cherry pick of #67097 on release-1.10.
#67097: Ignore EIO error in unmount path