Bug 1687298 - [OSP14] Fix VF-rep lookup routine to use parent PF number
Summary: [OSP14] Fix VF-rep lookup routine to use parent PF number
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-nova
Version: 14.0 (Rocky)
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: OSP DFG:Compute
QA Contact: OSP DFG:Compute
URL: https://github.com/openstack/os-vif/c...
Whiteboard:
Depends On:
Blocks: 1653846 1686757 1686770 1687300
TreeView+ depends on / blocked
 
Reported: 2019-03-11 08:46 UTC by Bertrand
Modified: 2023-03-21 19:12 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1687300 (view as bug list)
Environment:
Last Closed: 2019-03-15 15:19:53 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Bertrand 2019-03-11 08:46:46 UTC
Fix VF-rep lookup routine to use parent PF number

The current logic in get_representor_port() matches the VF number with
the one in 'phys_port_name' file. If and when multiple PFs on the same
card are configured in switchdev mode, we could end up returning a wrong
representor device. Fix this by including the parent PF number also in
this logic, when 'pfXvfY' (or vfY@pfX) format is used in 'phys_port_name'
file.

github: https://github.com/openstack/os-vif/commit/84688a22db22039f5566c1439c3983db23672a45

This patch appear to be missing from nova-compute container.

Comment 1 Stephen Finucane 2019-03-15 15:19:34 UTC
This was first resolved in python-os-vif-1.9.0-1.el7, which is included in the oldest version of nova-compute container I can see, 14.0-94 [1]. You haven't provided package versions but I suspect you simply need to update to a newer release that included that python-os-vif package version.

[1] https://access.redhat.com/containers/?architecture=AMD64&tab=package-list#/registry.access.redhat.com/rhosp14/openstack-nova-compute/images/14.0-94


Note You need to log in before you can comment on or make changes to this bug.