Bug 160169 - Restoring backup file and propagating new config causes extra backup file to be created
Restoring backup file and propagating new config causes extra backup file to ...
Status: CLOSED DEFERRED
Product: Red Hat Cluster Suite
Classification: Red Hat
Component: redhat-config-cluster (Show other bugs)
4
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jim Parsons
Cluster QE
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-06-12 11:25 EDT by Paul Kennedy
Modified: 2015-04-19 20:46 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-09-08 11:28:56 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Paul Kennedy 2005-06-12 11:25:21 EDT
Description of problem:

--------
Symptom
--------

Restoring a configuration file to an earlier version from a backup file
(/etc/cluster/cluster.conf.bak.1, /etc/cluster/cluster.conf.bak.2, or
/etc/cluster/cluster.conf.bak.3) causes an extra backup file to be created
because "Send to Cluster" includes saving file, and therefore backing up the file.

When you restore a file from a backup file, you need to do a "Save As" from the
backup file to /ect/cluster/cluster.conf. To propagate, you must click "Send to
Cluster", which automatically saves the configuration file. Therefore, when
restoring a file from a backup file you are forced to save the file twice,
thereby creating a backup file each time the file is saved. 

-----------
Workaround
-----------

None


Version-Release number of selected component (if applicable):
system-config-cluster 1.0.12 

How reproducible:


Steps to Reproduce:
1.  Remove all backup files from /etc/cluster/.
2.  At the Cluster Configuration tab, make a change to the configuration.
3.  Propagate the change by clicking "Send to Cluster" (acknowledging the 
    resultant dialog boxes with "Yes" or "OK").
4.  Observe that one backup file, /etc/cluster/cluster.conf.bak.1, has been
    created.
5.  Open backup file /etc/cluster/cluster.conf.bak.1:
    File => Open => /etc/cluster.conf.bak.1 => OK
6.  Restore to earlier configuration by saving backup file to
    /etc/cluster.conf:
    File => Save As => /etc/cluster.conf => OK, acknowledging resultant
    dialog box
7.  Observe that two backup files exist now: /etc/cluster/cluster.conf.bak.1
    and /etc/cluster/cluster.conf.bak.2.
8.  Propagate the change by clicking "Send to Cluster" (acknowledging the 
    resultant dialog boxes with "Yes" or "OK").
9.  Observe that three backup files exist now: etc/cluster/cluster.conf.bak.1,
    /etc/cluster/cluster.conf.bak.2, and /etc/cluster/cluster.conf.bak.3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Jim Parsons 2005-09-08 11:28:56 EDT
This requires some careful planning to address this issue, so deferring until
next update

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