Bug 112 - dpdk-18.05 not allowing to create bond interface with name "lan_bond"
Summary: dpdk-18.05 not allowing to create bond interface with name "lan_bond"
Status: CONFIRMED
Alias: None
Product: DPDK
Classification: Unclassified
Component: other (show other bugs)
Version: 18.05
Hardware: All Linux
: Normal normal
Target Milestone: ---
Assignee: Ashish Anand
URL:
Depends on:
Blocks:
 
Reported: 2018-11-29 07:08 CET by Ashish Anand
Modified: 2019-01-17 22:21 CET (History)
1 user (show)


Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Ashish Anand 2018-11-29 07:08:01 CET 
Before upgrading to dpdk latest stable release (18.05), i was using dpdk-stable-17.05.1. With dpdk-stable-17.05.1, i was able to create bond interface with the name as "lan_bond". After upgrading to dpdk-18.05, the api rte_eth_bond_create is failing . On further testing, i found that it is accepting the bond interface name as "net_bonding0" but failing to accept the name as "lan_bond".

Please help in this regard and let me know if more information is needed.

Thanks in advance.
Comment 1 Ajit Khaparde 2018-11-29 16:46:19 CET 
Declan, Can you take a look? Thanks
Comment 2 Declan Doherty 2019-01-17 12:58:50 CET 
Issue is seen due to changes to virtual device bus infrastructure in 17.08, all virtual devices must now use the standard naming convention for that devices driver as the prefix to the device name. Therefore "lan_bond" is no longer a valid device name.
Comment 3 Ajit Khaparde 2019-01-17 22:21:17 CET 
Ashish, Looks like it is working as expected then?
Note You need to log in before you can comment on or make changes to this bug.