We have a unit test for testGroupPermissions which assumes the build is running
see class HcfsFileSystemTest.java , "testGroupOwnership", which sets ownership
to from "daemon", and then to "root".
** Its an important test **: we must keep it, but fix it. If the test fails,
then changing permissions , which is an important part of the job submission
workflow in mapreduce
Suggested fix: Choose a user which is available on most linux systems, that is
less restrictive than "root" which can more flexibly be used to test that we
can change permissions from inside the glusterfs-plugin. Or, add the users to
use in unit tests as new environmental variables.
How reproducible: 100%.
Workaround: Run the build as root - in this case, chmod'ing always works, and
simultaneously we still are able to validate that our ability to change group
ownership is working properly.
Per 2013-12-04 bug triage meeting, re-assigning to jvyas.
This is now fixed, with our unit testing updates.
You can see the patch which fixes this here : https://github.com/gluster/glusterfs-hadoop/pull/75/files
The fix is odd to me - you said in BZ description, that testGroupOwnership is important test and we have to keep and fix it. But in the link from comment #2 I saw patch, which deletes the test method. Please explain this to me. Also, please provide me more info how to reproduce bug and how can be error recognized - there is lack information about it in description.
youre right, its no longer a bug, because the build passes as non root.
However, we've lost the feature of testGroupOwnership.
So ... We could keep this bug open, I think - until we can think of a way to write a unit test that confirms group ownership, which
- will work on all systems., but also
- which doesn't require root.
I think that this bug is still not done according comment #5 so I think it should stay in Assigned state till devels will solve it. -->ASSIGNED
glusterfs-hadoop is not actively maintained!