Description of problem: goferd continually connects and disconnects to qdrouterd Version-Release number of selected component (if applicable): 6.2.6 How reproducible: Intermittent Steps to Reproduce: This has been reproduced during errata install via katello-agent with an isolated capsule. It has also been reproduced with internal capsule, as described in the attached redmine. Restarting goferd on the client has been shown to temporarily fix the issue. Actual results: Feb 2 13:49:04 hostname goferd: [INFO][pulp.agent.id-number-hidden] gofer.messaging.adapter.connect:35 - retry in 10 seconds Feb 2 13:49:14 hostname goferd: [INFO][pulp.agent.id-number-hidden] gofer.messaging.adapter.connect:28 - connecting: proton+amqps://centosrhelupdateserver.domain.tld:5647 Feb 2 13:49:14 hostname goferd: [INFO][pulp.agent.id-number-hidden] gofer.messaging.adapter.proton.connection:87 - open: URL: amqps://centosrhelupdateserver.domain.tld:5647|SSL: ca: /etc/rhsm/ca/katello-default-ca.pem|key: None|certificate: /etc/pki/consumer/bundle.pem|host-validation: None Feb 2 13:49:14 hostname goferd: [INFO][pulp.agent.id-number-hidden] root:485 - connecting to centosrhelupdateserver.domain.tld:5647... Feb 2 13:50:17 hostname goferd: [INFO][pulp.agent.id-number-hidden] root:525 - Disconnected Feb 2 13:50:17 hostname goferd: [ERROR][pulp.agent.id-number-hidden] gofer.messaging.adapter.connect:33 - connect: proton+amqps://centosrhelupdateserver.domain.tld:5647, failed: Connection amqps://centosrhelupdateserver.domain.tld:5647 disconnected Expected results: goferd should be able to connect and communicate with pulp Additional info:
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/18386 has been resolved.
We are currently shipping qpid-proton-0.9-16 that includes the above mentioned fixes. The main remaining issue around gofer stability we are still tracking is: https://bugzilla.redhat.com/show_bug.cgi?id=1318015 Going to close this as currentrelease on 6.2.9 or later. Please re-open if this is still occurring on 6.2.9 or later releases.