RDO tickets are now tracked in Jira https://issues.redhat.com/projects/RDO/issues/
Bug 1007685 - openstack-status still uses quantum named services instead of neutron
Summary: openstack-status still uses quantum named services instead of neutron
Keywords:
Status: CLOSED DUPLICATE of bug 999507
Alias: None
Product: RDO
Classification: Community
Component: openstack-utils
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Pádraig Brady
QA Contact: Ami Jeain
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-13 06:49 UTC by Attila Fazekas
Modified: 2016-01-04 14:46 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-09-18 13:06:42 UTC
Embargoed:


Attachments (Terms of Use)

Description Attila Fazekas 2013-09-13 06:49:31 UTC
Description of problem:
openstack-status does not shows neutron service status.

[root@rhel-6 nova(keystone_admin)]# grep neutron /usr/bin/openstack-status
[root@rhel-6 nova(keystone_admin)]# grep quantum /usr/bin/openstack-status
rpm -q openstack-quantum > /dev/null && quantum='quantum'
if test "$quantum"; then
  for svc in quantum-server quantum-dhcp-agent quantum-l3-agent quantum-linuxbridge-agent quantum-openvswitch-agent openvswitch; do check_svc "$svc"; done


Version-Release number of selected component (if applicable):
RDO havana

http://repos.fedorapeople.org/repos/openstack/openstack-havana/epel-6/openstack-utils-2013.1-8.el6.noarch.rpm

How reproducible:
always

Steps to Reproduce:
$ openstack-status

(I have running services)


Actual results:
You see nothing about neutron or quantum.

Expected results:

See all neutron agent's status.

Additional info:
Including the 
$ neutron agent-list
output for remote agents would be a nice addition.

Comment 1 Mohammed Arafa 2013-09-15 03:08:31 UTC
is this a duplicate of bug 999507?

Comment 2 Pádraig Brady 2013-09-18 13:06:42 UTC

*** This bug has been marked as a duplicate of bug 999507 ***


Note You need to log in before you can comment on or make changes to this bug.