foreman on ubuntu-20.04-x86_64 with default parameters is expected to contain Service[postgresqld] that notifies Service[dynflow-sidekiq@orchestrator] Failure/Error: is_expected.to contain_service('postgresqld') .that_notifies('Service[dynflow-sidekiq@orchestrator]') expected that the catalogue would contain Service[postgresqld]

foreman on redhat-8-x86_64 with default parameters is expected to contain Service[postgresqld] that notifies Service[dynflow-sidekiq@orchestrator] Failure/Error: is_expected.to contain_service('postgresqld') .that_notifies('Service[dynflow-sidekiq@orchestrator]') expected that the catalogue would contain Service[postgresqld]

foreman on debian-11-x86_64 with default parameters is expected to contain Service[postgresqld] that notifies Service[dynflow-sidekiq@orchestrator] Failure/Error: is_expected.to contain_service('postgresqld') .that_notifies('Service[dynflow-sidekiq@orchestrator]') expected that the catalogue would contain Service[postgresqld]

foreman on centos-8-x86_64 with default parameters is expected to contain Service[postgresqld] that notifies Service[dynflow-sidekiq@orchestrator] Failure/Error: is_expected.to contain_service('postgresqld') .that_notifies('Service[dynflow-sidekiq@orchestrator]') expected that the catalogue would contain Service[postgresqld]

Process completed with exit code 1.

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_041159845.pp.Qv7egv 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-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 109.42 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_041354963.pp.up5PbT Last 10 lines of output were: Warning: /Stage[main]/Foreman::Service/Foreman::Dynflow::Pool[worker]/Foreman::Dynflow::Worker[worker-2]/File[/etc/foreman/dynflow/worker-2.yml]: 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-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 6.67 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