Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
First Last Prev Next    This bug is not in your last search results.
Bug 1322557 - Don't deploy aodh on the undercloud
Don't deploy aodh on the undercloud
Status: CLOSED ERRATA
Product: Red Hat OpenStack
Classification: Red Hat
Component: instack-undercloud (Show other bugs)
8.0 (Liberty)
Unspecified Unspecified
unspecified Severity unspecified
: ga
: 8.0 (Liberty)
Assigned To: James Slagle
Yurii Prokulevych
:
Depends On:
Blocks:
  Show dependency tree / graph
 
Reported: 2016-03-30 13:56 EDT by Mike Burns
Modified: 2016-04-07 17:50 EDT (History)
6 users (show)

See Also:
Fixed In Version: instack-undercloud-2.2.7-2.el7ost
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-04-07 17:50:10 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


External Trackers
Tracker ID Priority Status Summary Last Updated
OpenStack gerrit 299558 None None None 2016-03-30 13:58 EDT
Red Hat Product Errata RHEA-2016:0604 normal SHIPPED_LIVE Red Hat OpenStack Platform 8 director Enhancement Advisory 2016-04-07 21:03:56 EDT

  None (edit)
Description Mike Burns 2016-03-30 13:56:35 EDT 
Description of problem:
To avoid package conflicts, we shouldn't deploy aodh in OSP8.  The package conflicts will go away in OSP9 due to packaging, so we can include it there.

Version-Release number of selected component (if applicable):
Beta 9
Comment 3 Yurii Prokulevych 2016-04-04 07:11:57 EDT 
Verified with instack-undercloud-2.2.7-2.el7ost.noarch
aodh* packages ain't installed, dedicated user/tenant/service not created in keystone.
Comment 5 errata-xmlrpc 2016-04-07 17:50:10 EDT 
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://rhn.redhat.com/errata/RHEA-2016-0604.html
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.