Hide Forgot
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.
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.
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.
not a bug. closing