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 2011690 - foreman-maintain service list doesn't list foreman service when it is disabled
Summary: foreman-maintain service list doesn't list foreman service when it is disabled
Keywords:
Status: CLOSED DUPLICATE of bug 1995783
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Satellite Maintain
Version: 6.9.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-10-07 06:07 UTC by Krutika Kinge
Modified: 2023-10-20 01:32 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-05-20 23:27:33 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 6390171 0 None None None 2021-10-07 06:40:44 UTC

Description Krutika Kinge 2021-10-07 06:07:45 UTC 
Description of problem:

foreman-maintain service list does not list foreman service when it is disabled.

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

How reproducible:
100%

Steps to Reproduce:
1. disable the foreman service and then list the services:
    # systemctl disable foreman
    # satellite-maintain service list

Actual results:
the output does not list foreman service when it is disabled.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
# systemctl status foreman
● foreman.service - Foreman
   Loaded: loaded (/usr/lib/systemd/system/foreman.service; disabled; vendor preset: disabled)
  Drop-In: /etc/systemd/system/foreman.service.d
           └─installer.conf
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

# 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]
--------------------------------------------------------------------------------


Expected results:
foreman service should be listed as disabled like other services.

Additional info:

After enabling the service the output is listed:

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
# systemctl enable foreman
Created symlink from /etc/systemd/system/multi-user.target.wants/foreman.service to /usr/lib/systemd/system/foreman.service.

[root@rhsat69 ~]# systemctl status foreman
● foreman.service - Foreman
   Loaded: loaded (/usr/lib/systemd/system/foreman.service; enabled; vendor preset: disabled)
  Drop-In: /etc/systemd/system/foreman.service.d
           └─installer.conf
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

# foreman-maintain service list
Running Service List
================================================================================
List applicable services: 
dynflow-sidekiq@.service                      enabled 
foreman-proxy.service                         enabled 
foreman.service                               enabled      <========================= foreman service is listed
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]
--------------------------------------------------------------------------------
Comment 3 Brad Buckingham 2023-05-08 12:49:27 UTC 
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.
Comment 4 Eric Helms 2023-05-20 23:27:33 UTC 

*** This bug has been marked as a duplicate of bug 1995783 ***
Note You need to log in before you can comment on or make changes to this bug.