make ovs-vsctl not raise error if there's no portData available.

The attachment "Trusty Patch" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.]

Hello Jorge, or anyone else affected,

Accepted libvirt into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libvirt/1.2.2-0ubuntu13.1.17 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

These are the steps that I followed for verification:

1) I created 2 virtual machines

$ uvt-kvm create trusty
$ uvt-kvm create trusty2

2) On the primary (trusty) I created a machine called test

$ uvt-kvm create test

3) Installed openvswitch

$ sudo apt-get install openvswitch-switch

4) Created a new openvswitch bridge

$ sudo brctl addbr br0
$ sudo ovs-vsctl add-br br0
$ sudo ifconfig br0 up

5) Edited the network

$ virsh destroy test
$ virsh edit test

    <interface type='bridge'>
      <mac address='52:54:00:66:99:7b'/>
      <source bridge='br0'/>
      <virtualport type='openvswitch'>
        <parameters interfaceid='74178f6a-14bc-45d0-a54c-11aa8b907622'/>
      </virtualport>
      <model type='rtl8139'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/>
    </interface>

6) Start the domain

$ virsh start test

7) Migrate between both systems:

$ virsh migrate --live --p2p --persistent --abort-on-error trusty qemu+ssh://ubuntu@192.168.122.110/system

At this point the migration completes correctly, without the virCommandWait:2423 exception.

verification-done

This bug was fixed in the package libvirt - 1.2.2-0ubuntu13.1.17

---------------
libvirt (1.2.2-0ubuntu13.1.17) trusty; urgency=medium

  * d/p/fix-util-don-t-fail-if-no-portdata-is-found.patch:
    make ovs-vsctl not raise error if there's no portData available.
    (LP: #1540537).

 -- Jorge Niedbalski <email address hidden> Thu, 04 Feb 2016 16:58:31 +0100

The verification of the Stable Release Update for libvirt has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.