Hide Forgot
Description of problem: example: - run 'make rpm' on machine where qemu-img resides in '/usr/local/bin/qemu-img' - install vdsm rpm on Fedora host where qemu-img resides in '/usr/bin/qemu-img' - vi /usr/share/vdsm/constants.py - EXT_QEMUIMG = '/usr/local/bin/qemu-img' - createVolume will fail as vdsm uses the wrong PATH. desired behavior: - ignore build machine binary location, and use configuration.
The following patch should resolve this bug: http://gerrit.ovirt.org/#change,1114 Thanks Douglas
(In reply to comment #0) > Description of problem: > > example: > > - run 'make rpm' on machine where qemu-img resides in '/usr/local/bin/qemu-img' > - install vdsm rpm on Fedora host where qemu-img resides in '/usr/bin/qemu-img' > - vi /usr/share/vdsm/constants.py - EXT_QEMUIMG = '/usr/local/bin/qemu-img' > - createVolume will fail as vdsm uses the wrong PATH. > > desired behavior: > > - ignore build machine binary location, and use configuration. The build machine must be a clean environment of the target platform. Eventually you can avoid this behavior by setting the PATH: $ ./autogen.sh --system | grep qemu-img checking for qemu-img... /usr/local/bin/qemu-img $ PATH=/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sbin \ ./autogen.sh --system | grep qemu-img checking for qemu-img... /usr/bin/qemu-img
Hi Federico, I totally agree with your comment but please consider my reply comments at gerrit. I will let Dan/you decides which approach to take with this BZ (NOTABUG or apply the patch). http://gerrit.ovirt.org/#patch,sidebyside,1114,2,/COMMIT_MSG Thanks Douglas
The build machine must be a clean environment of the target platform.