Bug 149124
| Summary: | Cannot update version number of cluster.conf file: prevents use of ccs_tool update | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Cluster Suite | Reporter: | Paul Kennedy <pkennedy> |
| Component: | redhat-config-cluster | Assignee: | Jim Parsons <jparsons> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | Cluster QE <mspqa-list> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4 | CC: | adstrong, cluster-maint, henry.harris |
| 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-05-11 19:48:10 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: | |||
|
Description
Paul Kennedy
2005-02-18 23:17:59 UTC
config_version can now be updated , but needs to not autoincrement upon save if user has modifed current value. User can now manually set config_version. It is not currently autoincrementing if the user makes another config change without modifying config_version. So that still needs to be done, if I understand correctly. system-config-cluster-0.9.11-1.0 Fixed completely in 0.9.12 In 0.9.12 if the user specifies a config_version it is incremented by one. In this case the user should get exactly what they ask for. e.g. specify version 70 and it is written as 71, should write 70. This is finally fixed, and a new button has been added to the UI if the UI is run on a quorate cluster member that allows the new cfg to be propogated to all nodes. Fixed in 0.9.17-1.0 partially fixed. If someone specifies a version of 1 or less (including all negative numbers), it will jump one when it does the save, however, all other numbers greater than 1, it will not. Now negative numbers are not allowed, so this issue is moot. Fixed in 0.9.42 If I change the version from say 5 down to 1 and then save it, it will work and my new version is 1 (which is good), if I then do nothing to alter the config and save again, it will bump up to 2 (again I would argue expected behavior), after that if I just continue to save over and over again without changing the config at all, it will only bump the config version every _other_ time. Every time there is a save, it should always bump the version UNLESS the config version is what is changed, at which point the version should be _EXACTLY_ what the user defined as the version (as long as it's an integer from 1 to 9999) or zero if we allow it. Finally all fixed in 0.9.50-1.0 fix verified. *** Bug 158419 has been marked as a duplicate of this bug. *** |