Apparmor doesn't allow volume to attach in 13.10 Ubuntu
Bug #1259860 reported by
Rushi Agrawal
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
libvirt (Ubuntu) |
Expired
|
High
|
Unassigned |
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://
I looked into /var/log/
http://
As per this guy's question at ask.openstack.org,
https:/
I uninstalled apparmor, and restarted and tried again. EVERYTHING went smooth! Looks like some issue with apparmor conflicting with libvirt.
affects: | nova → ubuntu |
affects: | ubuntu → libvirt (Ubuntu) |
Changed in libvirt (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → High |
To post a comment you must log in.
When I simply create a vm, an extra disk and some xml like
<disk type='block'>
<driver name='qemu'/>
<source dev='/tmp/x.img'/>
<target dev='vdc' bus='virtio'/>
</disk>
and do
virsh attach-device saucy /tmp/x.xml --live
then the vm definition gets the /tmp/x.img definition, and d/libvirt/ libvirt- $uuid.files has /tmp/x.img rw.
/etc/apparmor.
Can someone with a saucy or trusty nova setup please set libvirtd. conf, (then do libvirt/ libvirtd. log; start libvirt-bin) libvirt/ libvirtd. log to
log_level = 1
in /etc/libvirt/
stop libvirt-bin; rm /var/log/
and reproduce this and attach /var/log/
this bug? I'd like to see which path this takes through libvirt
when done by nova.