Bug 999507

Summary:	openstack-status does not report the status of the neutron services
Product:	[Community] RDO	Reporter:	lpeer <lpeer>
Component:	openstack-utils	Assignee:	lpeer <lpeer>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Ami Jeain <ajeain>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	afazekas, bugzilla, chrisw, pbrady, yeylon
Target Milestone:	---
Target Release:	Havana
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:	openstack-utils-2013.2-1	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-01-15 16:50:45 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description lpeer 2013-08-21 12:44:50 UTC

Description of problem:

After installation of RDO allinone configuration, the execution of openstack-status does not report the status of the Neutron Services
 
This bug is related to the quantum-> neutron renaming.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 lpeer 2013-08-27 10:45:32 UTC

pull request link -

https://github.com/redhat-openstack/openstack-utils/pull/7

Comment 2 Mohammed Arafa 2013-09-15 03:04:15 UTC

hi
i just did a fresh install of havana and only see this:
openstack-nova-network:       dead (disabled on boot)
openstack-nova-scheduler:     active
openstack-nova-volume:        dead (disabled on boot)

nothing about quantum even

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

*** Bug 1007685 has been marked as a duplicate of this bug. ***

Comment 4 Pádraig Brady 2013-09-18 13:09:41 UTC

Version openstack-utils-2013.2-1 is now built and bubbling through fedora/epel/RDO update channels

Comment 5 Mohammed Arafa 2013-09-19 02:43:23 UTC

just updated to openstack-utils-2013.2-1.el6.1.noarch and ran openstack-status

it reports

== neutron services ==
neutron-server:               active
neutron-dhcp-agent:           active
neutron-l3-agent:             active
neutron-metadata-agent:       active
neutron-openvswitch-agent:    active

but doesnt report the networks that neutron is providing.

Comment 6 Pádraig Brady 2013-09-19 08:48:02 UTC

OK thanks for verifying.
Reporting networks is a separate functionality.
How would that logic go?

after_keystone_rc_is_sourced
if any_neutron_service_is_installed
  neutron net-list

Comment 7 Mohammed Arafa 2013-09-26 20:33:37 UTC

if the deployment is a large one, i would guess neutron net-list would be a longish list.