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 1888402 - [RFE] Satellite 6 with Content Hosts behind NAT is not working properly
Summary: [RFE] Satellite 6 with Content Hosts behind NAT is not working properly
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Registration
Version: 6.7.0
Hardware: All
OS: All
medium
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Sam Bible
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-10-14 18:49 UTC by achadha
Modified: 2023-12-15 19:47 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-07-29 07:08:14 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Comment 5 Mike McCune 2020-11-18 14:59:43 UTC
There exists the ability to override the IP address facts with subscription-manager as reported to the Satellite during registration.

You can do this via specification of facts file outlined here:

1) On host behind NAT network, search for all subscription-manager facts containing the NAT-ed IP address:

# subscription-manager facts |grep '.*ip.*address'

net.interface.eth0.ipv4_address: 10.10.99.99
net.interface.eth0.ipv4_address_list: 10.10.99.99
net.interface.eth0.ipv6_address.link: fe80::7e60:1587:6fcc:d58c
net.interface.eth0.ipv6_address.link_list: fe80::39a3:baf8:a2e2:3303, fe80::1a59:d181:6ef6:335d, fe80::7e60:1587:6fcc:d58c
net.interface.lo.ipv4_address: 127.0.0.1
net.interface.lo.ipv4_address_list: 127.0.0.1
net.interface.lo.ipv6_address.host: ::1
net.interface.lo.ipv6_address.host_list: ::1
network.ipv4_address: 10.10.99.99
network.ipv6_address: fe80::7e60:1587:6fcc:d58c, fe80::1a59:d181:6ef6:335d, fe80::39a3:baf8:a2e2:3303


2) Edit your override file, open a new file:

/etc/rhsm/facts/ip.facts

3) Ensure the contents contain the ipv4 network addresses and interfaces for the

{"network.ipv4_address": "10.10.99.99", "net.interface.eth0.ipv4_address":"10.10.99.99","net.interface.eth0.ipv4_address_list":"10.10.99.99"}


4) Delete the host entirely from the Satellite

5) re-register the host, verify the IP address in the Host Details in the UI shows the overridden value.

6) Check if the IP address is overridden in a way that allows the Remote Execution jobs on the Satellite reach the host.

I've not tried this *exact* scenario with a NAT network because we don't have that setup in any of our labs but I can verify the override works and the Satellite will store the IP as specified in the facts file.

Let us know if this helps the situation

Comment 8 Ron Lavi 2022-07-25 17:38:10 UTC
Hey achadha, is the issue resolved? Can we close this bug?


Note You need to log in before you can comment on or make changes to this bug.