[9.x swarm] Unknown overhead of package size for env with dpdk+vxlan

Bug #1658126 reported by Sergey Novikov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Confirmed
High
Fuel Sustaining
Mitaka
Confirmed
High
Fuel Sustaining
Newton
Incomplete
High
Fuel Sustaining

Bug Description

Detailed bug description:

The issue was found by https://product-ci.infra.mirantis.net/job/9.x.system_test.ubuntu.ovs_firewall_with_dpdk/1/testReport/(root)/deploy_ovs_firewall_and_dpdk_vxlan_ipv6/

Steps to reproduce:
            1. Create new environment with VxLAN segmentation for Neutron
            2. Add controller and compute nodes
            3. Enable OVS firewall driver for neutron security groups
            4. Configure private network in DPDK mode
            5. Configure HugePages for compute nodes
            6. Run network verification
            7. Deploy environment
            8. Run OSTF
            9. Boot instance
            10. Assign floating ip
            11. Ping instance:
                # ping -q -c 10 -w 40 -s 1423 <instance_floating_ip>

Expected results: Ping passes
because overhead should be

Outer IPv4 Header ----------- 20 bytes
Outer UDP Header ------------ 8 bytes
VXLAN Header ---------------- 8 bytes
----------------------------------------
                              36 bytes
Thus, if original MTU is 1500, then all packages with size < 1464 should pass
Actual result: Ping passes only for package size =< 1422
So, unknown overhead is 42 bytes

Tags: swarm-fail
Changed in fuel:
assignee: nobody → Fuel Sustaining (fuel-sustaining-team)
Changed in fuel:
importance: Medium → High
tags: added: swarm-fail
Dmitry Pyzhov (dpyzhov)
Changed in fuel:
milestone: 9.2 → 11.0
status: New → Confirmed
Revision history for this message
Michael Polenchuk (mpolenchuk) wrote :

Ping is successful for latest F10 iso, therefore mark it as incomplete for newton.

Revision history for this message
Michael Polenchuk (mpolenchuk) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.