foreman-nightly-rpm-pipeline 488 failed

jenkins · March 24, 2020, 10:40pm

Foreman RPM nightly pipeline failed:

https://ci.theforeman.org/job/foreman-nightly-rpm-pipeline/488/

foreman-nightly-centos7-test (failed)
foreman-nightly-centos7-upgrade-test (passed)

ekohl · March 24, 2020, 11:06pm

After merging socket activation in core and packaging it needs

github.com/theforeman/puppet-foreman

Refs #29144 - Use systemd socket activation

theforeman:master ← ekohl:29144-systemd-socket-activation

opened 02:55PM - 20 Mar 20 UTC

ekohl

+29 -10

When using systemd socket activation, it's important that the ListenSocket match…es what Puma binds on. Otherwise it may fail. This happens when is configured on [::]:3000 (dual stack) and Puma on 0.0.0.0:3000. Puma will then attempt to bind and fail because the port is already in use. The service bind is now made explicit because systemd's ListenSocket=3000 binds on :: where Puma by default binds on 0.0.0.0:3000. This is IPv4-only, but is what was done prior to this as well. Apache is configured dual stack and the recommended deployment. Note this depends on https://github.com/theforeman/foreman/pull/7536 and https://github.com/theforeman/foreman-packaging/pull/4894 (deb) / https://github.com/theforeman/foreman-packaging/pull/4895 (rpm).

system · March 31, 2020, 11:06pm

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.