Scenario: install foreman with journald Command "journalctl -u foreman" stdout is expected to match /Redirected to https:\/\/centos8-64-puppet8.example.com\/users\/login/ Failure/Error: its(:stdout) { is_expected.to match(%r{Redirected to https://#{host_inventory['fqdn']}/users/login}) } expected "-- Logs begin at Tue 2024-05-21 09:29:47 UTC, end at Tue 2024-05-21 09:45:03 UTC. --\nMay 21 09:31:4... Starting Foreman...\nMay 21 09:44:44 centos8-64-puppet8.example.com systemd[1]: Started Foreman.\n" to match /Redirected to https:\/\/centos8-64-puppet8.example.com\/users\/login/ Diff: @@ -1,226 +1,451 @@ -/Redirected to https:\/\/centos8-64-puppet8.example.com\/users\/login/ +-- Logs begin at Tue 2024-05-21 09:29:47 UTC, end at Tue 2024-05-21 09:45:03 UTC. -- +May 21 09:31:44 centos8-64-puppet8.example.com systemd[1]: Starting Foreman... +May 21 09:31:46 centos8-64-puppet8.example.com foreman[3010]: => Booting Puma +May 21 09:31:46 centos8-64-puppet8.example.com foreman[3010]: => Rails 6.1.7.7 application starting in production +May 21 09:31:46 centos8-64-puppet8.example.com foreman[3010]: => Run `bin/rails server --help` for more startup options +May 21 09:31:50 centos8-64-puppet8.example.com foreman[3010]: [3010] * Enabling systemd notification integration +May 21 09:31:50 centos8-64-puppet8.example.com foreman[3010]: [3010] Puma starting in cluster mode... +May 21 09:31:50 centos8-64-puppet8.example.com foreman[3010]: [3010] * Puma version: 6.4.2 (ruby 2.7.8-p225) ("The Eagle of Durango") +May 21 09:31:50 centos8-64-puppet8.example.com foreman[3010]: [3010] * Min threads: 5 +May 21 09:31:50 centos8-64-puppet8.example.com foreman[3010]: [3010] * Max threads: 5 +May 21 09:31:50 centos8-64-puppet8.example.com foreman[3010]: [3010] * Environment: production +May 21 09:31:50 centos8-64-puppet8.example.com foreman[3010]: [3010] * Master PID: 3010 +May 21 09:31:50 centos8-64-puppet8.example.com foreman[3010]: [3010] * Workers: 6 +May 21 09:31:50 centos8-64-puppet8.example.com foreman[3010]: [3010] * Restarts: (✔) hot (✖) phased +May 21 09:31:50 centos8-64-puppet8.example.com foreman[3010]: [3010] * Preloading application +May 21 09:31:50 centos8-64-puppet8.example.com foreman[3010]: [3010] * Activated unix:///run/foreman.sock +May 21 09:31:50 centos8-64-puppet8.example.com foreman[3010]: [3010] Use Ctrl-C to stop +May 21 09:31:50 centos8-64-puppet8.example.com foreman[3010]: [3010] Sending status to systemd every 1.0 sec +May 21 09:31:50 centos8-64-puppet8.example.com foreman[3010]: [3010] * Starting control server on unix:///usr/share/foreman/tmp/sockets/pumactl.sock +May 21 09:31:50 centos8-64-puppet8.example.com foreman[3010]: [3010] - Worker 0 (PID: 3018) booted in 0.08s, phase: 0 +May 21 09:31:50 centos8-64-puppet8.example.com foreman[3010]: [3010] - Worker 3 (PID: 3030) booted in 0.07s, phase: 0 +May 21 09:31:50 centos8-64-puppet8.example.com foreman[3010]: [3010] - Worker 4 (PID: 3033) booted in 0.08s, phase: 0 +May 21 09:31:50 centos8-64-puppet8.example.com foreman[3010]: [3010] - Worker 1 (PID: 3020) booted in 0.09s, phase: 0 +May 21 09:31:50 centos8-64-puppet8.example.com foreman[3010]: [3010] - Worker 2 (PID: 3025) booted in 0.1s, phase: 0 +May 21 09:31:50 centos8-64-puppet8.example.com foreman[3010]: [3010] - Worker 5 (PID: 3035) booted in 0.1s, phase: 0 +May 21 09:31:50 centos8-64-puppet8.example.com systemd[1]: Started Foreman. +May 21 09:31:50 centos8-64-puppet8.example.com foreman[3010]: [3010] === puma shutdown: 2024-05-21 09:31:50 +0000 === +May 21 09:31:50 centos8-64-puppet8.example.com foreman[3010]: [3010] - Goodbye! +May 21 09:31:50 centos8-64-puppet8.example.com foreman[3010]: [3010] - Gracefully shutting down workers... +May 21 09:31:50 centos8-64-puppet8.example.com systemd[1]: Stopping Foreman... +May 21 09:31:51 centos8-64-puppet8.example.com foreman[3010]: Exiting +May 21 09:31:51 centos8-64-puppet8.example.com systemd[1]: foreman.service: Succeeded. +May 21 09:31:51 centos8-64-puppet8.example.com systemd[1]: Sto

Scenario: install foreman with journald Command "journalctl -u dynflow-sidekiq@orchestrator" stdout is expected to match /orchestrator in passive mode/ Failure/Error: its(:stdout) { is_expected.to match(%r{orchestrator in passive mode}) } expected "-- Logs begin at Tue 2024-05-21 09:29:47 UTC, end at Tue 2024-05-21 09:45:03 UTC. --\nMay 21 09:31:5...centos8-64-puppet8.example.com systemd[1]: Started Foreman jobs daemon - orchestrator on sidekiq.\n" to match /orchestrator in passive mode/ Diff: @@ -1,42 +1,83 @@ -/orchestrator in passive mode/ +-- Logs begin at Tue 2024-05-21 09:29:47 UTC, end at Tue 2024-05-21 09:45:03 UTC. -- +May 21 09:31:51 centos8-64-puppet8.example.com systemd[1]: Starting Foreman jobs daemon - orchestrator on sidekiq... +May 21 09:31:51 centos8-64-puppet8.example.com dynflow-sidekiq@orchestrator[3240]: 2024-05-21T09:31:51.362Z pid=3240 tid=1mc INFO: Enabling systemd notification integration +May 21 09:31:51 centos8-64-puppet8.example.com dynflow-sidekiq@orchestrator[3240]: 2024-05-21T09:31:51.928Z pid=3240 tid=1mc INFO: Booting Sidekiq 6.5.12 with Sidekiq::RedisConnection::RedisAdapter options {:url=>"redis://localhost:6379/6"} +May 21 09:31:51 centos8-64-puppet8.example.com dynflow-sidekiq@orchestrator[3240]: 2024-05-21T09:31:51.929Z pid=3240 tid=1mc INFO: GitLab reliable fetch activated! +May 21 09:31:57 centos8-64-puppet8.example.com systemd[1]: Started Foreman jobs daemon - orchestrator on sidekiq. +May 21 09:32:52 centos8-64-puppet8.example.com systemd[1]: Stopping Foreman jobs daemon - orchestrator on sidekiq... +May 21 09:32:53 centos8-64-puppet8.example.com systemd[1]: dynflow-sidekiq@orchestrator.service: Succeeded. +May 21 09:32:53 centos8-64-puppet8.example.com systemd[1]: Stopped Foreman jobs daemon - orchestrator on sidekiq. +May 21 09:33:35 centos8-64-puppet8.example.com systemd[1]: Starting Foreman jobs daemon - orchestrator on sidekiq... +May 21 09:33:36 centos8-64-puppet8.example.com dynflow-sidekiq@orchestrator[5722]: 2024-05-21T09:33:36.146Z pid=5722 tid=3pi INFO: Enabling systemd notification integration +May 21 09:33:36 centos8-64-puppet8.example.com dynflow-sidekiq@orchestrator[5722]: 2024-05-21T09:33:36.743Z pid=5722 tid=3pi INFO: Booting Sidekiq 6.5.12 with Sidekiq::RedisConnection::RedisAdapter options {:url=>"redis://localhost:6379/6"} +May 21 09:33:36 centos8-64-puppet8.example.com dynflow-sidekiq@orchestrator[5722]: 2024-05-21T09:33:36.744Z pid=5722 tid=3pi INFO: GitLab reliable fetch activated! +May 21 09:33:42 centos8-64-puppet8.example.com systemd[1]: Started Foreman jobs daemon - orchestrator on sidekiq. +May 21 09:34:53 centos8-64-puppet8.example.com systemd[1]: Stopping Foreman jobs daemon - orchestrator on sidekiq... +May 21 09:34:54 centos8-64-puppet8.example.com systemd[1]: dynflow-sidekiq@orchestrator.service: Succeeded. +May 21 09:34:54 centos8-64-puppet8.example.com systemd[1]: Stopped Foreman jobs daemon - orchestrator on sidekiq. +May 21 09:34:54 centos8-64-puppet8.example.com systemd[1]: Starting Foreman jobs daemon - orchestrator on sidekiq... +May 21 09:34:54 centos8-64-puppet8.example.com dynflow-sidekiq@orchestrator[7329]: 2024-05-21T09:34:54.437Z pid=7329 tid=4sd INFO: Enabling systemd notification integration +May 21 09:34:55 centos8-64-puppet8.example.com dynflow-sidekiq@orchestrator[7329]: 2024-05-21T09:34:55.214Z pid=7329 tid=4sd INFO: Booting Sidekiq 6.5.12 with Sidekiq::RedisConnection::RedisAdapter options {:url=>"redis://localhost:6379/6"} +May 21 09:34:55 centos8-64-puppet8.example.com dynflow-sidekiq@orchestrator[7329]: 2024-05-21T09:34:55.215Z pid=7329 tid=4sd INFO: GitLab reliable fetch activated! +May 21 09:35:03 centos8-64-puppet8.example.com systemd[1]: Started Foreman jobs daemon - orchestrator on sidekiq. +May 21 09:35:27 centos8-64-puppet8.example.com systemd[1]: Stopping Foreman jobs daemon - orchestrator on sidekiq... +May 21 09:35:28 centos8-64-puppet8.example.com systemd[1]: dynflow-sidekiq@orchestrator.service: Succeeded. +May 21 09:35:28 centos8-64-puppet8.example.com s