instance not active in nova compute

Asked by amit on 2012-05-21

The output of
# nova-manage service list
2012-05-21 19:38:21 DEBUG nova.utils [req-def853c4-10ef-4df3-82a8-13b135c548dc None None] backend <module 'nova.db.sqlalchemy.api' from '/usr/lib/python2.7/dist-packages/nova/db/sqlalchemy/api.pyc'> from (pid=2696) __get_backend /usr/lib/python2.7/dist-packages/nova/utils.py:658
Binary Host Zone Status State Updated_At
nova-network oscloud1204 nova enabled :-) 2012-05-21 14:08:19
nova-cert oscloud1204 nova enabled :-) 2012-05-21 14:08:13
nova-scheduler oscloud1204 nova enabled :-) 2012-05-21 14:08:19
nova-compute oscloud1204 nova enabled XXX 2012-05-17 13:05:14
nova-volume oscloud1204 nova enabled :-) 2012-05-21 14:08:19

my /etc/nova/nova.conf is:

--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
--allow_admin_api=true
--use_deprecated_auth=false
--auth_strategy=keystone
--scheduler_driver=nova.scheduler.simple.SimpleScheduler
--s3_host=172.17.1.77
--ec2_host=172.17.1.77
--rabbit_host=172.17.1.77
--cc_host=172.17.1.77
--nova_url=http://172.17.1.77:8774/v1.1/
--routing_source_ip=172.17.1.77
--glance_api_servers=172.17.1.77:9292
--image_service=nova.image.glance.GlanceImageService
--iscsi_ip_prefix=172.17.3.
--sql_connection=mysql://novadbadmin:dieD9Mie@172.17.1.77/nova
--ec2_url=http://172.17.1.77:8773/services/Cloud
--keystone_ec2_url=http://172.17.1.77:5000/v2.0/ec2tokens
--api_paste_config=/etc/nova/api-paste.ini
--libvirt_type=kvm
--libvirt_use_virtio_for_bridges=true
--start_guests_on_host_boot=true
--resume_guests_state_on_host_boot=true
--vnc_enabled=true
--vncproxy_url=http://172.17.1.77:6080
--vnc_console_proxy_url=http://172.17.1.77:6080

# network specific settings
--network_manager=nova.network.manager.FlatDHCPManager
--public_interface=eth0
--flat_interface=eth0
--flat_network_bridge=br100
--fixed_range=172.17.3.0/24
--floating_range=172.17.1.0/24
--network_size=32
--flat_network_dhcp_start=172.17.3.100
--flat_injected=False
--force_dhcp_release
--iscsi_helper=tgtadm
--connection_type=libvirt
--root_helper=sudo nova-rootwrap
--verbose

everything was alright but when i am executing the command:

nova-manage network create private --fixed_range_v4=192.168.22.32/27 --num_networks=1 --bridge=br100 --bridge_interface=eth1 --network_size=32

it does not give any error to me.

The output of :

# nova-manage network list

id IPv4 IPv6 start address DNS1 DNS2 VlanID project uuid
2012-05-21 19:46:28 DEBUG nova.utils [req-ef062957-2b45-4c32-90a8-143ce81e9847 None None] backend <module 'nova.db.sqlalchemy.api' from '/usr/lib/python2.7/dist-packages/nova/db/sqlalchemy/api.pyc'> from (pid=2753) __get_backend /usr/lib/python2.7/dist-packages/nova/utils.py:658
1 172.17.3.96/27 None 172.17.3.98 8.8.4.4 None None None 90ebffbf-9ee4-4cbe-a0f9-b4cc1f2add61
2 10.10.0.0/27 None 10.10.0.2 8.8.4.4 None None cf1f1e55b74e4a35bfbb6fd485fb4443 9b41f204-82b5-42a4-a010-782bbfbd5626

root@oscloud1204:~# nova image-list
+--------------------------------------+-----------------------------+--------+--------+
| ID | Name | Status | Server |
+--------------------------------------+-----------------------------+--------+--------+
| b5145242-4904-4521-b0b0-4065bec67a24 | Ubuntu 11.10 cloudimg amd64 | ACTIVE | |
+--------------------------------------+-----------------------------+--------+--------+

root@oscloud1204:~# nova boot --flavor 1 --image b5145242-4904-4521-b0b0-4065bec67a24 --key_name key1 superfrobnicator
+-------------------------------------+--------------------------------------+
| Property | Value |
+-------------------------------------+--------------------------------------+
| OS-DCF:diskConfig | MANUAL |
| OS-EXT-SRV-ATTR:host | None |
| OS-EXT-SRV-ATTR:hypervisor_hostname | None |
| OS-EXT-SRV-ATTR:instance_name | instance-00000017 |
| OS-EXT-STS:power_state | 0 |
| OS-EXT-STS:task_state | scheduling |
| OS-EXT-STS:vm_state | error |
| accessIPv4 | |
| accessIPv6 | |
| adminPass | nhyaYJoDC2PM |
| config_drive | |
| created | 2012-05-21T14:33:16Z |
| flavor | m1.tiny |
| hostId | |
| id | 94efb18a-3063-40a2-b2af-9cd1beb5a4a4 |
| image | Ubuntu 11.10 cloudimg amd64 |
| key_name | key1 |
| metadata | {} |
| name | superfrobnicator |
| status | ERROR |
| tenant_id | 055dcbd953ae4e559f12f74728bebf8d |
| updated | 2012-05-21T14:33:17Z |
| user_id | 532c368b3e96438480f9ae858d1be8e8 |
+-------------------------------------+--------------------------------------+

why the status is ERROR

 status | ERROR
OS-EXT-STS:vm_state | error

root@oscloud1204:~# ifconfig
eth0 Link encap:Ethernet HWaddr 00:15:17:8e:2a:87
          inet addr:172.17.1.77 Bcast:172.17.255.255 Mask:255.255.0.0
          inet6 addr: fe80::215:17ff:fe8e:2a87/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:27666 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3539 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:2091666 (2.0 MB) TX bytes:588879 (588.8 KB)

lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MTU:16436 Metric:1
          RX packets:92283 errors:0 dropped:0 overruns:0 frame:0
          TX packets:92283 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:59335768 (59.3 MB) TX bytes:59335768 (59.3 MB)

virbr0 Link encap:Ethernet HWaddr 16:8a:1e:6a:82:f3
          inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0
          UP BROADCAST MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

i am unable to to execute the instance. The Whole configuration was done on single machine.
please reply

Question information

Language:
English Edit question
Status:
Answered
For:
OpenStack Compute (nova) Edit question
Assignee:
No assignee Edit question
Last query:
2012-05-31
Last reply:
2013-04-04
neo0 (tungns-inf) said : #1

Something wrong with your nova-compute:

nova-compute oscloud1204 nova enabled XXX 2012-05-17 13:05:14

So when you run an instance by: # nova boot --flavor 1 --image b5145242-4904-4521-b0b0-4065bec67a24 --key_name key1 superfrobnicator
It's return:

| OS-EXT-SRV-ATTR:host | None |
| OS-EXT-SRV-ATTR:hypervisor_hostname | None |

You must recheck nova-compute. Try to restart this service!

amit (amib) said : #2

I have checked all the things in nova compute and again my instance is not active, many times i restart the nova-compute servive. Please suggest me the where i am doing the wrong thing.

To configure the nova-compute i followed the link http://www.hastexo.com/resources/docs/installing-openstack-essex-20121-ubuntu-1204-precise-pangolin.

amit (amib) said : #3

root@oscloud1204:~# nova-manage service list
2012-05-29 14:46:43 DEBUG nova.utils [req-3e5ba45c-ad42-4594-91af-721eeb160bda None None] backend <module 'nova.db.sqlalchemy.api' from '/usr/lib/python2.7/dist-packages/nova/db/sqlalchemy/api.pyc'> from (pid=2812) __get_backend /usr/lib/python2.7/dist-packages/nova/utils.py:658
Binary Host Zone Status State Updated_At
nova-network oscloud1204 nova enabled :-) 2012-05-29 09:16:43
nova-cert oscloud1204 nova enabled :-) 2012-05-29 09:16:33
nova-scheduler oscloud1204 nova enabled :-) 2012-05-29 09:16:33
nova-compute oscloud1204 nova enabled XXX 2012-05-17 13:05:14
nova-volume oscloud1204 nova enabled :-) 2012-05-29 09:16:34

here the state of nova-compute is XXX

root@oscloud1204:~# /etc/init.d/nova-compute restart
Rather than invoking init scripts through /etc/init.d, use the service(8)
utility, e.g. service nova-compute restart

Since the script you are attempting to invoke has been converted to an
Upstart job, you may also use the stop(8) and then start(8) utilities,
e.g. stop nova-compute ; start nova-compute. The restart(8) utility is also available.
nova-compute start/running, process 2897

root@oscloud1204:~# /etc/init.d/nova-compute status
Rather than invoking init scripts through /etc/init.d, use the service(8)
utility, e.g. service nova-compute status

Since the script you are attempting to invoke has been converted to an
Upstart job, you may also use the status(8) utility, e.g. status nova-compute
nova-compute stop/waiting

why nova-compute is stopped here when i start this service earlier?

root@oscloud1204:~# tail -f /var/log/nova/nova-compute.log
2012-05-29 14:14:37 TRACE nova File "/usr/lib/python2.7/dist-packages/nova/rpc/amqp.py", line 299, in __iter__
2012-05-29 14:14:37 TRACE nova self._iterator.next()
2012-05-29 14:14:37 TRACE nova File "/usr/lib/python2.7/dist-packages/nova/rpc/impl_kombu.py", line 572, in iterconsume
2012-05-29 14:14:37 TRACE nova yield self.ensure(_error_callback, _consume)
2012-05-29 14:14:37 TRACE nova File "/usr/lib/python2.7/dist-packages/nova/rpc/impl_kombu.py", line 503, in ensure
2012-05-29 14:14:37 TRACE nova error_callback(e)
2012-05-29 14:14:37 TRACE nova File "/usr/lib/python2.7/dist-packages/nova/rpc/impl_kombu.py", line 553, in _error_callback
2012-05-29 14:14:37 TRACE nova raise rpc_common.Timeout()
2012-05-29 14:14:37 TRACE nova Timeout: Timeout while waiting on RPC response.
2012-05-29 14:14:37 TRACE nova

Why the logs shows that Time error? what does it mean?

please reply soon.

amit (amib) said : #4

now the instances got their ip by nova-network but when i execute the instances its state remain pending.

root@openstack:~# euca-describe-instances
RESERVATION r-3cayclvt testproject default
INSTANCE i-00000005 ami-00000004 192.168.0.66 10.0.0.3 pending mykeypair 0 m1.tiny 2012-05-30T12:38:06Znova aki-00000003 ami-00000000

root@openstack:~# nova list
+----+----------+--------+----------------------------------+
| ID | Name | Status | Networks |
+----+----------+--------+----------------------------------+
| 5 | Server 5 | BUILD | private_0=10.0.0.3, 192.168.0.66 |
+----+----------+--------+----------------------------------+

root@openstack:~# euca-describe-images
IMAGE ami-00000004 None (natty-server-cloudimg-amd64.img) available public machine aki-00000003 instance-store
IMAGE aki-00000003 None (natty-server-cloudimg-amd64-vmlinuz-virtual) available public kernel instance-store
IMAGE ami-00000002 None (ttylinux-uec-amd64-12.1_2.6.35-22_1.img) available public machine aki-00000001 instance-store
IMAGE aki-00000001 None (ttylinux-uec-amd64-12.1_2.6.35-22_1-vmlinuz) available public kernel instance-store

please reply soon its urgent.

Munesh Jadoun (munesh) said : #5

Amit is waiting for reply

Munesh Jadoun (munesh) said : #6

Ok

Warm Regards

Munesh Jadoun
CEO & Founder

-----------------------------------------------------------------
ZNet Technologies Pvt. Ltd. - Web Hosting Company.
Group Website: www.znetcorp.com
Ventures: www.znetlive.in | www.iconcube.com
Call: +91-141-4070666 | India Toll FREE: 1-800-102-9638 (ZNET)
India Address (HO): D-10/52, Opp. Chitrakoot Stadium, Chitrakoot, Vaishali Nagar, Jaipur-21 (India)
ZNET Participation at WHD.india. See pics at http://goo.gl/P01kN
VPS Super Saver!! Linux/Windows VPS at Just Rs. 699/mo.
-----------------------------------------------------------------
This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.

-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of Munesh Jadoun
Sent: Friday, June 08, 2012 7:16 PM
To: Munesh Singh
Subject: Re: [Question #197971]: instance not active in nova compute

Question #197971 on OpenStack Compute (nova) changed:
https://answers.launchpad.net/nova/+question/197971

Munesh Jadoun posted a new comment:
Amit is waiting for reply

--
You received this question notification because you are a direct subscriber of the question.

Munesh Jadoun (munesh) said : #7

Ok

Warm Regards

Munesh Jadoun
CEO & Founder

-----------------------------------------------------------------
ZNet Technologies Pvt. Ltd. - Web Hosting Company.
Group Website: www.znetcorp.com
Ventures: www.znetlive.in | www.iconcube.com
Call: +91-141-4070666 | India Toll FREE: 1-800-102-9638 (ZNET)
India Address (HO): D-10/52, Opp. Chitrakoot Stadium, Chitrakoot, Vaishali Nagar, Jaipur-21 (India)
ZNET Participation at WHD.india. See pics at http://goo.gl/P01kN
VPS Super Saver!! Linux/Windows VPS at Just Rs. 699/mo.
-----------------------------------------------------------------
This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.

-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of amit
Sent: Tuesday, May 29, 2012 2:56 PM
To: Munesh Singh
Subject: Re: [Question #197971]: instance not active in nova compute

Question #197971 on OpenStack Compute (nova) changed:
https://answers.launchpad.net/nova/+question/197971

amit gave more information on the question:
root@oscloud1204:~# nova-manage service list
2012-05-29 14:46:43 DEBUG nova.utils [req-3e5ba45c-ad42-4594-91af-721eeb160bda None None] backend <module 'nova.db.sqlalchemy.api' from '/usr/lib/python2.7/dist-packages/nova/db/sqlalchemy/api.pyc'> from (pid=2812) __get_backend /usr/lib/python2.7/dist-packages/nova/utils.py:658
Binary Host Zone Status State Updated_At
nova-network oscloud1204 nova enabled :-) 2012-05-29 09:16:43
nova-cert oscloud1204 nova enabled :-) 2012-05-29 09:16:33
nova-scheduler oscloud1204 nova enabled :-) 2012-05-29 09:16:33
nova-compute oscloud1204 nova enabled XXX 2012-05-17 13:05:14
nova-volume oscloud1204 nova enabled :-) 2012-05-29 09:16:34

here the state of nova-compute is XXX

root@oscloud1204:~# /etc/init.d/nova-compute restart Rather than invoking init scripts through /etc/init.d, use the service(8) utility, e.g. service nova-compute restart

Since the script you are attempting to invoke has been converted to an Upstart job, you may also use the stop(8) and then start(8) utilities, e.g. stop nova-compute ; start nova-compute. The restart(8) utility is also available.
nova-compute start/running, process 2897

root@oscloud1204:~# /etc/init.d/nova-compute status Rather than invoking init scripts through /etc/init.d, use the service(8) utility, e.g. service nova-compute status

Since the script you are attempting to invoke has been converted to an Upstart job, you may also use the status(8) utility, e.g. status nova-compute nova-compute stop/waiting

why nova-compute is stopped here when i start this service earlier?

root@oscloud1204:~# tail -f /var/log/nova/nova-compute.log
2012-05-29 14:14:37 TRACE nova File "/usr/lib/python2.7/dist-packages/nova/rpc/amqp.py", line 299, in __iter__
2012-05-29 14:14:37 TRACE nova self._iterator.next()
2012-05-29 14:14:37 TRACE nova File "/usr/lib/python2.7/dist-packages/nova/rpc/impl_kombu.py", line 572, in iterconsume
2012-05-29 14:14:37 TRACE nova yield self.ensure(_error_callback, _consume)
2012-05-29 14:14:37 TRACE nova File "/usr/lib/python2.7/dist-packages/nova/rpc/impl_kombu.py", line 503, in ensure
2012-05-29 14:14:37 TRACE nova error_callback(e)
2012-05-29 14:14:37 TRACE nova File "/usr/lib/python2.7/dist-packages/nova/rpc/impl_kombu.py", line 553, in _error_callback
2012-05-29 14:14:37 TRACE nova raise rpc_common.Timeout()
2012-05-29 14:14:37 TRACE nova Timeout: Timeout while waiting on RPC response.
2012-05-29 14:14:37 TRACE nova

Why the logs shows that Time error? what does it mean?

please reply soon.

--
You received this question notification because you are a direct subscriber of the question.

duypd (warsaw20062000) said : #8

You can use following command, replace your hostname to host:

nova-manage service disable --host=ubuntu --service=nova-compute
nova-manage service enable --host=ubuntu --service=nova-compute

Hi, I am having same issue. I am trying to install openstack and stuck at nova install. Has the issue described above been fixed?

root@ubuntu2:/var/log/nova# nova-manage network listservice
2013-04-03 23:43:00 DEBUG nova.utils [req-cf5d0b12-7d72-4ffa-a6e1-2af2546c66b8 None None] backend <module 'nova.db.sqlalchemy.api' from '/usr/lib/python2.7/dist-packages/nova/db/sqlalchemy/api.pyc'> from (pid=3413) __get_backend /usr/lib/python2.7/dist-packages/nova/utils.py:662
Binary Host Zone Status State Updated_At
nova-scheduler ubuntu2 nova enabled :-) 2013-04-04 06:42:56
nova-cert ubuntu2 nova enabled :-) 2013-04-04 06:42:52
nova-compute ubuntu2 nova enabled XXX 2013-04-04 06:37:36
nova-network ubuntu2 nova enabled XXX 2013-04-04 06:04:30
nova-consoleauth ubuntu2 nova enabled :-) 2013-04-04 06:42:56
root@ubuntu2:/var/log/nova#

Can you help with this problem?

Provide an answer of your own, or ask amit for more information if necessary.

To post a message you must log in.