Description of problem: Latest gluster versions has support for auto_unmount option which helps on gluster volume to be cleanly unmounted if there are some crashes in fuse bridge or main fuse process. The support is available in OCP 3.6 builds, we would like to qualify the same for CNS 3.6. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Things to verify: Actually from OCP/CNS side what we need to verify here is, whenever a mount happens in gluster client, 'auto_unmount' option has been passed to the fuse mounts. From CNS perspective thats the only change we have done. However with that option in place, if the main fuse process is killed, ideally the unmount of gluster volumes should happen automatically and cleanly. We could check that as well. If this latter functionality doesnt work, its actually a failure on the 'feature' in gluster, but its worth to check. Also we can check the response in app pod when these happens.
(In reply to Humble Chirammal from comment #5) > Things to verify: > > Actually from OCP/CNS side what we need to verify here is, whenever a mount > happens in gluster client, 'auto_unmount' option has been passed to the fuse > mounts. From CNS perspective thats the only change we have done. However > with that option in place, if the main fuse process is killed, ideally the > unmount of gluster volumes should happen automatically and cleanly. We could > check that as well. If this latter functionality doesnt work, its actually a > failure on the 'feature' in gluster, but its worth to check. Also we can > check the response in app pod when these happens. Verified the above and it works as mentioned.
doc text looks good to me
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2017:2878