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.
Description of problem:
The current ReaR 2.4 code has nothing to deal with NetworkManager managed interfaces (check /usr/share/rear/prep/GNU/Linux/210_include_dhclient.sh).
This leads to not being able to configure the recovery with DHCP, because internally it expects one of "dhclient" or "dhcpcd" (and related IPv6 versions).
With ReaR 2.6 the code has been redesigned to exit in error if USE_DHCLIENT=y is specified and no DHCP binary is found.
I think we need to at least fail and not let the code create the following /etc/rear/rescue.conf snippet in the ISO, when "dhclient" is not installed ("dhcp-client" package):
---
# The following 3 lines were added through 210_include_dhclient.sh
USE_DHCLIENT=yes
DHCLIENT_BIN=
DHCLIENT6_BIN=
---
Version-Release number of selected component (if applicable):
rear-2.4-18.el8.x86_64
How reproducible:
Always
Steps to Reproduce:
1. Create an ISO in full debug mode
2. Check /etc/rear/rescue.conf generated in the ISO
Hello Renaud,
(In reply to Renaud Métrich from comment #0)
> With ReaR 2.6 the code has been redesigned to exit in error if
> USE_DHCLIENT=y is specified and no DHCP binary is found.
To be sure, do I understand correctly that in ReaR 2.6 the problem is fixed? If so, it will be fixed by the upcoming rebase (bz1988493). You can try the package provided in Beta.
Description of problem: The current ReaR 2.4 code has nothing to deal with NetworkManager managed interfaces (check /usr/share/rear/prep/GNU/Linux/210_include_dhclient.sh). This leads to not being able to configure the recovery with DHCP, because internally it expects one of "dhclient" or "dhcpcd" (and related IPv6 versions). With ReaR 2.6 the code has been redesigned to exit in error if USE_DHCLIENT=y is specified and no DHCP binary is found. I think we need to at least fail and not let the code create the following /etc/rear/rescue.conf snippet in the ISO, when "dhclient" is not installed ("dhcp-client" package): --- # The following 3 lines were added through 210_include_dhclient.sh USE_DHCLIENT=yes DHCLIENT_BIN= DHCLIENT6_BIN= --- Version-Release number of selected component (if applicable): rear-2.4-18.el8.x86_64 How reproducible: Always Steps to Reproduce: 1. Create an ISO in full debug mode 2. Check /etc/rear/rescue.conf generated in the ISO