foreman-nightly-deb-pipeline 314 failed

jenkins · March 18, 2020, 8:33am

Foreman DEB nightly pipeline failed:

https://ci.theforeman.org/job/foreman-nightly-deb-pipeline/314/

foreman-nightly-ubuntu1804-upgrade-test (failed)
foreman-nightly-debian10-test (passed)
foreman-nightly-debian10-upgrade-test (failed)
foreman-nightly-ubuntu1804-test (passed)

ekohl · March 18, 2020, 1:14pm

For now we’ve reverted the puma change in upgrades:

github.com/theforeman/foreman-installer

Revert "Fixes #29282: Add migration to enable Puma"

committed 11:38AM - 18 Mar 20 UTC

ekohl

+0 -2

This reverts commit 0b244f5623889585eb2b1a16a20ef659ebd2195f. This currently do…esn't work because systemctl start foreman returns immediately, even before the service is up. Essentially it's a race condition which for some reason this isn't an issue in installation. There are two possible solutions to make this reliable: switch from the service type simple to notify. However, the puma-plugin-systemd is unmaintained and incompatible with the currently used puma version. The other solution is systemd socket activation where systemd immediately opens a socket that blocks until it's started up. This should work, but the SCL tooling is proving to complicate this. To unblock the current nightly packages, a short term revert is in order while we work on the proper solution.

I’m getting further with systemd socket activation and have an initial setup that now works on my EL7 setup. Going to test the same thing on Debian and Ubuntu and will work it into a PR if it does.

system · March 25, 2020, 1:14pm

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