Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1888437

Summary:	[DDF] This example configuration may prevent easy recovery if the network used to access NFS server is VLAN tagged and
Product:	Red Hat OpenStack	Reporter:	Direct Docs Feedback <ddf-bot>
Component:	documentation	Assignee:	Joanne O'Flynn <joflynn>
Status:	CLOSED CURRENTRELEASE	QA Contact:	RHOS Documentation Team <rhos-docs>
Severity:	high	Docs Contact:
Priority:	high
Version:	13.0 (Queens)	CC:	ebeaudoi, elicohen, gregraka, jbadiapa, joflynn, myadla, nweinber, rmetrich, vfarias
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-07-14 13:15:55 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Direct Docs Feedback 2020-10-14 20:47:44 UTC

This example configuration may prevent easy recovery if the network used to access NFS server is VLAN tagged and overcloud nodes vlan interfaces are all configured in open vswitch bridges. In this situation, 8021q module isn't loaded and ReaR won't copy it to the recovery image.

To avoid this issue, it's possible to add a line as described below which will copy all modules to the recovery image. 

MODULES=( 'all_modules' )


Reported by: vagnerfarias

https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/13/html/undercloud_and_control_plane_back_up_and_restore/install-and-configure-rear-osp-ctlplane-br#annotations:0a5e8485-7b1e-432b-ae8a-b78792d43c79

Comment 1 Vagner Farias 2020-10-14 21:02:13 UTC

Details at https://github.com/rear/rear/issues/1202#issuecomment-301070169. This is the default configuration in ReaR 2.5

Comment 6 Juan Badia Payno 2021-01-15 13:53:13 UTC

As a workaround to avoid the networking issue the "BACKUP_URL=iso:///backup/" can be added to the /etc/rear/local.conf. This configuration all the system backup will be attached to the iso and the restoration won't need the network.

Comment 7 Juan Badia Payno 2021-01-28 12:26:38 UTC


ReaR does not know how to deal with OVS interfaces so those interfaces are skipped on the restoration.
There are a couple of workarounds:
  1.- The one on commnet#6 of this BZ.
      Basically avoid network issues by adding all the backup data on the boot iso.

  2.- Configure manually those interfaces in the same way as [1]
    2.1 Add the configured commands on the PRE_RECOVERY_SCRIPT on the /etc/rear/local.conf
    PRE_RECOVERY_SCRIPT=/usr/share/rear/skel/default/etc/scripts/system-setup.d/77-my-network-setup.sh

    2.2 Create a file at /usr/share/rear/skel/default/etc/scripts/system-setup.d/77-my-network-setup.sh with the needed commands. 
    As an example **THIS MAY NOT WORK FOR YOU**
    [stack@site-undercloud-0 ~]$ cat /usr/share/rear/skel/default/etc/scripts/system-setup.d/77-my-network-setup.sh
    ip link add br-ctlplane type bridge
    ip link set br-ctlplane up
    ip link set eth0 up
    ip link set eth0 master br-ctlplane
    ip addr add 192.168.24.1/24 dev br-ctlplane
    ip addr add 192.168.24.3/32 dev br-ctlplane
    ip addr add 192.168.24.2/32 dev br-ctlplane

  3.- Configure manually those interfaces using the NETWORKING_PREPARATION_COMMANDS parameter
      3.1 Add the parameter to /etc/rear/local.conf with the needed commands
        NETWORKING_PREPARATION_COMMANDS=('command 1' ''command 2' 'so on')

[1] .- https://github.com/rear/rear/issues/1818

Comment 11 Joanne O'Flynn 2021-07-14 13:15:55 UTC

Published KBA:

https://access.redhat.com/articles/6182471