Il 21/05/2014 11:08, Sven Kieske ha scritto:
> Hi,
>
> and thanks for the list with the open bugs.
>
> Here are my proposed blockers (I won't add
> them directly without dev agreement)
> The list is not ordered in any way:
>
> Cache records in memory
>
https://bugzilla.redhat.com/show_bug.cgi?id=870330
> Status: Post
>
> ovirt-log-collector: conflicts with file from package sos >= 3.0
>
https://bugzilla.redhat.com/show_bug.cgi?id=1037663
> Status: Post
I'm working with sos maintainer for coordinating oVirt 3.4.2 release with sos 3.1.1
release fixing the issue
by moving all oVirt sos plugins to upstream sos fixing conflicts once for all.
Since a workaround exists (yum downgrade sos to 2.2-31.fc19 still available in F19) I
don't think it should be a blocker.
>
> Firmware missing
>
https://bugzilla.redhat.com/show_bug.cgi?id=1063001
> Status: Post
>
> Hot plug CPU - allow over-commit
>
https://bugzilla.redhat.com/show_bug.cgi?id=1097195
> Status: New
>
> Stucked tuned service during host deploying
>
https://bugzilla.redhat.com/show_bug.cgi?id=1069119
> Status: New
>
> Failed to reconfigure libvirt for VDSM
>
https://bugzilla.redhat.com/show_bug.cgi?id=1078309
> Status: NEW
Let's discuss this on sync meeting, not sure it's important enough for blocking
the release.
>
> [vdsm] Fix make distcheck target
>
https://bugzilla.redhat.com/show_bug.cgi?id=1098179
> Status: NEW
and this most certainly should not block a micro release. it is a
code-only change, with no functional effects.
>
> Run vm with odd number of cores drop libvirt error
>
https://bugzilla.redhat.com/show_bug.cgi?id=1070890
> Status: New