Bug 1041587

Summary:	oo-accept-broker failure points to incorrect conf file to fix
Product:	OpenShift Container Platform	Reporter:	Aaron Weitekamp <aweiteka>
Component:	Node	Assignee:	Luke Meyer <lmeyer>
Status:	CLOSED NOTABUG	QA Contact:	libra bugs <libra-bugs>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	2.0.0	CC:	aweiteka, bleanhar, libra-onpremise-devel
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-03 14:09: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 Aaron Weitekamp 2013-12-12 18:06:44 UTC

Description of problem:
running "oo-accept-broker -v" instructs admin to fix console.conf. Should be broker.conf.

Returns:
FAIL: SESSION_SECRET must be set in /etc/openshift/console.conf (Hint: use 'openssl rand -hex 64' to generate a unique secret.


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

openshift-origin-broker-1.15.1-2.el6op.noarch
openshift-origin-broker-util-1.17.5-2.el6op.noarch


How reproducible:
unclear


Steps to Reproduce:
1. Comment out SESSION_SECRET value in /etc/openshift/broker.conf
2. run oo-accept-broker -v

Actual results:
[root@broker1 broker]# oo-accept-broker -v
INFO: Broker package is: openshift-origin-broker
FAIL: SESSION_SECRET must be set in /etc/openshift/console.conf (Hint: use 'openssl rand -hex 64' to generate a unique secret.


Expected results:
[root@broker1 broker]# oo-accept-broker -v
INFO: Broker package is: openshift-origin-broker
FAIL: SESSION_SECRET must be set in /etc/openshift/broker.conf (Hint: use 'openssl rand -hex 64' to generate a unique secret.

Comment 2 Luke Meyer 2013-12-12 20:49:03 UTC

Hm - can you double-check? I did not see this result and the code looks right. Both of the conf files do need to have that set or oo-accept-broker will complain.

Comment 3 Brenton Leanhardt 2013-12-13 02:24:18 UTC

The Console and Broker must be installed on the same host.  oo-accept-console doesn't exist so some console checks are included as part of oo-accept-broker.

Comment 4 Aaron Weitekamp 2014-01-03 14:09:36 UTC

not a bug. closing