[Bug 1540537] Re: make ovs-vsctl not raise error if there's no portData available.

Jorge Niedbalski 1540537 at bugs.launchpad.net
Mon Feb 1 20:33:32 UTC 2016


** Changed in: libvirt (Ubuntu)
       Status: New => Fix Released

** Changed in: libvirt (Ubuntu Trusty)
       Status: New => In Progress

** Changed in: libvirt (Ubuntu Vivid)
       Status: New => In Progress

** Changed in: libvirt (Ubuntu Trusty)
     Assignee: (unassigned) => Jorge Niedbalski (niedbalski)

** Changed in: libvirt (Ubuntu Vivid)
     Assignee: (unassigned) => Jorge Niedbalski (niedbalski)

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1540537

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

Status in libvirt package in Ubuntu:
  Fix Released
Status in libvirt source package in Trusty:
  In Progress
Status in libvirt source package in Vivid:
  In Progress

Bug description:
  [Impact]

  Nova Live migration task can fail if the source host 
  doesn't have a specific port or interface available because the port have been already migrated.

  If this happens,  we need to make ovs-vsctl not raise error if there's
  no portData available.

  Example libvirtd.log:

  2:2015-12-01 17:44:34.360+0000: 3379: error : virCommandWait:2399 :
  internal error: Child process (ovs-vsctl --timeout=5 get Interface
  tape7ad3f81-dc external_ids:PortData) unexpected exit status 1: ovs-
  vsctl: no key "PortData" in Interface record "tape7ad3f81-dc" column
  external_ids

  
  [Test Case]

  The steps to reproduce the problem:

  1 define and start a domain with its network configured as:
      <interface type='bridge'>
            <source bridge='br0'/>
            <virtualport type='openvswitch'>
            </virtualport>
            <model type='virtio'/>
            <driver name='vhost' queues='4'/>
      </interface>

  2 do not set the network's portData.

  3 migrate(ToURI2) it with flag 91(1011011), which means:

    VIR_MIGRATE_LIVE
    VIR_MIGRATE_PEER2PEER
    VIR_MIGRATE_PERSIST_DEST
    VIR_MIGRATE_UNDEFINE_SOURCE
    VIR_MIGRATE_NON_SHARED_DISK

  4 migrate success, but we got an error log in libvirtd.log:
    error : virCommandWait:2423 : internal error: Child process (ovs-vsctl --timeout=5 get Interface
    vnet1 external_ids:PortData) unexpected exit status 1: ovs-vsctl: no key "PortData" in Interface
    record "vnet1" column external_ids

  [Regression Potential]

   * N/A

  [Other Info]
   
   * This upstream commit fixes the issue: https://github.com/libvirt/libvirt/commit/25df57db73adc3e610193ee1fcdd202c47ba471d

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1540537/+subscriptions



More information about the Ubuntu-sponsors mailing list