nova boot keeps in spawning [closed]

asked 2014-09-18 20:49:41 -0600

sowrdking gravatar image

Hi all,

My OS is CentOS7 and use nova network type. I can't boot my instance and the state keeps in spawning.

| ID                                   | Name           | Status | Task State | Power State | Networks |
| c801f8eb-c8a9-477f-9415-0012685e86e1 | admin-instance | BUILD  | spawning   | NOSTATE     |          |

I check the log in controller and compute, there are no error message. The compute node have log in nova-compute.log like this, WARNING nova.compute.manager [-] Found 1 in the database and 0 on the hypervisor.

Do anyone have an idea about this situation? P.S Will IP conflict cause this issue?

edit retag flag offensive reopen merge delete

Closed for the following reason question is not relevant or outdated by sowrdking
close date 2014-10-01 04:38:58.711667


I guess the log level is higher than DEBUG. I would suggest you enable debug logs for nova (debug=True in nova.conf) and restart the nova-compute service. The compute logs should give you a clue. Which hypervisor is configured? Query the hypervisor (eg. 'virsh list' if qemu/kvm) to confirm things.

unmesh-gurjar gravatar imageunmesh-gurjar ( 2014-09-19 01:17:01 -0600 )edit

1 answer

Sort by ยป oldest newest most voted

answered 2014-09-19 01:47:33 -0600

sowrdking gravatar image

updated 2014-09-19 04:41:26 -0600


I found out that the reason is because nova-manage cannot find my device "eth1", which I use it as a external interface. I did the steps the guide shows, but the eth1 isn't recognize by the system. I also use "ip a | grep state" , eth1 state isn't up and br100 is not bind.

If I bind br100 to my active interface eno1, br100 state is up. But then I cannot ping to controller or other website. So, is there steps missing when I create external interface "eth1"? I only add a copy of eno1 in /etc/sysconfig/network-scripts/ifcfg-eno1 to ifcfg-eth1 and modify the content.

Update================= I try to boot another instance and here is the compute log I found may be the root cause.

2014-09-19 05:29:24.212 4972 DEBUG nova.virt.disk.vfs.guestfs [req-55fa24cf-163d-47b5-a90b-92264dab990c 160c9c6f2bb44e41836462d78d53ace0 587a337af7884dd69b2a7d77eb68e572] Tearing down appliance teardown /usr/lib/python2.7/site-packages/nova/virt/disk/vfs/ 2014-09-19 05:29:24.214 4972 WARNING nova.virt.disk.vfs.guestfs [req-55fa24cf-163d-47b5-a90b-92264dab990c 160c9c6f2bb44e41836462d78d53ace0 587a337af7884dd69b2a7d77eb68e572] Failed to close augeas aug_close: do_aug_close: you must call 'aug-init' first to initialize Augeas 2014-09-19 05:29:24.249 4972 DEBUG nova.virt.disk.api [req-55fa24cf-163d-47b5-a90b-92264dab990c 160c9c6f2bb44e41836462d78d53ace0 587a337af7884dd69b2a7d77eb68e572] Unable to mount image /var/lib/nova/instances/63ed8a3b-d11f-46ca-8a5d-cf8ad1a54c94/disk with error Error mounting /var/lib/nova/instances/63ed8a3b-d11f-46ca-8a5d-cf8ad1a54c94/disk with libguestfs (mount_options: /dev/sda on / (options: ''): mount: /dev/sda is write-protected, mounting read-only mount: unknown filesystem type '(null)'). Cannot resize. is_image_partitionless /usr/lib/python2.7/site-packages/nova/virt/disk/ 2014-09-19 05:29:24.249 4972 DEBUG nova.openstack.common.lockutils [req-55fa24cf-163d-47b5-a90b-92264dab990c 160c9c6f2bb44e41836462d78d53ace0 587a337af7884dd69b2a7d77eb68e572] Released file lock "e56d642d025882a2734f5d19747f23205f5c0cc8" at /var/lib/nova/instances/locks/nova-e56d642d025882a2734f5d19747f23205f5c0cc8 lock /usr/lib/python2.7/site-packages/nova/openstack/common/

Any solution??

edit flag offensive delete link more

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2014-09-18 20:49:41 -0600

Seen: 1,076 times

Last updated: Sep 19 '14