Ask Your Question

Instance fails to start after host is rebooted

asked 2013-12-18 16:56:17 -0500

amansuri gravatar image

updated 2013-12-19 15:16:25 -0500

Hi Folks,

When creating a new instance, I selected the option "Boot from image (creates a new volume)" as the Instance Boot Source. The instance starts up OK. Then when I reboot the openstack server and try to start the instance, it fails. It says "(not found)" under 'Image Name'

In the /var/log/nova/compute.log, it shows the following error:

TRACE nova.openstack.common.rpc.amqp OSError: [Errno 2] No such file or directory: '/var/lib/nova/instances/8e4a79dc-8eeb-4766-9c4b-0199a5ca28d4/disk'

This file does not exist on the openstack server.

I can terminate the instance, attach the volume to a new instance, it starts up OK. However, I'm trying to determine why it doesn't start up in this case.

Thanks! -Ali

edit retag flag offensive close merge delete


I don't have much experience in nova, tho in case of cinder if you have rebooted the appliance. Make sure the volume service is up and the cinder-volume is available.

ikhan gravatar imageikhan ( 2013-12-18 21:27:59 -0500 )edit

I checked and the service is running. How do I check if the cinder-volume is available?

amansuri gravatar imageamansuri ( 2013-12-19 12:56:47 -0500 )edit

service cinder-volume status also check /var/log/cinder/cinder-volume log

ikhan gravatar imageikhan ( 2013-12-19 21:05:20 -0500 )edit

1 answer

Sort by ยป oldest newest most voted

answered 2013-12-18 20:58:11 -0500

jtopjian gravatar image

updated 2013-12-19 13:03:18 -0500

I have the same issue.

Do you also see several error messages in nova-compute.log like this:

Stderr: "qemu-nbd: Failed to bdrv_open '/var/lib/nova/instances/eedb5c43-efb8-4a44-8031-0704610ea319/disk': No such file or directory\n"
2013-12-17 08:07:50.932 28514 DEBUG nova.virt.disk.vfs.localfs [req-18f4a9e2-1dfd-4ac5-8c81-be7f773d104a 9dd665490aa643aab8095ad23a1e7d31 00cb7ac024214aaf9df2f179452c8121] Failed to mount image qemu-nbd error: Unexpected error while running command.
Command: sudo nova-rootwrap /etc/nova/rootwrap.conf qemu-nbd -c /dev/nbd8 /var/lib/nova/instances/eedb5c43-efb8-4a44-8031-0704610ea319/disk
Stderr: "qemu-nbd: Failed to bdrv_open '/var/lib/nova/instances/eedb5c43-efb8-4a44-8031-0704610ea319/disk': No such file or directory\n") setup /usr/lib/python2.7/dist-packages/nova/virt/disk/vfs/
2013-12-17 08:07:50.932 28514 WARNING nova.virt.disk.api [req-18f4a9e2-1dfd-4ac5-8c81-be7f773d104a 9dd665490aa643aab8095ad23a1e7d31 00cb7ac024214aaf9df2f179452c8121] Ignoring error injecting data into image (qemu-nbd error: Unexpected error while running command.
Command: sudo nova-rootwrap /etc/nova/rootwrap.conf qemu-nbd -c /dev/nbd8 /var/lib/nova/instances/eedb5c43-efb8-4a44-8031-0704610ea319/disk
Stderr: "qemu-nbd: Failed to bdrv_open '/var/lib/nova/instances/eedb5c43-efb8-4a44-8031-0704610ea319/disk': No such file or directory\n")

when you're booting from a volume?

If so, then I think this might be related to this bug and might be fixed in 2013.2.1:

edit flag offensive delete link more


I checked the log files, but there is no error such as that. Also, attaching a volume and booting the instance works OK, but the problem is when booting an instance from an image.

amansuri gravatar imageamansuri ( 2013-12-19 12:55:34 -0500 )edit

Do you have debug=true in nova.conf? That's where you'd see the above error.

jtopjian gravatar imagejtopjian ( 2013-12-19 12:59:09 -0500 )edit

actually, the errors are in mixed categories. I edited my answer to more clearly show the errors.

jtopjian gravatar imagejtopjian ( 2013-12-19 13:02:25 -0500 )edit

I did a grep for bdrv_open and it didn't turn up any entries in the logs

amansuri gravatar imageamansuri ( 2013-12-19 16:47:27 -0500 )edit

Get to know Ask OpenStack

Resources for moderators

Question Tools


Asked: 2013-12-18 16:56:17 -0500

Seen: 1,983 times

Last updated: Dec 19 '13