Bug 1376786 - ifdown function in net-lib.sh don't work correctly
Summary: ifdown function in net-lib.sh don't work correctly
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: dracut
Version: 7.3
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Lukáš Nykrýn
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-16 12:10 UTC by Jiri Konecny
Modified: 2020-12-15 07:45 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-12-15 07:45:59 UTC
Target Upstream Version:


Attachments (Terms of Use)
fix-ifdown.patch (3.16 KB, application/mbox)
2016-09-16 12:10 UTC, Jiri Konecny
no flags Details

Description Jiri Konecny 2016-09-16 12:10:08 UTC
Created attachment 1201610 [details]
fix-ifdown.patch

Description of problem:
The ifdown() function in net-lib.sh don't remove all Dracut flag files for interface so ifup script called after ifdown() don't work.
Another problem was the `echo "#empty" > /etc/resolv.conf` line when the ifdown is called on interface without the resolv.conf configuration.

How reproducible:
Always

Steps to Reproduce:
1. start Anaconda installation with rd.break kernel parameter
2. call command "ip a;. /usr/lib/net-lib.sh; ifdown eth0; ifup eth0; ip a" instead of eth0 use your interface
3. the interface will be still down even when ifup was called

Actual results:
Interface is not set-up correctly after ifup was called.

Expected results:
Interface should have the same configuration as before ifdown call.

Additional info:
This can be fixed in 7.4 no need to fix this in 7.3 now.
I'm attaching a patch file which should fix this behaviour.

Comment 4 RHEL Program Management 2020-12-15 07:45:59 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.


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