Re: [ovirt-devel] [ovirt-users] [QE][ACTION REQUIRED] oVirt 3.5.0 RC2 status (postponed)
----- Original Message -----
From: "Barak Azulay" <bazulay(a)redhat.com>
To: "Sandro Bonazzola" <sbonazzo(a)redhat.com>
Cc: Users(a)ovirt.org, devel(a)ovirt.org
Sent: Monday, August 18, 2014 1:13:13 PM
Subject: Re: [ovirt-users] [ovirt-devel] [QE][ACTION REQUIRED] oVirt 3.5.0 RC2
status (postponed)
----- Original Message -----
> From: "Sandro Bonazzola" <sbonazzo(a)redhat.com>
> To: "Barak Azulay" <bazulay(a)redhat.com>
> Cc: Users(a)ovirt.org, devel(a)ovirt.org
> Sent: Monday, August 18, 2014 12:38:04 PM
> Subject: Re: [ovirt-devel] [QE][ACTION REQUIRED] oVirt 3.5.0 RC2 status
> (postponed)
>
> Il 18/08/2014 11:20, Barak Azulay ha scritto:
> >
> >
> > ----- Original Message -----
> >> From: "Sandro Bonazzola" <sbonazzo(a)redhat.com>
> >> To: Users(a)ovirt.org, devel(a)ovirt.org
> >> Sent: Monday, August 18, 2014 10:32:04 AM
> >> Subject: [ovirt-devel] [QE][ACTION REQUIRED] oVirt 3.5.0 RC2 status
> >> (postponed)
> >>
> >> Hi,
> >> since we have still too many blockers for oVirt 3.5.0 RC2 release,
> >> we need to postpone it again to Thu *2014-08-21 08:00 UTC*
> >>
> >> Due to this delay, the oVirt schedule has changed as follow:
> >> - General availability: 2014-09-03 (Wed)
> >> - oVirt 3.5 Third Test Day: 2014-08-28 (Thu)
> >> - RC2 Build: 2014-08-21 (Thu)
> >>
> >> Maintainers:
> >> - Please be sure that 3.5 snapshot allow to create VMs before
> >> *2014-08-20
> >> 15:00 UTC*
> >> - Please be sure that no pending patches are going to block the release
> >> before *2014-08-20 15:00 UTC*
> >> - If any patch must block the RC release please raise the issue as soon
> >> as
> >> possible.
> >>
> >> The bug tracker [1] shows the following proposed blockers to be
> >> reviewed:
> >>
> >> Bug ID Whiteboard Status Summary
> >> 1127877 infra ASSIGNED vdsm-tool configure --force does not configure
> >> qemu.conf properly in the first run on a fresh install
> >
> > The above is not a blocker,
> > Anyway we'll try to push it ASAP .. patch in discussion.
>
> Well, looks like it will cause Hosted Engine deployment failure on a clean
> system.
It depends how the hosted engine setup is implemented - I have never used it
> Not sure if it may cause also a failure adding a clean system to the
> Engine.
no it shouldn't
It should, as starting vdsm fails - this should fail in the same way as
https://bugzilla.redhat.com/1125178
I don't know if this is a regression from 3.4, maybe it was the same.
Nir