NFS mount command error detection is faulty
Bug #1797233 reported by
Eric Harney
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
os-brick |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
NFS mount calls are considered successful in os-brick if "already mounted" appears in the stderr output of the mount command.
However, "busy or already mounted" can appear when the mount was not actually successful.
This causes Cinder to write data to a local disk instead of to an NFS target when it occurs.
To post a comment you must log in.
The test case for this behavior is to mount an NFS export with one SELinux context, and then have Cinder try to mount it with a different SELinux context. This hits a limitation in the Linux NFS client that produces this error.
See details in https:/ /bugzilla. redhat. com/show_ bug.cgi? id=253530 .