Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1098493

Summary: Packstack/puppets modify incorrect qpidd.conf
Product: Red Hat OpenStack Reporter: Pavel Sedlák <psedlak>
Component: openstack-packstackAssignee: Martin Magr <mmagr>
Status: CLOSED DUPLICATE QA Contact: Ami Jeain <ajeain>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 5.0 (RHEL 7)CC: aortega, derekh, freznice, mmagr, pematous, yeylon, zkraus
Target Milestone: ---   
Target Release: 5.0 (RHEL 7)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-05-28 11:06:51 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 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 ***