Project

General

Profile

Bug #25460

foreman-proxy service fails to start if IPv6 is disabled

Added by Evgeni Golov over 3 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
High
Assignee:
Category:
-
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Fixed in Releases:
Found in Releases:

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.
~~~

Associated revisions

Revision 0940a056 (diff)
Added by Evgeni Golov over 3 years ago

Fixes #25460 - only set the bind_host to :: if IPv6 is available

Revision 141d244a (diff)
Added by Evgeni Golov over 3 years ago

Refs #25460 - adjust tests to test to provide IPv6 fact if needed

History

#1 Updated by Evgeni Golov over 3 years ago

  • Priority changed from Urgent to High
  • Subject changed from On satellite 6.4, foreman-proxy service fails to start if IPv6 is disabled to foreman-proxy service fails to start if IPv6 is disabled
  • Project changed from Foreman to Installer
  • Found in Releases 1.18.0 added

#2 Updated by The Foreman Bot over 3 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/puppet-foreman_proxy/pull/466 added

#3 Updated by Evgeni Golov over 3 years ago

  • Assignee set to Evgeni Golov

#4 Updated by Evgeni Golov over 3 years ago

  • Status changed from Ready For Testing to Closed

Also available in: Atom PDF