failed to name sriov vfs because the names reserved for representors
Bug #1918397 reported by
waleed mousa
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | neutron |
Undecided
|
Unassigned | ||
Bug Description
After providing a patch to bind sriov vfs in mlnx devices after moving to switchdec, we saw in some cases that the names of the representors were reserved before for the vfs and that failed to get the old names again of the vfs after binding them and name them as ethX.
This creates lot of confusion because now all VFs have 2 visible netdevices, one being the VF representor, and the other being a mlx5-bound VF
Revision history for this message
| Hongbin Lu (hongbin.lu) wrote | #1 |
| Changed in neutron: | |
| status: | New → Incomplete |
| tags: | added: sriov-pci-pt |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #2 |
| Changed in neutron: | |
| status: | Incomplete → Expired |
To post a comment you must log in.
As I commented in https:/
* How did you deploy your OpenStack cloud (i.e. Kolla, Ansible, or manual install).
* Which OS you are using (i.e. Ubuntu, CentOS, etc.)
* Which version of neutron you installed (i.e. master, stable/victoria, etc.)
* How to reproduce the issue you reported.
* How did you configure neutron. Please provide the related config files.
* Please paste the logs of neutron services.
I marked this bug as "incomplete" for now. Please feel free to reset the status to "new" once you provided the information above.