Bug 1026086

Summary:	rerunning packstack will generate a new ssl file for horizon
Product:	[Community] RDO	Reporter:	Mohammed Arafa <bugzilla>
Component:	openstack-packstack	Assignee:	Ivan Chavero <ichavero>
Status:	CLOSED NOTABUG	QA Contact:	Nir Magnezi <nmagnezi>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	aortega, derekh, ichavero, yeylon
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:	2014-01-15 07:25:55 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 Mohammed Arafa 2013-11-03 14:47:43 UTC

Description of problem:
rerunning packstack will generate a new ssl file for horizon

i did this first
sed -i 's/CONFIG_HORIZON_SSL=n/CONFIG_HORIZON_SSL=y/g' packstack.answer
 then ran packstack

i then logged into the horizon dashboard and accepted the ssl file

later i decided to enable the demo user and add in the cirros image so i modifed the answer file and re ran packstack

i then logged into the horizon dashboard and accepted the _NEW_ ssl file

so thinking ahead one year from now, we _will_ need to generate a new ssl file so maybe a config option like "generate new ssl file for horizon =y" should be included ?

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Ivan Chavero 2014-01-15 07:25:55 UTC

Packstack generates self signed SSL certificates, this certificates are just for testing and they are not suppoused to be used in production. If you need a long term certificate you should get a verified certficate from verisign or create your CA and sign your certificates. And then add them to packstack answer file.