I've reproduced it. It seems that it's a fuel env's internal network issue.
Some details from the env: [root@nailgun ~]# fuel nodes DEPRECATION WARNING: /etc/fuel/client/config.yaml exists and will be used as the source for settings. This behavior is deprecated. Please specify the path to your custom settings file in the FUELCLIENT_CUSTOM_SETTINGS environment variable. id | status | name | cluster | ip | mac | roles | pending_roles | online | group_id ---|-------------|---------------------------|---------|-------------|-------------------|------------------|---------------|--------|--------- 8 | provisioned | slave-07_compute_cinder | 1 | 10.109.0.9 | 64:85:e9:65:de:5c | cinder, compute | | True | 1 6 | discover | Untitled (2d:b0) | None | 10.109.0.10 | 64:7b:55:fb:2d:b0 | | | True | None 7 | discover | Untitled (71:f0) | None | 10.109.0.11 | 64:7a:21:e8:71:f0 | | | True | None 4 | provisioned | slave-01_contrail-config | 1 | 10.109.0.3 | 64:c5:44:6b:a3:b2 | contrail-config | | True | 1 2 | provisioned | slave-03_contrail-db | 1 | 10.109.0.5 | 64:9f:32:d1:11:25 | contrail-db | | True | 1 1 | provisioned | slave-05_contrail-db | 1 | 10.109.0.7 | 64:8e:f7:00:12:c2 | contrail-db | | True | 1 9 | error | slave-06_controller | 1 | 10.109.0.8 | 64:6c:23:88:d2:ca | controller | | True | 1 5 | provisioned | slave-02_contrail-control | 1 | 10.109.0.4 | 64:c8:f8:5f:95:cf | contrail-control | | True | 1 3 | provisioned | slave-04_contrail-db | 1 | 10.109.0.6 | 64:e0:3c:30:2b:a3 | contrail-db | | True | 1
Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 10.109.1.1 0.0.0.0 UG 0 0 0 br-ex 10.109.0.0 0.0.0.0 255.255.255.0 U 0 0 0 br-fw-admin 10.109.1.0 0.0.0.0 255.255.255.224 U 0 0 0 br-ex 10.109.1.32 0.0.0.0 255.255.255.224 U 0 0 0 br-mgmt 10.109.1.64 0.0.0.0 255.255.255.224 U 0 0 0 br-storage 10.109.1.96 0.0.0.0 255.255.255.224 U 0 0 0 br-mesh 169.254.169.254 - 255.255.255.255 !H 0 - 0 - root@node-9:~# cat /etc/resolv.conf # re-generated by cloud-init boothook only at the first boot; search test.domain.local domain test.domain.local nameserver 10.109.0.2 root@node-9:~# ping 10.109.0.2 PING 10.109.0.2 (10.109.0.2) 56(84) bytes of data. 64 bytes from 10.109.0.2: icmp_seq=1 ttl=64 time=0.416 ms 64 bytes from 10.109.0.2: icmp_seq=2 ttl=64 time=3.11 ms ^C --- 10.109.0.2 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 999ms rtt min/avg/max/mdev = 0.416/1.764/3.113/1.349 ms root@node-9:~# ping ya.ru PING ya.ru (213.180.204.3) 56(84) bytes of data. ^C --- ya.ru ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms
root@node-9:~# tracepath ya.ru 1?: [LOCALHOST] pmtu 1500 1: 10.109.1.4 2997.930ms !H Resume: pmtu 1500
I've reproduced it.
It seems that it's a fuel env's internal network issue.
Some details from the env: client/ config. yaml exists and will be used as the source for settings. This behavior is deprecated. Please specify the path to your custom settings file in the FUELCLIENT_ CUSTOM_ SETTINGS environment variable. ------- ---|--- ------- ------- ------- ---|--- ------| ------- ------| ------- ------- -----|- ------- ------- ---|--- ------- -----|- ------- |------ --- compute_ cinder | 1 | 10.109.0.9 | 64:85:e9:65:de:5c | cinder, compute | | True | 1 contrail- config | 1 | 10.109.0.3 | 64:c5:44:6b:a3:b2 | contrail-config | | True | 1 contrail- db | 1 | 10.109.0.5 | 64:9f:32:d1:11:25 | contrail-db | | True | 1 contrail- db | 1 | 10.109.0.7 | 64:8e:f7:00:12:c2 | contrail-db | | True | 1 contrail- control | 1 | 10.109.0.4 | 64:c8:f8:5f:95:cf | contrail-control | | True | 1 contrail- db | 1 | 10.109.0.6 | 64:e0:3c:30:2b:a3 | contrail-db | | True | 1
[root@nailgun ~]# fuel nodes
DEPRECATION WARNING: /etc/fuel/
id | status | name | cluster | ip | mac | roles | pending_roles | online | group_id
---|---
8 | provisioned | slave-07_
6 | discover | Untitled (2d:b0) | None | 10.109.0.10 | 64:7b:55:fb:2d:b0 | | | True | None
7 | discover | Untitled (71:f0) | None | 10.109.0.11 | 64:7a:21:e8:71:f0 | | | True | None
4 | provisioned | slave-01_
2 | provisioned | slave-03_
1 | provisioned | slave-05_
9 | error | slave-06_controller | 1 | 10.109.0.8 | 64:6c:23:88:d2:ca | controller | | True | 1
5 | provisioned | slave-02_
3 | provisioned | slave-04_
Kernel IP routing table 764/3.113/ 1.349 ms
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 10.109.1.1 0.0.0.0 UG 0 0 0 br-ex
10.109.0.0 0.0.0.0 255.255.255.0 U 0 0 0 br-fw-admin
10.109.1.0 0.0.0.0 255.255.255.224 U 0 0 0 br-ex
10.109.1.32 0.0.0.0 255.255.255.224 U 0 0 0 br-mgmt
10.109.1.64 0.0.0.0 255.255.255.224 U 0 0 0 br-storage
10.109.1.96 0.0.0.0 255.255.255.224 U 0 0 0 br-mesh
169.254.169.254 - 255.255.255.255 !H 0 - 0 -
root@node-9:~# cat /etc/resolv.conf
# re-generated by cloud-init boothook only at the first boot;
search test.domain.local
domain test.domain.local
nameserver 10.109.0.2
root@node-9:~# ping 10.109.0.2
PING 10.109.0.2 (10.109.0.2) 56(84) bytes of data.
64 bytes from 10.109.0.2: icmp_seq=1 ttl=64 time=0.416 ms
64 bytes from 10.109.0.2: icmp_seq=2 ttl=64 time=3.11 ms
^C
--- 10.109.0.2 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 999ms
rtt min/avg/max/mdev = 0.416/1.
root@node-9:~# ping ya.ru
PING ya.ru (213.180.204.3) 56(84) bytes of data.
^C
--- ya.ru ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms
root@node-9:~# tracepath ya.ru
1?: [LOCALHOST] pmtu 1500
1: 10.109.1.4 2997.930ms !H
Resume: pmtu 1500