Bug 2173052

Summary:	Unable to connect to the server using 'ssh' as Network configuration not getting loaded during 'rear'
Product:	Red Hat Enterprise Linux 9	Reporter:	Siddharth <sgandhi>
Component:	rear	Assignee:	Pavel Cahyna <pcahyna>
Status:	CLOSED NOTABUG	QA Contact:	CS System Management SST QE <rhel-cs-system-management-subsystem-qe>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	9.1	CC:	daniel.moraes, jkastnin, pcahyna
Target Milestone:	rc	Keywords:	Triaged
Target Release:	---	Flags:	jkastnin: needinfo-
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-05-05 13:57:59 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:

Description Siddharth 2023-02-23 19:57:31 UTC

Description of problem: 

While doing some tests regarding rear + RHEL9 in order to validate the solution https://access.redhat.com/solutions/2115051) working fine for RHLE7 and RHEL8. So for RHEL7 and RHEL8 where I have ifcfg files for network configuration, I'm able to connect to the network during the rear restore 

I've noticed since RHEL9 works with keyfiles instead ifcfg files the rear is unable to bring the network up. 


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


How reproducible:

While booting the ISO created by ReaR, the ISO is not able to bring the network up because all network configuration is not there - RHEL9 is using keyfilkes instead ifcfg-files and looks like the NetworkManager is not supported by ReaR - at least I didn't find out NetworkManager service there. 



Additional info:

CU is using Netbackup services and to bring the network manually Netbackup services need to start before 'rear recover' with this CU was able to bring the network online and execute the recovery process - which worked as expected - but this is a Workaround solution.

So I believe there is an issue between ReaR and RHEL9 - due to NetworkManager (keyfiles) - and this one is not available on ReaR ISO.
So I've found one more issue - now related to Netbackup:

ReaR rescue is not able to bring Netbackup Services up. But I believe I know why - Netbackup services are using systemd files instead init.d ones for RHEL9. I'm using Netbackup 10.1 and this one was validated for RHEL8 as well - and works as expected!

This one was addressed before for RHEL8 
(https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/8.4_release_notes/bug_fixes)

Comment 1 Pavel Cahyna 2023-03-03 17:46:11 UTC

Thank you for the report, I will have a look.

Concerning Netbackup, do I understand correctly that the same version (10.1) is using systemd units on RHEL 9 and init scripts on RHEL 8, so the startup depends not on the Netbackup version, but the RHEL version? That sounds a bit unusual (since RHEL has supported systemd units since RHEL 7).

Comment 2 danmsi 2023-03-08 18:23:45 UTC

Hi Pavel,

Thank you for your reply.

The issue is not related to RedHat and yes to ReaR - rear is not able to bring Netbackup services online while using RHEL9 - due Netbackup services is using systemd files instead init.d files for this specific RedHat version.

Comment 4 Joerg 2023-04-19 13:13:35 UTC

@pcahyna The customer has confirmed that they use the same machine for recover as for backup. So same NIC, same MAC Addr.

Regards,  
Joerg