Skip to content
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: AccessMode not changed to <none> after claims released #11921

Closed
tgross opened this issue Jan 24, 2022 · 2 comments
Closed

CSI: AccessMode not changed to <none> after claims released #11921

tgross opened this issue Jan 24, 2022 · 2 comments
Assignees
Milestone

Comments

@tgross
Copy link
Member

tgross commented Jan 24, 2022

If a volume is claimed as single-node-writer and then the job is stopped and purged, the access mode is never updated even if the patch for fixing the volume claims (#11890) is applied. The access mode should be updated to <none> so that a subsequent job can change it to a new mode.

@tgross
Copy link
Member Author

tgross commented Mar 18, 2022

Looks like this was fixed as a side-effect of #11932 and #12112. Closing it out.

@tgross tgross closed this as completed Mar 18, 2022
@tgross tgross added this to the 1.3.0 milestone Mar 18, 2022
@github-actions
Copy link

I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 10, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant