Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 1718700

Summary: On satellite 6.5, foreman-proxy service fails to start if IPv6 is disabled
Product: Red Hat Satellite Reporter: Ram Nainsingh Tiruwa <ramsingh>
Component: InstallationAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED DUPLICATE QA Contact: Perry Gagne <pgagne>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.5.0CC: lee.patterson, zhunting
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-07-11 13:40:21 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:

Comment 3 Ram Nainsingh Tiruwa 2019-06-10 01:05:48 UTC 
Description of problem:

On satellite 6.5, Foreman-proxy service fails to start if IPv6 is disabled

Satellite 6.5.0

Steps to Reproduce:
1. Build a Satellite 6.5

2. Disable the IPv6

3. Reboot the system and run "# katello-service restart" and rerun the installer 

Actual results:

foreman-proxy service fails to start

Expected results:

foreman-proxy should start

Additional info:

installer fails with below error :

[ERROR 2019-06-04T16:31:37 main] Jun 04 16:31:27 satellite.example.local systemd[1]: Starting Foreman Proxy...
[ERROR 2019-06-04T16:31:37 main] Jun 04 16:31:28 satellite.example.local smart-proxy[16264]: Running Foreman Ansible Core in non-SCL context
[ERROR 2019-06-04T16:31:37 main] Jun 04 16:31:28 satellite.example.local smart-proxy[16264]: Errors detected on startup, see log for details. Exiting: Address family not supported by protocol - socket(2)
[ERROR 2019-06-04T16:31:37 main] Jun 04 16:31:28 satellite.example.local systemd[1]: foreman-proxy.service: main process exited, code=exited, status=1/FAILURE
[ERROR 2019-06-04T16:31:37 main] Jun 04 16:31:28 satellite.example.local systemd[1]: Failed to start Foreman Proxy.
[ERROR 2019-06-04T16:31:37 main] Jun 04 16:31:28 satellite.example.local systemd[1]: Unit foreman-proxy.service entered failed state.
[ERROR 2019-06-04T16:31:37 main] Jun 04 16:31:28 satellite.example.local systemd[1]: foreman-proxy.service failed.