Skip to content

[enterprise-4.5] Bug 1884643 update resolving multi-attach errors procedure #27705

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.

Sign up for GitHub

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

Merged
bmcelvee merged 1 commit into from
Nov 30, 2020
Merged

[enterprise-4.5] Bug 1884643 update resolving multi-attach errors procedure #27705

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 10 additions & 1 deletion modules/storage-multi-attach-error.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,6 +18,8 @@ Unable to attach or mount volumes: unmounted volumes=[sso-mysql-pvol], unattache
Multi-Attach error for volume "pvc-8837384d-69d7-40b2-b2e6-5df86943eef9" Volume is already used by pod(s) sso-mysql-1-ns6b4
--

.Procedure

To resolve the multi-attach issue, use one of the following solutions:

* Enable multiple attachments by using RWX volumes.
Expand All @@ -28,4 +30,11 @@ For most storage solutions, you can use ReadWriteMany (RWX) volumes to prevent m
+
For storage that does not support RWX, such as VMware vSphere, RWO volumes must be used instead. However, RWO volumes cannot be mounted on multiple nodes.
+
If you encounter a multi-attach error message with an RWO volume, you can either recover or delete the failed node to make the volume available to other nodes.
If you encounter a multi-attach error message with an RWO volume, force delete the pod on a shut down or crashed node.
+
[source,terminal]
----
$ oc delete pod <old_pod> --force=true --grace-period=0s
----
+
This command deletes the volumes stuck on shutdown or crashed nodes after six minutes.