Not able to reproduce I could see the arp table update on the router
namespaces on both nodes.
I tried to modify the ports on both the subnet 10.2.0.X and 10.0.0.X.
In this example I have change the 10.2.0.4 to 10.2.0.25 and 10.0.0.8 10.0.0.20.
In both cases I saw that the arp entry was updated.
There is one thing that is true on both our testing is, the VM is not
able to get the new IP until I reboot the VM. ( This might be filed as a
different bug in nova)
ARP output from Node 2:
root@ubuntu-new-compute:~/devstack# arp -a
? (10.2.0.4) at fa:16:3e:7e:0b:48 [ether] PERM on qr-b25bad4f-5f
? (10.0.0.6) at fa:16:3e:7a:78:fe [ether] PERM on qr-66c29926-29
? (10.2.0.3) at fa:16:3e:b6:19:da [ether] PERM on qr-b25bad4f-5f
? (10.0.0.2) at fa:16:3e:91:1a:d2 [ether] PERM on qr-b2b8c9a4-68
? (10.0.0.2) at fa:16:3e:91:1a:d2 [ether] PERM on qr-66c29926-29
? (10.0.0.6) at fa:16:3e:7a:78:fe [ether] PERM on qr-b2b8c9a4-68
? (10.2.0.25) at fa:16:3e:7e:0b:48 [ether] PERM on qr-b25bad4f-5f ( changed arp
info)
? (10.0.0.7) at fa:16:3e:5d:12:fd [ether] PERM on qr-66c29926-29
? (10.2.0.2) at fa:16:3e:b6:84:91 [ether] PERM on qr-b25bad4f-5f
? (10.0.0.8) at fa:16:3e:a1:cc:87 [ether] PERM on qr-66c29926-29
? (10.0.0.8) at fa:16:3e:a1:cc:87 [ether] PERM on qr-b2b8c9a4-68
? (10.0.0.20) at fa:16:3e:a1:cc:87 [ether] PERM on qr-66c29926-29 ( changed arp
info)
? (10.0.0.7) at fa:16:3e:5d:12:fd [ether] PERM on qr-b2b8c9a4-68
? (10.0.0.3) at fa:16:3e:fd:a1:d6 [ether] PERM on qr-66c29926-29
root@ubuntu-new-compute:~/devstack#
ARP Info from Node 1:
root@ubuntu-ctlr:~/devstack# arp -a
? (10.0.0.3) at fa:16:3e:fd:a1:d6 [ether] PERM on qr-66c29926-29
? (10.2.0.3) at fa:16:3e:b6:19:da [ether] PERM on qr-b25bad4f-5f
? (10.0.0.7) at fa:16:3e:5d:12:fd [ether] PERM on qr-66c29926-29
? (10.0.0.2) at fa:16:3e:91:1a:d2 [ether] PERM on qr-b2b8c9a4-68
? (10.0.0.2) at fa:16:3e:91:1a:d2 [ether] PERM on qr-66c29926-29
? (10.2.0.4) at fa:16:3e:7e:0b:48 [ether] PERM on qr-b25bad4f-5f
? (10.0.0.6) at fa:16:3e:7a:78:fe [ether] PERM on qr-66c29926-29
? (10.2.0.25) at fa:16:3e:7e:0b:48 [ether] PERM on qr-b25bad4f-5f
? (10.2.0.5) at <incomplete> on qr-b25bad4f-5f
? (10.0.0.5) at <incomplete> on qr-66c29926-29
? (10.0.0.20) at fa:16:3e:a1:cc:87 [ether] PERM on qr-66c29926-29
? (10.0.0.8) at fa:16:3e:a1:cc:87 [ether] PERM on qr-66c29926-29
? (10.2.0.2) at fa:16:3e:b6:84:91 [ether] PERM on qr-b25bad4f-5f
? (10.0.0.4) at <incomplete> on qr-66c29926-29
root@ubuntu-ctlr:~/devstack#
** Changed in: neutron
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1512199
Title:
change vm fixed ips will cause unable to communicate to vm in other
network
Status in neutron:
Invalid
Bug description:
I use dvr+kilo, vxlan. The environment is like:
vm2-2<- compute1 ----------vxlan------------- comupte2 ->vm2-1
vm3-1<-
vm2-1<- net2 ---------router1--------- net3 ->vm3-1
vm2-2<-
vm2-1(192.168.2.3) and vm2-2(192.168.2.4) are in the same net(net2
192.168.2.0/24) but not assigned to the same compute node. vm3-1 is in
net3(192.168.3.0/24). net2 and net3 are connected by router1. The three vms are
in default security-group. Not use firewall.
1. Using command below to change the ip of vm2-1.
neutron port-update portID --fixed-ip
subnet_id=subnetID,ip_address=192.168.2.10 --fixed-ip
subnet_id=subnetID,ip_address=192.168.2.20
In vm2-1 using "sudo udhcpc"(carrios) to get ip, the dhcp message is correct
but the ip not changed.
Then reboot vm2-1. The ip of vm2-1 turned to be 192.168.2.20.
2. Using vm2-2 could ping 192.168.2.20 successfully . But vm3-1 could
not ping 192.168.2.20 successfully.
By capturing packets and looking for related information, the reason maybe:
1. newIP(192.168.2.20) and MAC of vm2-1 was not wrote to arp cache in the
namespace of router1 in compute1 node.
2. In dvr mode, the arp request from gw port(192.168.2.1) from compute1 to
vm2-1 was dropped by flowtable in compute2. So the arp
request(192.168.2.1->192.168.2.20) could not arrive at vm2-1.
3. For vm2-2, the arp request(192.168.2.4->192.168.2.20) was not dropped and
could connect with vm2-1.
In my opinion, if both new fixed IPs of vm2-1(192.168.2.10 and
102.168.2.20) and MAC is wrote to arp cache in namespace of router1 in
compute1 node, the problem will resolved. But only one
ip(192.168.2.10) and MAC is wrote.
BTW, if only set one fixed ip for vm2-1, it works fine. But if set two
fixed ips for vm2-1, the problem above most probably happens.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1512199/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
