This bug is essential to fix, because any startup automation that will apply custom config on vpp will be effectively reduced to guessing the automatic name that vpp assigns.

It looks like VPP determines the type of interface based on the name that it gets. An interface that was originally TenGigabitEthernet8/0/0 was aliased as opflexvpp

with this config in the startup.conf

1. 1. Set interface name
       dev 0000:08:00.0 {   name opflexvpp }

Following this, attempt to create a subinterface off the main interface and enable dhcp client on it fail as indicated in the excerpt below.:

[2019-Aug-06 18:49:27.151347] [debug] [singular_db.hpp:74:find_or_add] interface:[opflexvpp type:AFPACKET hdl:hw-item:[rc:no-op data:4294967295] l2-address:[hw-item:[rc:un-set data:00]] admin-state:hw-item:[rc:no-op data:up] oper-state:down]
[2019-Aug-06 18:49:27.151393] [debug] [hw.cpp:130:write] af-packet-itf-create: hw-item:[rc:no-op data:4294967295] name:opflexvpp
[2019-Aug-06 18:49:27.153274] [debug] [interface.hpp:350:operator()] af-packet-itf-create: hw-item:[rc:no-op data:4294967295] name:opflexvpp res:-71 sw-if-index:0
[2019-Aug-06 18:49:27.153388] [debug] [singular_db.hpp:74:find_or_add] LLDP-global: system_name:overcloud-compute-acivpp-0 tx-hold:5 tx-interval:2
[2019-Aug-06 18:49:27.153441] [debug] [hw.cpp:130:write] Lldp-global-config: hw-item:[rc:un-set data:0] system_name:overcloud-compute-acivpp-0 tx-hold:5 tx-interval:2
[2019-Aug-06 18:49:27.153514] [debug] [rpc_cmd.hpp:116:operator()] Lldp-global-config: hw-item:[rc:un-set data:0] system_name:overcloud-compute-acivpp-0 tx-hold:5 tx-interval:2 0
[2019-Aug-06 18:49:27.153610] [debug] [singular_db.hpp:74:find_or_add] Lldp-binding: interface:[opflexvpp type:AFPACKET hdl:hw-item:[rc:invalid data:4294967295] l2-address:[hw-item:[rc:un-set data:00]] admin-state:hw-item:[rc:no-op data:up] oper-state:down] port_desc:uplink-interface hw-item:[rc:no-op data:0]
[2019-Aug-06 18:49:27.153658] [debug] [hw.cpp:130:write] Lldp-bind: hw-item:[rc:no-op data:0] itf:4294967295 port_desc:uplink-interface
[2019-Aug-06 18:49:27.153726] [debug] [rpc_cmd.hpp:116:operator()] Lldp-bind: hw-item:[rc:no-op data:0] itf:4294967295 port_desc:uplink-interface -2
[2019-Aug-06 18:49:27.153782] [error] [hw.cpp:149:write] Failed to execute: Lldp-bind: hw-item:[rc:invalid data:0] itf:4294967295 port_desc:uplink-interface
[2019-Aug-06 18:49:27.153865] [debug] [singular_db.hpp:74:find_or_add] interface:[opflexvpp.4093 type:AFPACKET hdl:hw-item:[rc:no-op data:4294967295] l2-address:[hw-item:[rc:un-set data:00]] admin-state:hw-item:[rc:no-op data:up] oper-state:down]
[2019-Aug-06 18:49:27.153919] [debug] [hw.cpp:130:write] sub-itf-create: hw-item:[rc:no-op data:4294967295] parent:4294967295 vlan:4093
[2019-Aug-06 18:49:27.153980] [debug] [interface.hpp:350:operator()] sub-itf-create: hw-item:[rc:no-op data:4294967295] parent:4294967295 vlan:4093 res:-2 sw-if-index:-1
[2019-Aug-06 18:49:27.154062] [debug] [hw.cpp:130:write] dhcp-events
[2019-Aug-06 18:49:27.154132] [debug] [singular_db.hpp:74:find_or_add] DHCP-client: interface:[opflexvpp.4093 type:AFPACKET