Canceling since a higher priority waiting request for '1164/merge' exists

Scenario: install foreman 2 workers behaves like an idempotent resource applies with no errors Failure/Error: raise CommandFailure, "Host '#{self}' exited with #{result.exit_code} running:\n #{cmdline}\nLast #{@options[:trace_limit]} lines of output were:\n#{result.formatted_output(@options[:trace_limit])}" Beaker::Host::CommandFailure: Host 'ubuntu2204-64-puppet7.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_101005625.pp.8NtfPo Last 10 lines of output were: �[mNotice: /Stage[main]/Foreman::Service/Foreman::Dynflow::Pool[worker]/Foreman::Dynflow::Worker[worker]/File[/etc/foreman/dynflow/worker.yml]/ensure: removed Info: Foreman::Dynflow::Pool[worker]: Unscheduling all events on Foreman::Dynflow::Pool[worker] �[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@orchestrator] has failures: true �[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@worker-1] has failures: true �[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@worker-2] has failures: true Warning: /Stage[main]/Foreman/Anchor[foreman::service]: Skipping because of failed dependencies Warning: /Stage[main]/Foreman::Register/Foreman_host[foreman-ubuntu2204-64-puppet7.example.com]: Skipping because of failed dependencies Info: Stage[main]: Unscheduling all events on Stage[main] Warning: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-ubuntu2204-64-puppet7.example.com]: Skipping because of failed dependencies �[mNotice: Applied catalog in 138.08 seconds Shared Example Group: "an idempotent resource" called from ./spec/acceptance/dynflow_spec.rb:5

Scenario: install foreman 2 workers behaves like an idempotent resource applies a second time without changes Failure/Error: raise CommandFailure, "Host '#{self}' exited with #{result.exit_code} running:\n #{cmdline}\nLast #{@options[:trace_limit]} lines of output were:\n#{result.formatted_output(@options[:trace_limit])}" Beaker::Host::CommandFailure: Host 'ubuntu2204-64-puppet7.example.com' exited with 4 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_101229126.pp.JCLA8p Last 10 lines of output were: May 14 10:12:28 ubuntu2204-64-puppet7.example.com dynflow-sidekiq@worker-2[12062]: /usr/share/foreman/vendor/ruby/3.0.0/gems/apipie-rails-1.3.0/lib/apipie/validator.rb:330:in `new' May 14 10:12:28 ubuntu2204-64-puppet7.example.com dynflow-sidekiq@worker-2[12062]: /usr/share/foreman/vendor/ruby/3.0.0/gems/apipie-rails-1.3.0/lib/apipie/validator.rb:330:in `build' �[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@orchestrator] has failures: true �[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@worker-1] has failures: true �[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@worker-2] has failures: true Warning: /Stage[main]/Foreman/Anchor[foreman::service]: Skipping because of failed dependencies Warning: /Stage[main]/Foreman::Register/Foreman_host[foreman-ubuntu2204-64-puppet7.example.com]: Skipping because of failed dependencies Warning: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-ubuntu2204-64-puppet7.example.com]: Skipping because of failed dependencies �[mNotice: Applied catalog in 12.46 seconds Shared Example Group: "an idempotent resource" called from ./spec/acceptance/dynflow_spec.rb:5

Scenario: install foreman 2 workers behaves like the foreman application Service "dynflow-sidekiq@orchestrator" is expected to be enabled Failure/Error: it { is_expected.to be_enabled } expected Service "dynflow-sidekiq@orchestrator" to be enabled Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Scenario: install foreman 2 workers behaves like the foreman application Service "dynflow-sidekiq@orchestrator" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "dynflow-sidekiq@orchestrator" to be running Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Scenario: install foreman 2 workers behaves like the foreman application Service "dynflow-sidekiq@worker-1" is expected to be enabled Failure/Error: it { is_expected.to be_enabled } expected Service "dynflow-sidekiq@worker-1" to be enabled Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Scenario: install foreman 2 workers behaves like the foreman application Service "dynflow-sidekiq@worker-1" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "dynflow-sidekiq@worker-1" to be running Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Scenario: install foreman 2 workers behaves like the foreman application Service "foreman" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "foreman" to be running Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Scenario: install foreman 2 workers behaves like the foreman application File "/run/foreman.sock" is expected to be socket Failure/Error: it { should be_socket } expected `File "/run/foreman.sock".socket?` to be truthy, got false Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Scenario: install foreman 2 workers behaves like the foreman application Command "curl -s --cacert /etc/foreman-certs/certificate.pem https://ubuntu2204-64-puppet7.example.com -w '%{redirect_url}' -o /dev/null" stdout is expected to eq "https://ubuntu2204-64-puppet7.example.com/users/login" Failure/Error: its(:stdout) { is_expected.to eq("https://#{host_inventory['fqdn']}#{params.fetch(:expected_login_url_path, '/users/login')}") } expected: #<Encoding:UTF-8> "https://ubuntu2204-64-puppet7.example.com/users/login" got: #<Encoding:US-ASCII> "" (compared using ==) Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Scenario: install foreman 2 workers Service "dynflow-sidekiq@worker-1" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "dynflow-sidekiq@worker-1" to be running

Canceling since a higher priority waiting request for '1164/merge' exists

Scenario: install foreman 2 workers behaves like an idempotent resource applies with no errors Failure/Error: raise CommandFailure, "Host '#{self}' exited with #{result.exit_code} running:\n #{cmdline}\nLast #{@options[:trace_limit]} lines of output were:\n#{result.formatted_output(@options[:trace_limit])}" Beaker::Host::CommandFailure: Host 'centos9-64-puppet8.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_101005616.pp.86FYB8 Last 10 lines of output were: Info: Podman::Quadlet[foreman.container]: Unscheduling all events on Podman::Quadlet[foreman.container] �[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@orchestrator] has failures: true �[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@worker-1] has failures: true �[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@worker-2] has failures: true �[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[foreman.service] has failures: true Warning: /Stage[main]/Foreman/Anchor[foreman::service]: Skipping because of failed dependencies Warning: /Stage[main]/Foreman::Register/Foreman_host[foreman-centos9-64-puppet8.example.com]: Skipping because of failed dependencies Warning: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-centos9-64-puppet8.example.com]: Skipping because of failed dependencies Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 79.26 seconds Shared Example Group: "an idempotent resource" called from ./spec/acceptance/dynflow_spec.rb:5

Scenario: install foreman 2 workers behaves like an idempotent resource applies a second time without changes Failure/Error: raise CommandFailure, "Host '#{self}' exited with #{result.exit_code} running:\n #{cmdline}\nLast #{@options[:trace_limit]} lines of output were:\n#{result.formatted_output(@options[:trace_limit])}" Beaker::Host::CommandFailure: Host 'centos9-64-puppet8.example.com' exited with 4 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_101128449.pp.qZ7JPL Last 10 lines of output were: May 14 10:11:46 centos9-64-puppet8.example.com foreman[3249]: time="2024-05-14T10:11:46Z" level=error msg="stat /usr/share/foreman/.config: no such file or directory" May 14 10:11:46 centos9-64-puppet8.example.com systemd[1]: foreman.service: Main process exited, code=exited, status=1/FAILURE May 14 10:11:46 centos9-64-puppet8.example.com foreman[3256]: time="2024-05-14T10:11:46Z" level=error msg="stat /usr/share/foreman/.config: no such file or directory" May 14 10:11:46 centos9-64-puppet8.example.com systemd[1]: foreman.service: Failed with result 'exit-code'. May 14 10:11:46 centos9-64-puppet8.example.com systemd[1]: Failed to start Foreman. Warning: /Stage[main]/Foreman/Anchor[foreman::service]: Skipping because of failed dependencies Warning: /Stage[main]/Foreman::Register/Foreman_host[foreman-centos9-64-puppet8.example.com]: Skipping because of failed dependencies Warning: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-centos9-64-puppet8.example.com]: Skipping because of failed dependencies �[mNotice: Applied catalog in 13.22 seconds Shared Example Group: "an idempotent resource" called from ./spec/acceptance/dynflow_spec.rb:5

Scenario: install foreman 2 workers behaves like the foreman application Service "dynflow-sidekiq@orchestrator" is expected to be enabled Failure/Error: it { is_expected.to be_enabled } expected Service "dynflow-sidekiq@orchestrator" to be enabled Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Scenario: install foreman 2 workers behaves like the foreman application Service "dynflow-sidekiq@orchestrator" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "dynflow-sidekiq@orchestrator" to be running Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Scenario: install foreman 2 workers behaves like the foreman application Service "dynflow-sidekiq@worker-1" is expected to be enabled Failure/Error: it { is_expected.to be_enabled } expected Service "dynflow-sidekiq@worker-1" to be enabled Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Canceling since a higher priority waiting request for '1164/merge' exists

Scenario: install foreman 2 workers behaves like an idempotent resource applies with no errors Failure/Error: raise CommandFailure, "Host '#{self}' exited with #{result.exit_code} running:\n #{cmdline}\nLast #{@options[:trace_limit]} lines of output were:\n#{result.formatted_output(@options[:trace_limit])}" Beaker::Host::CommandFailure: Host 'centos9-64-puppet7.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_100943623.pp.iLXPpS Last 10 lines of output were: Info: Podman::Quadlet[foreman.container]: Unscheduling all events on Podman::Quadlet[foreman.container] �[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@orchestrator] has failures: true �[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@worker-1] has failures: true �[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@worker-2] has failures: true �[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[foreman.service] has failures: true Warning: /Stage[main]/Foreman/Anchor[foreman::service]: Skipping because of failed dependencies Warning: /Stage[main]/Foreman::Register/Foreman_host[foreman-centos9-64-puppet7.example.com]: Skipping because of failed dependencies Info: Stage[main]: Unscheduling all events on Stage[main] Warning: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-centos9-64-puppet7.example.com]: Skipping because of failed dependencies �[mNotice: Applied catalog in 70.18 seconds Shared Example Group: "an idempotent resource" called from ./spec/acceptance/dynflow_spec.rb:5

Scenario: install foreman 2 workers behaves like the foreman application Service "dynflow-sidekiq@worker-1" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "dynflow-sidekiq@worker-1" to be running Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Scenario: install foreman 2 workers behaves like the foreman application Service "foreman" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "foreman" to be running Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Scenario: install foreman 2 workers behaves like an idempotent resource applies a second time without changes Failure/Error: raise CommandFailure, "Host '#{self}' exited with #{result.exit_code} running:\n #{cmdline}\nLast #{@options[:trace_limit]} lines of output were:\n#{result.formatted_output(@options[:trace_limit])}" Beaker::Host::CommandFailure: Host 'centos9-64-puppet7.example.com' exited with 4 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_101056900.pp.BbtMbq Last 10 lines of output were: May 14 10:11:16 centos9-64-puppet7.example.com foreman[3256]: time="2024-05-14T10:11:16Z" level=error msg="stat /usr/share/foreman/.config: no such file or directory" May 14 10:11:16 centos9-64-puppet7.example.com systemd[1]: foreman.service: Main process exited, code=exited, status=1/FAILURE May 14 10:11:16 centos9-64-puppet7.example.com foreman[3262]: time="2024-05-14T10:11:16Z" level=error msg="stat /usr/share/foreman/.config: no such file or directory" May 14 10:11:16 centos9-64-puppet7.example.com systemd[1]: foreman.service: Failed with result 'exit-code'. May 14 10:11:16 centos9-64-puppet7.example.com systemd[1]: Failed to start Foreman. Warning: /Stage[main]/Foreman/Anchor[foreman::service]: Skipping because of failed dependencies Warning: /Stage[main]/Foreman::Register/Foreman_host[foreman-centos9-64-puppet7.example.com]: Skipping because of failed dependencies Warning: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-centos9-64-puppet7.example.com]: Skipping because of failed dependencies �[mNotice: Applied catalog in 15.07 seconds Shared Example Group: "an idempotent resource" called from ./spec/acceptance/dynflow_spec.rb:5

Scenario: install foreman 2 workers behaves like the foreman application File "/run/foreman.sock" is expected to be socket Failure/Error: it { should be_socket } expected `File "/run/foreman.sock".socket?` to be truthy, got false Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Scenario: install foreman 2 workers behaves like the foreman application Service "dynflow-sidekiq@orchestrator" is expected to be enabled Failure/Error: it { is_expected.to be_enabled } expected Service "dynflow-sidekiq@orchestrator" to be enabled Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Scenario: install foreman 2 workers behaves like the foreman application Service "dynflow-sidekiq@orchestrator" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "dynflow-sidekiq@orchestrator" to be running Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Scenario: install foreman 2 workers behaves like the foreman application Command "curl -s --cacert /etc/foreman-certs/certificate.pem https://centos9-64-puppet8.example.com -w '%{redirect_url}' -o /dev/null" stdout is expected to eq "https://centos9-64-puppet8.example.com/users/login" Failure/Error: its(:stdout) { is_expected.to eq("https://#{host_inventory['fqdn']}#{params.fetch(:expected_login_url_path, '/users/login')}") } expected: #<Encoding:UTF-8> "https://centos9-64-puppet8.example.com/users/login" got: #<Encoding:US-ASCII> "" (compared using ==) Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Scenario: install foreman 2 workers behaves like the foreman application Service "dynflow-sidekiq@worker-1" is expected to be enabled Failure/Error: it { is_expected.to be_enabled } expected Service "dynflow-sidekiq@worker-1" to be enabled Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Scenario: install foreman 2 workers Service "dynflow-sidekiq@worker-1" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "dynflow-sidekiq@worker-1" to be running

Scenario: install foreman 2 workers behaves like the foreman application Service "dynflow-sidekiq@worker-1" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "dynflow-sidekiq@worker-1" to be running Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Scenario: install foreman 2 workers behaves like the foreman application Service "foreman" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "foreman" to be running Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Scenario: install foreman 2 workers behaves like the foreman application File "/run/foreman.sock" is expected to be socket Failure/Error: it { should be_socket } expected `File "/run/foreman.sock".socket?` to be truthy, got false Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Scenario: install foreman 2 workers behaves like the foreman application Command "curl -s --cacert /etc/foreman-certs/certificate.pem https://centos9-64-puppet7.example.com -w '%{redirect_url}' -o /dev/null" stdout is expected to eq "https://centos9-64-puppet7.example.com/users/login" Failure/Error: its(:stdout) { is_expected.to eq("https://#{host_inventory['fqdn']}#{params.fetch(:expected_login_url_path, '/users/login')}") } expected: #<Encoding:UTF-8> "https://centos9-64-puppet7.example.com/users/login" got: #<Encoding:US-ASCII> "" (compared using ==) Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Scenario: install foreman 2 workers Service "dynflow-sidekiq@worker-1" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "dynflow-sidekiq@worker-1" to be running

Canceling since a higher priority waiting request for '1164/merge' exists

foreman on centos-8-x86_64 with db_manage set to false is expected to contain Foreman::Rake[db:migrate] Failure/Error: it { should contain_foreman__rake('db:migrate') } expected that the catalogue would contain Foreman::Rake[db:migrate]

foreman on centos-8-x86_64 with db_manage set to false is expected to contain Foreman_config_entry[db_pending_seed] Failure/Error: it { should contain_foreman_config_entry('db_pending_seed') } expected that the catalogue would contain Foreman_config_entry[db_pending_seed]

foreman on centos-8-x86_64 with db_manage set to false is expected to contain Foreman::Rake[db:seed] Failure/Error: it { should contain_foreman__rake('db:seed') } expected that the catalogue would contain Foreman::Rake[db:seed]

foreman on centos-8-x86_64 with seed parameters is expected to contain Foreman::Rake[db:seed] with environment => {"SEED_ADMIN_USER"=>"joe", "SEED_ADMIN_PASSWORD"=>"secret"} Failure/Error: should contain_foreman__rake('db:seed') .with_environment( 'SEED_ADMIN_USER' => 'joe', 'SEED_ADMIN_PASSWORD' => 'secret' ) expected that the catalogue would contain Foreman::Rake[db:seed]

foreman on centos-9-x86_64 with db_manage set to false is expected to contain Foreman::Rake[db:migrate] Failure/Error: it { should contain_foreman__rake('db:migrate') } expected that the catalogue would contain Foreman::Rake[db:migrate]

foreman on centos-9-x86_64 with db_manage set to false is expected to contain Foreman_config_entry[db_pending_seed] Failure/Error: it { should contain_foreman_config_entry('db_pending_seed') } expected that the catalogue would contain Foreman_config_entry[db_pending_seed]

foreman on centos-9-x86_64 with db_manage set to false is expected to contain Foreman::Rake[db:seed] Failure/Error: it { should contain_foreman__rake('db:seed') } expected that the catalogue would contain Foreman::Rake[db:seed]

foreman on centos-9-x86_64 with seed parameters is expected to contain Foreman::Rake[db:seed] with environment => {"SEED_ADMIN_USER"=>"joe", "SEED_ADMIN_PASSWORD"=>"secret"} Failure/Error: should contain_foreman__rake('db:seed') .with_environment( 'SEED_ADMIN_USER' => 'joe', 'SEED_ADMIN_PASSWORD' => 'secret' ) expected that the catalogue would contain Foreman::Rake[db:seed]

foreman on debian-11-x86_64 with db_manage set to false is expected to contain Foreman::Rake[db:migrate] Failure/Error: it { should contain_foreman__rake('db:migrate') } expected that the catalogue would contain Foreman::Rake[db:migrate]

foreman on debian-11-x86_64 with db_manage set to false is expected to contain Foreman_config_entry[db_pending_seed] Failure/Error: it { should contain_foreman_config_entry('db_pending_seed') } expected that the catalogue would contain Foreman_config_entry[db_pending_seed]

Canceling since a higher priority waiting request for '1164/merge' exists

Scenario: install foreman 2 workers behaves like an idempotent resource applies with no errors Failure/Error: raise CommandFailure, "Host '#{self}' exited with #{result.exit_code} running:\n #{cmdline}\nLast #{@options[:trace_limit]} lines of output were:\n#{result.formatted_output(@options[:trace_limit])}" Beaker::Host::CommandFailure: Host 'centos8-64-puppet8.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_101001861.pp.eQqGym Last 10 lines of output were: Info: Podman::Quadlet[foreman.container]: Unscheduling all events on Podman::Quadlet[foreman.container] �[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@orchestrator] has failures: true �[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@worker-1] has failures: true �[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@worker-2] has failures: true �[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[foreman.service] has failures: true Warning: /Stage[main]/Foreman/Anchor[foreman::service]: Skipping because of failed dependencies Warning: /Stage[main]/Foreman::Register/Foreman_host[foreman-centos8-64-puppet8.example.com]: Skipping because of failed dependencies Info: Stage[main]: Unscheduling all events on Stage[main] Warning: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-centos8-64-puppet8.example.com]: Skipping because of failed dependencies �[mNotice: Applied catalog in 115.88 seconds Shared Example Group: "an idempotent resource" called from ./spec/acceptance/dynflow_spec.rb:5

Scenario: install foreman 2 workers behaves like an idempotent resource applies a second time without changes Failure/Error: raise CommandFailure, "Host '#{self}' exited with #{result.exit_code} running:\n #{cmdline}\nLast #{@options[:trace_limit]} lines of output were:\n#{result.formatted_output(@options[:trace_limit])}" Beaker::Host::CommandFailure: Host 'centos8-64-puppet8.example.com' exited with 4 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_101201202.pp.fvOiQG Last 10 lines of output were: May 14 10:12:21 centos8-64-puppet8.example.com systemd[1]: Failed to start Foreman. �[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@orchestrator] has failures: true �[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@worker-1] has failures: true �[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@worker-2] has failures: true �[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[foreman.service] has failures: true Warning: /Stage[main]/Foreman/Anchor[foreman::service]: Skipping because of failed dependencies Warning: /Stage[main]/Foreman::Register/Foreman_host[foreman-centos8-64-puppet8.example.com]: Skipping because of failed dependencies Warning: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-centos8-64-puppet8.example.com]: Skipping because of failed dependencies �[mNotice: Applied catalog in 15.57 seconds Shared Example Group: "an idempotent resource" called from ./spec/acceptance/dynflow_spec.rb:5

Scenario: install foreman 2 workers behaves like the foreman application Service "dynflow-sidekiq@orchestrator" is expected to be enabled Failure/Error: it { is_expected.to be_enabled } expected Service "dynflow-sidekiq@orchestrator" to be enabled Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Scenario: install foreman 2 workers behaves like the foreman application Service "dynflow-sidekiq@orchestrator" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "dynflow-sidekiq@orchestrator" to be running Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Scenario: install foreman 2 workers behaves like the foreman application Service "dynflow-sidekiq@worker-1" is expected to be enabled Failure/Error: it { is_expected.to be_enabled } expected Service "dynflow-sidekiq@worker-1" to be enabled Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Scenario: install foreman 2 workers behaves like the foreman application Service "dynflow-sidekiq@worker-1" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "dynflow-sidekiq@worker-1" to be running Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Scenario: install foreman 2 workers behaves like the foreman application Service "foreman" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "foreman" to be running Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Scenario: install foreman 2 workers behaves like the foreman application File "/run/foreman.sock" is expected to be socket Failure/Error: it { should be_socket } expected `File "/run/foreman.sock".socket?` to be truthy, got false Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Scenario: install foreman 2 workers behaves like the foreman application Command "curl -s --cacert /etc/foreman-certs/certificate.pem https://centos8-64-puppet8.example.com -w '%{redirect_url}' -o /dev/null" stdout is expected to eq "https://centos8-64-puppet8.example.com/users/login" Failure/Error: its(:stdout) { is_expected.to eq("https://#{host_inventory['fqdn']}#{params.fetch(:expected_login_url_path, '/users/login')}") } expected: #<Encoding:UTF-8> "https://centos8-64-puppet8.example.com/users/login" got: #<Encoding:US-ASCII> "" (compared using ==) Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Scenario: install foreman 2 workers Service "dynflow-sidekiq@worker-1" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "dynflow-sidekiq@worker-1" to be running

Canceling since a higher priority waiting request for '1164/merge' exists

Scenario: install foreman 2 workers behaves like an idempotent resource applies with no errors Failure/Error: raise CommandFailure, "Host '#{self}' exited with #{result.exit_code} running:\n #{cmdline}\nLast #{@options[:trace_limit]} lines of output were:\n#{result.formatted_output(@options[:trace_limit])}" Beaker::Host::CommandFailure: Host 'debian12-64-puppet7.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_100947853.pp.BdzDkp Last 10 lines of output were: Warning: /Stage[main]/Redis::Service/Service[redis-server]: Skipping because of failed dependencies Warning: /Stage[main]/Foreman::Service/Foreman::Dynflow::Worker[orchestrator]/Service[dynflow-sidekiq@orchestrator]: Skipping because of failed dependencies Warning: /Stage[main]/Foreman::Service/Foreman::Dynflow::Pool[worker]/Foreman::Dynflow::Worker[worker-1]/Service[dynflow-sidekiq@worker-1]: Skipping because of failed dependencies Warning: /Stage[main]/Foreman::Service/Foreman::Dynflow::Pool[worker]/Foreman::Dynflow::Worker[worker-2]/Service[dynflow-sidekiq@worker-2]: Skipping because of failed dependencies Warning: /Stage[main]/Foreman::Service/Foreman::Dynflow::Pool[worker]/Foreman::Dynflow::Worker[worker]/Service[dynflow-sidekiq@worker]: Skipping because of failed dependencies Warning: /Stage[main]/Foreman::Service/Foreman::Dynflow::Pool[worker]/Foreman::Dynflow::Worker[worker]/File[/etc/foreman/dynflow/worker.yml]: Skipping because of failed dependencies Warning: /Stage[main]/Foreman/Anchor[foreman::service]: Skipping because of failed dependencies Warning: /Stage[main]/Foreman::Register/Foreman_host[foreman-debian12-64-puppet7.example.com]: Skipping because of failed dependencies Warning: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-debian12-64-puppet7.example.com]: Skipping because of failed dependencies �[mNotice: Applied catalog in 99.15 seconds Shared Example Group: "an idempotent resource" called from ./spec/acceptance/dynflow_spec.rb:5

Scenario: install foreman 2 workers behaves like an idempotent resource applies a second time without changes Failure/Error: raise CommandFailure, "Host '#{self}' exited with #{result.exit_code} running:\n #{cmdline}\nLast #{@options[:trace_limit]} lines of output were:\n#{result.formatted_output(@options[:trace_limit])}" Beaker::Host::CommandFailure: Host 'debian12-64-puppet7.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_101131684.pp.FmpnB4 Last 10 lines of output were: Warning: /Stage[main]/Foreman::Service/Foreman::Dynflow::Worker[orchestrator]/Service[dynflow-sidekiq@orchestrator]: Skipping because of failed dependencies Warning: /Stage[main]/Foreman::Service/Foreman::Dynflow::Pool[worker]/Foreman::Dynflow::Worker[worker-1]/Service[dynflow-sidekiq@worker-1]: Skipping because of failed dependencies Warning: /Stage[main]/Foreman::Service/Foreman::Dynflow::Pool[worker]/Foreman::Dynflow::Worker[worker-2]/Service[dynflow-sidekiq@worker-2]: Skipping because of failed dependencies Warning: /Stage[main]/Foreman::Service/Foreman::Dynflow::Pool[worker]/Foreman::Dynflow::Worker[worker]/Service[dynflow-sidekiq@worker]: Skipping because of failed dependencies Warning: /Stage[main]/Foreman::Service/Foreman::Dynflow::Pool[worker]/Foreman::Dynflow::Worker[worker]/File[/etc/foreman/dynflow/worker.yml]: Skipping because of failed dependencies Warning: /Stage[main]/Foreman/Anchor[foreman::service]: Skipping because of failed dependencies Warning: /Stage[main]/Foreman::Register/Foreman_host[foreman-debian12-64-puppet7.example.com]: Skipping because of failed dependencies Warning: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-debian12-64-puppet7.example.com]: Skipping because of failed dependencies Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 10.54 seconds Shared Example Group: "an idempotent resource" called from ./spec/acceptance/dynflow_spec.rb:5

Scenario: install foreman 2 workers behaves like the foreman application Service "dynflow-sidekiq@orchestrator" is expected to be enabled Failure/Error: it { is_expected.to be_enabled } expected Service "dynflow-sidekiq@orchestrator" to be enabled Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Scenario: install foreman 2 workers behaves like the foreman application Service "dynflow-sidekiq@orchestrator" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "dynflow-sidekiq@orchestrator" to be running Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Scenario: install foreman 2 workers behaves like the foreman application Service "dynflow-sidekiq@worker-1" is expected to be enabled Failure/Error: it { is_expected.to be_enabled } expected Service "dynflow-sidekiq@worker-1" to be enabled Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Scenario: install foreman 2 workers behaves like the foreman application Service "dynflow-sidekiq@worker-1" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "dynflow-sidekiq@worker-1" to be running Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Scenario: install foreman 2 workers behaves like the foreman application Service "foreman" is expected to be enabled Failure/Error: it { is_expected.to be_enabled } expected Service "foreman" to be enabled Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Scenario: install foreman 2 workers behaves like the foreman application Service "foreman" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "foreman" to be running Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Scenario: install foreman 2 workers behaves like the foreman application Port "443" is expected to be listening Failure/Error: it { is_expected.to be_listening } expected Port "443" to be listening Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Scenario: install foreman 2 workers behaves like the foreman application File "/run/foreman.sock" is expected to be socket Failure/Error: it { should be_socket } expected `File "/run/foreman.sock".socket?` to be truthy, got false Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Canceling since a higher priority waiting request for '1164/merge' exists

Scenario: install foreman 2 workers behaves like an idempotent resource applies with no errors Failure/Error: raise CommandFailure, "Host '#{self}' exited with #{result.exit_code} running:\n #{cmdline}\nLast #{@options[:trace_limit]} lines of output were:\n#{result.formatted_output(@options[:trace_limit])}" Beaker::Host::CommandFailure: Host 'ubuntu2004-64-puppet8.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_101022922.pp.YRuLGt Last 10 lines of output were: �[mNotice: /Stage[main]/Foreman::Service/Foreman::Dynflow::Pool[worker]/Foreman::Dynflow::Worker[worker]/File[/etc/foreman/dynflow/worker.yml]/ensure: removed Info: Foreman::Dynflow::Pool[worker]: Unscheduling all events on Foreman::Dynflow::Pool[worker] �[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@orchestrator] has failures: true �[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@worker-1] has failures: true �[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@worker-2] has failures: true Warning: /Stage[main]/Foreman/Anchor[foreman::service]: Skipping because of failed dependencies Warning: /Stage[main]/Foreman::Register/Foreman_host[foreman-ubuntu2004-64-puppet8.example.com]: Skipping because of failed dependencies Warning: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-ubuntu2004-64-puppet8.example.com]: Skipping because of failed dependencies Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 147.32 seconds Shared Example Group: "an idempotent resource" called from ./spec/acceptance/dynflow_spec.rb:5

Scenario: install foreman 2 workers behaves like an idempotent resource applies a second time without changes Failure/Error: raise CommandFailure, "Host '#{self}' exited with #{result.exit_code} running:\n #{cmdline}\nLast #{@options[:trace_limit]} lines of output were:\n#{result.formatted_output(@options[:trace_limit])}" Beaker::Host::CommandFailure: Host 'ubuntu2004-64-puppet8.example.com' exited with 4 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_101256099.pp.yDPo9d Last 10 lines of output were: May 14 10:12:55 ubuntu2004-64-puppet8.example.com dynflow-sidekiq@worker-2[11202]: /usr/share/foreman/vendor/ruby/2.7.0/gems/apipie-rails-1.3.0/lib/apipie/validator.rb:337:in `instance_exec' May 14 10:12:55 ubuntu2004-64-puppet8.example.com dynflow-sidekiq@worker-2[11202]: /usr/share/foreman/vendor/ruby/2.7.0/gems/apipie-rails-1.3.0/lib/apipie/validator.rb:337:in `initialize' �[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@orchestrator] has failures: true �[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@worker-1] has failures: true �[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@worker-2] has failures: true Warning: /Stage[main]/Foreman/Anchor[foreman::service]: Skipping because of failed dependencies Warning: /Stage[main]/Foreman::Register/Foreman_host[foreman-ubuntu2004-64-puppet8.example.com]: Skipping because of failed dependencies Warning: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-ubuntu2004-64-puppet8.example.com]: Skipping because of failed dependencies �[mNotice: Applied catalog in 13.47 seconds Shared Example Group: "an idempotent resource" called from ./spec/acceptance/dynflow_spec.rb:5

Scenario: install foreman 2 workers behaves like the foreman application Service "dynflow-sidekiq@orchestrator" is expected to be enabled Failure/Error: it { is_expected.to be_enabled } expected Service "dynflow-sidekiq@orchestrator" to be enabled Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Scenario: install foreman 2 workers behaves like the foreman application Service "dynflow-sidekiq@orchestrator" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "dynflow-sidekiq@orchestrator" to be running Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Scenario: install foreman 2 workers behaves like the foreman application Service "dynflow-sidekiq@worker-1" is expected to be enabled Failure/Error: it { is_expected.to be_enabled } expected Service "dynflow-sidekiq@worker-1" to be enabled Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Scenario: install foreman 2 workers behaves like the foreman application Service "dynflow-sidekiq@worker-1" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "dynflow-sidekiq@worker-1" to be running Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Scenario: install foreman 2 workers behaves like the foreman application Service "foreman" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "foreman" to be running Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Scenario: install foreman 2 workers behaves like the foreman application File "/run/foreman.sock" is expected to be socket Failure/Error: it { should be_socket } expected `File "/run/foreman.sock".socket?` to be truthy, got false Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Scenario: install foreman 2 workers behaves like the foreman application Command "curl -s --cacert /etc/foreman-certs/certificate.pem https://ubuntu2004-64-puppet8.example.com -w '%{redirect_url}' -o /dev/null" stdout is expected to eq "https://ubuntu2004-64-puppet8.example.com/users/login" Failure/Error: its(:stdout) { is_expected.to eq("https://#{host_inventory['fqdn']}#{params.fetch(:expected_login_url_path, '/users/login')}") } expected: #<Encoding:UTF-8> "https://ubuntu2004-64-puppet8.example.com/users/login" got: #<Encoding:US-ASCII> "" (compared using ==) Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Scenario: install foreman 2 workers Service "dynflow-sidekiq@worker-1" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "dynflow-sidekiq@worker-1" to be running

Canceling since a higher priority waiting request for '1164/merge' exists

Scenario: install foreman 2 workers behaves like an idempotent resource applies with no errors Failure/Error: raise CommandFailure, "Host '#{self}' exited with #{result.exit_code} running:\n #{cmdline}\nLast #{@options[:trace_limit]} lines of output were:\n#{result.formatted_output(@options[:trace_limit])}" Beaker::Host::CommandFailure: Host 'debian11-64-puppet7.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_100956535.pp.C2szeA Last 10 lines of output were: �[mNotice: /Stage[main]/Foreman::Service/Foreman::Dynflow::Pool[worker]/Foreman::Dynflow::Worker[worker]/File[/etc/foreman/dynflow/worker.yml]/ensure: removed Info: Foreman::Dynflow::Pool[worker]: Unscheduling all events on Foreman::Dynflow::Pool[worker] �[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@orchestrator] has failures: true �[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@worker-1] has failures: true �[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@worker-2] has failures: true Warning: /Stage[main]/Foreman/Anchor[foreman::service]: Skipping because of failed dependencies Warning: /Stage[main]/Foreman::Register/Foreman_host[foreman-debian11-64-puppet7.example.com]: Skipping because of failed dependencies Warning: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-debian11-64-puppet7.example.com]: Skipping because of failed dependencies Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 108.03 seconds Shared Example Group: "an idempotent resource" called from ./spec/acceptance/dynflow_spec.rb:5

Canceling since a higher priority waiting request for '1164/merge' exists

Scenario: install foreman 2 workers behaves like an idempotent resource applies with no errors Failure/Error: raise CommandFailure, "Host '#{self}' exited with #{result.exit_code} running:\n #{cmdline}\nLast #{@options[:trace_limit]} lines of output were:\n#{result.formatted_output(@options[:trace_limit])}" Beaker::Host::CommandFailure: Host 'debian12-64-puppet8.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_100952707.pp.ViMCdj Last 10 lines of output were: Warning: /Stage[main]/Redis::Service/Service[redis-server]: Skipping because of failed dependencies Warning: /Stage[main]/Foreman::Service/Foreman::Dynflow::Worker[orchestrator]/Service[dynflow-sidekiq@orchestrator]: Skipping because of failed dependencies Warning: /Stage[main]/Foreman::Service/Foreman::Dynflow::Pool[worker]/Foreman::Dynflow::Worker[worker-1]/Service[dynflow-sidekiq@worker-1]: Skipping because of failed dependencies Warning: /Stage[main]/Foreman::Service/Foreman::Dynflow::Pool[worker]/Foreman::Dynflow::Worker[worker-2]/Service[dynflow-sidekiq@worker-2]: Skipping because of failed dependencies Warning: /Stage[main]/Foreman::Service/Foreman::Dynflow::Pool[worker]/Foreman::Dynflow::Worker[worker]/Service[dynflow-sidekiq@worker]: Skipping because of failed dependencies Warning: /Stage[main]/Foreman::Service/Foreman::Dynflow::Pool[worker]/Foreman::Dynflow::Worker[worker]/File[/etc/foreman/dynflow/worker.yml]: Skipping because of failed dependencies Warning: /Stage[main]/Foreman/Anchor[foreman::service]: Skipping because of failed dependencies Warning: /Stage[main]/Foreman::Register/Foreman_host[foreman-debian12-64-puppet8.example.com]: Skipping because of failed dependencies Warning: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-debian12-64-puppet8.example.com]: Skipping because of failed dependencies �[mNotice: Applied catalog in 98.66 seconds Shared Example Group: "an idempotent resource" called from ./spec/acceptance/dynflow_spec.rb:5

Scenario: install foreman 2 workers behaves like an idempotent resource applies a second time without changes Failure/Error: raise CommandFailure, "Host '#{self}' exited with #{result.exit_code} running:\n #{cmdline}\nLast #{@options[:trace_limit]} lines of output were:\n#{result.formatted_output(@options[:trace_limit])}" Beaker::Host::CommandFailure: Host 'debian11-64-puppet7.example.com' exited with 4 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_101149497.pp.r9gmjG Last 10 lines of output were: May 14 10:11:48 debian11-64-puppet7.example.com dynflow-sidekiq@worker-2[13081]: /usr/share/foreman/vendor/ruby/2.7.0/gems/apipie-rails-1.3.0/lib/apipie/validator.rb:330:in `new' May 14 10:11:48 debian11-64-puppet7.example.com dynflow-sidekiq@worker-2[13081]: /usr/share/foreman/vendor/ruby/2.7.0/gems/apipie-rails-1.3.0/lib/apipie/validator.rb:330:in `build' �[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@orchestrator] has failures: true �[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@worker-1] has failures: true �[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@worker-2] has failures: true Warning: /Stage[main]/Foreman/Anchor[foreman::service]: Skipping because of failed dependencies Warning: /Stage[main]/Foreman::Register/Foreman_host[foreman-debian11-64-puppet7.example.com]: Skipping because of failed dependencies Warning: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-debian11-64-puppet7.example.com]: Skipping because of failed dependencies �[mNotice: Applied catalog in 14.89 seconds Shared Example Group: "an idempotent resource" called from ./spec/acceptance/dynflow_spec.rb:5

Scenario: install foreman 2 workers behaves like the foreman application Service "dynflow-sidekiq@orchestrator" is expected to be enabled Failure/Error: it { is_expected.to be_enabled } expected Service "dynflow-sidekiq@orchestrator" to be enabled Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Scenario: install foreman 2 workers behaves like an idempotent resource applies a second time without changes Failure/Error: raise CommandFailure, "Host '#{self}' exited with #{result.exit_code} running:\n #{cmdline}\nLast #{@options[:trace_limit]} lines of output were:\n#{result.formatted_output(@options[:trace_limit])}" Beaker::Host::CommandFailure: Host 'debian12-64-puppet8.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_101136471.pp.UaBMAa Last 10 lines of output were: Warning: /Stage[main]/Foreman::Service/Foreman::Dynflow::Worker[orchestrator]/Service[dynflow-sidekiq@orchestrator]: Skipping because of failed dependencies Warning: /Stage[main]/Foreman::Service/Foreman::Dynflow::Pool[worker]/Foreman::Dynflow::Worker[worker-1]/Service[dynflow-sidekiq@worker-1]: Skipping because of failed dependencies Warning: /Stage[main]/Foreman::Service/Foreman::Dynflow::Pool[worker]/Foreman::Dynflow::Worker[worker-2]/Service[dynflow-sidekiq@worker-2]: Skipping because of failed dependencies Warning: /Stage[main]/Foreman::Service/Foreman::Dynflow::Pool[worker]/Foreman::Dynflow::Worker[worker]/Service[dynflow-sidekiq@worker]: Skipping because of failed dependencies Warning: /Stage[main]/Foreman::Service/Foreman::Dynflow::Pool[worker]/Foreman::Dynflow::Worker[worker]/File[/etc/foreman/dynflow/worker.yml]: Skipping because of failed dependencies Warning: /Stage[main]/Foreman/Anchor[foreman::service]: Skipping because of failed dependencies Warning: /Stage[main]/Foreman::Register/Foreman_host[foreman-debian12-64-puppet8.example.com]: Skipping because of failed dependencies Warning: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-debian12-64-puppet8.example.com]: Skipping because of failed dependencies Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 11.08 seconds Shared Example Group: "an idempotent resource" called from ./spec/acceptance/dynflow_spec.rb:5

Scenario: install foreman 2 workers behaves like the foreman application Service "dynflow-sidekiq@orchestrator" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "dynflow-sidekiq@orchestrator" to be running Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Scenario: install foreman 2 workers behaves like the foreman application Service "dynflow-sidekiq@orchestrator" is expected to be enabled Failure/Error: it { is_expected.to be_enabled } expected Service "dynflow-sidekiq@orchestrator" to be enabled Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Scenario: install foreman 2 workers behaves like the foreman application Service "dynflow-sidekiq@worker-1" is expected to be enabled Failure/Error: it { is_expected.to be_enabled } expected Service "dynflow-sidekiq@worker-1" to be enabled Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Scenario: install foreman 2 workers behaves like the foreman application Service "dynflow-sidekiq@orchestrator" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "dynflow-sidekiq@orchestrator" to be running Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Scenario: install foreman 2 workers behaves like the foreman application Service "dynflow-sidekiq@worker-1" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "dynflow-sidekiq@worker-1" to be running Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Canceling since a higher priority waiting request for '1164/merge' exists

Scenario: install foreman 2 workers behaves like the foreman application Service "foreman" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "foreman" to be running Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Scenario: install foreman 2 workers behaves like the foreman application Service "dynflow-sidekiq@worker-1" is expected to be enabled Failure/Error: it { is_expected.to be_enabled } expected Service "dynflow-sidekiq@worker-1" to be enabled Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Scenario: install foreman 2 workers behaves like an idempotent resource applies with no errors Failure/Error: raise CommandFailure, "Host '#{self}' exited with #{result.exit_code} running:\n #{cmdline}\nLast #{@options[:trace_limit]} lines of output were:\n#{result.formatted_output(@options[:trace_limit])}" Beaker::Host::CommandFailure: Host 'ubuntu2004-64-puppet7.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_101018449.pp.rQMm8l Last 10 lines of output were: �[mNotice: /Stage[main]/Foreman::Service/Foreman::Dynflow::Pool[worker]/Foreman::Dynflow::Worker[worker]/File[/etc/foreman/dynflow/worker.yml]/ensure: removed Info: Foreman::Dynflow::Pool[worker]: Unscheduling all events on Foreman::Dynflow::Pool[worker] �[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@orchestrator] has failures: true �[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@worker-1] has failures: true �[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@worker-2] has failures: true Warning: /Stage[main]/Foreman/Anchor[foreman::service]: Skipping because of failed dependencies Warning: /Stage[main]/Foreman::Register/Foreman_host[foreman-ubuntu2004-64-puppet7.example.com]: Skipping because of failed dependencies Warning: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-ubuntu2004-64-puppet7.example.com]: Skipping because of failed dependencies Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 159.27 seconds Shared Example Group: "an idempotent resource" called from ./spec/acceptance/dynflow_spec.rb:5

Scenario: install foreman 2 workers behaves like the foreman application File "/run/foreman.sock" is expected to be socket Failure/Error: it { should be_socket } expected `File "/run/foreman.sock".socket?` to be truthy, got false Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Scenario: install foreman 2 workers behaves like the foreman application Service "dynflow-sidekiq@worker-1" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "dynflow-sidekiq@worker-1" to be running Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Scenario: install foreman 2 workers behaves like an idempotent resource applies a second time without changes Failure/Error: raise CommandFailure, "Host '#{self}' exited with #{result.exit_code} running:\n #{cmdline}\nLast #{@options[:trace_limit]} lines of output were:\n#{result.formatted_output(@options[:trace_limit])}" Beaker::Host::CommandFailure: Host 'ubuntu2004-64-puppet7.example.com' exited with 4 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_101304128.pp.7QYEg0 Last 10 lines of output were: May 14 10:13:03 ubuntu2004-64-puppet7.example.com dynflow-sidekiq@worker-2[11208]: /usr/share/foreman/vendor/ruby/2.7.0/gems/apipie-rails-1.3.0/lib/apipie/validator.rb:337:in `instance_exec' May 14 10:13:03 ubuntu2004-64-puppet7.example.com dynflow-sidekiq@worker-2[11208]: /usr/share/foreman/vendor/ruby/2.7.0/gems/apipie-rails-1.3.0/lib/apipie/validator.rb:337:in `initialize' �[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@orchestrator] has failures: true �[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@worker-1] has failures: true �[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@worker-2] has failures: true Warning: /Stage[main]/Foreman/Anchor[foreman::service]: Skipping because of failed dependencies Warning: /Stage[main]/Foreman::Register/Foreman_host[foreman-ubuntu2004-64-puppet7.example.com]: Skipping because of failed dependencies Warning: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-ubuntu2004-64-puppet7.example.com]: Skipping because of failed dependencies �[mNotice: Applied catalog in 18.88 seconds Shared Example Group: "an idempotent resource" called from ./spec/acceptance/dynflow_spec.rb:5

Scenario: install foreman 2 workers behaves like the foreman application Command "curl -s --cacert /etc/foreman-certs/certificate.pem https://debian11-64-puppet7.example.com -w '%{redirect_url}' -o /dev/null" stdout is expected to eq "https://debian11-64-puppet7.example.com/users/login" Failure/Error: its(:stdout) { is_expected.to eq("https://#{host_inventory['fqdn']}#{params.fetch(:expected_login_url_path, '/users/login')}") } expected: #<Encoding:UTF-8> "https://debian11-64-puppet7.example.com/users/login" got: #<Encoding:US-ASCII> "" (compared using ==) Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Scenario: install foreman 2 workers behaves like the foreman application Service "dynflow-sidekiq@orchestrator" is expected to be enabled Failure/Error: it { is_expected.to be_enabled } expected Service "dynflow-sidekiq@orchestrator" to be enabled Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Scenario: install foreman 2 workers behaves like the foreman application Service "foreman" is expected to be enabled Failure/Error: it { is_expected.to be_enabled } expected Service "foreman" to be enabled Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Scenario: install foreman 2 workers Service "dynflow-sidekiq@worker-1" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "dynflow-sidekiq@worker-1" to be running

Scenario: install foreman 2 workers behaves like the foreman application Service "dynflow-sidekiq@orchestrator" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "dynflow-sidekiq@orchestrator" to be running Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Scenario: install foreman 2 workers behaves like the foreman application Service "foreman" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "foreman" to be running Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Scenario: install foreman 2 workers behaves like the foreman application Service "dynflow-sidekiq@worker-1" is expected to be enabled Failure/Error: it { is_expected.to be_enabled } expected Service "dynflow-sidekiq@worker-1" to be enabled Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Scenario: install foreman 2 workers behaves like the foreman application Port "443" is expected to be listening Failure/Error: it { is_expected.to be_listening } expected Port "443" to be listening Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Scenario: install foreman 2 workers behaves like the foreman application Service "dynflow-sidekiq@worker-1" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "dynflow-sidekiq@worker-1" to be running Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Scenario: install foreman 2 workers behaves like the foreman application File "/run/foreman.sock" is expected to be socket Failure/Error: it { should be_socket } expected `File "/run/foreman.sock".socket?` to be truthy, got false Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Scenario: install foreman 2 workers behaves like the foreman application Service "foreman" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "foreman" to be running Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Scenario: install foreman 2 workers behaves like the foreman application File "/run/foreman.sock" is expected to be socket Failure/Error: it { should be_socket } expected `File "/run/foreman.sock".socket?` to be truthy, got false Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Scenario: install foreman 2 workers behaves like the foreman application Command "curl -s --cacert /etc/foreman-certs/certificate.pem https://ubuntu2004-64-puppet7.example.com -w '%{redirect_url}' -o /dev/null" stdout is expected to eq "https://ubuntu2004-64-puppet7.example.com/users/login" Failure/Error: its(:stdout) { is_expected.to eq("https://#{host_inventory['fqdn']}#{params.fetch(:expected_login_url_path, '/users/login')}") } expected: #<Encoding:UTF-8> "https://ubuntu2004-64-puppet7.example.com/users/login" got: #<Encoding:US-ASCII> "" (compared using ==) Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Scenario: install foreman 2 workers Service "dynflow-sidekiq@worker-1" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "dynflow-sidekiq@worker-1" to be running

Canceling since a higher priority waiting request for '1164/merge' exists

Scenario: install foreman 2 workers behaves like an idempotent resource applies with no errors Failure/Error: raise CommandFailure, "Host '#{self}' exited with #{result.exit_code} running:\n #{cmdline}\nLast #{@options[:trace_limit]} lines of output were:\n#{result.formatted_output(@options[:trace_limit])}" Beaker::Host::CommandFailure: Host 'debian11-64-puppet8.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_101003613.pp.x2MzmC Last 10 lines of output were: �[mNotice: /Stage[main]/Foreman::Service/Foreman::Dynflow::Pool[worker]/Foreman::Dynflow::Worker[worker]/File[/etc/foreman/dynflow/worker.yml]/ensure: removed Info: Foreman::Dynflow::Pool[worker]: Unscheduling all events on Foreman::Dynflow::Pool[worker] �[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@orchestrator] has failures: true �[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@worker-1] has failures: true �[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@worker-2] has failures: true Warning: /Stage[main]/Foreman/Anchor[foreman::service]: Skipping because of failed dependencies Warning: /Stage[main]/Foreman::Register/Foreman_host[foreman-debian11-64-puppet8.example.com]: Skipping because of failed dependencies Warning: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-debian11-64-puppet8.example.com]: Skipping because of failed dependencies Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 109.07 seconds Shared Example Group: "an idempotent resource" called from ./spec/acceptance/dynflow_spec.rb:5

Scenario: install foreman 2 workers behaves like an idempotent resource applies a second time without changes Failure/Error: raise CommandFailure, "Host '#{self}' exited with #{result.exit_code} running:\n #{cmdline}\nLast #{@options[:trace_limit]} lines of output were:\n#{result.formatted_output(@options[:trace_limit])}" Beaker::Host::CommandFailure: Host 'debian11-64-puppet8.example.com' exited with 4 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_101157526.pp.Mw3wDT Last 10 lines of output were: May 14 10:11:56 debian11-64-puppet8.example.com dynflow-sidekiq@worker-2[13075]: /usr/share/foreman/vendor/ruby/2.7.0/gems/apipie-rails-1.3.0/lib/apipie/validator.rb:330:in `new' May 14 10:11:56 debian11-64-puppet8.example.com dynflow-sidekiq@worker-2[13075]: /usr/share/foreman/vendor/ruby/2.7.0/gems/apipie-rails-1.3.0/lib/apipie/validator.rb:330:in `build' �[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@orchestrator] has failures: true �[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@worker-1] has failures: true �[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@worker-2] has failures: true Warning: /Stage[main]/Foreman/Anchor[foreman::service]: Skipping because of failed dependencies Warning: /Stage[main]/Foreman::Register/Foreman_host[foreman-debian11-64-puppet8.example.com]: Skipping because of failed dependencies Warning: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-debian11-64-puppet8.example.com]: Skipping because of failed dependencies �[mNotice: Applied catalog in 14.93 seconds Shared Example Group: "an idempotent resource" called from ./spec/acceptance/dynflow_spec.rb:5

Scenario: install foreman 2 workers behaves like the foreman application Service "dynflow-sidekiq@orchestrator" is expected to be enabled Failure/Error: it { is_expected.to be_enabled } expected Service "dynflow-sidekiq@orchestrator" to be enabled Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Scenario: install foreman 2 workers behaves like the foreman application Service "dynflow-sidekiq@orchestrator" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "dynflow-sidekiq@orchestrator" to be running Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Scenario: install foreman 2 workers behaves like the foreman application Service "dynflow-sidekiq@worker-1" is expected to be enabled Failure/Error: it { is_expected.to be_enabled } expected Service "dynflow-sidekiq@worker-1" to be enabled Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Scenario: install foreman 2 workers behaves like the foreman application Service "dynflow-sidekiq@worker-1" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "dynflow-sidekiq@worker-1" to be running Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Scenario: install foreman 2 workers behaves like the foreman application Service "foreman" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "foreman" to be running Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Scenario: install foreman 2 workers behaves like the foreman application File "/run/foreman.sock" is expected to be socket Failure/Error: it { should be_socket } expected `File "/run/foreman.sock".socket?` to be truthy, got false Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Scenario: install foreman 2 workers behaves like the foreman application Command "curl -s --cacert /etc/foreman-certs/certificate.pem https://debian11-64-puppet8.example.com -w '%{redirect_url}' -o /dev/null" stdout is expected to eq "https://debian11-64-puppet8.example.com/users/login" Failure/Error: its(:stdout) { is_expected.to eq("https://#{host_inventory['fqdn']}#{params.fetch(:expected_login_url_path, '/users/login')}") } expected: #<Encoding:UTF-8> "https://debian11-64-puppet8.example.com/users/login" got: #<Encoding:US-ASCII> "" (compared using ==) Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Scenario: install foreman 2 workers Service "dynflow-sidekiq@worker-1" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "dynflow-sidekiq@worker-1" to be running

Canceling since a higher priority waiting request for '1164/merge' exists

Scenario: install foreman 2 workers behaves like an idempotent resource applies with no errors Failure/Error: raise CommandFailure, "Host '#{self}' exited with #{result.exit_code} running:\n #{cmdline}\nLast #{@options[:trace_limit]} lines of output were:\n#{result.formatted_output(@options[:trace_limit])}" Beaker::Host::CommandFailure: Host 'ubuntu2204-64-puppet8.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_101019484.pp.bEgWgs Last 10 lines of output were: �[mNotice: /Stage[main]/Foreman::Service/Foreman::Dynflow::Pool[worker]/Foreman::Dynflow::Worker[worker]/File[/etc/foreman/dynflow/worker.yml]/ensure: removed Info: Foreman::Dynflow::Pool[worker]: Unscheduling all events on Foreman::Dynflow::Pool[worker] �[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@orchestrator] has failures: true �[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@worker-1] has failures: true �[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@worker-2] has failures: true Warning: /Stage[main]/Foreman/Anchor[foreman::service]: Skipping because of failed dependencies Warning: /Stage[main]/Foreman::Register/Foreman_host[foreman-ubuntu2204-64-puppet8.example.com]: Skipping because of failed dependencies Warning: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-ubuntu2204-64-puppet8.example.com]: Skipping because of failed dependencies Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 152.79 seconds Shared Example Group: "an idempotent resource" called from ./spec/acceptance/dynflow_spec.rb:5

Scenario: install foreman 2 workers behaves like an idempotent resource applies a second time without changes Failure/Error: raise CommandFailure, "Host '#{self}' exited with #{result.exit_code} running:\n #{cmdline}\nLast #{@options[:trace_limit]} lines of output were:\n#{result.formatted_output(@options[:trace_limit])}" Beaker::Host::CommandFailure: Host 'ubuntu2204-64-puppet8.example.com' exited with 4 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_101257827.pp.D3ThaU Last 10 lines of output were: May 14 10:12:57 ubuntu2204-64-puppet8.example.com dynflow-sidekiq@worker-2[12057]: /usr/share/foreman/vendor/ruby/3.0.0/gems/apipie-rails-1.3.0/lib/apipie/validator.rb:330:in `new' May 14 10:12:57 ubuntu2204-64-puppet8.example.com dynflow-sidekiq@worker-2[12057]: /usr/share/foreman/vendor/ruby/3.0.0/gems/apipie-rails-1.3.0/lib/apipie/validator.rb:330:in `build' �[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@orchestrator] has failures: true �[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@worker-1] has failures: true �[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@worker-2] has failures: true Warning: /Stage[main]/Foreman/Anchor[foreman::service]: Skipping because of failed dependencies Warning: /Stage[main]/Foreman::Register/Foreman_host[foreman-ubuntu2204-64-puppet8.example.com]: Skipping because of failed dependencies Warning: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-ubuntu2204-64-puppet8.example.com]: Skipping because of failed dependencies �[mNotice: Applied catalog in 12.84 seconds Shared Example Group: "an idempotent resource" called from ./spec/acceptance/dynflow_spec.rb:5

Scenario: install foreman 2 workers behaves like the foreman application Service "dynflow-sidekiq@orchestrator" is expected to be enabled Failure/Error: it { is_expected.to be_enabled } expected Service "dynflow-sidekiq@orchestrator" to be enabled Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Scenario: install foreman 2 workers behaves like the foreman application Service "dynflow-sidekiq@orchestrator" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "dynflow-sidekiq@orchestrator" to be running Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Scenario: install foreman 2 workers behaves like the foreman application Service "dynflow-sidekiq@worker-1" is expected to be enabled Failure/Error: it { is_expected.to be_enabled } expected Service "dynflow-sidekiq@worker-1" to be enabled Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Scenario: install foreman 2 workers behaves like the foreman application Service "dynflow-sidekiq@worker-1" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "dynflow-sidekiq@worker-1" to be running Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Scenario: install foreman 2 workers behaves like the foreman application Service "foreman" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "foreman" to be running Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Scenario: install foreman 2 workers behaves like the foreman application File "/run/foreman.sock" is expected to be socket Failure/Error: it { should be_socket } expected `File "/run/foreman.sock".socket?` to be truthy, got false Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Scenario: install foreman 2 workers behaves like the foreman application Command "curl -s --cacert /etc/foreman-certs/certificate.pem https://ubuntu2204-64-puppet8.example.com -w '%{redirect_url}' -o /dev/null" stdout is expected to eq "https://ubuntu2204-64-puppet8.example.com/users/login" Failure/Error: its(:stdout) { is_expected.to eq("https://#{host_inventory['fqdn']}#{params.fetch(:expected_login_url_path, '/users/login')}") } expected: #<Encoding:UTF-8> "https://ubuntu2204-64-puppet8.example.com/users/login" got: #<Encoding:US-ASCII> "" (compared using ==) Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Scenario: install foreman 2 workers Service "dynflow-sidekiq@worker-1" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "dynflow-sidekiq@worker-1" to be running

Canceling since a higher priority waiting request for '1164/merge' exists

foreman on redhat-8-x86_64 with db_manage set to false is expected to contain Foreman::Rake[db:migrate] Failure/Error: it { should contain_foreman__rake('db:migrate') } expected that the catalogue would contain Foreman::Rake[db:migrate]

foreman on redhat-8-x86_64 with db_manage set to false is expected to contain Foreman_config_entry[db_pending_seed] Failure/Error: it { should contain_foreman_config_entry('db_pending_seed') } expected that the catalogue would contain Foreman_config_entry[db_pending_seed]

foreman on redhat-8-x86_64 with db_manage set to false is expected to contain Foreman::Rake[db:seed] Failure/Error: it { should contain_foreman__rake('db:seed') } expected that the catalogue would contain Foreman::Rake[db:seed]

foreman on redhat-8-x86_64 with seed parameters is expected to contain Foreman::Rake[db:seed] with environment => {"SEED_ADMIN_USER"=>"joe", "SEED_ADMIN_PASSWORD"=>"secret"} Failure/Error: should contain_foreman__rake('db:seed') .with_environment( 'SEED_ADMIN_USER' => 'joe', 'SEED_ADMIN_PASSWORD' => 'secret' ) expected that the catalogue would contain Foreman::Rake[db:seed]

foreman on ubuntu-20.04-x86_64 with db_manage set to false is expected to contain Foreman::Rake[db:migrate] Failure/Error: it { should contain_foreman__rake('db:migrate') } expected that the catalogue would contain Foreman::Rake[db:migrate]

Canceling since a higher priority waiting request for '1164/merge' exists

foreman on ubuntu-20.04-x86_64 with db_manage set to false is expected to contain Foreman_config_entry[db_pending_seed] Failure/Error: it { should contain_foreman_config_entry('db_pending_seed') } expected that the catalogue would contain Foreman_config_entry[db_pending_seed]

Scenario: install foreman 2 workers behaves like an idempotent resource applies with no errors Failure/Error: raise CommandFailure, "Host '#{self}' exited with #{result.exit_code} running:\n #{cmdline}\nLast #{@options[:trace_limit]} lines of output were:\n#{result.formatted_output(@options[:trace_limit])}" Beaker::Host::CommandFailure: Host 'centos8-64-puppet7.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_101015752.pp.DQLTFG Last 10 lines of output were: Info: Podman::Quadlet[foreman.container]: Unscheduling all events on Podman::Quadlet[foreman.container] �[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@orchestrator] has failures: true �[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@worker-1] has failures: true �[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@worker-2] has failures: true �[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[foreman.service] has failures: true Warning: /Stage[main]/Foreman/Anchor[foreman::service]: Skipping because of failed dependencies Warning: /Stage[main]/Foreman::Register/Foreman_host[foreman-centos8-64-puppet7.example.com]: Skipping because of failed dependencies Info: Stage[main]: Unscheduling all events on Stage[main] Warning: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-centos8-64-puppet7.example.com]: Skipping because of failed dependencies �[mNotice: Applied catalog in 122.51 seconds Shared Example Group: "an idempotent resource" called from ./spec/acceptance/dynflow_spec.rb:5

foreman on ubuntu-20.04-x86_64 with db_manage set to false is expected to contain Foreman::Rake[db:seed] Failure/Error: it { should contain_foreman__rake('db:seed') } expected that the catalogue would contain Foreman::Rake[db:seed]

Scenario: install foreman 2 workers behaves like an idempotent resource applies a second time without changes Failure/Error: raise CommandFailure, "Host '#{self}' exited with #{result.exit_code} running:\n #{cmdline}\nLast #{@options[:trace_limit]} lines of output were:\n#{result.formatted_output(@options[:trace_limit])}" Beaker::Host::CommandFailure: Host 'centos8-64-puppet7.example.com' exited with 4 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_101222043.pp.VysPfc Last 10 lines of output were: May 14 10:12:39 centos8-64-puppet7.example.com systemd[1]: Starting Foreman... May 14 10:12:39 centos8-64-puppet7.example.com foreman[3770]: Error: creating runtime static files directory "/usr/share/foreman/.local/share/containers/storage/libpod": mkdir /usr/share/foreman/.local: permission denied May 14 10:12:39 centos8-64-puppet7.example.com systemd[1]: foreman.service: Main process exited, code=exited, status=125/n/a May 14 10:12:39 centos8-64-puppet7.example.com systemd[1]: foreman.service: Failed with result 'exit-code'. May 14 10:12:39 centos8-64-puppet7.example.com systemd[1]: Failed to start Foreman. Warning: /Stage[main]/Foreman/Anchor[foreman::service]: Skipping because of failed dependencies Warning: /Stage[main]/Foreman::Register/Foreman_host[foreman-centos8-64-puppet7.example.com]: Skipping because of failed dependencies Warning: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-centos8-64-puppet7.example.com]: Skipping because of failed dependencies �[mNotice: Applied catalog in 13.16 seconds Shared Example Group: "an idempotent resource" called from ./spec/acceptance/dynflow_spec.rb:5

foreman on ubuntu-20.04-x86_64 with seed parameters is expected to contain Foreman::Rake[db:seed] with environment => {"SEED_ADMIN_USER"=>"joe", "SEED_ADMIN_PASSWORD"=>"secret"} Failure/Error: should contain_foreman__rake('db:seed') .with_environment( 'SEED_ADMIN_USER' => 'joe', 'SEED_ADMIN_PASSWORD' => 'secret' ) expected that the catalogue would contain Foreman::Rake[db:seed]

Scenario: install foreman 2 workers behaves like the foreman application Service "dynflow-sidekiq@orchestrator" is expected to be enabled Failure/Error: it { is_expected.to be_enabled } expected Service "dynflow-sidekiq@orchestrator" to be enabled Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

foreman on centos-8-x86_64 with db_manage set to false is expected to contain Foreman::Rake[db:migrate] Failure/Error: it { should contain_foreman__rake('db:migrate') } expected that the catalogue would contain Foreman::Rake[db:migrate]

Scenario: install foreman 2 workers behaves like the foreman application Service "dynflow-sidekiq@orchestrator" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "dynflow-sidekiq@orchestrator" to be running Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

foreman on centos-8-x86_64 with db_manage set to false is expected to contain Foreman_config_entry[db_pending_seed] Failure/Error: it { should contain_foreman_config_entry('db_pending_seed') } expected that the catalogue would contain Foreman_config_entry[db_pending_seed]

Scenario: install foreman 2 workers behaves like the foreman application Service "dynflow-sidekiq@worker-1" is expected to be enabled Failure/Error: it { is_expected.to be_enabled } expected Service "dynflow-sidekiq@worker-1" to be enabled Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Scenario: install foreman 2 workers behaves like the foreman application Service "dynflow-sidekiq@worker-1" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "dynflow-sidekiq@worker-1" to be running Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Scenario: install foreman 2 workers behaves like the foreman application Service "foreman" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "foreman" to be running Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Scenario: install foreman 2 workers behaves like the foreman application File "/run/foreman.sock" is expected to be socket Failure/Error: it { should be_socket } expected `File "/run/foreman.sock".socket?` to be truthy, got false Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15

Scenario: install foreman 2 workers behaves like the foreman application Command "curl -s --cacert /etc/foreman-certs/certificate.pem https://centos8-64-puppet7.example.com -w '%{redirect_url}' -o /dev/null" stdout is expected to eq "https://centos8-64-puppet7.example.com/users/login" Failure/Error: its(:stdout) { is_expected.to eq("https://#{host_inventory['fqdn']}#{params.fetch(:expected_login_url_path, '/users/login')}") } expected: #<Encoding:UTF-8> "https://centos8-64-puppet7.example.com/users/login" got: #<Encoding:US-ASCII> "" (compared using ==) Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15