Bug 1492355
Summary: | sporadic deadlock of qdrouterd on bursts of goferd (dis)connection requests | |||
---|---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Pavel Moravec <pmoravec> | |
Component: | Qpid | Assignee: | Mike Cressman <mcressma> | |
Status: | CLOSED ERRATA | QA Contact: | Roman Plevka <rplevka> | |
Severity: | high | Docs Contact: | ||
Priority: | high | |||
Version: | 6.2.11 | CC: | bbuckingham, egolov, ehelms, luislgf, lzap, mcressma, mmithaiw, rplevka, tross, xdmoon | |
Target Milestone: | Unspecified | Keywords: | Triaged | |
Target Release: | Unused | |||
Hardware: | x86_64 | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | qpid-dispatch-0.4-27 | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1530689 (view as bug list) | Environment: | ||
Last Closed: | 2018-02-05 13:55:32 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: |
Description
Pavel Moravec
2017-09-16 19:26:59 UTC
I believe this was fixed in DISPATCH-518. https://issues.apache.org/jira/browse/DISPATCH-518 pre-verified as fixed in a build: https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=600616 (qpid-dispatch-0.4-27.el7sat) VERIFIED on satellite-6.2.14-1.0.el7sat.noarch I also tried the following: - create a docker image with rhel with installed katello-consumer-ca and installed katello-agent (yet not registered to satellite) - as a startup script, run subscription-manager registration and append a conditional loop that will start up the gofer daemon on some sort of trigger (i mounted an external dir and made a conditional to check for a presence of some file). - start up many containers (tried with 10,30,50). - after all the containers are up and their registration is finished (verify by listing the content hosts in satellite and that there are no more requests arriving to /rhsm endpoint), pull the trigger (in my case, create the file) to break the waiting loop, that would run goferd on all containers simultaneously. - observe the number pulp.agent* queues bumps by the number of the running containers in a moment - watch the logs for any errors - no erorrs detected 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-2018:0273 |