For the pep8 issue, as mentioned you should check pep8 --version and use 1.4.6.
If you use older version, just upgrade with python-pip
(yum install python-pip , and then `pip-install install pep8 --upgrade`)
Second, try to follow http://www.ovirt.org/Vdsm_Developers , it specifies the
repositories you need to set (which should solve and selinux-policy package you
miss) and should be the same for ovirt-3.3.
About the hostname issue, can you detail more about the issue .. I'm not
familiar with such error
There are some differences between ovirt-3.3 branch and master in the
requirements scope, each with specific reason.
you should checkout ovirt-3.3 branch and not ovirt-3.3.0 for those tests
We are working on the quality and constantly trying to increase and improve the
About the builds process you can talk with eedri for more details
----- Original Message -----
> From: "Sandro Bonazzola" <sbona...@redhat.com>
> To: "patrick hurrelmann" <patrick.hurrelm...@lobster.de>, "oVirt Mailing
> List" <us...@ovirt.org>, "vdsm-devel"
> Sent: Tuesday, November 12, 2013 12:31:04 PM
> Subject: Re: [vdsm] [Users] Low quality of el6 vdsm rpms
> Il 12/11/2013 10:34, Patrick Hurrelmann ha scritto:
> > Hi all,
> > sorry for this rant, but...
> > I now tried several times to test the beta 3.3.1 rpms, but they can't
> > even be installed in the most times.
> I'm glad to read you're testing 3.3.1. May I ask you to add yourself to
> http://www.ovirt.org/Testing/Ovirt_3.3.1_testing ?
> > One time it required a future
> > selinux-policy, although the needed selinux fix was delivered in a much
> > lower version. Now the rpms have broken requirements. It requires
> > "hostname" instead of "/bin/hostname". This broken requirement is not
> > included in the vdsm 3.3 branch, so I wonder where it comes from?
> > Anyway. So I proceeded and tried to build vdsm myself once again.
> > Currently the build fails with (but worked fine some days ago):
> > /usr/bin/pep8 --exclude="config.py,constants.py" --filename '*.py,*.py.in'
> > \
> > client lib/cpopen/*.py lib/vdsm/*.py lib/vdsm/*.py.in tests
> > vds_bootstrap vdsm-tool vdsm/*.py vdsm/*.py.in vdsm/netconf
> > vdsm/sos/vdsm.py.in vdsm/storage vdsm/vdsm vdsm_api vdsm_hooks vdsm_reg
> > vdsm/storage/imageRepository/formatConverter.py:280:29: E128
> > continuation line under-indented for visual indent
> > - How can the quality of the vdsm builds be increased? It is frustrating
> > to spend time on testing and then the hosts cannot even be installed to
> > broken vdsm rpms.
> > - How are the builds prepared? Is there a Jenkins job that prepares
> > "stable" rpms in addition to the nightly job? Or is this totally
> > handcrafted?
> > - How can it be that the rpm spec differs between the 3.3 branch and
> > released rpms? What is the source/branch for el6 vdsm rpms? Maybe I'm
> > just tracking on the wrong source tree...
> Since this is VDSM related, adding vdsm-devel list to the discussion.
> > Thx and Regards
> > Patrick
> Sandro Bonazzola
> Better technology. Faster innovation. Powered by community collaboration.
> See how it works at redhat.com
> vdsm-devel mailing list
vdsm-devel mailing list