yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #01330
[Bug 908194] Re: ARP table removed for br0 on host when node terminated
This bug lacks the necessary information to effectively reproduce and
fix it, therefore it has been closed. Feel free to reopen the bug by
providing the requested information and set the bug status back to
''New''.
** Changed in: nova
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/908194
Title:
ARP table removed for br0 on host when node terminated
Status in OpenStack Compute (Nova):
Invalid
Bug description:
openstack-nova-2011.3-13.fc16.noarch
Test case:
Fedora 16 Guest
Fedora 16 Host
Start two test guests
ping the bridge gateway from each host
terminate one of the virtual machines with euca-terminate-instances
The remaining VM takes 30-60 seconds before network connectivity is restored. Immediately after termination on the host:
[root@beast net]# cat /proc/net/arp
IP address HW type Flags HW address Mask Device
192.168.1.1 0x1 0x2 00:1d:7e:c1:2a:81 * wlan0
It appears the act of qemu being terminated clears the arp cache.
After 30-60 seconds elapsed:
[root@beast net]# cat /proc/net/arp
IP address HW type Flags HW address Mask Device
192.168.1.1 0x1 0x2 00:1d:7e:c1:2a:81 * wlan0
10.0.0.3 0x1 0x2 02:16:3e:62:ee:4b * br0
The vnets:
vnet0 Link encap:Ethernet HWaddr FE:16:3E:3F:89:E3
vnet1 Link encap:Ethernet HWaddr FE:16:3E:62:EE:4B
tcpdump of br0 shows:
at same time as kill of vm:
09:02:49.498818 ARP, Request who-has 10.0.0.3 tell reserved, length 28^M
09:02:49.499612 ARP, Reply 10.0.0.3 is-at 02:16:3e:62:ee:4b (oui
Unknown), length 28
Note "02:..." is the guests MAC address
Some time later (30-60 seconds) the network enables again when this arp is detected:
09:03:34.499680 ARP, Request who-has reserved tell 10.0.0.3, length 28^M
09:03:34.499722 ARP, Reply reserved is-at fe:16:3e:62:ee:4b (oui
Unknown), length 28^M
Note "fe:...." is the guests VNET address
Then the networking is active again.
start two
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/908194/+subscriptions