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.
Same as rhcd who is also optional and is also missing.
Comment 3Pablo Mendez Hernandez
2022-11-02 16:17:58 UTC
I think that it would make sense if the installer added it somehow to the list of Satellite services if run with `--foreman-proxy-plugin-remote-execution-script-mode=pull-mqtt`. Otherwise the user could believe to have a perfectly working Satellite environment and not be able to execute ReX.
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.13 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/RHSA-2023:2097
Description of problem: I have installed Satellite with "--foreman-proxy-plugin-remote-execution-script-mode=pull-mqtt" installer option and mosquitto service is missing in `satellite-maintain service status -b` output Version-Release number of selected component (if applicable): satellite-6.12.0-4.el8sat.noarch How reproducible: always Steps to Reproduce: 1. Install Satellite with "--foreman-proxy-plugin-remote-execution-script-mode=pull-mqtt" installer option 2. satellite-maintain service status -b Actual results: mosquitto is not there in the output Expected results: Should be there Additional info: [root@f09-h26-b01-5039ms ~]# rpm -q satellite satellite-6.12.0-4.el8sat.noarch [root@f09-h26-b01-5039ms ~]# systemctl status mosquitto ● mosquitto.service - Mosquitto MQTT Broker Loaded: loaded (/usr/lib/systemd/system/mosquitto.service; enabled; vendor preset: disabled) Drop-In: /etc/systemd/system/mosquitto.service.d └─limits.conf, mosquitto-override.conf Active: active (running) since Mon 2022-10-24 10:24:58 UTC; 1 day 1h ago Docs: man:mosquitto.conf(5) man:mosquitto(8) Main PID: 24407 (mosquitto) Tasks: 1 (limit: 409984) Memory: 189.2M CGroup: /system.slice/mosquitto.service └─24407 /usr/sbin/mosquitto -c /etc/mosquitto/mosquitto.conf Oct 25 09:15:21 f09-h26-b01-5039ms.rdu2.scalelab.redhat.com mosquitto[24407]: 1666689321: New client connected from 172.21.7.254:42742 as auto-5001D6DA-4D4F-EE95-B12F-2F9599509737 (p2, c1, k15, u'f09-h26-b01-5039ms.rdu2.scalelab.redhat.> Oct 25 09:15:21 f09-h26-b01-5039ms.rdu2.scalelab.redhat.com mosquitto[24407]: 1666689321: Client auto-91194EBA-7E99-400E-5C4E-B0F6D8993EEB disconnected. Oct 25 09:15:21 f09-h26-b01-5039ms.rdu2.scalelab.redhat.com mosquitto[24407]: 1666689321: New connection from 172.21.7.254:42750 on port 1883. Oct 25 09:15:21 f09-h26-b01-5039ms.rdu2.scalelab.redhat.com mosquitto[24407]: 1666689321: New client connected from 172.21.7.254:42750 as auto-6F130BA0-1ECA-1C36-7524-768310AFCC38 (p2, c1, k15, u'f09-h26-b01-5039ms.rdu2.scalelab.redhat.> Oct 25 09:15:21 f09-h26-b01-5039ms.rdu2.scalelab.redhat.com mosquitto[24407]: 1666689321: Client auto-95A7A95A-0AC2-DB3A-468F-6EAAAF1E5806 disconnected. Oct 25 09:15:21 f09-h26-b01-5039ms.rdu2.scalelab.redhat.com mosquitto[24407]: 1666689321: Client auto-5001D6DA-4D4F-EE95-B12F-2F9599509737 disconnected. Oct 25 09:15:21 f09-h26-b01-5039ms.rdu2.scalelab.redhat.com mosquitto[24407]: 1666689321: Client auto-6F130BA0-1ECA-1C36-7524-768310AFCC38 disconnected. Oct 25 09:17:10 f09-h26-b01-5039ms.rdu2.scalelab.redhat.com mosquitto[24407]: 1666689430: New connection from 172.21.7.254:45950 on port 1883. Oct 25 09:17:10 f09-h26-b01-5039ms.rdu2.scalelab.redhat.com mosquitto[24407]: 1666689430: New client connected from 172.21.7.254:45950 as auto-BD63053B-FCD6-9F4D-7208-B8F690830554 (p2, c1, k15, u'f09-h26-b01-5039ms.rdu2.scalelab.redhat.> Oct 25 09:17:10 f09-h26-b01-5039ms.rdu2.scalelab.redhat.com mosquitto[24407]: 1666689430: Client auto-BD63053B-FCD6-9F4D-7208-B8F690830554 disconnected. [root@f09-h26-b01-5039ms ~]# satellite-maintain service status -b Running Status Services ================================================================================ Get status of applicable services: Displaying the following service(s): redis, postgresql, pulpcore-api, pulpcore-content, pulpcore-worker, pulpcore-worker, pulpcore-worker, pulpcore-worker, pulpcore-worker, pulpcore-worker, pulpcore-worker, pulpcore-worker, tomcat, dynflow-sidekiq@orchestrator, foreman, httpd, dynflow-sidekiq@worker-1, dynflow-sidekiq@worker-hosts-queue-1, foreman-proxy / displaying redis [OK] / displaying postgresql [OK] / displaying pulpcore-api [OK] / displaying pulpcore-content [OK] / displaying pulpcore-worker [OK] / displaying pulpcore-worker [OK] / displaying pulpcore-worker [OK] / displaying pulpcore-worker [OK] / displaying pulpcore-worker [OK] / displaying pulpcore-worker [OK] / displaying pulpcore-worker [OK] / displaying pulpcore-worker [OK] / displaying tomcat [OK] / displaying dynflow-sidekiq@orchestrator [OK] / displaying foreman [OK] / displaying httpd [OK] / displaying dynflow-sidekiq@worker-1 [OK] / displaying dynflow-sidekiq@worker-hosts-queue-1 [OK] - displaying foreman-proxy [OK] - All services are running [OK] --------------------------------------------------------------------------------