Hide Forgot
Also check - https://bugzilla.redhat.com/show_bug.cgi?id=1643177
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: -- Logs begin at Fri 2018-10-19 12:36:58 MDT, end at Fri 2018-10-19 13:14:57 MDT. -- Oct 19 13:14:56 satellite.example.com systemd[1]: Starting Foreman Proxy... Oct 19 13:14:57 satellite.example.com smart-proxy[24755]: Running Foreman Ansible Core in non-SCL context Oct 19 13:14:57 satellite.example.com smart-proxy[24755]: Errors detected on startup, see log for details. Exiting: Address fa mily not supported by protocol - socket(2) Oct 19 13:14:57 satellite.example.com systemd[1]: foreman-proxy.service: main process exited, code=exited, status=1/FAILURE Oct 19 13:14:57 satellite.example.com systemd[1]: Failed to start Foreman Proxy. Oct 19 13:14:57 satellite.example.com systemd[1]: Unit foreman-proxy.service entered failed state. Oct 19 13:14:57 satellite.example.com systemd[1]: foreman-proxy.service failed.
*** Bug 1643177 has been marked as a duplicate of this bug. ***
This was introduced in 77ed56fb0392f8c5f0fec094ccc422b98f2f62fb which changed the bind host to :: instead of *. If the IPv6 kernel module is disabled then you can't listen on ::. The workaround is to listen on * again by rerunning the installer with: --foreman-proxy-bind-host '*' Note that you must quote the * because the shell will expand it otherwise. The long term solution is adding a migration and/or check to the installer that does this automatically for the user.
Confirmed on my system that Ewound's workaround in c8 does indeed resolve the issue. Thanks!
Created redmine issue https://projects.theforeman.org/issues/25460 from this bug
Upstream bug assigned to egolov
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/25460 has been resolved.
Verified fix in 6.4.2 snap 1 1. Disabled IPv6 using the ipv6.disable kernel flag method from https://access.redhat.com/solutions/8709 2. Removed IPv6 entries (including localhost) from /etc/hosts 3. ran "satellite-installer --scenario satellite -v" The install was successful and foreman-proxy started.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:0345