Ask Your Question
0

unable to launch instance in openstack getting error

asked 2015-07-04 06:29:03 -0500

ravindert gravatar image

updated 2015-07-06 12:54:40 -0500

sunnyarora gravatar image

Hi ,

I am getting the below error when launching the instance so please help me to fix this issue.

Error: Failed to launch instance “vm1″: Please try again later [Error: Build of instance f1e9ec07-b945-4013-be9d-efa7e30ed8fa aborted: Failure prepping block device.].

Error logs captured from nova-compute.log.

2015-06-28 11:47:30.756 11380 TRACE nova.compute.manager [instance: e08e0496-1393-460a-aa6e-009c8f8eda15] block_device_mapping) as resources:
2015-06-28 11:47:30.756 11380 TRACE nova.compute.manager [instance: e08e0496-1393-460a-aa6e-009c8f8eda15] File “/usr/lib/python2.7/contextlib.py”, line 17, in __enter__
2015-06-28 11:47:30.756 11380 TRACE nova.compute.manager [instance: e08e0496-1393-460a-aa6e-009c8f8eda15] return self.gen.next()
2015-06-28 11:47:30.756 11380 TRACE nova.compute.manager [instance: e08e0496-1393-460a-aa6e-009c8f8eda15] File “/usr/lib/python2.7/dist-packages/nova/compute/manager.py”, line 2264, in _build_resources
2015-06-28 11:47:30.756 11380 TRACE nova.compute.manager [instance: e08e0496-1393-460a-aa6e-009c8f8eda15] reason=msg)
2015-06-28 11:47:30.756 11380 TRACE nova.compute.manager [instance: e08e0496-1393-460a-aa6e-009c8f8eda15] BuildAbortException: Build of instance e08e0496-1393-460a-aa6e-009c8f8eda15 aborted: Failure prepping block device.
2015-06-28 11:47:30.756 11380 TRACE nova.compute.manager [instance: e08e0496-1393-460a-aa6e-009c8f8eda15]
2015-06-28 11:47:30.848 11380 INFO nova.network.neutronv2.api [-] [instance: e08e0496-1393-460a-aa6e-009c8f8eda15] Unable to reset device ID for port None
2015-06-28 11:47:37.511 11380 AUDIT nova.compute.resource_tracker [-] Auditing locally available compute resources
2015-06-28 11:47:38.561 11380 AUDIT nova.compute.resource_tracker [-] Total physical ram (MB): 3952, total allocated virtual ram (MB): 1536
2015-06-28 11:47:38.566 11380 AUDIT nova.compute.resource_tracker [-] Free disk (GB): 14
2015-06-28 11:47:38.569 11380 AUDIT nova.compute.resource_tracker [-] Total usable vcpus: 2, total allocated vcpus: 0
2015-06-28 11:47:38.570 11380 AUDIT nova.compute.resource_tracker [-] PCI stats: []

2015-06-28 11:47:38.740 11380 INFO nova.scheduler.client.report [-] Compute_service record updated for (‘controller’, ‘controller’)
2015-06-28 11:47:38.741 11380 INFO nova.compute.resource_tracker [-] Compute_service record updated for controller:controller
2015-06-28 11:48:39.512 11380 AUDIT nova.compute.resource_tracker [-] Auditing locally available compute resources
2015-06-28 11:48:39.890 11380 AUDIT nova.compute.resource_tracker [-] Total physical ram (MB): 3952, total allocated virtual ram (MB): 1536
2015-06-28 11:48:39.892 11380 AUDIT nova.compute.resource_tracker [-] Free disk (GB): 14
2015-06-28 11:48:39.893 11380 AUDIT nova.compute.resource_tracker [-] Total usable vcpus: 2, total allocated vcpus: 0
2015-06-28 11:48:39.895 11380 AUDIT nova.compute.resource_tracker [-] PCI stats: []
2015-06-28 11:48:39.898 11380 INFO nova.compute.resource_tracker [-] Compute_service record updated for controller:controller

Below is the nova.conf and compute.conf configuration files.

[DEFAULT]
#dhcpbridge_flagfile=/etc/nova/nova.conf
#dhcpbridge=/usr/bin/nova-dhcpbridge
logdir=/var/log/nova
state_path=/var/lib/nova
lock_path=/var/lock/nova
force_dhcp_release=True
iscsi_helper=tgtadm
libvirt_use_virtio_for_bridges=True
verbose=True
connection_type=libvirt
ec2_private_dns_show_ip=True
api_paste_config=/etc/nova/api-paste.ini
enabled_apis=ec2,osapi_compute,metadata
#libvirt_type=qemu
#libvirt_type=qemu

root_helper=sudo nova-rootwrap /etc/nova/rootwrap.conf
verbose=True
rpc_backend = nova.rpc.impl_kombu
rabbit_host = 127.0.0.1
rabbit_password = rabbit
my_ip = 10.0.0.1
vncserver_listen = 10.0.0.1
vncserver_proxyclient_address = 10.0.0.1
novncproxy_base_url=http://10.0.0 ...
(more)
edit retag flag offensive close merge delete

1 answer

Sort by » oldest newest most voted
0

answered 2015-09-08 12:44:39 -0500

Lingeswaran gravatar image

Can you tried to launch from Volume tab ? Creating the new volume - > Action - > Launch instance ..

Regards Lingesh http://www.unixarena.com (http://www.UnixArena.com)

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2015-07-04 06:29:03 -0500

Seen: 1,283 times

Last updated: Jul 06 '15