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 1 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_112659114.pp.YmVrPU Last 10 lines of output were: Info: Loading facts Info: Loading facts Info: Loading facts Info: Loading facts Info: Loading facts Info: Loading facts Info: Loading facts Warning: /etc/puppetlabs/puppet/hiera.yaml: Use of 'hiera.yaml' version 3 is deprecated. It should be converted to version 5 (file: /etc/puppetlabs/puppet/hiera.yaml) Error: Evaluation Error: Error while evaluating a Resource Statement, Evaluation Error: Error while evaluating a Resource Statement, Duplicate declaration: Service[foreman.service] is already declared at (file: /etc/puppetlabs/code/environments/production/modules/foreman/manifests/service.pp, line: 47); cannot redeclare (file: /etc/puppetlabs/code/environments/production/modules/podman/manifests/quadlet.pp, line: 114) (file: /etc/puppetlabs/code/environments/production/modules/podman/manifests/quadlet.pp, line: 114, column: 7) (file: /etc/puppetlabs/code/environments/production/modules/foreman/manifests/service.pp, line: 58) on node debian11-64-puppet8.example.com 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 1 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_112703150.pp.8n9Ygi Last 10 lines of output were: Info: Loading facts Info: Loading facts Info: Loading facts Info: Loading facts Info: Loading facts Info: Loading facts Info: Loading facts Warning: /etc/puppetlabs/puppet/hiera.yaml: Use of 'hiera.yaml' version 3 is deprecated. It should be converted to version 5 (file: /etc/puppetlabs/puppet/hiera.yaml) Error: Evaluation Error: Error while evaluating a Resource Statement, Evaluation Error: Error while evaluating a Resource Statement, Duplicate declaration: Service[foreman.service] is already declared at (file: /etc/puppetlabs/code/environments/production/modules/foreman/manifests/service.pp, line: 47); cannot redeclare (file: /etc/puppetlabs/code/environments/production/modules/podman/manifests/quadlet.pp, line: 114) (file: /etc/puppetlabs/code/environments/production/modules/podman/manifests/quadlet.pp, line: 114, column: 7) (file: /etc/puppetlabs/code/environments/production/modules/foreman/manifests/service.pp, line: 58) on node debian11-64-puppet8.example.com 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 "apache2" is expected to be enabled Failure/Error: it { is_expected.to be_enabled } expected Service "apache2" 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 "apache2" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "apache2" 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@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