Status: Accepted
Owner: [email protected]
Labels: Type-Defect
New issue 917 by [email protected]: Node evacuation fails if a node in a
different nodegroup is unavailable
http://code.google.com/p/ganeti/issues/detail?id=917
What software version are you running? Please provide the output of "gnt-
cluster --version", "gnt-cluster version", and "hspace --version".
gnt-cluster (ganeti v2.10.1) 2.10.1
Software version: 2.10.1
Internode protocol: 2100000
Configuration format: 2100000
OS api version: 20
Export interface: 0
VCS version: (ganeti) version v2.10.1
hspace (ganeti) version v2.10.1
compiled with ghc 7.4
running on linux x86_64
What distribution are you using?
Ubuntu Precise Server
What steps will reproduce the problem?
1. Have a cluster with at least two nodegroups (group1: node1, node2,
node3; group2: node4, node5, node6)
2. Power off node1
3. Run "gnt-node evacuate -s node4"
What is the expected output? What do you see instead?
Expected: All secondaries of node4 are getting moved to either node5 or
node6.
What happens: Can't get data for node node1: Error 7: Failed connect to
10.0.0.1:1811; Connection refused
Please provide any additional information below.
Since the offline node is in a different nodegroup I would expect the
evacuation to succeed. For unknown reasons it tries to connect to nodes in
other nodegroups.
--
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
