Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1704654

Summary: [kselftests] net/fib_rule_tests.sh: tos 0x10 renamed to lowdelay
Product: Red Hat Enterprise Linux 8 Reporter: Hangbin Liu <haliu>
Component: iprouteAssignee: Andrea Claudi <aclaudi>
Status: CLOSED ERRATA QA Contact: Jaroslav Aster <jaster>
Severity: medium Docs Contact:
Priority: medium    
Version: 8.1CC: aloughla, atragler, ivecera, jaster, rkhan
Target Milestone: rcFlags: pm-rhel: mirror+
Target Release: 8.2   
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:43:54 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: 1752857    
Bug Blocks: 1704655    

Description Hangbin Liu 2019-04-30 09:20:55 UTC
Description of problem:
run kernel selftests net/fib_rule_tests.sh failed as current iproute renamed 0x10 to lowdelay

Version-Release number of selected component (if applicable):
iproute-4.18.0-11.el8.x86_64

How reproducible:


Steps to Reproduce:
# ip rule add tos 0x10 table 100

Actual results:
# ip rule
0:      from all lookup local
32765:  from all tos lowdelay lookup 100
32766:  from all lookup main
32767:  from all lookup default

Expected results:
# ip rule
0:      from all lookup local
32765:  from all tos 0x10 lookup 100
32766:  from all lookup main
32767:  from all lookup default

Additional info:

in /etc/iproute2/rt_dsfield it shows

# Deprecated values dropped upstream
# Kept in RHEL for backwards-compatibility
0x00   default
0x10   lowdelay
0x08   throughput
0x04   reliability
# This value overlap with ECT, do not use it!
0x02   mincost
# These values seems do not want to die, Cisco likes them by a strange reason.
0x20   priority
0x40   immediate
[snip]

I'm not sure if we need to keep this. Upstream commit said

commit eb5d01ff38080935a1a528e4c99cab42bf93d762
Author: Stephen Hemminger <stephen>
Date:   Sun Sep 14 20:40:37 2014 -0700

    update dsfield file values

    Update the rt_dsfield file to contain values defined in current RFC.
    The days of TOS precedence are gone, even Cisco doesn't refer
    to these in the documents.

Comment 1 Phil Sutter 2019-05-03 11:53:06 UTC
Hi Hangbin,

It was a deliberate decision to keep these outdated names, see: https://bugzilla.redhat.com/show_bug.cgi?id=1595683

Since one can't know what a user keeps in his rt_dsfield file, I guess the *real* solution to this problem is to introduce a flag which makes iproute ignore all those configs and instead print the numeric values. Maybe we could introduce '-N'/'-Numeric' flag upstream?

Cheers, Phil

Comment 2 Hangbin Liu 2019-05-05 03:15:13 UTC
(In reply to Phil Sutter from comment #1)
> Maybe we could introduce '-N'/'-Numeric' flag upstream?

Yes, that makes sense to me.

Thanks
Hangbin

Comment 3 Hangbin Liu 2019-06-21 04:45:40 UTC
FYI, upstream iproute-next commit ca697cee4cfcb8 ("ip: add a new parameter -Numeric")

Comment 8 errata-xmlrpc 2020-04-28 16:43:54 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