Bug #22289
closed
foreman-installer deploys a non-working "qdrouterd.conf " after qpid-dispatch-router has been upgraded from 0.8.0-1.el7 to 1.0.0-1.el7 in epel repos
Description
after following the installation docs the service "qdrouterd" fails to start with this error:
"2018-01-14 23:22:56.581174 +0000 MAIN (critical) Router start-up failed: Python: Exception: Cannot load configuration file /etc/qpid-dispatch/qdrouterd.conf: No such entity type 'org.apache.qpid.dispatch.container'
The config works with previous version qpid-dispatch-router-0.8.0-1.el7.x86_64.rpm but since epel upgraded to qpid-dispatch-router-1.0.0-1.el7.x86_64.rpm it stopped working.
More users have reported the issue here: https://community.theforeman.org/t/qpid-broken-default-configuration/8052
Updated by Stephen Benjamin about 7 years ago
Was deprecated in favor of 'router', see https://qpid.apache.org/releases/qpid-dispatch-0.6.0/book/schema.html
We'll need to update the module
Updated by The Foreman Bot about 7 years ago
- Status changed from New to Ready For Testing
- Assignee set to Stephen Benjamin
- Pull request https://github.com/theforeman/puppet-qpid/pull/83 added
Updated by Justin Sherrill about 7 years ago
- Translation missing: en.field_release changed from 339 to 329
Updated by The Foreman Bot about 7 years ago
- Pull request https://github.com/theforeman/puppet-foreman_proxy_content/pull/155 added
Updated by Anonymous about 7 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset puppet-qpid|6a0450649716c317437c8e612fda2459fba8dd27.