Bug 1441738 - aodh configured via wsgi causes httpd restart on updates
Summary: aodh configured via wsgi causes httpd restart on updates
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: puppet-aodh
Version: 10.0 (Newton)
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: z3
: 10.0 (Newton)
Assignee: Alex Schultz
QA Contact: Amit Ugol
URL:
Whiteboard:
Depends On:
Blocks: 1421883 1441736 1441760 1441769 1446511
TreeView+ depends on / blocked
 
Reported: 2017-04-12 15:12 UTC by Alex Schultz
Modified: 2017-06-28 14:48 UTC (History)
9 users (show)

Fixed In Version: puppet-aodh-9.5.0-2.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1441736
Environment:
Last Closed: 2017-06-28 14:48:28 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1664418 0 None None None 2017-04-12 15:11:59 UTC
OpenStack gerrit 453431 0 None None None 2017-04-12 15:11:59 UTC
Red Hat Product Errata RHBA-2017:1585 0 normal SHIPPED_LIVE Red Hat OpenStack Platform 10 director Bug Fix Advisory 2017-06-28 18:42:51 UTC

Description Alex Schultz 2017-04-12 15:12:00 UTC 
This is the bug for the puppet-aodh prereq

+++ This bug was initially created as a clone of Bug #1441736 +++

Description of problem:
The aodh deployment via wsgi is configured in step4 of the deployment process but httpd is configured in step3 so during updates httpd is restarted multiple times on controllers.

Version-Release number of selected component (if applicable):
puppet-aodh-9.5.0-1.el7ost
Comment 3 errata-xmlrpc 2017-06-28 14:48:28 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-2017:1585
Note You need to log in before you can comment on or make changes to this bug.