[DPDK] Network verification fails while adding new compute node
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Committed
|
Medium
|
Ihor Kalnytskyi | ||
Mitaka |
Won't Fix
|
Medium
|
Ihor Kalnytskyi |
Bug Description
Network verification fails after adding of new compute node with enabled DPDK to operational cluster:
[root@nailgun ~]# fuel task --task 54
id | status | name | cluster | progress | uuid
---+---
54 | error | verify_networks | 1 | 100 | 3905c182-
Verification failed.
Node Name Node MAC address Node Interface Expected VLAN (not received)
slave-04_compute 64:80:9a:af:3b:ef 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
Steps to reproduce:
1. Deploy environment with 1 controller and N compute nodes with enabled DPDK (use VLAN and KVM, allocate HugePages for DPDK on computes)
2. Add new compute node and enable DPDK
3. Run network verification
Expected result: verification is passed
Actual result: verification fails, no tagged (private network) traffic is received on new compute from controller, because it's skipped
Here is the patch for nailgun which helps: http://
Changed in fuel: | |
importance: | Undecided → High |
status: | New → Confirmed |
no longer affects: | fuel/newton |
Igor K. helped me to investigate this issue and asked me to assign this bug to him.