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.
DescriptionCristian Muresanu
2018-12-08 17:20:21 UTC
Description of problem:
katello-agent failed to connect because qdrouterd it is not listening to an IPv6 address (it's listening just to an IPv4 address)
Version-Release number of selected component (if applicable):
Saltelit 6.2
katello-ca-consumer-scgxp0287cld.prod.cloud.ihf-1.0-1.noarch
katello-host-tools-3.0.2-1.el7sat.noarch
katello-host-tools-fact-plugin-3.0.2-1.el7sat.noarch
katello-agent-3.0.2-1.el7sat.noarch
How reproducible:
netstat -tlpn | grep qdrouterd
tcp 0 0 0.0.0.0:5646 0.0.0.0:* LISTEN 19584/qdrouterd
changing the "listener" in /etc/qpid-dispatch/qdrouterd.conf doesn't work, we'll get the same results.
from
listener {
addr: 0.0.0.0
port: 5647
sasl-mechanisms: ANONYMOUS
ssl-profile: server
}
to
listener {
addr: ::
port: 5647
sasl-mechanisms: ANONYMOUS
ssl-profile: server
}
=> Same results, won't work
Steps to Reproduce:
1.
2.
3.
Actual results:
Nov 29 23:51:45 scgsd0003cld goferd: [INFO][worker-0] gofer.messaging.adapter.connect:28 - connecting: proton+amqps://scgxp0287cld.prod.cloud.ihf:5647
Nov 29 23:51:45 scgsd0003cld goferd: [INFO][worker-0] gofer.messaging.adapter.proton.connection:87 - open: URL: amqps://scgxp0287cld.prod.cloud.ihf:5647|SSL: ca: /etc/rhsm/ca/katello-default-ca.pem|key: None|certificate: /etc/pki/consumer/bundle.pem|host-validation: None
Nov 29 23:51:45 scgsd0003cld goferd: [INFO][worker-0] root:498 - connecting to scgxp0287cld.prod.cloud.ihf:5647...
Nov 29 23:51:45 scgsd0003cld goferd: [INFO][worker-0] root:542 - Disconnected
Nov 29 23:51:45 scgsd0003cld goferd: [ERROR][worker-0] gofer.messaging.adapter.connect:33 - connect: proton+amqps://scgxp0287cld.prod.cloud.ihf:5647, failed: Connection amqps://scgxp0287cld.prod.cloud.ihf:5647 disconnected
Nov 29 23:51:45 scgsd0003cld goferd: [INFO][worker-0] gofer.messaging.adapter.connect:35 - retry in 12 seconds
Expected results:
No Error
Additional info:
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/RHSA-2019:1222
Description of problem: katello-agent failed to connect because qdrouterd it is not listening to an IPv6 address (it's listening just to an IPv4 address) Version-Release number of selected component (if applicable): Saltelit 6.2 katello-ca-consumer-scgxp0287cld.prod.cloud.ihf-1.0-1.noarch katello-host-tools-3.0.2-1.el7sat.noarch katello-host-tools-fact-plugin-3.0.2-1.el7sat.noarch katello-agent-3.0.2-1.el7sat.noarch How reproducible: netstat -tlpn | grep qdrouterd tcp 0 0 0.0.0.0:5646 0.0.0.0:* LISTEN 19584/qdrouterd changing the "listener" in /etc/qpid-dispatch/qdrouterd.conf doesn't work, we'll get the same results. from listener { addr: 0.0.0.0 port: 5647 sasl-mechanisms: ANONYMOUS ssl-profile: server } to listener { addr: :: port: 5647 sasl-mechanisms: ANONYMOUS ssl-profile: server } => Same results, won't work Steps to Reproduce: 1. 2. 3. Actual results: Nov 29 23:51:45 scgsd0003cld goferd: [INFO][worker-0] gofer.messaging.adapter.connect:28 - connecting: proton+amqps://scgxp0287cld.prod.cloud.ihf:5647 Nov 29 23:51:45 scgsd0003cld goferd: [INFO][worker-0] gofer.messaging.adapter.proton.connection:87 - open: URL: amqps://scgxp0287cld.prod.cloud.ihf:5647|SSL: ca: /etc/rhsm/ca/katello-default-ca.pem|key: None|certificate: /etc/pki/consumer/bundle.pem|host-validation: None Nov 29 23:51:45 scgsd0003cld goferd: [INFO][worker-0] root:498 - connecting to scgxp0287cld.prod.cloud.ihf:5647... Nov 29 23:51:45 scgsd0003cld goferd: [INFO][worker-0] root:542 - Disconnected Nov 29 23:51:45 scgsd0003cld goferd: [ERROR][worker-0] gofer.messaging.adapter.connect:33 - connect: proton+amqps://scgxp0287cld.prod.cloud.ihf:5647, failed: Connection amqps://scgxp0287cld.prod.cloud.ihf:5647 disconnected Nov 29 23:51:45 scgsd0003cld goferd: [INFO][worker-0] gofer.messaging.adapter.connect:35 - retry in 12 seconds Expected results: No Error Additional info: