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 randomly drops SSL connections either from goferd or for inter-qdrouterd connections. Further analysis indirectly proved the upstream PROTON-1587 is the cause.
Please backport the fix:
https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;a=commitdiff;h=c31ca95#patch1
to Satellite 6.3.1 / over qpid-proton-c-0.16.0-9.el7.x86_64
Version-Release number of selected component (if applicable):
Sat 6.3.1
qpid-proton-c-0.16.0-9
How reproducible:
???
Steps to Reproduce:
n.a.
Actual results:
random AMQP connection drops due to TCP/SSL connection drops with errors like:
Condition('amqp:connection:framing-error', 'SSL Failure: Unknown error')
Expected results:
No such errors
Additional info:
Jeff,
am I right this bug can affect also goferd that uses qpid-proton library? (and if so, does it mean the fix shall occur also in Sat tools repo, nt only in Sat and Caps repos)?
(In reply to Pavel Moravec from comment #4)
> Jeff,
> am I right this bug can affect also goferd that uses qpid-proton library?
> (and if so, does it mean the fix shall occur also in Sat tools repo, nt only
> in Sat and Caps repos)?
Yes, goferd uses proton. Yes, it needs to be in sat tools.
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-2018:1951