Project

General

Profile

Actions
Copy link

Bug #25460

closed

foreman-proxy service fails to start if IPv6 is disabled

Added by Evgeni Golov about 6 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
High
Assignee:
Evgeni Golov
Category:
-
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
1643183
Pull request:
https://github.com/theforeman/puppet-foreman_proxy/pull/466
Fixed in Releases:
Found in Releases:
1.18.0
Red Hat JIRA:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1643183

Description of problem:

On satellite 6.4, foreman-proxy service fails to start if IPv6 is disabled

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

Satellite 6.4.0

How reproducible:

Always

Steps to Reproduce:
1. Build a Satellite 6.4
2. Disable the IPv6 using the following article.

https://access.redhat.com/solutions/8709

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

Actual results:

foreman-proxy service fails to start

Expected results:

foreman-proxy should start

Additional info:

journalctl log for foreman-proxy:

systemd1: Starting Foreman Proxy...
smart-proxy24755: Running Foreman Ansible Core in non-SCL context
smart-proxy24755: Errors detected on startup, see log for details. Exiting: Address family not supported by protocol - socket(2)
systemd1: foreman-proxy.service: main process exited, code=exited, status=1/FAILURE
systemd1: Failed to start Foreman Proxy.
systemd1: Unit foreman-proxy.service entered failed state.
systemd1: foreman-proxy.service failed.
~~~

Actions
Copy link

Also available in: Atom PDF