[NETVIRT-1058] DataPath not working with IPV6 and packet getting dropped at Table 213 Created: 08/Jan/18  Updated: 05/Mar/18  Resolved: 05/Mar/18

Status: Verified
Project: netvirt
Component/s: None
Affects Version/s: Oxygen
Fix Version/s: Oxygen

Type: Bug Priority: Highest
Reporter: RajaRajan Manickam Assignee: Shashidhar R
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

DevStack(pike)

 

Attachments: File data.pcap    
Priority: Highest

 Description   

DataPath not working with IPV6 and packet getting dropped at Table 213

Steps:

  1. Create Network,Subnet(SLAAC),Port.
  2. Create Router and associate subnet to it
  3. Boot VM and check IPV6 address assigned.(If not assigned, then reboot the VM)
  4. Verify data path.

Observation:

      Ping fails with IPV6. To confirm, same testing has been performed with IPV4 and it was working as expected.

 

Configuration:

neutron net-create mynet1

neutron subnet-create mynet1 2001:db8:1234::/64 --ip-version 6 --ipv6-ra-mode slaac --ipv6-address-mode slaac --name net1-snet2
neutron port-create mynet1 --name myport12 --security-group=CUSTM_SGP
neutron port-create mynet1 --name myport22 --security-group=CUSTM_SGP
neutron port-create mynet1 --name myport13 --security-group=CUSTM_SGP
neutron port-create mynet1 --name myport23 --security-group=CUSTM_SGP
nova boot --image cirros-0.4.0-x86_64-uec --flavor m1.tiny --nic port-id=$(neutron port-list | grep 'myport12' | awk '{print $2}') myhost12 --availability-zone nova:rajarajan-14
nova boot --image cirros-0.4.0-x86_64-uec --flavor m1.tiny --nic port-id=$(neutron port-list | grep 'myport22' | awk '{print $2}') myhost22 --availability-zone nova:rajarajan-15
nova boot --image cirros-0.4.0-x86_64-uec --flavor m1.tiny --nic port-id=$(neutron port-list | grep 'myport13' | awk '{print $2}') myhost13 --availability-zone nova:rajarajan-14
nova boot --image cirros-0.4.0-x86_64-uec --flavor m1.tiny --nic port-id=$(neutron port-list | grep 'myport23' | awk '{print $2}') myhost23 --availability-zone nova:rajarajan-15
neutron router-create R1
neutron router-interface-add R1 net1-snet2

 Comments   
Comment by Nishchya Gupta [ 17/Jan/18 ]

Unable to see this issue with karaf-0.8.0-20180104.014256-1201.

vm's are pinging fine.

followed below steps(From both CLI and GUI):

neutron net-create mynet1
neutron subnet-create mynet1 2001:db8:1234::/64 --ip-version 6 --ipv6-ra-mode slaac --ipv6-address-mode slaac --name net1-snet2
neutron security-group-create SG2

neutron port-create mynet1 --name myport12 --security-group=SG2
neutron port-create mynet1 --name myport22 --security-group=SG2
neutron port-create mynet1 --name myport13 --security-group=SG2
neutron port-create mynet1 --name myport23 --security-group=SG2
nova boot --flavor m1.tiny --image cirros-0.3.4-x86_64-uec  --nic port-id=$(neutron port-list | grep 'myport12' | awk '{print $2}') myhost12 --availability-zone nova:Openstack-Controller
nova boot --flavor m1.tiny --image cirros-0.3.4-x86_64-uec  --nic port-id=$(neutron port-list | grep 'myport22' | awk '{print $2}') myhost22 --availability-zone nova:Openstack-Controller
nova boot --flavor m1.tiny --image cirros-0.3.4-x86_64-uec  --nic port-id=$(neutron port-list | grep 'myport13' | awk '{print $2}') myhost13 --availability-zone nova:Openstack-Controller
nova boot --flavor m1.tiny --image cirros-0.3.4-x86_64-uec  --nic port-id=$(neutron port-list | grep 'myport23' | awk '{print $2}') myhost23 --availability-zone nova:Openstack-Controller
 
neutron router-create R1
neutron router-interface-add R1 net1-snet2

SG2 was having 2 rules:

      Egress IPv6 ICMP Any SG2

      Ingress IPv6 ICMP Any SG2

Comment by RajaRajan Manickam [ 17/Jan/18 ]

Hi,

  I have verified with below SG configuration and observed this. Can you please check whether the below SG configuration  has any issues.

 

 

 These are the SG list.

 

stack@rajarajan-14:~$ neutron security-group-rule-list | grep -i IPV6 | grep -i CUSTM_SGP | grep -i ingress
neutron CLI is deprecated and will be removed in the future. Use openstack CLI instead.

56214434-e34a-4f3a-812e-6590eff42f5c 9eefc0a4d9164d4d8aaa74f4ae5cd77c CUSTM_SGP      ingress   IPv6      tcp           any            
6a6cc10e-5ced-4238-8a70-c4e623b3eaa0 9eefc0a4d9164d4d8aaa74f4ae5cd77c CUSTM_SGP      ingress   IPv6      any           any            
8c6abceb-d594-4f2f-961d-03eb8d723d9c 9eefc0a4d9164d4d8aaa74f4ae5cd77c CUSTM_SGP      ingress   IPv6      icmp          any            
954720be-f98d-4284-81bf-f2ce023ef3cb 9eefc0a4d9164d4d8aaa74f4ae5cd77c CUSTM_SGP      ingress   IPv6      udp           any            

stack@rajarajan-14:~$ neutron security-group-rule-list | grep -i IPV6 | grep -i CUSTM_SGP | grep -i egress
neutron CLI is deprecated and will be removed in the future. Use openstack CLI instead.

8dccffb1-080f-4a80-aa24-41ea75d2835b 9eefc0a4d9164d4d8aaa74f4ae5cd77c CUSTM_SGP      egress    IPv6      tcp           any            
a6262f06-0bd5-4a55-8d6a-05a57956c452 9eefc0a4d9164d4d8aaa74f4ae5cd77c CUSTM_SGP      egress    IPv6      any           any            
b8b461b0-1c2e-4258-873f-592e5537d39a 9eefc0a4d9164d4d8aaa74f4ae5cd77c CUSTM_SGP      egress    IPv6      udp           any            
cd3b8d3a-9c19-4386-ab57-b846ca70d6f3 9eefc0a4d9164d4d8aaa74f4ae5cd77c CUSTM_SGP      egress    IPv6      icmp          any            

stack@rajarajan-14:~$

 

Devstack  Version: Pike

 

neutron CLI is deprecated and will be removed in the future. Use openstack CLI instead.
---------------------------------------------------------------------------------------------------------------------------------------------------+

id                                   name      tenant_id                        security_group_rules                                                

---------------------------------------------------------------------------------------------------------------------------------------------------+

16d0dc4e-0c26-4b56-9c53-aa6f8a9d8e27 CUSTM_SGP 9eefc0a4d9164d4d8aaa74f4ae5cd77c egress, IPv4                                                        
                                                                                   egress, IPv4, icmp                                                  
                                                                                   egress, IPv4, tcp                                                   
                                                                                   egress, IPv4, udp                                                   
                                                                                   egress, IPv6                                                        
                                                                                   egress, IPv6, icmp                                                  
                                                                                   egress, IPv6, tcp                                                   
                                                                                   egress, IPv6, udp                                                   
                                                                                   ingress, IPv4                                                       
                                                                                   ingress, IPv4, icmp                                                 
                                                                                   ingress, IPv4, tcp                                                  
                                                                                   ingress, IPv4, udp                                                  
                                                                                   ingress, IPv6                                                       
                                                                                   ingress, IPv6, icmp                                                 
                                                                                   ingress, IPv6, tcp                                                  
                                                                                   ingress, IPv6, udp                                        

 

 

 

 

Comment by Nishchya Gupta [ 18/Jan/18 ]

Hi,

Below are my configuration, which looks similar to yours and ping is working fine

Devstack  Version: newton

$ neutron security-group-rule-list | grep -i CUSTM_SGP

0ea81ab4-9471-4175-b8a2-f19c049a3028 CUSTM_SGP      egress    IPv4      1-65535/tcp   CUSTM_SGP (group)
2825ff5a-26e3-4452-9094-9088c9f96c29 CUSTM_SGP      ingress   IPv6      icmp          CUSTM_SGP (group)
31a86bf4-5d1e-4252-95cc-709a8a2efbe1 CUSTM_SGP      egress    IPv6      icmp          CUSTM_SGP (group)
45286ae3-aae0-4e7b-ab27-c027b179f5c3 CUSTM_SGP      egress    IPv4      1-65535/udp   CUSTM_SGP (group)
48a40aeb-9e8d-4f5c-b647-380bdd984c86 CUSTM_SGP      ingress   IPv4      1-65535/tcp   CUSTM_SGP (group)
67711fe3-5034-45eb-81b0-c784618434e6 CUSTM_SGP      egress    IPv6      1-65535/tcp   CUSTM_SGP (group)
a2ec79e2-a1c1-4a31-8850-4f834902d0fd CUSTM_SGP      ingress   IPv4      1-65535/udp   CUSTM_SGP (group)
b0a132f1-a4f2-4219-b51e-06a5fc8b93fc CUSTM_SGP      egress    IPv4      any           any              
bf066473-bc5d-474c-8999-8fcad8455a9e CUSTM_SGP      ingress   IPv6      1-65535/tcp   CUSTM_SGP (group)
c9a9116b-6947-4ded-889f-7b646410f74c CUSTM_SGP      egress    IPv4      icmp          CUSTM_SGP (group)
ce76ddfe-3084-4efb-ac80-1f11dbcefbb6 CUSTM_SGP      egress    IPv6      1-65535/udp   CUSTM_SGP (group)
e430d73b-552f-4961-8a01-3823af39c3a6 CUSTM_SGP      ingress   IPv4      icmp          CUSTM_SGP (group)
f2231daa-12bc-4206-ad77-1e5a5a324334 CUSTM_SGP      egress    IPv6      any           any              
f9d75735-308a-47bb-9c98-21002f7565a0 CUSTM_SGP      ingress   IPv6      1-65535/udp   CUSTM_SGP (group)

 

$ neutron security-group-rule-list | grep -i IPV6 | grep -i CUSTM_SGP | grep -i ingress

2825ff5a-26e3-4452-9094-9088c9f96c29 CUSTM_SGP      ingress   IPv6      icmp          CUSTM_SGP (group)
bf066473-bc5d-474c-8999-8fcad8455a9e CUSTM_SGP      ingress   IPv6      1-65535/tcp   CUSTM_SGP (group)
f9d75735-308a-47bb-9c98-21002f7565a0 CUSTM_SGP      ingress   IPv6      1-65535/udp   CUSTM_SGP (group)

 

$ neutron security-group-rule-list | grep -i IPV6 | grep -i CUSTM_SGP | grep -i egress

31a86bf4-5d1e-4252-95cc-709a8a2efbe1 CUSTM_SGP      egress    IPv6      icmp          CUSTM_SGP (group)
67711fe3-5034-45eb-81b0-c784618434e6 CUSTM_SGP      egress    IPv6      1-65535/tcp   CUSTM_SGP (group)
ce76ddfe-3084-4efb-ac80-1f11dbcefbb6 CUSTM_SGP      egress    IPv6      1-65535/udp   CUSTM_SGP (group)
f2231daa-12bc-4206-ad77-1e5a5a324334 CUSTM_SGP      egress    IPv6      any           any              
Comment by Nishchya Gupta [ 19/Jan/18 ]

Cannot reproduce issue with karaf-0.8.0-20180104.014256-1201.

Devstackversion: newton

Detils are provided in comments

Comment by RajaRajan Manickam [ 19/Jan/18 ]

Hi,

 

 Can you please confirm with Devstack pike version. This issue was observed with devstack pike version. Not with Newton.

Comment by Kit Lou [ 27/Feb/18 ]

Please provide an update on this issue.  Is this a true blocker?  Any ETA on resolution?

Comment by Shashidhar R [ 28/Feb/18 ]

After latest pipeline changes (https://git.opendaylight.org/gerrit/#/c/66973/) issue reported here is not observed.

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