Bug 1035053 - the service files are not prepended with openstack
Summary: the service files are not prepended with openstack
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RDO
Classification: Community
Component: openstack-heat
Version: unspecified
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Jeff Peeler
QA Contact: Amit Ugol
URL:
Whiteboard:
Depends On:
Blocks: 1035045
TreeView+ depends on / blocked
 
Reported: 2013-11-27 00:26 UTC by Steven Dake
Modified: 2016-04-26 18:20 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 1035045
Environment:
Last Closed: 2014-01-13 15:54:14 UTC


Attachments (Terms of Use)

Description Steven Dake 2013-11-27 00:26:31 UTC
+++ This bug was initially created as a clone of Bug #1035045 +++

Description of problem:
 sudo service --status-all | grep openstack

shows no heat services

but they are there:
 sudo service --status-all | grep heat
heat-api (pid  25695) is running...
heat-api-cfn is stopped
heat-api-cloudwatch is stopped
heat-engine (pid  25740) is running...


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


How reproducible:
100%

Steps to Reproduce:
1.sudo service --status-all | grep openstack
2.
3.

Actual results:
shows no heat services

Expected results:
openstack-heat-api (and others)

Additional info:

--- Additional comment from Angus Salkeld on 2013-11-26 18:43:46 EST ---

$ sudo service heat-api-cfn status
heat-api-cfn: unrecognized service
$ sudo service openstack-heat-api-cfn status
heat-api-cfn is stopped

ls /etc/init.d/openstack-heat-*
/etc/init.d/openstack-heat-api      /etc/init.d/openstack-heat-api-cloudwatch
/etc/init.d/openstack-heat-api-cfn  /etc/init.d/openstack-heat-engine


(it must just be the way it's printed out) - still confusing.

--- Additional comment from RHEL Product and Program Management on 2013-11-26 19:10:34 EST ---

Since this issue was entered in bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

Comment 1 Jeff Peeler 2014-01-13 15:54:14 UTC
Closing as this was fixed a while ago. Quickly looking at the spec, it looks like it was first put in the 2013.2.1-1.0 build.


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