Fix bug when unpublishing already unmounted file system #106
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.
Is this a bug fix or adding new feature?
/kind bug
What is this PR about? / Why do we need it?
Fix bug when unpublishing already unmounted file system. This happens when lingering EFS mount is found on the node such as:
This will cause kubelet to keep unmounting the volume with no success since the volume is already unmounted.
The lingering volume in node object could be caused when the EFS filesystem is unmounted out of band or bugs.
What testing is done?