Bug 2035939

Summary: Enable ignoring some network interfaces or IP addresses when creating the rescue ISO
Product: Red Hat Enterprise Linux 8 Reporter: Renaud Métrich <rmetrich>
Component: rearAssignee: Pavel Cahyna <pcahyna>
Status: CLOSED ERRATA QA Contact: David Jež <djez>
Severity: medium Docs Contact: Šárka Jana <sjanderk>
Priority: medium    
Version: 8.5CC: djez, ovasik, pcahyna, sjanderk
Target Milestone: rcFlags: pm-rhel: mirror+
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
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 )`.
Story Points: ---
Clone Of:
: 2056665 (view as bug list) Environment:
Last Closed: 2022-05-10 14:34:16 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:
Embargoed:
Bug Depends On:    
Bug Blocks: 2056665    

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