[NETVIRT-400] openflow for ARP is not correctly set Created: 29/Dec/16  Updated: 09/Mar/18  Resolved: 09/Mar/18

Status: Resolved
Project: netvirt
Component/s: None
Affects Version/s: Carbon
Fix Version/s: None

Type: Bug Priority: Medium
Reporter: Ruijing Guo Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


External issue ID: 7456

 Description   

1. ARP rules (not correct)
vagrant@compute:~/devstack$ sudo ovs-ofctl dump-flows -OOpenflow13 br-int | grep arp | grep 10.1.0.2
cookie=0x0, duration=2448.117s, table=20, n_packets=10, n_bytes=420, priority=1024,arp,tun_id=0x58,arp_tpa=10.1.0.2,arp_op=1 actions=move:NXM_OF_ETH_SRC[]>NXM_OF_ETH_DST[],set_field:fa:16:3e:df:5b:6f>eth_src,load:0x2->NXM_OF_ARP_OP[],move:NXM_NX_ARP_SHA[]>NXM_NX_ARP_THA[],move:NXM_OF_ARP_SPA[]>NXM_OF_ARP_TPA[],load:0xfa163edf5b6f->NXM_NX_ARP_SHA[],load:0xa010002->NXM_OF_ARP_SPA[],IN_PORT

RJ’s Note: fa:16:3e:df:5b:6f is private network DHCP server(not expected). fa:16:3e:f3:db:1f is tempest* network DHCP server (expected)

2. Tunnel id is correct
vagrant@compute:~/devstack$ sudo ovs-ofctl dump-ports-desc -OOpenflow13 br-int | grep tap
6(tap4cb434bf-ce): addr:fe:16:3e:3d:aa:7c
vagrant@compute:~/devstack$ sudo ovs-ofctl dump-flows -OOpenflow13 br-int | grep 'table=0.*port=6'
cookie=0x0, duration=3931.023s, table=0, n_packets=447, n_bytes=51743, in_port=6,dl_src=fa:16:3e:3d:aa:7c actions=set_field:0x58->tun_id,load:0x1->NXM_NX_REG0[],goto_table:20

3. Neutron net list
vagrant@control:~/tempest$ neutron net-list
------------------------------------------------------------------------------------------------------------------------------

id name subnets

------------------------------------------------------------------------------------------------------------------------------

53c2d45b-60c2-4874-b117-92569c47788a tempest-network-smoke--843741885 ba21f190-1f7c-4cfc-9a52-7d8a115008ac 10.1.0.0/28
b48192eb-93bc-46ec-ad70-0d1f7d3970a7 private 2f429ae4-1fe5-4a37-9148-2335812c154f fdc2:6e77:fcb3::/64
    9a892ea9-90d7-4d60-9d74-d130b387df95 10.1.0.0/26
b75f70e1-5829-4024-8b50-96b72c2e4bc1 public 19604601-2e5e-4364-aa53-3291c5a8d0e5 172.24.5.0/24
    61456b7d-a0bc-4e66-a36f-cc60ea3c1340 2001:db8::/64

------------------------------------------------------------------------------------------------------------------------------

4. DHCP namespace
vagrant@control:~/tempest$ sudo ip netns
qdhcp-53c2d45b-60c2-4874-b117-92569c47788a
qdhcp-b48192eb-93bc-46ec-ad70-0d1f7d3970a7

5. Tempest* DHCP MAC
vagrant@control:~/tempest$ sudo ip netns exec qdhcp-53c2d45b-60c2-4874-b117-92569c47788a ifconfig tap1b44b6bf-b5 | grep HWaddr
tap1b44b6bf-b5 Link encap:Ethernet HWaddr fa:16:3e:f3:db:1f

6. private DHCP MAC
vagrant@control:~/tempest$ sudo ip netns exec qdhcp-b48192eb-93bc-46ec-ad70-0d1f7d3970a7 ifconfig tap09bc0606-79 | grep HWaddr
tap09bc0606-79 Link encap:Ethernet HWaddr fa:16:3e:df:5b:6f

7. VM in tempest* cannot access to metada server:
$ sudo arp -d 10.1.0.2; ping -c 1 10.1.0.2; sudo arp; curl http://169.254.169.254
curl: (7) couldn't connect to host

8. VM in tempest* can access to metadata server after manually set ARP for DHCP server

$ sudo arp -d 10.1.0.2; sudo arp -s 10.1.0.2 fa:16:3e:f3:db:1f; curl http://169.254.169.254
1.0
2007-01-19
2007-03-01
2007-08-29
2007-10-10
2007-12-15
2008-02-01
2008-09-01
2009-04-04



 Comments   
Comment by Ruijing Guo [ 05/Jan/17 ]

The workaround is to delete private network before tempest run

Comment by Sam Hague [ 09/Mar/18 ]

Legacy NetVirt is deprecated.

Generated at Wed Feb 07 20:21:28 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.