[ovirt-devel] oVirt 4.2.0 RC3 status

[Dan Kenigsberg]

On Mon, Dec 18, 2017 at 9:16 AM, Sandro Bonazzola <sbonazzo at redhat.com>
wrote:

> Hi,
> according to https://bugzilla.redhat.com/buglist.cgi?quicksearch=
> flag%3Ablocker%2B%20target_milestone%3Aovirt-4.2.0%
> 20status%3Anew%2Cassigned%2Cpost%2Cmodified
> we just need to rebuild VDSM to complete the acknowledged blockers.
>
> We still have a proposed blocker in NEW state according to
> https://bugzilla.redhat.com/buglist.cgi?quicksearch=
> flag%3Ablocker%3F%20target_milestone%3Aovirt-4.2.0%
> 20status%3Anew%2Cassigned%2Cpost%2Cmodified
>
> 1525907 <https://bugzilla.redhat.com/show_bug.cgi?id=1525907> Storage vdsm
> General danken at redhat.com NEW VDSM is in recovery mode after a restart in
> fresh install... <https://bugzilla.redhat.com/show_bug.cgi?id=1525907>
> urgent urgent ovirt-4.2.0 Sat 18:12
>
> Dan, please review, let us know if we have to block on this or if we can
> postpone to 4.2.1.
>

I don't think it is for me to review.

The bug is very confusing and sparse in information, but it seems to claim
that self-hosted engine is not deployable. I think that it is for Simone to
reply to that claim. Is it true? When? Do you think, like Adam, that this
is a problem of host connectivity to its storage?


Yaniv Bronheim, if we don't need to block on this, please tag VDSM for
> release.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/devel/attachments/20171218/1c8c4278/attachment.html>