Bug 833859 - [OSS] broker and node unable to reboot due to configuration is not persistent.
Summary: [OSS] broker and node unable to reboot due to configuration is not persistent.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OKD
Classification: Red Hat
Component: Pod
Version: 2.x
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Krishna Raman
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-06-20 13:28 UTC by Johnny Liu
Modified: 2015-05-15 01:58 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-25 18:26:55 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Johnny Liu 2012-06-20 13:28:13 UTC
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):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Krishna Raman 2012-06-20 20:31:39 UTC
Fixed. However, if reboot causes the IP address of broker or node to change then you will need to run the setup scripts again.

Comment 2 Peter Ruan 2012-06-21 04:28:23 UTC
verified by rebooting my nodes multiple times and they come back everytime.


Note You need to log in before you can comment on or make changes to this bug.