Description of problem:
An update of ccsd with a cluster.conf version that is equal to or less
than the current verion in memory, that node will revert all the way
back to version "1" (or what ever version the original file was) and
be out of sync with the rest of the cluster which is left at the
current verion in memory.
Version-Release number of selected component (if applicable):
Expected Results: It should just fail, keep the current verion in
memory, and write out a reject file for the one attempting to update
this some how got opened again by a reload of the browser
Updating version to the right level in the defects. Sorry for the storm.