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:
After disabling Satellite services using the 'satellite-maintain service disable' command, not all services are re-enabled after running the 'satellite-maintain service enable' command.
Version-Release number of selected component (if applicable):
Satellite 6.10.2
How reproducible:
100%
Steps to Reproduce:
1. On a functional Satellite instance, check the status of services (should return Status: ok)
# hammer ping
2. Disable applicable services:
# satellite-maintain service disable
3. Enable applicable services:
# satellite-maintain service enable
4. Reboot Satellite server
5. Check the status of services
# hammer ping
Actual results:
Before making any changes, Satellite services return Status: ok.
~~~
[root@sat610 ~]# hammer ping
database:
Status: ok
Server Response: Duration: 0ms
katello_agent:
Status: ok
message: 0 Processed, 0 Failed
Server Response: Duration: 0ms
candlepin:
Status: ok
Server Response: Duration: 27ms
candlepin_auth:
Status: ok
Server Response: Duration: 37ms
candlepin_events:
Status: ok
message: 84 Processed, 0 Failed
Server Response: Duration: 0ms
katello_events:
Status: ok
message: 9 Processed, 0 Failed
Server Response: Duration: 1ms
pulp3:
Status: ok
Server Response: Duration: 94ms
pulp3_content:
Status: ok
Server Response: Duration: 99ms
foreman_tasks:
Status: ok
Server Response: Duration: 10ms
~~~
Disable applicable services:
~~~
# satellite-maintain service disable
Disabling the following service(s):
rh-redis5-redis, postgresql, pulpcore-api, pulpcore-content, qdrouterd, qpidd, pulpcore-worker, pulpcore-worker, pulpcore-worker, pulpcore-worker, pulpcore-worker, pulpcore-worker, tomcat, dynflow-sidekiq@orchestrator, foreman, httpd, puppetserver, dynflow-sidekiq@worker-1, dynflow-sidekiq@worker-hosts-queue-1, foreman-proxy
Skipping disable for pulpcore-worker, pulpcore-worker, pulpcore-worker, pulpcore-worker, pulpcore-worker, pulpcore-worker.
| All services disabled [OK]
~~~
Enable applicable services. Note: The 'foreman, pulpcore-api, pulpcore-content' services were disabled but not enabled.
~~~
# satellite-maintain service enable
Enabling the following service(s):
rh-redis5-redis, postgresql, qdrouterd, qpidd, tomcat, dynflow-sidekiq@orchestrator, httpd, puppetserver, dynflow-sidekiq@worker-1, dynflow-sidekiq@worker-hosts-queue-1, foreman-proxy
- All services enabled [OK]
~~~~
After rebooting the Satellite server, pulp3_content and foreman_tasks services failed.
~~~
[root@sat610 ~]# hammer ping
database:
Status: ok
Server Response: Duration: 0ms
katello_agent:
Status: ok
message: 0 Processed, 0 Failed
Server Response: Duration: 0ms
candlepin:
Status: ok
Server Response: Duration: 25ms
candlepin_auth:
Status: ok
Server Response: Duration: 30ms
candlepin_events:
Status: ok
message: 0 Processed, 0 Failed
Server Response: Duration: 0ms
katello_events:
Status: ok
message: 0 Processed, 0 Failed
Server Response: Duration: 0ms
pulp3:
Status: ok
Server Response: Duration: 6104ms
pulp3_content:
Status: FAIL
Server Response: Message: No pulpcore content apps are running at https://sat610.example.org/pulp/api/v3.
foreman_tasks:
Status: FAIL
Server Response: Message: some executors are not responding, check /foreman_tasks/dynflow/status
~~~
The 'foreman' and 'pulpcore-api' services started but remained disabled. The 'pulpcore-content' service remained disabled and inactive.
~~~
# 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
Active: active (running) since Thu 2022-02-17 15:36:12 GMT; 9min ago
# systemctl status pulpcore-api
pulpcore-api.service - Pulp API Server
Loaded: loaded (/etc/systemd/system/pulpcore-api.service; disabled; vendor preset: disabled)
Active: active (running) since Thu 2022-02-17 15:36:14 GMT; 9min ago
# systemctl status pulpcore-content
pulpcore-content.service - Pulp Content App
Loaded: loaded (/etc/systemd/system/pulpcore-content.service; disabled; vendor preset: disabled)
Active: inactive (dead)
~~~
After starting the pulpcore-content service manually, all Satellite services return Status: ok.
~~~
# hammer ping
database:
Status: ok
Server Response: Duration: 0ms
katello_agent:
Status: ok
message: 0 Processed, 0 Failed
Server Response: Duration: 0ms
candlepin:
Status: ok
Server Response: Duration: 33ms
candlepin_auth:
Status: ok
Server Response: Duration: 24ms
candlepin_events:
Status: ok
message: 0 Processed, 0 Failed
Server Response: Duration: 0ms
katello_events:
Status: ok
message: 0 Processed, 0 Failed
Server Response: Duration: 1ms
pulp3:
Status: ok
Server Response: Duration: 197ms
pulp3_content:
Status: ok
Server Response: Duration: 246ms
foreman_tasks:
Status: ok
Server Response: Duration: 3ms
~~~
Expected results:
All services disabled by 'satellite-maintain service disable' should be enabled 'satellite-maintain service enable'.
If enabling the services fails, a reason should be given for the failed enable.
Additional info:
'satellite-maintain service list' reports same status before and after disabling and re-enabling services (satellite-maintain service disable; satellite-maintain service enable; reboot). Also 'hammer ping' reports all ok.
VERIFIED with Satellite 6.14 SNAP4.0 @RHEL8.8
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 (Important: Satellite 6.14 security and bug fix update), 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/RHSA-2023:6818