Bug 1098493 - Packstack/puppets modify incorrect qpidd.conf
Summary: Packstack/puppets modify incorrect qpidd.conf
Keywords:
Status: CLOSED DUPLICATE of bug 1097306
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-packstack
Version: 5.0 (RHEL 7)
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 5.0 (RHEL 7)
Assignee: Martin Magr
QA Contact: Ami Jeain
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-05-16 11:14 UTC by Pavel Sedlák
Modified: 2014-09-08 05:43 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-05-28 11:06:51 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Pavel Sedlák 2014-05-16 11:14:43 UTC
When installing via packstack, with AMQ=qpid (qpid from brew),
at the end there are two qpidd.conf files:

- /etc/qpidd.conf (used by qpid proc) < deployed by qpid-cpp-server pkg
    cluster-mechanism=DIGEST-MD5 ANONYMOUS
    acl-file=/etc/qpid/qpidd.acl
    auth=yes
- /etc/qpid/qpidd.conf < no owner pkg (packstack/puppets?)
    auth=no

Probably it's related to that on fedora/epel/or-something-else we can have newer qpid which has different location of config (/etc/qpid/qpidd.conf)?
So probably packstack/puppets will have to support both locations?
Or should qpid-cpp-server-0.18 ship/use also /etc/qpid/qpidd.conf?


Name        : openstack-packstack
Version     : 2014.1.1
Release     : 0.11.1.dev1055.el7ost

Name        : openstack-puppet-modules
Version     : 2014.1
Release     : 9.el7ost

Name        : qpid-cpp-server
Version     : 0.18
Release     : 22.el7

Comment 2 Petr Matousek 2014-05-20 15:30:57 UTC
Note: having symbolic link /etc/qpid/qpidd.conf -> /etc/qpidd.conf do not solve the installation issue. Please see bug 1097306, comment 15 for details.

Comment 3 Martin Magr 2014-05-28 11:06:51 UTC

*** This bug has been marked as a duplicate of bug 1097306 ***


Note You need to log in before you can comment on or make changes to this bug.