yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #96118
[Bug 2116087] [NEW] remote-managed vnic-type binding profile validation error
Public bug reported:
When using the remote-managed workflow [0], Neutron fails to bind the
port when surplus capabilities are present.
It appears that more recent hardware, such as the NVIDIA BlueField-3
DPU, exposes these capabilities in a different way than the hardware
used during original development.
Symptom:
WARNING neutron.plugins.ml2.drivers.ovn.mech_driver.mech_driver Refusing to bind port 36581579-67f7-4a96-836a-ef864d850efa due to no OVN chassis for host: X
The input port looks like this:
{'admin_state_up': True,
'allowed_address_pairs': [],
'binding:host_id': 'XXX',
'binding:profile': {'capabilities': ['rx',
'tx',
'sg',
'tso',
'gso',
'gro',
'rxvlan',
'txvlan',
'rxhash',
'rdma',
'txudptnl'],
'card_serial_number': '52TF43G01CW',
'pci_slot': '0000:41:10.0',
'pci_vendor_info': '15b3:101e',
'pf_mac_address': '58:a2:e1:f9:4f:72',
'physical_network': 'physnet1',
'vf_num': 126},
'binding:vnic_type': 'remote-managed',
...}
The result from validate_and_get_data_from_binding_profile() is unexpectedly:
BPInfo(
bp_param={},
vnic_type='remote-managed',
capabilities=['rx', 'tx', 'sg', 'tso', 'gso', 'gro', 'rxvlan', 'txvlan', 'rxhash', 'rdma', 'txudptnl'])
So we likely need to expand the validation code to accept additional
capabilities being present for remote-managed VNICs.
0: https://docs.openstack.org/neutron/latest/admin/ovn/smartnic_dpu.html
** Affects: neutron
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/2116087
Title:
remote-managed vnic-type binding profile validation error
Status in neutron:
New
Bug description:
When using the remote-managed workflow [0], Neutron fails to bind the
port when surplus capabilities are present.
It appears that more recent hardware, such as the NVIDIA BlueField-3
DPU, exposes these capabilities in a different way than the hardware
used during original development.
Symptom:
WARNING neutron.plugins.ml2.drivers.ovn.mech_driver.mech_driver Refusing to bind port 36581579-67f7-4a96-836a-ef864d850efa due to no OVN chassis for host: X
The input port looks like this:
{'admin_state_up': True,
'allowed_address_pairs': [],
'binding:host_id': 'XXX',
'binding:profile': {'capabilities': ['rx',
'tx',
'sg',
'tso',
'gso',
'gro',
'rxvlan',
'txvlan',
'rxhash',
'rdma',
'txudptnl'],
'card_serial_number': '52TF43G01CW',
'pci_slot': '0000:41:10.0',
'pci_vendor_info': '15b3:101e',
'pf_mac_address': '58:a2:e1:f9:4f:72',
'physical_network': 'physnet1',
'vf_num': 126},
'binding:vnic_type': 'remote-managed',
...}
The result from validate_and_get_data_from_binding_profile() is unexpectedly:
BPInfo(
bp_param={},
vnic_type='remote-managed',
capabilities=['rx', 'tx', 'sg', 'tso', 'gso', 'gro', 'rxvlan', 'txvlan', 'rxhash', 'rdma', 'txudptnl'])
So we likely need to expand the validation code to accept additional
capabilities being present for remote-managed VNICs.
0:
https://docs.openstack.org/neutron/latest/admin/ovn/smartnic_dpu.html
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/2116087/+subscriptions
Follow ups