On 08/07/2013 01:42 PM, Ofer Schreiber wrote:
As you probably know, we're heading towards the 3.3 release of ovirt.
I'd like to get a short status about your project, and it's readiness for the
If your project is blocker free, please let me know of the relevant build to pick up into
the RC repo.
Current known blockers (as in https://bugzilla.redhat.com/show_bug.cgi?id=918494
Tracker: oVirt 3.3 release):
984586 ovirt-engine-backend infra Cannot start a VM with USB Native - Exit
message: internal error Could not format channel target type.
988299 ovirt-engine-core gluster Impossible to start VM from Gluster Storage
There's an issue with running this on CentOS 6.4 as there is no qemu 1.3
available for this distro.
Deepak (deepakcs) has initiated a conversation asking for inputs on how
to handle this dependency. We could take a call based on the resolution.
987939 ovirt-engine-installer integration engine-setup ->
engine-cleanup -> engine-setup -> fails
988004 vdsm network [vdsm] OSError: [Errno 2] No such file or
988065 vdsm virt Migration fails - AttributeError:
'ConsoleDevice' object has no attribute 'alias'
988397 vdsm network ovirt-node post-installation setup networks fails
when NetworkManager is running
988990 vdsm network oVirt 3.3 - (vdsm-network): netinfo - ValueError:
unknown bridge ens3
990854 vdsm network Multiple Gateways: Upgrade VDSM to 3.3 must
reconfigure networking on host
990963 vdsm vdsm must require selinux-policy-3.12.1-68.fc19
988986 ovirt-node libvirt network directory is not persisted
990509 selinux-policy Current selinux policy prevents running a VM
with volumes under /var/run/vdsm/storage
Engine-devel mailing list