Project

General

Profile

Bug #10023

qpid-dispatch isn't deployed with katello 2.2

Added by Andrew Lau over 5 years ago. Updated over 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
Difficulty:
Triaged:
Yes
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:

Description

Deployed katello 2.2 on CentOS 6.6 and the qpid-dispatch router isn't installed, I have no config file /etc/qpid-dispatch and no service running on the port 5647 with the gofred

History

#1 Updated by Stephen Benjamin over 5 years ago

  • Status changed from New to Need more information

Can you attach a foreman-debug here or upload it when prompted by the tool? I'd like to see the output of the installation, and other system info. Did you have any errors? Is this an upgrade? You followed the instructions on the web site if it was an upgrade?

#2 Updated by Stephen Benjamin over 5 years ago

  • Status changed from Need more information to New

Disregard, we found the problem. Looks like we dropped the ball on this, and the dispatch router stuff didn't make the installer in the RC, so a bunch of things are broken :-( It'll make the next release of 2.2.

Thanks for letting us know about it.

#3 Updated by Eric Helms over 5 years ago

  • Legacy Backlogs Release (now unused) set to 23
  • Triaged changed from No to Yes

#4 Updated by Eric Helms over 5 years ago

  • Status changed from New to Need more information

This should be fixed for RC3 - if you are able to test it, and find this resolved please update status to 'Resolved' or ping me and I can update it. Thanks!

#5 Updated by Andrew Lau over 5 years ago

Eric Helms wrote:

This should be fixed for RC3 - if you are able to test it, and find this resolved please update status to 'Resolved' or ping me and I can update it. Thanks!

Upgraded to RC3 and it appears to be fixed :)

#6 Updated by Andrew Lau over 5 years ago

Service is now deployed with the installer, but after a reboot and some time has passed the connection error returns, still debugging why this occurs..
Service is running and firewall is not blocking the port.

Apr 8 21:49:34 katello1 goferd: [INFO][MainThread] gofer.messaging.adapter.proton.connection:100 - connecting: URL: amqps://katello1.prod.example.net:5647|SSL: ca: /etc/rhsm/ca/katello-server-ca.pem|key: None|certificate: /etc/pki/consumer/bundle.pem|host-validation: None
Apr 8 21:49:34 katello1 goferd: [INFO][MainThread] root:473 - connecting to katello1.prod.example.net:5647...
Apr 8 21:49:34 katello1 goferd: [INFO][MainThread] root:513 - Disconnected
Apr 8 21:49:34 katello1 goferd: [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - amqps://katello1.prod.example.net:5647
Apr 8 21:49:34 katello1 goferd: [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - Traceback (most recent call last):
Apr 8 21:49:34 katello1 goferd: [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - File "/usr/lib/python2.7/site-packages/gofer/messaging/adapter/proton/connection.py", line 102, in open
Apr 8 21:49:34 katello1 goferd: [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - self._impl = BlockingConnection(url, ssl_domain=domain)
Apr 8 21:49:34 katello1 goferd: [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - File "/usr/lib64/python2.7/site-packages/proton/utils.py", line 197, in init
Apr 8 21:49:34 katello1 goferd: [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - msg="Opening connection")
Apr 8 21:49:34 katello1 goferd: [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - File "/usr/lib64/python2.7/site-packages/proton/utils.py", line 228, in wait
Apr 8 21:49:34 katello1 goferd: [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - self.container.process()
Apr 8 21:49:34 katello1 goferd: [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - File "/usr/lib64/python2.7/site-packages/proton/__init__.py", line 3725, in dispatch
Apr 8 21:49:34 katello1 goferd: [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - ev.dispatch(self.handler)
Apr 8 21:49:34 katello1 goferd: [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - File "/usr/lib64/python2.7/site-packages/proton/__init__.py", line 3650, in dispatch
Apr 8 21:49:34 katello1 goferd: [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - result = dispatch(handler, type.method, self)
Apr 8 21:49:34 katello1 goferd: [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - File "/usr/lib64/python2.7/site-packages/proton/__init__.py", line 3539, in dispatch
Apr 8 21:49:34 katello1 goferd: [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - return m(*args)
Apr 8 21:49:34 katello1 goferd: [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - File "/usr/lib64/python2.7/site-packages/proton/utils.py", line 249, in on_transport_tail_closed
Apr 8 21:49:34 katello1 goferd: [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - self.on_transport_closed(event)
Apr 8 21:49:34 katello1 goferd: [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - File "/usr/lib64/python2.7/site-packages/proton/utils.py", line 253, in on_transport_closed
Apr 8 21:49:34 katello1 goferd: [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - raise ConnectionException("Connection %s disconnected" % self.url);
Apr 8 21:49:34 katello1 goferd: [ERROR][MainThread] gofer.messaging.adapter.proton.connection:106 - ConnectionException: Connection amqps://katello1.prod.example.net:5647 disconnected
Apr 8 21:49:34 katello1 goferd: [INFO][MainThread] gofer.messaging.adapter.proton.connection:108 - retry in 106 seconds

#7 Updated by Eric Helms over 5 years ago

Was that traceback from an agent? Do you see anything on the server logs related to qpid or qdrouterd crashing?

#8 Updated by Andrew Lau over 5 years ago

That was from the log of the server running katello-agent as well. Does qpid or qdrouterd also post messages to /var/log/messages ? If so I didn't see anything relating to them crashing.

#9 Updated by Eric Helms over 5 years ago

Making sure I setup the right reproducer, is the following correct:

1 Katello 2.2 RC3
1 client machine (that is not a capsule or the main server) with katello-agent installed

Any other conditions in your setup? Does the error happen during an action perform or just in the logs after installing katello-agent?

#10 Updated by Andrew Lau over 5 years ago

Haven't seen it recently after fresh RC3 deploy.

It would just appear in the logs, and I was testing on katello server (main) with katello-agent installed connecting to self.

#11 Updated by Eric Helms over 5 years ago

  • Status changed from Need more information to Resolved

I am going to set this issue to resolved based on the original bug, if you see the disconnect happen again lets open a new bug dedicated to it.

Also available in: Atom PDF