Bug 1437207

Summary:	When ceilometer Api is disabled, ceilometer user is not created causing stuff to fail
Product:	Red Hat OpenStack	Reporter:	Pradeep Kilambi <pkilambi>
Component:	puppet-tripleo	Assignee:	Pradeep Kilambi <pkilambi>
Status:	CLOSED ERRATA	QA Contact:	Sasha Smolyak <ssmolyak>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	11.0 (Ocata)	CC:	jjoyce, jschluet, mburns, pkilambi, slinaber, tvignaud
Target Milestone:	rc	Keywords:	Triaged
Target Release:	11.0 (Ocata)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-tripleo-heat-templates-6.0.0-4.el7ost puppet-tripleo-6.3.0-9.el7ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-05-17 20:15:56 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:
Bug Blocks:	1382700

Description Pradeep Kilambi 2017-03-29 18:52:19 UTC

When we deploy overcloud with disbale-ceilometer-api.yaml , it skips the cceilometer-api service. But that ties in with ceilometer user. So ceilometer user is not created in keystone. But since we still configure ceilometer.conf with ceilometer user, keystone auth fails when ceilometer-upgrade is run to talk to gnocchi.

Need to figure out how we can decouple ceilometer user creation from ceilometer API.

This seems to be in puppet-tripleo

https://github.com/openstack/puppet-tripleo/blob/master/manifests/profile/base/keystone.pp#L249-L251

Comment 1 Pradeep Kilambi 2017-03-29 18:59:05 UTC

Note more than ceilometer-upgrade fails, including agents when dispatching data.

Comment 4 Jon Schlueter 2017-04-07 14:40:05 UTC

For Beta of OSP 11 we can not disable ceilometer api due to this bug.

Comment 12 Sasha Smolyak 2017-04-23 12:40:42 UTC

Sanity tests with ceilo api disabled passed

Comment 13 errata-xmlrpc 2017-05-17 20:15:56 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/RHEA-2017:1245