====================================================================== ERROR: testUmaskChange (tests.TestCPopen) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/sbonazzo/cpopen/tests/tests.py", line 188, in testUmaskChange p = CPopen(['umask'], childUmask=0o007) File "../build/lib.linux-x86_64-2.7/cpopen/__init__.py", line 52, in __init__ stderr=stderr) File "/usr/lib/python2.7/subprocess.py", line 710, in __init__ errread, errwrite) File "../build/lib.linux-x86_64-2.7/cpopen/__init__.py", line 69, in _execute_child_v276 errread, errwrite, File "../build/lib.linux-x86_64-2.7/cpopen/__init__.py", line 89, in _execute_child_v275 self._childUmask, OSError: [Errno 2] No such file or directory ----------------------------------------------------------------------
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
In oVirt testing is done on single release by default. Therefore I'm removing the 4.0 flag. If you think this bug must be tested in 4.0 as well, please re-add the flag. Please note we might not have testing resources to handle the 4.0 clone.
can be that umask does not exist in your env? should be /usr/bin/umask .. Simone can you check it please? its part of the basic bash package
umask is not a program in debian, it's a bash builtin. note that also in fedora /usr/bin/umask is just: $ cat /usr/bin/umask #!/bin/sh builtin umask "$@" please use something like true ( /bin/true in debian, /usr/bin/true in fedora )
Moving to Milan since he's porting vdsm to Debian
Moving from 4.0 alpha to 4.0 beta since 4.0 alpha has been already released and bug is not ON_QA.
oVirt 4.0 beta has been released, moving to RC milestone.
I don't think anybody cares about using Debian hosts anymore and I've abandoned my Debian work for that reason long time ago. So I suggest closing this bug as WONTFIX.