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:
Assume scenario:
- a goferd client connects to qdrouterd
- qdrouterd does reverse DNS lookup (PTR query) for client's IP address against a DNS server
- assume the DNS server is broken, such that it does not reply to the query or replies after say one minute
- qdrouterd while waiting to the response stops send any AMQP data to any other connection
Consequences:
- that causes inter-qdrouterd connection timeouts due to unresponded heartbeats
- any communication between Satellite and katello-agent is postponed/delayed, causing optionally task timeouts
Please backport https://issues.apache.org/jira/browse/DISPATCH-443 once the fix is available.
Version-Release number of selected component (if applicable):
qpid-dispatch-router-0.4-11.el7.x86_64
How reproducible:
100%
Steps to Reproduce:
0. Setup Satellite with Capsule, either with external DNS server
1. Break your DNS server such that it does not respond (on time) to some DNS PTR queries (i.e. remove some IP range from its managed rages)
2. Kick off goferd on a client such that DNS PTR query against its IP address is responded after a long time or never.
3. Observe no communication can flow through the qdrouterd where the goferd is connecting to - including inter-qdrouterd communication or new task (package install) request.
Actual results:
- Package installs to other clients will timeout (assuming the DNS query is still being "processed").
- inter-qdrouterd connection flapping (see https://access.redhat.com/solutions/2429011 for particular logs)
Expected results:
- other clients can communicate with the qdrouterd, they can accept and acknowledge tasks (to istall a package) etc.
- inter-qdrouterd connection is stable
Additional info:
I am moving this to VERIFIED. We have not been able to reproduce the issue, and we have already deployed this code at certain customers with no negative imapct. Therefore, we are markign this as verified to deliver with 6.2.4. If you are still seeing this issue after 6.2.4 please feel free to re-open and provide additional information on how to reproduce.
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:2699
Comment 13Red Hat Bugzilla
2023-09-14 03:27:42 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days