Ask Your Question
1

mitaka nova-osapi_compute nova_metadata down

asked 2016-05-26 10:01:35 -0500

GG1982 gravatar image

Hi guys! After a fresh install of nova (Mitaka according to this documentation http://docs.openstack.org/mitaka/install-guide-ubuntu/nova.html (http://docs.openstack.org/mitaka/inst...)) on the controller node, I checked the status of services with the command:

 openstack compute service list

I got this output:

+----+------------------+--------------+----------+---------+-------+----------------------------+
| Id | Binary           | Host         | Zone     | Status  | State | Updated At                 |
+----+------------------+--------------+----------+---------+-------+----------------------------+
|  3 | nova-consoleauth | oscontroll01 | internal | enabled | up    | 2016-05-26T14:52:53.000000 |  
|  4 | nova-scheduler   | oscontroll01 | internal | enabled | up    | 2016-05-26T14:52:53.000000 |
|  5 | nova-conductor   | oscontroll01 | internal | enabled | up    | 2016-05-26T14:52:48.000000 |
| 15 | nova-compute     | oscompute01  | nova     | enabled | up    | 2016-05-26T14:52:47.000000 |
+----+------------------+--------------+----------+---------+-------+----------------------------+

So, everything seems OK.

I also checked with the commande:

nova-manage service list

Adn then I got this output:

Option "verbose" from group "DEFAULT" is deprecated for removal.  Its value may be silently ignored in the future.
DEPRECATED: Use the nova service-* commands from python-novaclient instead or the os-services REST resource. The service subcommand will be removed in the 14.0 release.
Binary           Host                                 Zone             Status     State Updated_At
2016-05-26 16:55:05.968 18829 DEBUG nova.servicegroup.drivers.db [req-9ac2cdf8-a0da-4033-b19a-7e24d6faf429 - - - - -] Seems service nova-osapi_compute on host 0.0.0.0 is down. Last heartbeat was 2016-05-26 13:35:00. Elapsed time is 4805.968678 is_up /usr/lib/python2.7/dist-packages/nova/servicegroup/drivers/db.py:82
nova-osapi_compute 0.0.0.0                              internal         enabled    XXX   None
2016-05-26 16:55:05.969 18829 DEBUG nova.servicegroup.drivers.db [req-9ac2cdf8-a0da-4033-b19a-7e24d6faf429 - - - - -] Seems service nova-metadata on host 0.0.0.0 is down. Last heartbeat was 2016-05-26 13:35:05. Elapsed time is 4800.969194 is_up /usr/lib/python2.7/dist-packages/nova/servicegroup/drivers/db.py:82
nova-metadata    0.0.0.0                              internal         enabled    XXX   None
nova-consoleauth oscontroll01                         internal         enabled    :-)   2016-05-26 14:55:03
nova-scheduler   oscontroll01                         internal         enabled    :-)   2016-05-26 14:55:04
nova-conductor   oscontroll01                         internal         enabled    :-)   2016-05-26 14:54:58
nova-compute     oscompute01                          nova             enabled    :-)   2016-05-26 14:54:57

After that, I checked if something is listening on port 8774 (osapi_compute) and 8775 (metadata) with this command:

netstat -tapun | grep 877

I got htis ouput:

tcp        0      0 0.0.0.0:8774            0.0.0.0:*               LISTEN      18082/python
tcp        0      0 0.0.0.0:8775            0.0.0.0:*               LISTEN      18082/python

I assumed that the services are running, I can also telnet on those services and they are responding.

I searched this symptom on the net, but found nothing.

Any help will be really appreciated

edit retag flag offensive close merge delete

Comments

This https://bugs.launchpad.net/fuel/+bug/1539100 (discussion) says the report in mitaka should filter these services out. Sounds like they are down by design.

kenedy gravatar imagekenedy ( 2016-09-29 04:23:35 -0500 )edit

1 answer

Sort by ยป oldest newest most voted
0

answered 2016-05-26 14:54:46 -0500

Michal gravatar image

updated 2016-05-26 15:00:11 -0500

Did you try to curl your metadata service?

controller:root:~> curl http://127.0.0.1:8775/
1.0
2007-01-19
2007-03-01
2007-08-29
2007-10-10
2007-12-15
2008-02-01
2008-09-01
2009-04-04
latest

More about medata service here: https://vietstack.wordpress.com/2014/09/27/introduction-of-metadata-service-in-openstack/ (https://vietstack.wordpress.com/2014/...) and here http://kimizhang.com/metadata-service-in-dhcp-namespace/ (http://kimizhang.com/metadata-service...)

edit flag offensive delete link more

Comments

I got the same output as you showned with the command : curl http://127.0.0.1:8775/ The neutron module is not yet installed.

Do you think the issue can come from that?

GG1982 gravatar imageGG1982 ( 2016-05-27 06:10:05 -0500 )edit

Hi,

Please read https://vietstack.wordpress.com/2014/09/27/introduction-of-metadata-service-in-openstack/ (https://vietstack.wordpress.com/2014/...)

Unless you are using old legacy nova-networking due to some reasons, AFAIK, metadata works either trough neutron-dhcp-agent or neutron-l3-agent. Install neutron and let us know if works.

Michal gravatar imageMichal ( 2016-05-31 04:24:50 -0500 )edit
1

I have installed Neutron, but still the same. With the command neutron agent-list, every agent is up. I suspect something with nova as I have also this problem with nova-osapi_compute

GG1982 gravatar imageGG1982 ( 2016-06-02 07:47:39 -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: 2016-05-26 10:01:35 -0500

Seen: 988 times

Last updated: May 26 '16