Bug 1900575

Summary: foreman-maintain service list doesn't list sidekiq services
Product: Red Hat Satellite Reporter: Pavel Moravec <pmoravec>
Component: Satellite MaintainAssignee: Amit Upadhye <aupadhye>
Status: CLOSED ERRATA QA Contact: Gaurav Talreja <gtalreja>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.8.0CC: apatel, aupadhye, kgaikwad, pcreech
Target Milestone: 6.9.0Keywords: Triaged
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: rubygem-foreman_maintain-0.7.4 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1919441 (view as bug list) Environment:
Last Closed: 2021-04-21 14:48:24 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 Pavel Moravec 2020-11-23 12:07:09 UTC
Description of problem:
See Summary and Reproducer


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


How reproducible:
100%


Steps to Reproduce:
1. foreman-maintain service list

2. foreman-maintain service restart


Actual results:
1. output does not list either of three sidekiq services
2. restart does bounce all three services (which is good)


Expected results:
1. service list to enumarate the three missing services (no other misses)


Additional info:

Comment 1 Amit Upadhye 2020-12-16 11:24:07 UTC
Hello Pavel,

I have created pr for the issue. The output now displays the dynflow-sidekiq@.service as below,

~~~
# bin/foreman-maintain service list
Running Service List
================================================================================
List applicable services: 
dynflow-sidekiq@.service                      enabled 
foreman-proxy.service                         enabled 
httpd.service                                 enabled 
postgresql.service                            enabled 
pulp_celerybeat.service                       enabled 
pulp_resource_manager.service                 enabled 
pulp_streamer.service                         enabled 
pulp_workers.service                          enabled 
puppetserver.service                          enabled 
qdrouterd.service                             enabled 
qpidd.service                                 enabled 
rh-mongodb34-mongod.service                   enabled 
rh-redis5-redis.service                       enabled 
smart_proxy_dynflow_core.service              enabled 
squid.service                                 enabled 
tomcat.service                                enabled

All services listed                                                   [OK]
--------------------------------------------------------------------------------
~~~

With my limited knowledge of systemd the dynflow-sidekiq is instantiated service, and so has one unit file listed under 'systemctl list-unit-files'. As per that output of 'service list' command depends and resembles to 'systemctl list-unit-files', and so we dont have all three services listed here.
_
Amit Upadhye.

Comment 2 Bryan Kearney 2021-01-08 13:40:06 UTC
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/31520 has been resolved.

Comment 3 Gaurav Talreja 2021-01-15 11:44:43 UTC
Verified.

Tested on Satellite 6.9.0 Snap 9.
Version: rubygem-foreman_maintain-0.7.4-1.el7sat.noarch

Steps:
1. # foreman-maintain service list  (shows the output as same as Comment 1).


Observation:
The `dynflow-sidekiq@.service` listed in the output of the above command, is an instantiated service, which has one unit file listed under 'systemctl list-unit-files'
Also, it has 3 instances/services `dynflow-sidekiq@orchestrator`, `dynflow-sidekiq@worker`, `dynflow-sidekiq@worker-hosts-queue`, which are being displayed and restarted here with `foreman-maintain service restart` as an individual service.

Comment 6 errata-xmlrpc 2021-04-21 14:48:24 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Satellite 6.9 Satellite Maintenance Release), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2021:1312