Bug 1376786

Summary: ifdown function in net-lib.sh don't work correctly
Product: Red Hat Enterprise Linux 7 Reporter: Jiri Konecny <jkonecny>
Component: dracutAssignee: Lukáš Nykrýn <lnykryn>
Status: CLOSED WONTFIX QA Contact: qe-baseos-daemons
Severity: medium Docs Contact:
Priority: unspecified    
Version: 7.3CC: dracut-maint-list
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-12-15 07:45:59 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
fix-ifdown.patch none

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.