Status: New
Owner: ----
New issue 851 by [email protected]: gnt-cluster verify leaves out
one node on N+1 Memory redundancy
http://code.google.com/p/ganeti/issues/detail?id=851
What software version are you running? Please provide the output of "gnt-
cluster --version", "gnt-cluster version", and "hspace --version".
What distribution are you using?
root@node2 ~ # gnt-cluster --version
gnt-cluster (ganeti v2.10.4) 2.10.4
root@node2 ~ # gnt-cluster version
Software version: 2.10.4
Internode protocol: 2100000
Configuration format: 2100000
OS api version: 20
Export interface: 0
VCS version: (ganeti) version v2.10.4
root@node2 ~ # hspace --version
hspace (ganeti) version v2.10.4
compiled with ghc 7.4
running on linux x86_64
root@node2 ~ # cat /etc/debian_version
7.5
root@node2 ~ # dpkg -l ganeti
[...]2.10.4-1~bpo70+1[...]
What steps will reproduce the problem?
gnt-cluster verify
What is the expected output? What do you see instead?
[...]
| Tue Jun 10 12:04:56 2014 * Verifying N+1 Memory redundancy
| Tue Jun 10 12:04:56 2014 - ERROR: node node2.xxxxxxxxx.de: not enough
memory to accomodate instance failovers should node node1.xxxxxxxxx.de fail
(12800MiB needed, 8140MiB available)
Tue Jun 10 12:04:56 2014 - ERROR: node node1.xxxxxxxxx.de: not enough
memory to accomodate instance failovers should node node2.xxxxxxxxx.de
fail (22???MiB needed, 16???MiB available)
[...]
Please provide any additional information below.
this is for a two-node cluster so if one Server failes the other node will
have to start swaping - and this isn't just in one direction
--
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
