Comment #2 on issue 892 by [email protected]: Feature request: No
DNS-Entrys for secondary network
http://code.google.com/p/ganeti/issues/detail?id=892
well it does, or at least if you have a IPv6-Network as primary
root@node1 ~ # gnt-cluster verify | censor
[...]
Mon Jul 21 14:58:43 2014 - ERROR: node node1.yyyyyy.xxxxxxxxx.de: ssh
communication with node 'node1.yyyyyy.xxxxxxxxx.de': ssh problem: ssh:
Could not resolve hostname node1.yyyyyy.xxxxxxxxx.de: Name or service not
known\'r\n
Mon Jul 21 14:58:43 2014 - ERROR: node node1.yyyyyy.xxxxxxxxx.de: ssh
communication with node 'node2.yyyyyy.xxxxxxxxx.de': ssh problem: ssh:
Could not resolve hostname node2.yyyyyy.xxxxxxxxx.de: Name or service not
known\'r\n
Mon Jul 21 14:58:43 2014 - ERROR: node node2.yyyyyy.xxxxxxxxx.de: ssh
communication with node 'node1.yyyyyy.xxxxxxxxx.de': ssh problem: ssh:
Could not resolve hostname node1.yyyyyy.xxxxxxxxx.de: Name or service not
known\'r\n
Mon Jul 21 14:58:43 2014 - ERROR: node node2.yyyyyy.xxxxxxxxx.de: ssh
communication with node 'node2.yyyyyy.xxxxxxxxx.de': ssh problem: ssh:
Could not resolve hostname node2.yyyyyy.xxxxxxxxx.de: Name or service not
known\'r\n
[...]
root@node1 ~ # host node1.yyyyyy.xxxxxxxxx.de
node1.yyyyyy.xxxxxxxxx.de has IPv6 address 2a00:xxx::1
root@node1 ~ # gnt-cluster info | grep primary
primary ip version: 6
--
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
