Ask Your Question
0

unable to launch instance from boot from image and create new volume.

asked 2014-05-13 03:15:31 -0500

Deeptanshu gravatar image

Hi,

We have stored default glance images path on Swift storage. Images are working fine at swift. We are able to create instances from " boot from image" option . When we are using "boot from images and create an new volume " option , instance end up with the error state. We have tried to launch instance from RAW and QCOW2 format, but both images are throwing error. We are able to create the volumes on block storage without any error.

Do we require any modification for launching the instance from "boot from image and create new volume" when glance images are residing on swift storage?

Please check the logs below and suggest any solution.

/var/log/nova/nova-scheduler.log

2014-05-13 12:46:49.394 15939 INFO nova.scheduler.filter_scheduler [req-81d672d9-c9fd-49ad-94bd-0ccd8b0e9ea0 43bcaaeec0c74103aec1d3ee5b05528f c9b3b746c0c2459b9c81145023cfe6a4] Attempting to build 1 instance(s) uuids: [u'01ea9a8b-f861-4c12-9bba-42f3b9c7f67a'] 2014-05-13 12:46:49.410 15939 INFO nova.scheduler.filter_scheduler [req-81d672d9-c9fd-49ad-94bd-0ccd8b0e9ea0 43bcaaeec0c74103aec1d3ee5b05528f c9b3b746c0c2459b9c81145023cfe6a4] Choosing host WeighedHost [host: compute, weight: 6693.0] for instance 01ea9a8b-f861-4c12-9bba-42f3b9c7f67a 2014-05-13 12:47:26.384 15939 INFO nova.scheduler.filter_scheduler [req-81d672d9-c9fd-49ad-94bd-0ccd8b0e9ea0 43bcaaeec0c74103aec1d3ee5b05528f c9b3b746c0c2459b9c81145023cfe6a4] Attempting to build 1 instance(s) uuids: [u'01ea9a8b-f861-4c12-9bba-42f3b9c7f67a'] 2014-05-13 12:47:26.386 15939 ERROR nova.scheduler.filter_scheduler [req-81d672d9-c9fd-49ad-94bd-0ccd8b0e9ea0 43bcaaeec0c74103aec1d3ee5b05528f c9b3b746c0c2459b9c81145023cfe6a4] [instance: 01ea9a8b-f861-4c12-9bba-42f3b9c7f67a] Error from last host: compute (node compute.znetcloud.com ): [u'Traceback (most recent call last):\n', u' File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 1043, in _build_instance\n set_access_ip=set_access_ip)\n', u' File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 1426, in _spawn\n LOG.exception(_(\'Instance failed to spawn\'), instance=instance)\n', u' File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 1423, in _spawn\n block_device_info)\n', u' File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 2088, in spawn\n write_to_disk=True)\n', u' File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 3084, in to_xml\n disk_info, rescue, block_device_info)\n', u' File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 2960, in get_guest_config\n inst_type):\n', u' File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 2777, in get_guest_storage_config\n info)\n', u' File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 1042, in volume_driver_method\n return method(connection_info, args, *kwargs)\n', u' File "/usr/lib/python2.7/dist-packages/nova/openstack/common/lockutils.py", line 246, in inner\n return f(args, *kwargs)\n', u' File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/volume.py", line 285, in connect_volume\n self._run_iscsiadm(iscsi_properties, ("--rescan",))\n', u' File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/volume.py", line 218, in _run_iscsiadm\n check_exit_code=check_exit_code)\n', u' File "/usr/lib/python2.7/dist-packages/nova/utils.py", line 177, in execute\n return processutils.execute(cmd, *kwargs)\n', u' File "/usr/lib/python2.7/dist-packages/nova/openstack/common/processutils.py", line 178, in execute\n cmd=\' \'.join(cmd))\n', u"ProcessExecutionError: Unexpected error while running command.\nCommand: sudo nova-rootwrap /etc/nova/rootwrap ... (more)

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted
0

answered 2014-05-13 03:35:36 -0500

dbaxps gravatar image

updated 2014-05-13 03:42:08 -0500

View https://bugs.launchpad.net/nova/+bug/...
Escalated to https://blueprints.launchpad.net/nova...

It's known Bug for Havana, even for simple glance image. Creating cinder volume at bootup via image doesn't
 work for me in Havana.
edit flag offensive delete link more

Comments

Hi,

We are able to create instance when glance images are residing on the controller from " boot from image and create new volume. When we stored images on swift and use the given option it is throwing error. We have configure both cinder and swift storage on the same storage machine.

Deeptanshu gravatar imageDeeptanshu ( 2014-05-13 03:56:57 -0500 )edit

As per the suggested bug storage backend is not slow. We have both the Swift and glance on the same machine.

Deeptanshu gravatar imageDeeptanshu ( 2014-05-13 04:00:31 -0500 )edit

Hi,

This is resolved in Icehouse. We have upgraded to icehouse.

Deeptanshu gravatar imageDeeptanshu ( 2014-05-29 21:19:12 -0500 )edit

I know. I've already setup IceHouse via packstack on F20 boxes Neutron OVS&VLAN.

dbaxps gravatar imagedbaxps ( 2014-05-29 21:36:18 -0500 )edit

HI,

Is it possible to create instance from now RAW images when using " boot from image and create new volume" ?

Deeptanshu gravatar imageDeeptanshu ( 2014-05-29 21:39:59 -0500 )edit

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: 2014-05-13 03:15:31 -0500

Seen: 793 times

Last updated: May 13 '14