openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-06 06:46:26 +01:00
Code Issues Releases Activity

Merge pull request #27707 from openshift-cherrypick-robot/cherry-pick-27703-to-enterprise-4.7

Browse Source 
[enterprise-4.7] Bug 1884643 update resolving multi-attach errors procedure
This commit is contained in:
Brandi McElveen Munilla
2020-11-30 09:01:27 -05:00
committed by GitHub
parent d06c4b9741 177631b8d2
commit cef64f9b11
1 changed files with 10 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
modules/storage-multi-attach-error.adoc
View File

@@ -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.
@@ -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.