[Bug 1746630] Re: virsh api is stuck when vm is down with NFS broken

Launchpad Bug Tracker 1746630 at bugs.launchpad.net
Thu Feb 15 21:47:22 UTC 2018


This bug was fixed in the package libvirt - 1.3.1-1ubuntu10.18

---------------
libvirt (1.3.1-1ubuntu10.18) xenial; urgency=medium

  * virsh api is stuck when vm is down with NFS borken (LP: #1746630)
    - d/p/0001-qemu-driver-Remove-unnecessary-flag-in-qemuDomainGet.patch
      qemu: driver: Remove unnecessary flag in qemuDomainGetStatsBlock
    - d/p/0002-qemu-driver-Separate-bulk-stats-worker-for-block-dev.patch
      qemu: driver: Separate bulk stats worker for block devices
    - d/p/0003-qemu-bulk-stats-Don-t-access-possibly-blocked-storag.patch
      qemu: bulk stats: Don't access possibly blocked storage

 -- Seyeong Kim <seyeong.kim at canonical.com>  Thu, 01 Feb 2018 09:43:45
+0900

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

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to Ubuntu Cloud Archive.
https://bugs.launchpad.net/bugs/1746630

Title:
  virsh api is stuck when vm is down with NFS broken

Status in Ubuntu Cloud Archive:
  New
Status in libvirt:
  Fix Released
Status in libvirt package in Ubuntu:
  Fix Released
Status in libvirt source package in Xenial:
  Fix Released

Bug description:
  [Impact]

  virsh command is hang if there is broken VM on broken NFS

  This is affected to Xenial, UCA-Mitaka

  [Test Case]

  1. deploy VM with NFS storage ( running )
  2. block NFS via iptables
  - iptables -A OUTPUT -d NFS_SERVER_IP -p tcp --dport 2049 -j DROP ( on host machine )
  3. virsh blkdeviotune generic hda => hang
  4. virsh domstats => hang
  5. virsh list => lang

  [Regression]
  After patch, we can command domstats and list with short timeout. and libvirt-bin needs to be restarted. so if there are many VMs it will be affected short time while it is restarting.

  [Others]

  This bug is fixed in redhat bug report[1] and mailing list[2] and git
  commit[3][4][5]

  and it is merged 1.3.5 upstream

  https://libvirt.org/git/?p=libvirt.git;a=blobdiff;f=docs/news.html.in;h=1ad8337f5f8443b5ac76450dc3370f95c51503fd;hp=d035f6833fb5eaaced8f5a7010872f3e61b6955b;hb=7324444bc70dcc3e2d1fe0baa640712efb99e273;hpb=d57e73d06fe5901ac4ab9c025b3531251292b509

  [1] https://bugzilla.redhat.com/show_bug.cgi?id=1337073
  [2] https://www.redhat.com/archives/libvir-list/2016-May/msg01353.html
  [3] https://libvirt.org/git/?p=libvirt.git;a=commit;h=5d2b0e6f12b4e57d75ed1047ab1c36443b7a54b3
  [4] https://libvirt.org/git/?p=libvirt.git;a=commit;h=3aa5d51a9530a8737ca584b393c29297dd9bbc37
  [5] https://libvirt.org/git/?p=libvirt.git;a=commit;h=71d2c172edb997bae1e883b2e1bafa97d9f953a1

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1746630/+subscriptions



More information about the Ubuntu-openstack-bugs mailing list