Verified on 6.8.6 Snap1 1- Upgrade the satellite to 6.8.6 2- Restarted qpidd.service on the satellite. 3- Checked the "journalctl -u qpidd.service -f logs", didn't see any socket error. # journalctl -u qpidd.service -f -- Logs begin at Fri 2021-04-02 20:09:33 EDT. -- Apr 06 04:13:19 XYZ.com systemd[1]: Starting An AMQP message broker daemon.... Apr 06 04:13:23 XYZ.com systemd[1]: Started An AMQP message broker daemon.. Apr 06 04:14:24 XYZ.com systemd[1]: Stopping An AMQP message broker daemon.... Apr 06 04:14:24 XYZ.com systemd[1]: Stopped An AMQP message broker daemon.. Apr 06 04:14:24 XYZ.com systemd[1]: Starting An AMQP message broker daemon.... Apr 06 04:14:27 XYZ.com systemd[1]: Started An AMQP message broker daemon.. Apr 06 04:14:39 XYZ.com systemd[1]: Stopping An AMQP message broker daemon.... Apr 06 04:14:39 XYZ.com systemd[1]: Stopped An AMQP message broker daemon.. Apr 06 04:14:39 XYZ.com systemd[1]: Starting An AMQP message broker daemon.... Apr 06 04:14:43 XYZ.com systemd[1]: Started An AMQP message broker daemon.. 4- Checked the fixed package. # rpm -qa|grep foreman-installer-2.1.2.14-1 foreman-installer-2.1.2.14-1.el7sat.noarch
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.8.6 Async 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/RHBA-2021:1181