Bug 1347827 - For RHOS 8 -> 9 upgrades the keystone module in liberty needs keystone::wsgi::apache::admin_bind_host param
Summary: For RHOS 8 -> 9 upgrades the keystone module in liberty needs keystone::wsgi:...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-puppet-modules
Version: 8.0 (Liberty)
Hardware: All
OS: Linux
urgent
urgent
Target Milestone: async
: 8.0 (Liberty)
Assignee: Emilien Macchi
QA Contact: Alexander Chuzhoy
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-06-17 18:26 UTC by Michele Baldessari
Modified: 2016-09-30 07:30 UTC (History)
6 users (show)

Fixed In Version: openstack-puppet-modules-7.1.2-1.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-20 19:53:02 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:1471 0 normal SHIPPED_LIVE openstack-puppet-modules bug fix advisory 2016-07-20 23:52:15 UTC

Description Michele Baldessari 2016-06-17 18:26:30 UTC 
Description of problem:
In order to upgrade RHOS8 to RHOS9 there is a step before we upgrade all
the packages on the controllers, where we need to move keystone under wsgi.

This step has to be done using liberty puppet modules (as we have not upgraded
yet).

So we need to include a backport for this:
https://bugs.launchpad.net/puppet-keystone/+bug/1592060

The review has already landed in upstream stable/liberty but we need it in a released rpm as well
https://review.openstack.org/#/c/329114/
Comment 3 Alexander Chuzhoy 2016-07-20 15:52:18 UTC 
Verified:
Environment:
openstack-puppet-modules-7.1.2-1.el7ost.noarch


Verified that /usr/share/openstack-puppet/modules/keystone/manifests/wsgi/apache.pp has all the changes from https://review.openstack.org/#/c/329114/
Comment 5 errata-xmlrpc 2016-07-20 19:53:02 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.

https://access.redhat.com/errata/RHBA-2016:1471
Note You need to log in before you can comment on or make changes to this bug.