[Expired for nova (Ubuntu) because there has been no activity for 60
days.]
** Changed in: nova (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1732087
Tit
This smells like something I saw under bug 1495895; my hunch is that
apparmor is block access to the second disk for the instance but its a
bit hard to say right now; please could you look in /var/log/kern.log
for any DENIED type messages from apparmor for the qemu processes.
** Changed in: nova (
(just as an aside - /openstack/venvs/nova-16.0.3 indicates you're not
using the Ubuntu supplied debs for OpenStack - did you mean to raise
this against the nova project itself?)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
OCATA AND PIKE deploy on the same environment.
OCATA, can attach
# qemu-img --version
qemu-img version 2.8.0(Debian 1:2.8+dfsg-3ubuntu2.5~cloud0)
Copyright (c) 2003-2016 Fabrice Bellard and the QEMU Project developers
# virsh --version
2.5.0
PIKE, can not attach.
QEMU 2.10.1
virsh 3.6.0
--
You
NFS,
Failed to attach volume at mountpoint: /dev/vdb: libvirtError: internal
error: unable to execute QEMU command 'device_add': Property 'virtio-
blk-device.drive' can't find value 'drive-virtio-disk1'
2017-11-14 22:00:07.790 68261 ERROR nova.virt.libvirt.driver [instance:
c1018f47-437e-4b04-bc
Openstack pike stable.
QEMU 2.10.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1732087
Title:
Can not attach a volume to a instance
To manage notifications about this bug go to:
https://bugs.laun
