Updates:
Status: Accepted
Labels: Priority-Critical Milestone-Release2.9
Comment #1 on issue 607 by [email protected]: Fail re-add node on Ganeti
2.9.0
http://code.google.com/p/ganeti/issues/detail?id=607
I confirm that the problem is reproducible in 2.9.0, even with a simpler
procedure:
1. Create cluster
2. Offline one node:
gnt-node modify -O yes node2
3. Try to readd it
gnt-node add --readd node2
~# gnt-node add --readd wpeg2.hot.corp.google.com
The authenticity of host 'node2.example.com (192.168.0.2)' can't be
established.
RSA key fingerprint is 3e:1f:86:0e:99:db:c7:2c:45:81:55:95:85:66:2d:7d.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added 'node2.example.com' (RSA) to the list of known
hosts.
Restarting OpenBSD Secure Shell server: sshd.
Thu Nov 7 12:08:25 2013 - INFO: Readding a node, the offline/drained
flags were reset
Thu Nov 7 12:08:25 2013 - INFO: Node will be a master candidate
Thu Nov 7 12:08:27 2013 Configuration data is not consistent: Node
node2.example.com state is invalid: master_candidate=True, drain=False,
offline=True
--
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
