Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
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 4RHEL 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.
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.