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

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:44 UTC, end at Tue 2024-05-21 09:45:18 UTC. --\nMay 21 09:31:5...centos8-64-puppet7.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:44 UTC, end at Tue 2024-05-21 09:45:18 UTC. -- +May 21 09:31:50 centos8-64-puppet7.example.com systemd[1]: Starting Foreman jobs daemon - orchestrator on sidekiq... +May 21 09:31:50 centos8-64-puppet7.example.com dynflow-sidekiq@orchestrator[3243]: 2024-05-21T09:31:50.675Z pid=3243 tid=1mf INFO: Enabling systemd notification integration +May 21 09:31:51 centos8-64-puppet7.example.com dynflow-sidekiq@orchestrator[3243]: 2024-05-21T09:31:51.268Z pid=3243 tid=1mf INFO: Booting Sidekiq 6.5.12 with Sidekiq::RedisConnection::RedisAdapter options {:url=>"redis://localhost:6379/6"} +May 21 09:31:51 centos8-64-puppet7.example.com dynflow-sidekiq@orchestrator[3243]: 2024-05-21T09:31:51.269Z pid=3243 tid=1mf INFO: GitLab reliable fetch activated! +May 21 09:31:56 centos8-64-puppet7.example.com systemd[1]: Started Foreman jobs daemon - orchestrator on sidekiq. +May 21 09:32:54 centos8-64-puppet7.example.com systemd[1]: Stopping Foreman jobs daemon - orchestrator on sidekiq... +May 21 09:32:54 centos8-64-puppet7.example.com systemd[1]: dynflow-sidekiq@orchestrator.service: Succeeded. +May 21 09:32:54 centos8-64-puppet7.example.com systemd[1]: Stopped Foreman jobs daemon - orchestrator on sidekiq. +May 21 09:33:36 centos8-64-puppet7.example.com systemd[1]: Starting Foreman jobs daemon - orchestrator on sidekiq... +May 21 09:33:36 centos8-64-puppet7.example.com dynflow-sidekiq@orchestrator[5739]: 2024-05-21T09:33:36.486Z pid=5739 tid=3qv INFO: Enabling systemd notification integration +May 21 09:33:37 centos8-64-puppet7.example.com dynflow-sidekiq@orchestrator[5739]: 2024-05-21T09:33:37.060Z pid=5739 tid=3qv INFO: Booting Sidekiq 6.5.12 with Sidekiq::RedisConnection::RedisAdapter options {:url=>"redis://localhost:6379/6"} +May 21 09:33:37 centos8-64-puppet7.example.com dynflow-sidekiq@orchestrator[5739]: 2024-05-21T09:33:37.061Z pid=5739 tid=3qv INFO: GitLab reliable fetch activated! +May 21 09:33:42 centos8-64-puppet7.example.com systemd[1]: Started Foreman jobs daemon - orchestrator on sidekiq. +May 21 09:34:50 centos8-64-puppet7.example.com systemd[1]: Stopping Foreman jobs daemon - orchestrator on sidekiq... +May 21 09:34:51 centos8-64-puppet7.example.com systemd[1]: dynflow-sidekiq@orchestrator.service: Succeeded. +May 21 09:34:51 centos8-64-puppet7.example.com systemd[1]: Stopped Foreman jobs daemon - orchestrator on sidekiq. +May 21 09:34:51 centos8-64-puppet7.example.com systemd[1]: Starting Foreman jobs daemon - orchestrator on sidekiq... +May 21 09:34:51 centos8-64-puppet7.example.com dynflow-sidekiq@orchestrator[7357]: 2024-05-21T09:34:51.890Z pid=7357 tid=4rl INFO: Enabling systemd notification integration +May 21 09:34:52 centos8-64-puppet7.example.com dynflow-sidekiq@orchestrator[7357]: 2024-05-21T09:34:52.627Z pid=7357 tid=4rl INFO: Booting Sidekiq 6.5.12 with Sidekiq::RedisConnection::RedisAdapter options {:url=>"redis://localhost:6379/6"} +May 21 09:34:52 centos8-64-puppet7.example.com dynflow-sidekiq@orchestrator[7357]: 2024-05-21T09:34:52.628Z pid=7357 tid=4rl INFO: GitLab reliable fetch activated! +May 21 09:35:00 centos8-64-puppet7.example.com systemd[1]: Started Foreman jobs daemon - orchestrator on sidekiq. +May 21 09:35:22 centos8-64-puppet7.example.com systemd[1]: Stopping Foreman jobs daemon - orchestrator on sidekiq... +May 21 09:35:24 centos8-64-puppet7.example.com systemd[1]: dynflow-sidekiq@orchestrator.service: Succeeded. +May 21 09:35:24 centos8-64-puppet7.example.com s