Open Stack

Juan,

If you look at the stack trace:

32cb3ae0-20d7-4f6d-bdff-c040976e4a80] Injecting key into image
c8704b4a-5e04-4134-9d75-cf2289c94bb0


The next thing that runs:

2013-05-16 18:27:35.512 INFO nova.virt.disk.mount.nbd
[req-729ca77e-3963-4af9-a06d-f5b7f10221c7 522c7d49af3141948d6d7ba89e3601f4
d1a1563eb7604307bc385817ab0adccf] NBD mount error: qemu-nbd error:
Unexpected error while running command.
Command: sudo nova-rootwrap /etc/nova/rootwrap.conf qemu-nbd -c /dev/nbd6
/var/lib/nova/instances/32cb3ae0-20d7-4f6d-bdff-c040976e4a80/disk
Exit code: 1
Stdout: ''
Stderr: "qemu-nbd: Failed to bdrv_open
'/var/lib/nova/instances/32cb3ae0-20d7-4f6d-bdff-c040976e4a80/disk': No
such file or directory\n"

Go ahead and try what Rafi is advising, it _should_ fix your problem as it
effectively disables file injections.

-Mike Wilson




On Mon, Jun 3, 2013 at 2:51 PM, Juan José Pavlik Salles
<jjpavlik at gmail.com>wrote:

> Sorry Rafi, but i can't see how you relate this problem with file
> injection. From my point of view it seems that nova is trynig to boot from
> a file image when the image is on a cinder volume. Maybe you are seeing
> something i don't, what do you think?
>
>
> 2013/6/3 Rafi Khardalian <rafi at metacloud.com>
>
>> I checked the code path for file injection and I can't see any way it
>> would ever work when booting from a volume.  Please open a bug about this.
>>  To work around the issue, you can disable file injection entirely by
>> adding the following to nova.conf on your compute nodes:
>>
>>     libvirt_inject_partition = -2
>>
>> My personal recommendation is never to use file injection and rely on
>> guest-level configuration tools such as cloud-init to perform equivalent
>> functions.  Nonetheless, as long as file injection officially exists as a
>> Nova feature, this is a valid bug.
>>
>> Rafi
>>
>>
>> On Thu, May 16, 2013 at 11:38 AM, Juan José Pavlik Salles <
>> jjpavlik at gmail.com> wrote:
>>
>>> Hi guys, i ran into a problem trying to boot from a volume in my grizzly
>>> deployment. I've created a 10Gbytes volume but when i try to boot my ubuntu
>>> image it doesn't work. In nova-compu.log i found:
>>>
>>> 2013-05-16 18:27:33.181 AUDIT nova.compute.manager
>>> [req-729ca77e-3963-4af9-a06d-f5b7f10221c7 522c7d49af3141948d6d7ba89e3601f4
>>> d1a1563eb7604307bc385817ab0adccf] [instance:
>>> 32cb3ae0-20d7-4f6d-bdff-c040976e4a80] Booting with volume
>>> d8773ff1-52a7-421e-bac8-102f0c0eb69d at vda
>>> 2013-05-16 18:27:35.457 INFO nova.virt.libvirt.driver
>>> [req-729ca77e-3963-4af9-a06d-f5b7f10221c7 522c7d49af3141948d6d7ba89e3601f4
>>> d1a1563eb7604307bc385817ab0adccf] [instance:
>>> 32cb3ae0-20d7-4f6d-bdff-c040976e4a80] Creating image
>>> 2013-05-16 18:27:35.458 INFO nova.virt.libvirt.driver
>>> [req-729ca77e-3963-4af9-a06d-f5b7f10221c7 522c7d49af3141948d6d7ba89e3601f4
>>> d1a1563eb7604307bc385817ab0adccf] [instance:
>>> 32cb3ae0-20d7-4f6d-bdff-c040976e4a80] Injecting key into image
>>> c8704b4a-5e04-4134-9d75-cf2289c94bb0
>>> 2013-05-16 18:27:35.512 INFO nova.virt.disk.mount.nbd
>>> [req-729ca77e-3963-4af9-a06d-f5b7f10221c7 522c7d49af3141948d6d7ba89e3601f4
>>> d1a1563eb7604307bc385817ab0adccf] NBD mount error: qemu-nbd error:
>>> Unexpected error while running command.
>>> Command: sudo nova-rootwrap /etc/nova/rootwrap.conf qemu-nbd -c
>>> /dev/nbd6 /var/lib/nova/instances/32cb3ae0-20d7-4f6d-bdff-c040976e4a80/disk
>>> Exit code: 1
>>> Stdout: ''
>>> Stderr: "qemu-nbd: Failed to bdrv_open
>>> '/var/lib/nova/instances/32cb3ae0-20d7-4f6d-bdff-c040976e4a80/disk': No
>>> such file or directory\n"
>>> 2013-05-16 18:27:35.512 INFO nova.virt.disk.mount.api
>>> [req-729ca77e-3963-4af9-a06d-f5b7f10221c7 522c7d49af3141948d6d7ba89e3601f4
>>> d1a1563eb7604307bc385817ab0adccf] Device allocation failed. Will retry in 2
>>> seconds.
>>> 2013-05-16 18:27:37.567 INFO nova.virt.disk.mount.nbd
>>> [req-729ca77e-3963-4af9-a06d-f5b7f10221c7 522c7d49af3141948d6d7ba89e3601f4
>>> d1a1563eb7604307bc385817ab0adccf] NBD mount error: qemu-nbd error:
>>> Unexpected error while running command.
>>> Command: sudo nova-rootwrap /etc/nova/rootwrap.conf qemu-nbd -c
>>> /dev/nbd14 /var/lib/nova/instances/32cb3ae0-20d7-4f6d-bdff-c040976e4a80/disk
>>> Exit code: 1
>>> Stdout: ''
>>> Stderr: "qemu-nbd: Failed to bdrv_open
>>> '/var/lib/nova/instances/32cb3ae0-20d7-4f6d-bdff-c040976e4a80/disk': No
>>> such file or directory\n"
>>>
>>> The error actually makes sense, because the disk (the volume) is and
>>> iscsi target, not a file in the instance directory. But why does nova look
>>> for the file, instead of using the volume i choose? I can boot an ephimeral
>>> instance and attach this volume and it works, but i want to create
>>> persistent instances. Thanks!
>>>
>>>
>>> --
>>> Pavlik Salles Juan José
>>>
>>> _______________________________________________
>>> OpenStack-operators mailing list
>>> OpenStack-operators at lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>>>
>>>
>>
>
>
> --
> Pavlik Salles Juan José
>
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20130603/ea9e1a49/attachment.html>