Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
On 6.4 capsule using katello-service,
# katello-service start
systemctl start rh-mongodb34-mongod.service
systemctl start qpidd.service
systemctl start qdrouterd.service
systemctl start squid.service
systemctl start pulp_workers.service
systemctl start pulp_celerybeat.service
systemctl start smart_proxy_dynflow_core.service
systemctl start pulp_streamer.service
systemctl start foreman-proxy.service
systemctl start pulp_resource_manager.service
systemctl start httpd.service
systemctl start puppetserver.service
systemctl start goferd.service
On 6.4 capsule using foreman-maintain service,
# foreman-maintain service start
Running Start Services
================================================================================
Check if command is run as root user: [OK]
--------------------------------------------------------------------------------
Start applicable services:
Starting the following service(s):
rh-mongodb34-mongod, squid, foreman-proxy, smart_proxy_dynflow_core, pulp_streamer, pulp_celerybeat, pulp_resource_manager, pulp_workers, puppetserver
\ All services started [OK]
--------------------------------------------------------------------------------
Version-Release number of selected component (if applicable):
# rpm -qa | grep maintain
rubygem-foreman_maintain-0.2.6-1.el7sat.noarch
How reproducible: always
Steps to Reproduce:
1. katello-service start
2. foreman-maintain service start
Actual results:
Diff of following service which are handled by katello-service but not foreman-maintain service.
- qpidd.service
- qdrouterd.service
- httpd.service
- goferd.service
Expected results: foreman-maintain service should able to handle those services.
Additional info:
# foreman-maintain service stop --only httpd
Running Stop Services
================================================================================
Check if command is run as root user: [OK]
--------------------------------------------------------------------------------
Stop applicable services:
Stopping the following service(s):
[FAIL]
No services found matching your parameters
--------------------------------------------------------------------------------
Scenario [Stop Services] failed.
The following steps ended up in failing state:
[service-stop]
Resolve the failed steps and rerun
the command. In case the failures are false positives,
use --whitelist="service-stop"
# katello-service stop --only httpd
systemctl stop httpd.service
Success!
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, 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-2018:2926
Description of problem: On 6.4 capsule using katello-service, # katello-service start systemctl start rh-mongodb34-mongod.service systemctl start qpidd.service systemctl start qdrouterd.service systemctl start squid.service systemctl start pulp_workers.service systemctl start pulp_celerybeat.service systemctl start smart_proxy_dynflow_core.service systemctl start pulp_streamer.service systemctl start foreman-proxy.service systemctl start pulp_resource_manager.service systemctl start httpd.service systemctl start puppetserver.service systemctl start goferd.service On 6.4 capsule using foreman-maintain service, # foreman-maintain service start Running Start Services ================================================================================ Check if command is run as root user: [OK] -------------------------------------------------------------------------------- Start applicable services: Starting the following service(s): rh-mongodb34-mongod, squid, foreman-proxy, smart_proxy_dynflow_core, pulp_streamer, pulp_celerybeat, pulp_resource_manager, pulp_workers, puppetserver \ All services started [OK] -------------------------------------------------------------------------------- Version-Release number of selected component (if applicable): # rpm -qa | grep maintain rubygem-foreman_maintain-0.2.6-1.el7sat.noarch How reproducible: always Steps to Reproduce: 1. katello-service start 2. foreman-maintain service start Actual results: Diff of following service which are handled by katello-service but not foreman-maintain service. - qpidd.service - qdrouterd.service - httpd.service - goferd.service Expected results: foreman-maintain service should able to handle those services. Additional info: # foreman-maintain service stop --only httpd Running Stop Services ================================================================================ Check if command is run as root user: [OK] -------------------------------------------------------------------------------- Stop applicable services: Stopping the following service(s): [FAIL] No services found matching your parameters -------------------------------------------------------------------------------- Scenario [Stop Services] failed. The following steps ended up in failing state: [service-stop] Resolve the failed steps and rerun the command. In case the failures are false positives, use --whitelist="service-stop" # katello-service stop --only httpd systemctl stop httpd.service Success!