Bug 1232756

Summary: openstack-service status return 0 regardless of non-existing service
Product: Red Hat OpenStack Reporter: Martin Pavlásek <mpavlase>
Component: openstack-utilsAssignee: Lon Hohberger <lhh>
Status: CLOSED WONTFIX QA Contact: Shai Revivo <srevivo>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.0 (Kilo)CC: mburns, srevivo
Target Milestone: ---Keywords: Automation, ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-10-12 21:55:38 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 Martin Pavlásek 2015-06-17 12:39:53 UTC
Description of problem:
openstack-service CLI don't care about name of non-existing service - with know prefix (such as 'n' for 'nova')

Version-Release number of selected component (if applicable):
openstack-utils-2014.2-1.el7ost.noarch
openstack-packstack-2015.1-0.3.dev1565.gd1211af.el7ost.noarch

How reproducible:
100%

Steps to Reproduce:
1. openstack-service status openstack-noa # there is missing 'v' by purpose
2. echo $?

Actual results:
0

Expected results:
non-zero return code

Additional info:

Comment 5 Lon Hohberger 2016-01-04 21:56:31 UTC
This appears to be intentional.

There's no method to report failures when performing an operation on multiple services.  That is, the command would have to be significantly expanded in scope to make deterministic behavior if e.g. some services are running, some are not, some are disabled/crashed, and some are not found.

It looks fairly trivial to make it report an error if *no* matching services are found, but not if some are found while others are not.

Comment 8 Mike Burns 2016-10-12 19:56:10 UTC
Per comment 5 and because we're not expending much effort on openstack-utils, I'm going to nack this bug

Comment 9 RHEL Program Management 2016-10-12 21:55:38 UTC
Development Management has reviewed and declined this request.
You may appeal this decision by reopening this request.