Bug 160169
| Summary: | Restoring backup file and propagating new config causes extra backup file to be created | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Cluster Suite | Reporter: | Paul Kennedy <pkennedy> |
| Component: | redhat-config-cluster | Assignee: | Jim Parsons <jparsons> |
| Status: | CLOSED DEFERRED | QA Contact: | Cluster QE <mspqa-list> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4 | CC: | adstrong, cluster-maint, jha |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2005-09-08 15:28:56 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
This requires some careful planning to address this issue, so deferring until next update |
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: