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.

Currently, we have a package "NetworkManager-config-routing-rules" which provides /etc/NetworkManager/dispatcher.d/10-ifcfg-rh-routes.sh .

The name of this package is not nice, because it contains no configuration file.





An alternative would be to merge the script into NetworkManager package.

Pro/contra for having a separate package:

  + users who don't have route-files (the majority!), don't pay for
    the overhead to invoke the dispatcher script. Although we have now 
    "nowait", there is still an overhead. NM even optimizes for the 
    case where there are no pre-up scripts -- if we always install 
    such a script, the optimization becomes useless
    https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/src/nm-dispatcher.c?id=d5c192201a4621c1b62479082147e462b5cf897a#n504
 
  + without a separate package, the user has no way to disable
    10-ifcfg-rh-routes.sh to avoid the overhead. Otherwise, he
    can simply remove NetworkManager-config-routing-rules package.

  - users who need support for policy routing, need to install the
    package explicitly. Which is non-obvious:
    See https://bugzilla.redhat.com/show_bug.cgi?id=1160013#c44

  - yet another NetworkManager-* package...



I propose to keep the package, but rename it to NetworkManager-dispatcher-routing-rules

[root@wlan-r2s5 ~]# rpm -q --qf '[%{provides}\n]' NetworkManager-config-routing-rules
NetworkManager-config-routing-rules

Installing:
 NetworkManager-dispatcher-routing-rules                  noarch                  1:1.4.0-0.1.git20160606.b769b4df.el7                     beaker-Server-optional                  123 k
     replacing  NetworkManager-config-routing-rules.x86_64 1:1.0.6-27.el7


[root@wlan-r2s5 ~]# rpm -q --qf '[%{provides}\n]' NetworkManager-dispatcher-routing-rules
NetworkManager-config-routing-rules
NetworkManager-dispatcher-routing-rules
[root@wlan-r2s5 ~]# rpm -q --qf '[%{obsoletes}\n]' NetworkManager-dispatcher-routing-rules
NetworkManager-config-routing-rules

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/RHSA-2016-2581.html