Red Hat Bugzilla – Bug 1017839
Backing up /etc/openshift/ should be mentioned in Procedure 3.6. Recovering a Failed Node Host
Last modified: 2015-07-19 20:23:05 EDT
Description of problem:
There is no mention of backing up /etc/openshift. There are important configs under that directory, some of which are specific to a particular node. eg, /etc/openshift/port-proxy.cfg
I hesitate to add anything about backing up /etc/openshift as it's not strictly required - that's all standard config that can be easily reproduced and if they have an automated method for creating nodes, it would be generated as part of that. The only thing unique to a node in there is the public hostname and IP which they'd have from other records.
AFAICS /etc/openshift/port-proxy.cfg and /etc/openshift/node.conf are otherwise generic.
"Just keep /var/lib/openshift on an external volume" is such simple advice that I'd hate to complicate it.
(In reply to Luke Meyer from comment #6)
> The only thing unique to a node in there is the
> public hostname and IP which they'd have from other records.
Turns out /etc/openshift/port-proxy.cfg DOES have node-specific stuff in it. It probably shouldn't be there, but it is for now, so ignore c6 and continue on.