Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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 1677290 - Satellite Restore/Migration is failing due to nic naming convention changes in RHEL from eth0 to ens123
Summary: Satellite Restore/Migration is failing due to nic naming convention changes i...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Installation
Version: 6.3.5
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Devendra Singh
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-02-14 13:28 UTC by shisingh
Modified: 2023-09-14 05:33 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-04-16 13:09:42 UTC
Target Upstream Version:
Embargoed:
shisingh: needinfo-

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SAT-20072 0 None None None 2023-09-14 05:33:13 UTC

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
Note You need to log in before you can comment on or make changes to this bug.