2012-10-15 15:58:27 |
Mate Lakat |
description |
floating ip exercises are failing, at least on XenServer:
I guess, that it is happening since https://github.com/openstack/nova/commit/5fd7a9dba127bae812333196a5fa48a933212aeb
See the exercise.sh log
+ nova add-floating-ip f72920ee-eda7-41be-b826-044b052914f6 172.24.4.226
+ timeout 15 sh -c 'while ! ping -c1 -w1 172.24.4.226; do sleep 1; done'
PING 172.24.4.226 (172.24.4.226) 56(84) bytes of data.
--- 172.24.4.226 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms
PING 172.24.4.226 (172.24.4.226) 56(84) bytes of data.
From 172.24.4.226 icmp_seq=1 Destination Host Unreachable
--- 172.24.4.226 ping statistics ---
1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms
PING 172.24.4.226 (172.24.4.226) 56(84) bytes of data.
--- 172.24.4.226 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms
PING 172.24.4.226 (172.24.4.226) 56(84) bytes of data.
--- 172.24.4.226 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms
PING 172.24.4.226 (172.24.4.226) 56(84) bytes of data.
--- 172.24.4.226 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms
PING 172.24.4.226 (172.24.4.226) 56(84) bytes of data.
From 172.24.4.226 icmp_seq=1 Destination Host Unreachable
--- 172.24.4.226 ping statistics ---
1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms
PING 172.24.4.226 (172.24.4.226) 56(84) bytes of data.
--- 172.24.4.226 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms
+ echo 'Couldn'\''t ping server with floating ip'
Couldn't ping server with floating ip
+ exit 1 |
floating ip exercises are failing, at least on XenServer:
I guess, that it is happening since https://github.com/openstack/nova/commit/5fd7a9dba127bae812333196a5fa48a933212aeb
See the exercise.sh log
+ nova add-floating-ip f72920ee-eda7-41be-b826-044b052914f6 172.24.4.226
+ timeout 15 sh -c 'while ! ping -c1 -w1 172.24.4.226; do sleep 1; done'
PING 172.24.4.226 (172.24.4.226) 56(84) bytes of data.
--- 172.24.4.226 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms
PING 172.24.4.226 (172.24.4.226) 56(84) bytes of data.
From 172.24.4.226 icmp_seq=1 Destination Host Unreachable
--- 172.24.4.226 ping statistics ---
1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms
PING 172.24.4.226 (172.24.4.226) 56(84) bytes of data.
--- 172.24.4.226 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms
PING 172.24.4.226 (172.24.4.226) 56(84) bytes of data.
--- 172.24.4.226 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms
PING 172.24.4.226 (172.24.4.226) 56(84) bytes of data.
--- 172.24.4.226 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms
PING 172.24.4.226 (172.24.4.226) 56(84) bytes of data.
From 172.24.4.226 icmp_seq=1 Destination Host Unreachable
--- 172.24.4.226 ping statistics ---
1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms
PING 172.24.4.226 (172.24.4.226) 56(84) bytes of data.
--- 172.24.4.226 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms
+ echo 'Couldn'\''t ping server with floating ip'
Couldn't ping server with floating ip
+ exit 1
It turned out, that the private ips were not pingable. |
|
2012-10-16 13:29:54 |
Mate Lakat |
description |
floating ip exercises are failing, at least on XenServer:
I guess, that it is happening since https://github.com/openstack/nova/commit/5fd7a9dba127bae812333196a5fa48a933212aeb
See the exercise.sh log
+ nova add-floating-ip f72920ee-eda7-41be-b826-044b052914f6 172.24.4.226
+ timeout 15 sh -c 'while ! ping -c1 -w1 172.24.4.226; do sleep 1; done'
PING 172.24.4.226 (172.24.4.226) 56(84) bytes of data.
--- 172.24.4.226 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms
PING 172.24.4.226 (172.24.4.226) 56(84) bytes of data.
From 172.24.4.226 icmp_seq=1 Destination Host Unreachable
--- 172.24.4.226 ping statistics ---
1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms
PING 172.24.4.226 (172.24.4.226) 56(84) bytes of data.
--- 172.24.4.226 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms
PING 172.24.4.226 (172.24.4.226) 56(84) bytes of data.
--- 172.24.4.226 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms
PING 172.24.4.226 (172.24.4.226) 56(84) bytes of data.
--- 172.24.4.226 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms
PING 172.24.4.226 (172.24.4.226) 56(84) bytes of data.
From 172.24.4.226 icmp_seq=1 Destination Host Unreachable
--- 172.24.4.226 ping statistics ---
1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms
PING 172.24.4.226 (172.24.4.226) 56(84) bytes of data.
--- 172.24.4.226 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms
+ echo 'Couldn'\''t ping server with floating ip'
Couldn't ping server with floating ip
+ exit 1
It turned out, that the private ips were not pingable. |
The dnsmasq hostsfile does not contain the newly created hosts, when you launch the instances.
Problem since:
https://review.openstack.org/#/c/14174/
https://github.com/openstack/nova/commit/5fd7a9dba127bae812333196a5fa48a933212aeb
0.) See my relevant configuration entries:
stack@DevStackOSDomU:~/devstack$ cat /etc/nova/nova.conf |
grep -e compute_scheduler_driver -e multi_host -e network_manager
compute_scheduler_driver=nova.scheduler.filter_scheduler.FilterScheduler
multi_host=True
network_manager=nova.network.manager.FlatDHCPManager
1.) See that there is no dnsmasq running
stack@DevStackOSDomU:~/devstack$ ps ax | grep dnsmasq
12742 pts/19 S+ 0:00 grep dnsmasq
2.) Fire up an instance
stack@DevStackOSDomU:~/devstack$ . openrc admin
stack@DevStackOSDomU:~/devstack$ nova boot --image=tty --flavor=m1.tiny sampleserver
.
.
.
| id | 6e90a769-0bdf-42bd-86a7-da776700bf6a |
.
.
.
3.) Wait until it is running
stack@DevStackOSDomU:~/devstack$ nova show 6e90a769-0bdf-42bd-86a7-da776700bf6a
+-------------------+----------- ... -+
| Property | Value ... |
+-------------------+----------- ... -+
.
.
.
| private network | 10.0.0.2 ... | <- see the IP
.
.
.
| status | ACTIVE ... | <- instance is active
+-------------------+----------- ... -+
4.) And look at the DHCP database - it is empty!!!:
stack@DevStackOSDomU:~/devstack$ ps ax | grep dnsmasq
... --dhcp-hostsfile=/opt/stack/data/nova/networks/nova-xenbr1.conf ...
stack@DevStackOSDomU:~/devstack$ cat /opt/stack/data/nova/networks/nova-xenbr1.conf
stack@DevStackOSDomU:~/devstack$ wc /opt/stack/data/nova/networks/nova-xenbr1.conf
0 0 0 /opt/stack/data/nova/networks/nova-xenbr1.conf
5.) Restart nova-network
stack@DevStackOSDomU:~/devstack$ pkill -HUP -f "nova-network"
stack@DevStackOSDomU:~/devstack$ NL=`echo -ne '\015'`
stack@DevStackOSDomU:~/devstack$ screen -S stack -p n-net -X stuff "cd /opt/stack/nova && /usr/local/bin/nova-network$NL"
6.) See, that dhcp entries are there now:
stack@DevStackOSDomU:~/devstack$ cat /opt/stack/data/nova/networks/nova-xenbr1.conf
fa:16:3e:46:6a:be,sampleserver.novalocal,10.0.0.2
stack@DevStackOSDomU:~/devstack$ wc /opt/stack/data/nova/networks/nova-xenbr1.conf
0 1 49 /opt/stack/data/nova/networks/nova-xenbr1.conf |
|