On Wed, Oct 09, 2013 at 04:45:22PM +0100, Dan Kenigsberg wrote:
On Wed, Oct 09, 2013 at 11:15:41AM -0400, Mike Burns wrote:
Minutes: http://ovirt.org/meetings/ovirt/2013/ovirt.2013-10-09-14.06.html Minutes (text): http://ovirt.org/meetings/ovirt/2013/ovirt.2013-10-09-14.06.txt Log: http://ovirt.org/meetings/ovirt/2013/ovirt.2013-10-09-14.06.log.html
========================= #ovirt: oVirt Weekly sync =========================
Meeting started by mburns at 14:06:41 UTC. The full logs are available at http://ovirt.org/meetings/ovirt/2013/ovirt.2013-10-09-14.06.log.html .
Meeting summary --------------- * agenda and roll call (mburns, 14:07:00) * 3.3 updates (mburns, 14:07:17) * 3.4 planning (mburns, 14:07:24) * conferences and workshops (mburns, 14:07:31) * infra update (mburns, 14:07:34)
* 3.3 updates (mburns, 14:08:42) * 3.3.0.1 vdsm packages are posted to updates-testing (mburns, 14:09:04) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1009100 (sbonazzo, 14:10:33) * 2 open bugs blocking 3.3.0.1 (mburns, 14:29:35) * 1 is deferred due to qemu-kvm feature set in el6 (mburns, 14:29:49) * other is allowed versions for vdsm (mburns, 14:30:01) * vdsm version bug will be backported to 3.3.0.1 today (mburns, 14:30:13) * ACTION: sbonazzo to build engine 3.3.0.1 tomorrow (mburns, 14:30:22) * ACTION: mburns to post 3.3.0.1 to ovirt.org tomorrow (mburns, 14:30:32) * expected release: next week (mburns, 14:30:46) * ACTION: danken and sbonazzo to provide release notes for 3.3.0.1 (mburns, 14:37:56)
""" A vdsm bug (BZ#1007980) made it impossible to migrate or re-run a VM with a glusterfs-backed virtual disk if the VM was originally started with an empty cdrom.
If you have encountered this bug, you would have to manually find the affected VMs with
psql -U engine -d engine -c "select distinct vm_name from vm_static, vm_device where vm_guid=vm_id and device='cdrom' and address ilike '%pci%';"
and remove their junk cdrom address with
psql -U engine -d engine -c "update vm_device set address='' where device='cdrom' and address ilike '%pci%';" """
Apparently, another bug is hampering VM migration on ovirt/gluster Bug 987555 - Glusterfs ports conflict with qemu live migration Could gluster choose a disjoint range of ports?