Hide Forgot
Description of problem: qdrouterd plays important role in katello communication between Satellite and Capsule / Content Hosts. In case its config is malformed (or e.g. lacks some option after failing upgrade), various issues can occur that are hard to be identified without the config file. Please collect /etc/qpid-dispatch/qdrouterd.conf Version-Release number of selected component (if applicable): katello-debug-3.0.0-3.el7sat.noarch How reproducible: 100% Steps to Reproduce: 1. foreman-debug 2. Unpack it 3. Check if /etc/qpid-dispatch/qdrouterd.conf is present Actual results: No /etc/qpid-dispatch/qdrouterd.conf collected. Expected results: /etc/qpid-dispatch/qdrouterd.conf to be collected Additional info: Proposing patch: --- /usr/share/foreman/script/foreman-debug.d/katello-debug.sh 2016-04-01 17:19:17.000000000 +0200 +++ /usr/share/foreman/script/foreman-debug.d/katello-debug.sh.new 2016-04-28 11:05:07.863000000 +0200 @@ -55,6 +55,9 @@ fi add_cmd "qpid-stat --ssl-certificate=/etc/pki/katello/qpid_client_striped.crt -b amqps://localhost:5671 -q" "qpid_stat_queues" add_cmd "qpid-stat --ssl-certificate=/etc/pki/katello/qpid_client_striped.crt -b amqps://localhost:5671 -u" "qpid_stat_subscriptions" +# Qpid dispatch router (*) +add_files /etc/qpid-dispatch/qdrouterd.conf + # Gofer add_files /etc/gofer add_files /var/log/gofer (in longer term, there should be "if [ $NOGENERIC -eq 0 ]; then" clause but until sosreport collects the file in downstream (matter of 1-2 years, due to [1]), I suggest collecting it every time in foreman-debug) [1] https://github.com/sosreport/sos/issues/623
*** Bug 1331301 has been marked as a duplicate of this bug. ***
Created redmine issue http://projects.theforeman.org/issues/14881 from this bug
Moving to POST since upstream bug http://projects.theforeman.org/issues/14881 has been closed
~]# tar xvf /tmp/foreman-debug-ZA9ep.tar.xz | grep -i qdrouterd foreman-debug-ZA9ep/etc/qpid-dispatch/qdrouterd.conf VERIFIED with sat62-sna12.1
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-2016:1501