Bug 1034362 - Glance appears to ignore qpid_host setting in glance-api.conf
Summary: Glance appears to ignore qpid_host setting in glance-api.conf
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-glance
Version: 4.0
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: z4
: 3.0
Assignee: Flavio Percoco
QA Contact: Yogev Rabl
URL:
Whiteboard:
Depends On: 1020025
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-25 16:51 UTC by Scott Lewis
Modified: 2019-09-10 14:08 UTC (History)
9 users (show)

Fixed In Version: openstack-glance-2013.1.4-2.el6ost
Doc Type: Bug Fix
Doc Text:
Cause: The Image Service configuration file exposed the wrong parameter name for qpid's host. Consequence: The Image Service notification service wouldn't connect to qpid nodes. Fix: Replaced qpid_host with qpid_hostname in glance-api. Result: The qpid nodes operate as expected.
Clone Of: 1020025
Environment:
Last Closed: 2014-01-30 19:49:57 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 52931 0 None None None Never
OpenStack gerrit 54339 0 None None None Never
OpenStack gerrit 56208 0 None None None Never
Red Hat Product Errata RHBA-2014:0110 0 normal SHIPPED_LIVE Red Hat Enterprise Linux OpenStack Platform 3 bug fix advisory 2014-01-31 00:48:26 UTC

Comment 2 Yogev Rabl 2014-01-26 18:34:39 UTC 
The bug was verified: 
version: 
python-glanceclient-0.9.0-2.el6ost.noarch
python-glance-2013.1.4-2.el6ost.noarch
openstack-glance-2013.1.4-2.el6ost.noarch
Comment 4 errata-xmlrpc 2014-01-30 19:49:57 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2014-0110.html
Note You need to log in before you can comment on or make changes to this bug.