Status: Accepted
Owner: [email protected]
Labels: Milestone-Release2.12 Type-Defect Priority-Medium
New issue 843 by [email protected]: Node demotion does not remove config
file
http://code.google.com/p/ganeti/issues/detail?id=843
What steps will reproduce the problem?
1. Create a cluster and add a few nodes that are master candidate from the
beginning.
2. Demote a node:
gnt-node modify --master-candidate=False NODE1
Wed May 28 12:42:58 2014 Configuration data is not consistent: Not enough
master candidates: actual 4, target 5
Modified node NODE
- master_candidate -> False
3. run 'gnt-cluster verify'
Wed May 28 12:59:52 2014 * Verifying configuration file consistency
Wed May 28 12:59:53 2014 - ERROR: cluster: File
/var/lib/ganeti/config.data should not exist on node(s) NODE1
Wed May 28 12:59:53 2014 - ERROR: cluster: File
/var/lib/ganeti/config.data found with 2 different checksums (variant 1 on
NODE2, NODE3, NODE4, NODE5; variant 2 on NODE1)
Apparently, the config file is not removed on demotion and the stale old
file sticks around and is not updated anymore.
Please use labels and text to provide additional information.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
