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.

Description of problem:

but 
ifdown ethx && ifup ethx
fixes, or works as expected

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


How reproducible:

route-ethx and rule-ethx for each eth0 and eth1

eth0 is on a routeable IP

from eth0-ownNet table external

table external default via eth0-ownNet-gateway
table external to aHost-on.eth1-ownNet dev eth1

eth1 is on a private IP

from eth1-ownNet table internal

table internal default via eth1-ownNet-gateway
table internal to eth1-ownNet dev eth1

routing to aHost-on.eth1-ownNet does not get initialized @ boot time
service network restart
also fails
but ifdown & ifup on the relevant interface fixes it




Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

I'm sorry, but the bug description is too vague. It's hard to even make sense of it what the reporter had in mind.

And since there hasn't been any traffic after BZ was created, I'm closing this BZ.