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:

IP address of 127.x.x.x family is not removed from eth interface during ifdown eth

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

initscripts-9.03.49-1.el6.x86_64

How reproducible:

Always

Steps to Reproduce:
1. configure /etc/sysconfig/network-scripts/ifcfg-eth0 with IPADDR=127.x.x.x (any IP from 127.0.0.0/8 will do)
2. ifup eth0
3. Check that the IP is present there:
# ip addr sh eth0
4. ifdown eth0


Actual results:

Address from step 1 is still present on the interface

Expected results:

Address from step 1 is removed from the interface after step 4

Additional info:

ifdown works properly with any (tested) IP ouside of 127.0.0.0/8

Culprit is fix for bug https://bugzilla.redhat.com/show_bug.cgi?id=698781

Can you try this patch? https://git.fedorahosted.org/cgit/initscripts.git/commit/?id=be40a46a55b6e53a02c4824da68fd7d2f96c2fc6

https://git.fedorahosted.org/cgit/initscripts.git/commit/?h=rhel6-branch&id=78cbc202ad90ffc9256bfd3b45c423eeff0e97b5

I think this fix may be causing a regression:

https://bugzilla.redhat.com/show_bug.cgi?id=1292875


I apologize if opening a new bug was not warranted.


Thank you,

Patrick

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/RHBA-2016-0951.html