[DPDK] Network verification failed after successful deployment
Bug #1566963 reported by
Maksym Strukov
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
High
|
Fedor Zhadaev | ||
Mitaka |
Fix Released
|
High
|
Fedor Zhadaev |
Bug Description
Steps:
1. Create new environment with VLAN segmentation for Neutron
2. Use KVM as hypervisor
3. Add controller and compute nodes
4. Configure HugePages for compute nodes: 256 2m pages for Nova and 128 mb for DPDK
5. Configure private network in DPDK mode
6. Run network verification
7. Deploy environment
8. Run network verification
Expected:
Network verification OK
Actual:
Node Name Node MAC address Node Interface Expected VLAN (not received)
slave-01_controller 64:a9:16:44:7e:5e enp0s6 1024, 1026, 1027, 1028, 1029, 1030, 1025, 1000, 1001, 1002, 1003, 1004, 1005, 1006, 1007, 1008, 1009, 1010, 1011, 1012, 1013, 1014, 1015, 1016, 1017, 1018, 1019, 1020, 1021, 1022, 1023
Env: 9.0-161
Changed in fuel: | |
importance: | Undecided → High |
Changed in fuel: | |
milestone: | none → 9.0 |
assignee: | nobody → Fuel Library Team (fuel-library) |
status: | New → Confirmed |
tags: | added: area-library |
tags: | added: feature-dpdk team-telco |
Changed in fuel: | |
assignee: | Fuel Library Team (fuel-library) → Fuel Telco (fuel-telco-team) |
Changed in fuel: | |
milestone: | 9.0 → 10.0 |
tags: | added: module-netcheck |
summary: |
- Network verification failed after successful deployment + [DPDK] Network verification failed after successful deployment |
Changed in fuel: | |
assignee: | Fuel Telco (fuel-telco-team) → Fuel Python Team (fuel-python) |
tags: |
added: area-python removed: area-library |
Changed in fuel: | |
assignee: | Fuel Python Team (fuel-python) → Fedor Zhadaev (fzhadaev) |
Changed in fuel: | |
status: | In Progress → Fix Committed |
To post a comment you must log in.
Possibly invalid: network checker could not be used for Private on DPDK node. So, if we have only 2 nodes: controller and dpdk-enabled compute, there is no interface to check it.
Should be fixed in network checker to carefully ignore DPDK/SR-IOV configuration, or network checker should be redesigned to support DPDK/SR-IOV, or test should be modified.