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 1362561 - 'Rule 0 is special. It cannot be deleted or overridden.' has appeared in ip-rule man-page
Summary: 'Rule 0 is special. It cannot be deleted or overridden.' has appeared in ip-r...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: iproute
Version: 7.3
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Phil Sutter
QA Contact: Jaroslav Aster
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-02 13:55 UTC by Jaroslav Aster
Modified: 2016-11-03 23:40 UTC (History)
1 user (show)

Fixed In Version: iproute-3.10.0-72.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-03 23:40:09 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2016:2162 0 normal SHIPPED_LIVE iproute bug fix and enhancement update 2016-11-03 13:14:33 UTC

Description Jaroslav Aster 2016-08-02 13:55:49 UTC
Description of problem:

'Rule 0 is special. It cannot be deleted or overridden.' has appeared in ip-rule man-page. This sentence was removed from ip-rule man-page, as a fix of bug 1169874, because it is not true on rhel-7. It is a regression.


Version-Release number of selected component (if applicable):

iproute-3.10.0-71.el7


How reproducible:

100%


Steps to Reproduce:

# rpm -q iproute
iproute-3.10.0-71.el7.x86_64

# man ip-rule | col -b | grep 'Rule 0 is special. It cannot be deleted or overridden.'
              Rule 0 is special. It cannot be deleted or overridden.


Actual results:

There is 'Rule 0 is special. It cannot be deleted or overridden.' in ip-rule man-page.


Expected results:

There is no 'Rule 0 is special. It cannot be deleted or overridden.' in ip-rule man-page.

Comment 2 Phil Sutter 2016-08-02 16:07:40 UTC
Oh, indeed. I have fixed this upstream with following commit:

commit 0ce05841d58b42ef39ce7144dc31e77970e5d2e0
Author: Phil Sutter <phil>
Date:   Fri Mar 4 12:52:41 2016 +0100

    doc, man: ip-rule: Remove incorrect statement about rule 0
    
    The documentation is wrong here: it is indeed possible to remove policy
    rule 0 and recreate it afterwards. Therefore remove these statements.
    
    Signed-off-by: Phil Sutter <phil>

Comment 6 errata-xmlrpc 2016-11-03 23:40:09 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://rhn.redhat.com/errata/RHEA-2016-2162.html


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