Ask Your Question

Hokam Singh's profile - activity

2015-11-27 06:01:20 -0500 received badge  Good Question (source)
2015-10-15 14:29:42 -0500 received badge  Nice Question (source)
2015-03-09 01:15:38 -0500 received badge  Taxonomist
2014-04-24 08:43:27 -0500 received badge  Student (source)
2014-04-24 08:14:27 -0500 received badge  Famous Question (source)
2014-04-02 04:20:19 -0500 received badge  Notable Question (source)
2014-04-02 04:20:19 -0500 received badge  Famous Question (source)
2014-03-11 06:18:52 -0500 received badge  Famous Question (source)
2014-02-11 03:30:21 -0500 received badge  Popular Question (source)
2014-02-11 03:30:21 -0500 received badge  Notable Question (source)
2014-01-30 00:48:46 -0500 received badge  Enthusiast
2014-01-20 23:53:34 -0500 received badge  Popular Question (source)
2014-01-20 08:31:12 -0500 commented question Not able to launch instances. Please help

Hi Prathamesh, thanks for the response. My problem is later one. The instance launch works fine and it also goes to running state, but it takes lot of time to go in running state and second, the login to machine does not work. When i log-in to machine, it shows Read from socket failed: Connection reset by peer. Some time it also shows ssh: connect to host 10.0.0.3 port 22: No route to host.

2014-01-20 08:06:33 -0500 received badge  Notable Question (source)
2014-01-20 00:55:47 -0500 received badge  Popular Question (source)
2014-01-19 04:35:12 -0500 commented answer Keypair creation is failing

Hi, Thanks for the response. I am getting below output for the ssh-keygen -q -l -f id_rsa.pub command: 2048 06:0a:12:6f:92:2c:09:ca:6f:d0:17:9b:5d:eb:ab:fd id_rsa.pub (RSA). The above command is working fine but the nova keypair-add command is failing. Please help.

2014-01-19 03:54:20 -0500 asked a question Not able to launch instances. Please help

Hi, On my CentOs6.2 system, I have installed the openstack as specified in the openstack installation guide. In my openstack system, i have one controller node and 2 compute nodes. One compute node is on controller node and other is on different node. I used nova networking for IP allocation. I have following configuration of openstack on my systems.

On my controller and 1st compute node following services run :

  • openstack-nova-api
  • openstack-nova-cert
  • openstack-nova-compute
  • openstack-nova-network
  • openstack-nova-scheduler
  • openstack-nova-conductor
  • openstack-glance-api
  • openstack-glance-registry
  • openstack-keystone
  • openstack-dashboard
  • mysqld
  • libvirtd
  • messagebus
  • qpidd
  • memcached

And on 2nd compute node following services run :

  • openstack-nova-compute
  • openstack-nova-metadata-api
  • openstack-nova-network
  • libvirtd
  • messagebus
  • qpidd
  • memcached

Using the above configuration, when i launch the instance for "cirros" image then the instance run successfully and login to instances also works fine. And when i launch instances for the other images(some downloaded from the openstack site and some created via the virtual box VMDK, VDI and VHD files), then it shows the instance in running state but login to instance fails. For "CentOS" images, some times the console hangs on the green loading screen and does not ask for login credentials and some time it shows the following error messages.

udevd[490]: worker [514] unexpectedly returned with status 0x0100
udevd[490]: worker [514] failed while handling '/devices/LNXSYSTM:00/LNXPWRBN:00/input/input0'
udevd[490]: worker [516] unexpectedly returned with status 0x0100
udevd[490]: worker [516] failed while handling '/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:00'
udevd[490]: worker [524] unexpectedly returned with status 0x0100
udevd[490]: worker [524] failed while handling '/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:01'

And for "Ubuntu" images, console show the logs for more than 40 minutes and after that it shows the login screen.

I am unable to launch instances for CentOS and Ubuntu images using the above configuration. If anybody faced such issue then please assist me to fix it.

2014-01-18 09:54:20 -0500 asked a question Instance failed to spawn : "qemu-img: could not open...."

On my system instance launch for cirros image(specified in the deployment guide) is successfully working. But when i am launching the instance using vmdk image(created via virtual box), then instance is failing while spawning with below error.

2014-01-18 20:44:24.719 4416 ERROR nova.compute.manager [req-84ff997d-3d40-48d5-b2d9-d0dda580ae39 ff1e1cb9c1104fc9867f47fc7abfd99b cb0927687433462c807ba29e446b2972] [instance: 4a519faa-a6c6-46c5-962f-637989c227cc] **Instance failed to spawn**<br>
2014-01-18 20:44:24.719 4416 TRACE nova.compute.manager [instance: 4a519faa-a6c6-46c5-962f-637989c227cc] Traceback (most recent call last):<br>
2014-01-18 20:44:24.719 4416 TRACE nova.compute.manager [instance: 4a519faa-a6c6-46c5-962f-637989c227cc]   File "/usr/lib/python2.6/site-packages/nova/compute/manager.py", line 1417, in _spawn<br>
2014-01-18 20:44:24.719 4416 TRACE nova.compute.manager [instance: 4a519faa-a6c6-46c5-962f-637989c227cc]     block_device_info)<br>
2014-01-18 20:44:24.719 4416 TRACE nova.compute.manager [instance: 4a519faa-a6c6-46c5-962f-637989c227cc]   File "/usr/lib/python2.6/site-packages/nova/virt/libvirt/driver.py", line 2059, in spawn<br>
2014-01-18 20:44:24.719 4416 TRACE nova.compute.manager [instance: 4a519faa-a6c6-46c5-962f-637989c227cc]     admin_pass=admin_password)<br>
2014-01-18 20:44:24.719 4416 TRACE nova.compute.manager [instance: 4a519faa-a6c6-46c5-962f-637989c227cc]   File "/usr/lib/python2.6/site-packages/nova/virt/libvirt/driver.py", line 2364, in _create_image<br>
2014-01-18 20:44:24.719 4416 TRACE nova.compute.manager [instance: 4a519faa-a6c6-46c5-962f-637989c227cc]     project_id=instance['project_id'])<br>
2014-01-18 20:44:24.719 4416 TRACE nova.compute.manager [instance: 4a519faa-a6c6-46c5-962f-637989c227cc]   File "/usr/lib/python2.6/site-packages/nova/virt/libvirt/imagebackend.py", line 174, in cache<br>
2014-01-18 20:44:24.719 4416 TRACE nova.compute.manager [instance: 4a519faa-a6c6-46c5-962f-637989c227cc]     *args, *kwargs)<br>
2014-01-18 20:44:24.719 4416 TRACE nova.compute.manager [instance: 4a519faa-a6c6-46c5-962f-637989c227cc]   File "/usr/lib/python2.6/site-packages/nova/virt/libvirt/imagebackend.py", line 291, in create_image<br>
2014-01-18 20:44:24.719 4416 TRACE nova.compute.manager [instance: 4a519faa-a6c6-46c5-962f-637989c227cc]     prepare_template(target=base, max_size=size, *args, *kwargs)<br>
2014-01-18 20:44:24.719 4416 TRACE nova.compute.manager [instance: 4a519faa-a6c6-46c5-962f-637989c227cc]   File "/usr/lib/python2.6/site-packages/nova/openstack/common/lockutils.py", line 246, in inner<br>
2014-01-18 20:44:24.719 4416 TRACE nova.compute.manager [instance: 4a519faa-a6c6-46c5-962f-637989c227cc]     return f(*args, *kwargs)<br>
2014-01-18 20:44:24.719 4416 TRACE nova.compute.manager [instance: 4a519faa-a6c6-46c5-962f-637989c227cc]   File "/usr/lib/python2.6/site-packages/nova/virt/libvirt/imagebackend.py", line 162, in call_if_not_exists<br>
2014-01-18 20:44:24.719 4416 TRACE nova.compute.manager [instance: 4a519faa-a6c6-46c5-962f-637989c227cc]     fetch_func(target=target, *args, *kwargs)<br>
2014-01-18 20:44:24.719 4416 TRACE nova.compute.manager [instance: 4a519faa-a6c6-46c5-962f-637989c227cc]   File "/usr/lib/python2.6/site-packages/nova/virt/libvirt/utils.py", line 618, in fetch_image<br>
2014-01-18 20:44:24.719 4416 TRACE nova.compute.manager [instance: 4a519faa-a6c6-46c5-962f-637989c227cc]     max_size=max_size)<br>
2014-01-18 20:44:24.719 4416 TRACE nova.compute.manager [instance: 4a519faa-a6c6-46c5-962f-637989c227cc]   File "/usr/lib/python2.6/site-packages/nova/virt/images.py", line 199, in fetch_to_raw<br>
2014-01-18 20:44:24.719 4416 TRACE nova.compute.manager [instance: 4a519faa-a6c6-46c5-962f-637989c227cc]     data = qemu_img_info(path_tmp)<br>
2014-01-18 20:44:24.719 4416 TRACE nova.compute.manager [instance: 4a519faa-a6c6-46c5-962f-637989c227cc]   File "/usr/lib/python2.6/site-packages/nova/virt/images.py", line 172, in qemu_img_info<br ...
(more)
2014-01-18 09:26:19 -0500 received badge  Organizer (source)
2014-01-18 01:00:39 -0500 received badge  Editor (source)
2014-01-17 23:55:19 -0500 asked a question Keypair creation is failing

As per the openstack deployment guide, i followed the below instructions to create keypair but it is failing.

$ ssh-keygen
$ cd .ssh
$ nova keypair-add --pub_key id_rsa.pub mykey

As i am running the last command to add keypair, it is failing with below error :
ERROR: Keypair data is invalid: failed to generate fingerprint (HTTP 400) (Request-ID: req-8926bb92-34f0-47b7-9f3a-b2012796383b)

How can i resolve the issue?

Any help will be appreciated. Thanks in advance.