Bug 2070629
Summary: | Since implementation of uplink_status_propagation, default behavior changed for VF link propagation from auto to disabled | |||
---|---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Rafael Urena <rurena> | |
Component: | openstack-neutron | Assignee: | Rodolfo Alonso <ralonsoh> | |
Status: | CLOSED ERRATA | QA Contact: | Bharath M V <bmv> | |
Severity: | high | Docs Contact: | ||
Priority: | urgent | |||
Version: | 16.1 (Train) | CC: | aruffin, cfields, chrisw, dhill, jamsmith, jelynch, jhardee, jlibosva, ralonsoh, scohen, spapa, tdoucet | |
Target Milestone: | z9 | Keywords: | Triaged | |
Target Release: | 16.1 (Train on RHEL 8.2) | |||
Hardware: | x86_64 | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | openstack-neutron-15.2.1-1.20220406134004.40d217c.el8ost | Doc Type: | Enhancement | |
Doc Text: |
With this update, if the uplink_status_propagation extension is enabled, all single root I/O virtualization (SR-IOV) ports created before the extension enablement set the virtual function (VF) link state to 'auto'. Before this update, an SR-IOV port set the link state to enabled or disabled.
|
Story Points: | --- | |
Clone Of: | ||||
: | 2072460 (view as bug list) | Environment: | ||
Last Closed: | 2022-12-07 20:28:59 UTC | Type: | --- | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | ||||
Bug Blocks: | 2072460, 2072461 |
Description
Rafael Urena
2022-03-31 15:27:04 UTC
Hello Rafael: As commented via mail, the OSP13 behaviour was a workaround for existing customers that needed this feature. The original U/S stable/queens branch didn't set the VF state to "auto" but to "enable/disable". Now we have the consequences of this workaround: the customers migrating to OSP16 now will have VF ports with state "enable/disable" instead of "auto". By default, any existing port won't have the "uplink_status_propagation" flag. This is a DB port child register created when the Neutron port resource is created and the extension enabled. It wasn't considered, when the extension was implemented, that this could apply to existing ports. In this case, this BZ should be considered as a RFE. Regards. KCS has been updated with these changes. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: Red Hat OpenStack Platform 16.1.9 (openstack-neutron) security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:8870 |