Bug 1752857

Summary: Rebase iproute to v5.3.0
Product: Red Hat Enterprise Linux 8 Reporter: Andrea Claudi <aclaudi>
Component: iprouteAssignee: Andrea Claudi <aclaudi>
Status: CLOSED ERRATA QA Contact: Jaroslav Aster <jaster>
Severity: medium Docs Contact:
Priority: medium    
Version: 8.2CC: ahleihel, atragler, jaster
Target Milestone: rcKeywords: Rebase
Target Release: 8.2Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: iproute-5.3.0-1.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-04-28 16:44:02 UTC Type: Bug
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: 1634274, 1641122, 1704654, 1717466, 1722275, 1722278, 1727293, 1739277, 1745937, 1746382, 1748721, 1758457, 1758585, 1762304    

Description Andrea Claudi 2019-09-17 12:27:49 UTC 
Description of problem:
RHEL-8.1 ships iproute v4.18, and currently the same version is planned to be shipped in RHEL-8.2.

However several components of kernel will be rebased to v5.3, most notably netlink (see bz#1729404). This will require iproute to catch up with this to avoid netlink-related issues.

My proposal is to rebase iproute to v5.3. This greatly simplifies devel effort, avoiding countless backports due to RFE, bug-fixing and netlink rebase. We can catch up early regressions and covscan issues with CI and gating; this kind of work is even more valuable, since these issues (if any) are likely to be present upstream, and probably need a fix there, now or in the future.
Comment 1 Jaroslav Aster 2019-10-08 15:49:42 UTC 
Hi Andrea,

agree with rebase, but before I'll set qa_ack, could you please write here some summary about new version? New features, what should be tested (sorted by priority), potential risk. Thanks.
Comment 5 errata-xmlrpc 2020-04-28 16:44:02 UTC 
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, 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/RHBA-2020:1785