Bug 1394689

Summary:	'openstack-service restart' fails to restart zaqar
Product:	Red Hat OpenStack	Reporter:	Udi Kalifon <ukalifon>
Component:	openstack-utils	Assignee:	Lon Hohberger <lhh>
Status:	CLOSED UPSTREAM	QA Contact:	Shai Revivo <srevivo>
Severity:	low	Docs Contact:
Priority:	low
Version:	10.0 (Newton)	CC:	apevec, jpichon, lhh, mburns, srevivo
Target Milestone:	---	Keywords:	ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-12-02 18:16:10 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:
Embargoed:

Description Udi Kalifon 2016-11-14 09:17:12 UTC

Description of problem:
Running 'openstack-service restart' causes an error:

$ sudo openstack-service restart
Failed to restart openstack-zaqar@.service: Unit name openstack-zaqar@.service is missing the instance name.
See system logs and 'systemctl status openstack-zaqar@.service' for details.

$ systemctl status openstack-zaqar@.service
Failed to get properties: Unit name openstack-zaqar@.service is missing the instance name.

I have 3 services running that belog to zaqar:
  openstack-zaqar.service
  openstack-zaqar
  system-openstack\x2dzaqar.slice


Version-Release number of selected component (if applicable):
I don't know which package owns openstack-service (couldn't find it with yum whatprovides)


How reproducible:
100%


Steps to Reproduce:
1. Run 'openstack-service restart'

Comment 2 Julie Pichon 2016-11-14 17:09:02 UTC

Looks like this belongs to the openstack-utils component [1], I'll move the bug - I'm not sure about the DFG though.

[1] https://github.com/redhat-openstack/openstack-utils/blob/master/utils/openstack-service

Comment 3 Mike Burns 2016-11-14 17:21:04 UTC

openstack-utils is not installed by default and not actively maintained.  It is in the Developer tools/utilities channel which has lower support than our main channel.  Please use systemctl directly to manage services.  

openstack-service specifically knows nothing about pacemaker and doesn't handle this correctly if a service is in pacemaker, so we should avoid it's use in general.

Comment 4 Alan Pevec 2016-12-02 18:16:10 UTC

Reported upstream https://github.com/redhat-openstack/openstack-utils/issues/25