This is similar to https://bugzilla.redhat.com/show_bug.cgi?id=1337479. But the fix is to move mount/unmount to volume manager (along with detach/attach). Does this problem exist in openshift 3.3 (kubernetes 1.3.4)?
This does not need to be addressed in 3.2. Believed fixed in 3.3. Moving ON_QA.
Issue has been fixed with 3.3, any chance can this be fixed in 3.2.1? As described in https://bugzilla.redhat.com/show_bug.cgi?id=1347666#c45.
The fix, adding volume manager, is rather a big architectural change in 1.3.
(In reply to hchen from comment #5) > The fix, adding volume manager, is rather a big architectural change in 1.3. Thanks for quick confirmation. -- Understand. We can also add these info into the customer issue https://bugzilla.redhat.com/show_bug.cgi?id=1347666 requesting to also doc this in the workaround towards NFS server which will cause problem when end user about to delete their logging pods. Please help to assign this bz back to ON_QA for closure if you think this solution is acceptable.
Set to verified according to comment #6.
I would disagree that this is like https://bugzilla.redhat.com/show_bug.cgi?id=1337479 because it is not an NFS mount, either by PVC or by direct volume. It is a hostmount, whose backing device happens to be on an NFS mount. Also, I couldn't reproduce this. The project deleted fully and instantly in my installation. I'll try again.
I could not reproduce this on an OSE 3.2.1 system. Pods with the privileged hostmount went away as expected, whether deleted directly or as part of the project deletion.
(In reply to Luke Meyer from comment #9) > I could not reproduce this on an OSE 3.2.1 system. Pods with the privileged > hostmount went away as expected, whether deleted directly or as part of the > project deletion. Yes, this also not reproduce to me when I tried it again today. Appologize for bring it out in the other bz.