yahoo-eng-team team mailing list archive

[Rushi Agrawal <rushi.agr@xxxxxxxxx>]

Public bug reported:

Host machine: Ubuntu desktop 13.10
Setup: devstack

When I try to attach a volume to an instance via the CLI, the volume
doesn't get attached. It's status still shows 'available'. While the
logs tell that 'device /dev/vdx is busy'. Here are the logs from screen
http://paste.openstack.org/show/54808/

I looked into /var/log/libvirt/libvirtd.log and found this:
http://paste.openstack.org/show/54809/

As per this guy's question at ask.openstack.org,
https://ask.openstack.org/en/question/7128/deviceisbusy-the-supplied-device-vdx-is-busy/
I uninstalled apparmor, and restarted and tried again. EVERYTHING went smooth! Looks like some issue with apparmor conflicting with libvirt.

** Affects: nova
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1259860

Title:
  Apparmor doesn't allow volume to attach in 13.10 Ubuntu

Status in OpenStack Compute (Nova):
  New

Bug description:
  Host machine: Ubuntu desktop 13.10
  Setup: devstack

  When I try to attach a volume to an instance via the CLI, the volume
  doesn't get attached. It's status still shows 'available'. While the
  logs tell that 'device /dev/vdx is busy'. Here are the logs from
  screen http://paste.openstack.org/show/54808/

  I looked into /var/log/libvirt/libvirtd.log and found this:
  http://paste.openstack.org/show/54809/

  As per this guy's question at ask.openstack.org,
  https://ask.openstack.org/en/question/7128/deviceisbusy-the-supplied-device-vdx-is-busy/
  I uninstalled apparmor, and restarted and tried again. EVERYTHING went smooth! Looks like some issue with apparmor conflicting with libvirt.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1259860/+subscriptions