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.
Bug 2035939 - Enable ignoring some network interfaces or IP addresses when creating the rescue ISO
Summary: Enable ignoring some network interfaces or IP addresses when creating the res...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: rear
Version: 8.5
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Pavel Cahyna
QA Contact: David Jež
Šárka Jana
URL:
Whiteboard:
Depends On:
Blocks: 2056665
TreeView+ depends on / blocked
 
Reported: 2021-12-28 17:15 UTC by Renaud Métrich
Modified: 2022-05-10 14:55 UTC (History)
4 users (show)

Fixed In Version: rear-2.6-4.el8
Doc Type: Enhancement
Doc Text:
.Certain network interfaces and IP addresses can be excluded when creating a rescue image You can use the `EXCLUDE_IP_ADDRESSES` variable to ignore certain IP addresses, and the `EXCLUDE_NETWORK_INTERFACES` variable to ignore certain network interfaces when creating a rescue image. On servers with floating addresses, you need to stop the ReaR rescue environment from configuring floating addresses that are moved to a fail-over server until the original server is recovered. Otherwise, a conflict with the fail-over server would occur and cause a consequent disruption of the services running on the fail-over server. To prevent conflicts, you can perform the following actions in the ReaR configuration file `/etc/rear/local.conf`: * exclude the IP addresses in the ReaR by providing the `EXCLUDE_IP_ADDRESSES` variable as a bash array of addresses. For example: `EXCLUDE_IP_ADDRESSES=( 192.0.2.27 192.0.2.10 )`, * exclude the network interfaces in the ReaR by providing the `EXCLUDE_NETWORK_INTERFACES` variable as a bash array of interfaces. For example: `EXCLUDE_NETWORK_INTERFACES=( eno1d1 )`.
Clone Of:
: 2056665 (view as bug list)
Environment:
Last Closed: 2022-05-10 14:34:16 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github rear rear pull 2736 0 None open New IGNORED_IP_ADDRESSES and IGNORED_NETWORK_INTERFACES directives 2021-12-28 17:15:03 UTC
Red Hat Issue Tracker RHELPLAN-106644 0 None None None 2021-12-28 17:21:52 UTC
Red Hat Product Errata RHBA-2022:1966 0 None None None 2022-05-10 14:34:25 UTC

Description Renaud Métrich 2021-12-28 17:15:04 UTC 
Description of problem:

Please backport PR https://github.com/rear/rear/pull/2736 once accepted.
This is quite needed in Enterprise environments when some IP addresses are used as floating addresses for services. Not doing so makes restoring the rescue potentially "kill" the service IP address and causing outage.

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

All rear releases

How reproducible:

Always

Steps to Reproduce:
1. Setup a floating IP address on system1
2. Create a ReaR ISO of system2
3. Setup the floating IP address on another system (system2)
4. Boot the system1 recovery

Actual results:

floating IP address on system2 is not usable due to duplicate IP on the network
Comment 1 Pavel Cahyna 2022-02-15 16:32:29 UTC 
jsmeix from upstream prefers to name the variables EXCLUDE_IP_ADDRESSES and EXCLUDE_NETWORK_INTERFACES, is that ok? I can make amends to the PR if you want.
Comment 13 errata-xmlrpc 2022-05-10 14:34:16 UTC 
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 (rear bug fix and enhancement update), 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://access.redhat.com/errata/RHBA-2022:1966
Note You need to log in before you can comment on or make changes to this bug.