Red Hat Bugzilla – Bug 833859
[OSS] broker and node unable to reboot due to configuration is not persistent.
Last modified: 2015-05-14 21:58:42 EDT
Description of problem:
Following http://www.krishnaraman.net/multi-node-openshift-origin-from-scratch/ to setup Multi-node OpenShift Origin PaaS from scratch.
After multi-node env is setup, broker and node machine can not be rebooted, once reboot, the multi-node env is broken.
for broker, after reboot, named can not be started up due to /var/named/forwarders.conf syntax error, looks like forwarders.conf is restored after reboot.
and /etc/resolve.conf will be re-writen by dhclient.
From now on, user must re-run ss-setup-broker, ss-setup-node and ss-register-dns commands.
We need figure out a method to make these configuration persistent.
BTW, in the instruction,
3. Restart the node environment so that it can start services
If user follow this, due to /etc/resolve.conf is re-writen, that will cause mcolective connection is broken.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Fixed. However, if reboot causes the IP address of broker or node to change then you will need to run the setup scripts again.
verified by rebooting my nodes multiple times and they come back everytime.