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:
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
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