<div dir="ltr">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?</div>
<div class="gmail_extra"><br><br><div class="gmail_quote">2013/6/3 Rafi Khardalian <span dir="ltr"><<a href="mailto:rafi@metacloud.com" target="_blank">rafi@metacloud.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div class="gmail_extra"><div>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:</div>
<div class="gmail_extra"><br></div><div class="gmail_extra"> libvirt_inject_partition = -2</div><div class="gmail_extra"><br></div><div class="gmail_extra">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.</div>
<div class="gmail_extra"><br>Rafi</div><div class="gmail_extra"><br></div><br><div class="gmail_quote"><div><div class="h5">On Thu, May 16, 2013 at 11:38 AM, Juan José Pavlik Salles <span dir="ltr"><<a href="mailto:jjpavlik@gmail.com" target="_blank">jjpavlik@gmail.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div><div class="h5"><div dir="ltr">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:<div>
<br></div><div><div>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</div>
<div>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</div>
<div>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</div>
<div>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.</div>
<div>Command: sudo nova-rootwrap /etc/nova/rootwrap.conf qemu-nbd -c /dev/nbd6 /var/lib/nova/instances/32cb3ae0-20d7-4f6d-bdff-c040976e4a80/disk</div><div>Exit code: 1</div><div>Stdout: ''</div><div>Stderr: "qemu-nbd: Failed to bdrv_open '/var/lib/nova/instances/32cb3ae0-20d7-4f6d-bdff-c040976e4a80/disk': No such file or directory\n"</div>
<div>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.</div>
<div>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.</div>
<div>Command: sudo nova-rootwrap /etc/nova/rootwrap.conf qemu-nbd -c /dev/nbd14 /var/lib/nova/instances/32cb3ae0-20d7-4f6d-bdff-c040976e4a80/disk</div><div>Exit code: 1</div><div>Stdout: ''</div><div>Stderr: "qemu-nbd: Failed to bdrv_open '/var/lib/nova/instances/32cb3ae0-20d7-4f6d-bdff-c040976e4a80/disk': No such file or directory\n"</div>
<div><br></div><div>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!</div>
<span><font color="#888888">
<div><br></div><div><div><br></div>-- <br><div dir="ltr">Pavlik Salles Juan José</div>
</div></font></span></div></div>
<br></div></div>_______________________________________________<br>
OpenStack-operators mailing list<br>
<a href="mailto:OpenStack-operators@lists.openstack.org" target="_blank">OpenStack-operators@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
<br></blockquote></div><br></div></div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr">Pavlik Salles Juan José</div>
</div>