Bug 1294685

Summary:	Keystone errors and warnings are dumped to the console when deploying an overcloud
Product:	Red Hat OpenStack	Reporter:	Udi Kalifon <ukalifon>
Component:	python-tripleoclient	Assignee:	RHOS Maint <rhos-maint>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Shai Revivo <srevivo>
Severity:	medium	Docs Contact:
Priority:	low
Version:	8.0 (Liberty)	CC:	aschultz, brad, hbrock, jcoufal, jslagle, mburns, rhel-osp-director-maint
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-03-21 00:44:23 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:

Description Udi Kalifon 2015-12-29 16:50:27 UTC

Description of problem:
After the deployment finishes you see the following messages on the console:

The following cert files already exist, use --rebuild to remove the existing files before regenerating:
/etc/keystone/ssl/certs/ca.pem already exists
/etc/keystone/ssl/private/signing_key.pem already exists
/etc/keystone/ssl/certs/signing_cert.pem already exists

The errors might be harmless, I don't know how or what to test to find out if it's really a problem or not.


Version-Release number of selected component (if applicable):
python-tripleoclient-0.0.11-5.el7ost.noarch


How reproducible:
100%


Steps to Reproduce:
1. Deploy an overcloud

Comment 2 Mike Burns 2016-04-07 21:03:37 UTC

This bug did not make the OSP 8.0 release.  It is being deferred to OSP 10.

Comment 4 James Slagle 2016-10-14 15:16:13 UTC

Removing from OSP10, not a blocker/regression.

Further, I think this issue may be fixes since we no longer generate those keystone certificates locally via the client. Brad, can you confirm?

Comment 5 Brad P. Crochet 2017-03-21 00:44:23 UTC

I concur. Shouldn't be an issue anymore.