Bug 1811633

Summary:	OSP16 \| STF \| Currently ceilometer can't be deployed with QDR because there is no redis deployed. Enable the pacemaker version in ceilometer-write -qdr
Product:	Red Hat OpenStack	Reporter:	Leonid Natapov <lnatapov>
Component:	openstack-tripleo-heat-templates	Assignee:	Martin Magr <mmagr>
Status:	CLOSED ERRATA	QA Contact:	Leonid Natapov <lnatapov>
Severity:	high	Docs Contact:
Priority:	high
Version:	16.0 (Train)	CC:	csibbitt, mburns, mmagr
Target Milestone:	z2	Keywords:	Triaged
Target Release:	16.0 (Train on RHEL 8.1)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	DFG:CloudOps
Fixed In Version:	openstack-tripleo-heat-templates-11.3.2-0.20200316143449.69c07ca.el8ost	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-05-14 12:16:18 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:
Bug Depends On:	1771000
Bug Blocks:

Description Leonid Natapov 2020-03-09 11:45:54 UTC

OSP16 | STF | Currently ceilometer can not be deployed with QDR because there is no redis deployed  We need to enable the pacemaker version in ceilometer-write -qdr.

Actual Results:
QDR and ceilometer fails to deploy on controllers.

Expected Results:
QDR and ceilometer can be successfully deployed on all overcloud nodes.

Comment 7 Leonid Natapov 2020-04-23 05:07:51 UTC

ceilometer-write-qdr successfully deployed 


Following templates were used:

  --environment-file /usr/share/openstack-tripleo-heat-templates/environments/disable-panko.yaml \
  --environment-file /usr/share/openstack-tripleo-heat-templates/environments/metrics/qdr-edge-only.yaml \
  --environment-file /usr/share/openstack-tripleo-heat-templates/environments/metrics/ceilometer-write-qdr.yaml \

Comment 11 errata-xmlrpc 2020-05-14 12:16:18 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-2020:2114