Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1900575 - foreman-maintain service list doesn't list sidekiq services
Summary: foreman-maintain service list doesn't list sidekiq services
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Satellite Maintain
Version: 6.8.0
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: 6.9.0
Assignee: Amit Upadhye
QA Contact: Gaurav Talreja
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-11-23 12:07 UTC by Pavel Moravec
Modified: 2024-03-25 17:12 UTC (History)
4 users (show)

Fixed In Version: rubygem-foreman_maintain-0.7.4
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1919441 (view as bug list)
Environment:
Last Closed: 2021-04-21 14:48:24 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 31520 0 Normal Closed foreman-maintain service list doesn't list sidekiq services 2021-02-08 07:36:03 UTC
Red Hat Product Errata RHBA-2021:1312 0 None None None 2021-04-21 14:48:34 UTC

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
Note You need to log in before you can comment on or make changes to this bug.