Bug 1677290

Summary:	Satellite Restore/Migration is failing due to nic naming convention changes in RHEL from eth0 to ens123
Product:	Red Hat Satellite	Reporter:	shisingh
Component:	Installation	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED WONTFIX	QA Contact:	Devendra Singh <desingh>
Severity:	medium	Docs Contact:
Priority:	high
Version:	6.3.5	CC:	cmarinea, zhunting
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused	Flags:	shisingh: needinfo-
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-04-16 13:09:42 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 shisingh 2019-02-14 13:28:34 UTC

Description of problem: Satellite Migration/Restore from one RHEL Server to other RHEL server is failing due to changes in the naming conventions of nic interfaces.

Version-Release number of selected component (if applicable): 
Red Hat Satellite 6.3.5
RHEL 7.6



How reproducible: Always


Steps to Reproduce:
1. Create two Red Hat Satellite 6.3 Server each having different types of network interfaces e.g Sat1 and Sat2.

2. Make sure that the naming conventions on the Red Hat Satellite Server are different i.e on Sat1 Satellite Server it is named as eth0, eth1 and on Sat2 Satellite Server it is named as ens123, ens234.

3. Configure dhcp and dns on one Red Hat Satellite Server Sat1 and sync some of the Red Hat Repositories.

4. Take a satellite backup for Sat1 Satellite Server

5. Run satellite-restore on the Sat2.

Actual results: Satellite-restore fails with the below mentioned error message:

============
[ERROR 2019-02-11 09:04:03 verbose]  Could not get the ip address from fact ipaddress_eth1 at /usr/share/foreman-installer/modules/foreman_proxy/manifests/proxydhcp.pp:8 on node dpl001a.mgt.ccveu.net
[ERROR 2019-02-11 09:04:03 verbose] /usr/share/ruby/vendor_ruby/puppet/parser/functions/fail.rb:3:in `block in <top (required)>'
============


Expected results: It should complete the satellite restore process using the backup provided.


Additional info: 

If we change the name of the nic interface in the "/etc/foreman-installer/scenarios.d/satellite_answers.yaml" configuration file from the backup and then run the satellite-restore, it continues the process successfully.

Comment 1 Christian Marineau 2019-02-15 16:39:32 UTC

I would expect Satellite administrator to re-install their server as-is. Especially if there are using the dhcp feature in Satellite that needs to rely on the name of the interfaces. However, it is something annoying and easy to forget. Maybe something to adjust in our Docs as a requirement for restoring, and a good candidate for a KCS?

Comment 4 Zach Huntington-Meath 2020-04-16 13:09:42 UTC

The installer cannot guess what changed, the admin has to know what is going to change.

Comment 5 Red Hat Bugzilla 2023-09-14 05:23:35 UTC

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days