Ask Your Question
0

Juno nova service-list has nova-console listed with down status [closed]

asked 2016-02-01 03:42:36 -0500

evan gravatar image

updated 2016-02-29 15:11:19 -0500

Hi everyone:

I've those compute nodes,running on Juno, currently found there are some package loss (10%< x <3%) of ping from outside network(mgmt network) to instances, while 0% loss ping to physical interfaces of network node. Please take a look at the following command issued on controller node:

# nova service-list
+----+------------------+------------+----------+---------+-------+----------------------------+-----------------+
| Id | Binary           | Host       | Zone     | Status  | State | Updated_at                 | Disabled Reason |
+----+------------------+------------+----------+---------+-------+----------------------------+-----------------+
| 1  | nova-conductor   | controller | internal | enabled | up    | 2016-02-01T09:28:53.000000 | -               |
| 2  | nova-scheduler   | controller | internal | enabled | up    | 2016-02-01T09:28:53.000000 | -               |
| 3  | nova-cert        | controller | internal | enabled | up    | 2016-02-01T09:28:53.000000 | -               |
| 4  | nova-consoleauth | controller | internal | enabled | up    | 2016-02-01T09:28:58.000000 | -               |
| 5  | nova-compute     | compute1   | nova     | enabled | up    | 2016-02-01T09:28:53.000000 | None            |
| 6  | nova-compute     | compute2   | nova     | enabled | up    | 2016-02-01T09:28:52.000000 | None            |
| 7  | nova-compute     | compute3   | nova     | enabled | up    | 2016-02-01T09:28:54.000000 | None            |
| 8  | nova-console     | controller | internal | enabled | down  | 2016-01-19T08:57:18.000000 | -               |
......
+----+------------------+------------+----------+---------+-------+----------------------------+-----------------+

What I'm concerned is that why there is one called nova-console and it's down although it's not expected here. Anything wrong with it?

edit retag flag offensive reopen merge delete

Closed for the following reason the question is answered, right answer was accepted by evan
close date 2016-02-22 20:55:50.063148

1 answer

Sort by ยป oldest newest most voted
1

answered 2016-02-22 20:54:10 -0500

evan gravatar image

updated 2016-02-29 15:11:58 -0500

ID  | nova-console     | controller | internal | enabled | down

This is not a real problem actually and not relevant to the package loss. Ping package loss is caused by more than 1 default route on Network node. As for nova-console, it' not expected here so manually delete this service(nova service-delete nova_console_service_id), thus the status of controller (Services Down) on Dashboard will change to Up status. Why it's shown here, I guess once a time I started it by mistake as it exists.

# systemctl status openstack-nova-console
openstack-nova-console.service - OpenStack Nova Console Proxy Server
   Loaded: loaded (/usr/lib/systemd/system/openstack-nova-console.service; disabled; vendor preset: disabled)
   Active: inactive (dead)
edit flag offensive delete link more

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2016-02-01 03:42:36 -0500

Seen: 309 times

Last updated: Feb 29 '16