On Mar 26, 2015, at 09:36 , Francesco Romani <fromani(a)redhat.com> wrote:
----- Original Message -----
> From: "Michal Skrivanek" <mskrivan(a)redhat.com>
> To: "Francesco Romani" <fromani(a)redhat.com>
> Cc: "Sandro Bonazzola" <sbonazzo(a)redhat.com>, devel(a)ovirt.org
> Sent: Thursday, March 26, 2015 9:27:58 AM
> Subject: Re: [ovirt-devel] [URGENT][ACTION REQUIRED] please fix VDSM requirements
>> ----- Original Message -----
>>> From: "Sandro Bonazzola" <sbonazzo(a)redhat.com>
>>> To: "Christopher Pereira" <kripper(a)imatronix.cl>,
>>> "Francesco Romani" <fromani(a)redhat.com>
>>> Sent: Thursday, March 26, 2015 9:05:02 AM
>>> Subject: Re: [ovirt-devel] [URGENT][ACTION REQUIRED] please fix VDSM
>>> Il 26/03/2015 08:56, Christopher Pereira ha scritto:
>>>> On 25-03-2015 10:07, Sandro Bonazzola wrote:
>>>>> Il 25/03/2015 14:05, Christopher Pereira ha scritto:
>>>>>> Maybe you want to add some more dependencies to the nightly build
>>>>> Thanks for reporting, we're already on it.
>>>> During the "Waiting for the host to become operational in the
>>>> stage, the hosted-engine-setup fails because of the following VDSM
>>>> "VIR_MIGRATE_AUTO_CONVERGE not found in libvirt, support for
>>>> clusterLevel >= 3.6 is disabled. For Fedora 20 users, please
>>>> libvirt from the virt-preview repository"
>>>> According to , libvirt version >= 1.2.3 is required.
>>>> Any suggestion where to get this packages + dependencies for CentOS 7?
>> I need to check/start a few discussions, but most likely we'll need Centos
>> I'm not aware of any (reliable) repos like virt-preview for Centos.
>> Bottom line: for hosted engine we may need to revert the patch requiring
>> So unfortunate.
> Just get the right libvirt from anywhere in the interim period. Centos 7.1 is
> going to be released any day now
I also believe it is better (less noise to everyone) to wait few days for Centos 7.1,
which indeed should be out soon: http://seven.centos.org/2015/03/centos-7-next-release/
OTOH, I wrote the above only because Centos 7.1 is not yet released, so one must use
the RC (Release Candidate) Centos repos, and because I can't recommend any extra
which is absolutely fine, IMHO.
if someone wants to work with nightly he/she needs to know some things.
no nightly builds in any project are intended as a problem-free general-public ready
releases…especially this early in 3.6 cycle
Waiting for all the libraries to go out significantly hurts the development process.
IMO the best compromise is that CI on master needs to be ready for these things and update
to the similar (at least Beta or RC) repositories of our dependencies
RedHat Engineering Virtualization R & D