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 1 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_112654033.pp.KtcCGd 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 centos9-64-puppet7.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 'centos9-64-puppet7.example.com' exited with 1 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_112656771.pp.PyUweW 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 centos9-64-puppet7.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 "httpd" is expected to be enabled Failure/Error: it { is_expected.to be_enabled } expected Service "httpd" 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 "httpd" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "httpd" 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

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 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 1 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_112649657.pp.97lXer 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 centos9-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 'centos9-64-puppet8.example.com' exited with 1 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_112652541.pp.qJB66u 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 centos9-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 "httpd" is expected to be enabled Failure/Error: it { is_expected.to be_enabled } expected Service "httpd" 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 "httpd" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "httpd" 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

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

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 1 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_112700971.pp.SnPG2k 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 centos8-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 'centos8-64-puppet8.example.com' exited with 1 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_112703936.pp.CzJbTt 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 centos8-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 "httpd" is expected to be enabled Failure/Error: it { is_expected.to be_enabled } expected Service "httpd" 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 "httpd" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "httpd" 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

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

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-puppet7.example.com' exited with 1 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_112658127.pp.cwv78t 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 centos8-64-puppet7.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 'centos8-64-puppet7.example.com' exited with 1 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_112701063.pp.qZTq9k 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 centos8-64-puppet7.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 "httpd" is expected to be enabled Failure/Error: it { is_expected.to be_enabled } expected Service "httpd" 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 "httpd" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "httpd" 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

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

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 1 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_112653469.pp.o4kUTL 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 ubuntu2204-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 'ubuntu2204-64-puppet8.example.com' exited with 1 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_112658423.pp.8UPqXD 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 ubuntu2204-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

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

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 1 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_112651909.pp.XftxRa 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 debian12-64-puppet7.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 'debian12-64-puppet7.example.com' exited with 1 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_112656041.pp.yAn2Pz 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 debian12-64-puppet7.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

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

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 1 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_112650793.pp.uw1rGs 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-puppet7.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-puppet7.example.com' exited with 1 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_112654922.pp.h3eXJC 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-puppet7.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

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

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 1 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_112654137.pp.Q3UQSJ 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 debian12-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 'debian12-64-puppet8.example.com' exited with 1 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_112658540.pp.0oS0Mu 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 debian12-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

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

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-puppet7.example.com' exited with 1 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_112657449.pp.3NhNhp 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 ubuntu2004-64-puppet7.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 'ubuntu2004-64-puppet7.example.com' exited with 1 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_112702561.pp.Q6WEas 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 ubuntu2004-64-puppet7.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

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

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 1 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_112719720.pp.GshfmM 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 ubuntu2004-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 'ubuntu2004-64-puppet8.example.com' exited with 1 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_112724798.pp.N3BjHa 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 ubuntu2004-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

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

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 not to contain Class[foreman::database::postgresql] Failure/Error: it { should_not contain_class('foreman::database::postgresql') } Puppet::PreformattedError: 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: /home/runner/work/puppet-foreman/puppet-foreman/spec/fixtures/modules/foreman/manifests/service.pp, line: 47); cannot redeclare (file: /home/runner/work/puppet-foreman/puppet-foreman/spec/fixtures/modules/podman/manifests/quadlet.pp, line: 114) (file: /home/runner/work/puppet-foreman/puppet-foreman/spec/fixtures/modules/podman/manifests/quadlet.pp, line: 114, column: 7) (file: /home/runner/work/puppet-foreman/puppet-foreman/spec/fixtures/modules/foreman/manifests/service.pp, line: 58) on node fv-az1380-906.0iobsfatwvhuvgmqxjqze0bk2d.ex.internal.cloudapp.net

foreman::providers on centos-8-x86_64 with foreman is expected to compile into a catalogue without dependency cycles Failure/Error: it { is_expected.to compile.with_all_deps } error during compilation: 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: /home/runner/work/puppet-foreman/puppet-foreman/spec/fixtures/modules/foreman/manifests/service.pp, line: 47); cannot redeclare (file: /home/runner/work/puppet-foreman/puppet-foreman/spec/fixtures/modules/podman/manifests/quadlet.pp, line: 114) (file: /home/runner/work/puppet-foreman/puppet-foreman/spec/fixtures/modules/podman/manifests/quadlet.pp, line: 114, column: 7) (file: /home/runner/work/puppet-foreman/puppet-foreman/spec/fixtures/modules/foreman/manifests/service.pp, line: 58) on node fv-az1380-906.0iobsfatwvhuvgmqxjqze0bk2d.ex.internal.cloudapp.net

foreman::cli on centos-8-x86_64 with settings from foreman is expected to compile into a catalogue without dependency cycles Failure/Error: it { is_expected.to compile.with_all_deps } error during compilation: 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: /home/runner/work/puppet-foreman/puppet-foreman/spec/fixtures/modules/foreman/manifests/service.pp, line: 47); cannot redeclare (file: /home/runner/work/puppet-foreman/puppet-foreman/spec/fixtures/modules/podman/manifests/quadlet.pp, line: 114) (file: /home/runner/work/puppet-foreman/puppet-foreman/spec/fixtures/modules/podman/manifests/quadlet.pp, line: 114, column: 7) (file: /home/runner/work/puppet-foreman/puppet-foreman/spec/fixtures/modules/foreman/manifests/service.pp, line: 58) on node fv-az1380-906.0iobsfatwvhuvgmqxjqze0bk2d.ex.internal.cloudapp.net

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') } Puppet::PreformattedError: 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: /home/runner/work/puppet-foreman/puppet-foreman/spec/fixtures/modules/foreman/manifests/service.pp, line: 47); cannot redeclare (file: /home/runner/work/puppet-foreman/puppet-foreman/spec/fixtures/modules/podman/manifests/quadlet.pp, line: 114) (file: /home/runner/work/puppet-foreman/puppet-foreman/spec/fixtures/modules/podman/manifests/quadlet.pp, line: 114, column: 7) (file: /home/runner/work/puppet-foreman/puppet-foreman/spec/fixtures/modules/foreman/manifests/service.pp, line: 58) on node fv-az1380-906.0iobsfatwvhuvgmqxjqze0bk2d.ex.internal.cloudapp.net

foreman::providers on centos-8-x86_64 with foreman is expected to contain Package[puppet-agent-oauth] that comes before Class[foreman] Failure/Error: it { should contain_package(oauth_os).that_comes_before('Class[foreman]') } Puppet::PreformattedError: 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: /home/runner/work/puppet-foreman/puppet-foreman/spec/fixtures/modules/foreman/manifests/service.pp, line: 47); cannot redeclare (file: /home/runner/work/puppet-foreman/puppet-foreman/spec/fixtures/modules/podman/manifests/quadlet.pp, line: 114) (file: /home/runner/work/puppet-foreman/puppet-foreman/spec/fixtures/modules/podman/manifests/quadlet.pp, line: 114, column: 7) (file: /home/runner/work/puppet-foreman/puppet-foreman/spec/fixtures/modules/foreman/manifests/service.pp, line: 58) on node fv-az1380-906.0iobsfatwvhuvgmqxjqze0bk2d.ex.internal.cloudapp.net

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') } Puppet::PreformattedError: 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: /home/runner/work/puppet-foreman/puppet-foreman/spec/fixtures/modules/foreman/manifests/service.pp, line: 47); cannot redeclare (file: /home/runner/work/puppet-foreman/puppet-foreman/spec/fixtures/modules/podman/manifests/quadlet.pp, line: 114) (file: /home/runner/work/puppet-foreman/puppet-foreman/spec/fixtures/modules/podman/manifests/quadlet.pp, line: 114, column: 7) (file: /home/runner/work/puppet-foreman/puppet-foreman/spec/fixtures/modules/foreman/manifests/service.pp, line: 58) on node fv-az1380-906.0iobsfatwvhuvgmqxjqze0bk2d.ex.internal.cloudapp.net

foreman::cli on centos-8-x86_64 with settings from foreman is expected to contain Package[foreman-cli] with ensure => "installed" Failure/Error: should contain_package('foreman-cli') .with_ensure('installed') Puppet::PreformattedError: 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: /home/runner/work/puppet-foreman/puppet-foreman/spec/fixtures/modules/foreman/manifests/service.pp, line: 47); cannot redeclare (file: /home/runner/work/puppet-foreman/puppet-foreman/spec/fixtures/modules/podman/manifests/quadlet.pp, line: 114) (file: /home/runner/work/puppet-foreman/puppet-foreman/spec/fixtures/modules/podman/manifests/quadlet.pp, line: 114, column: 7) (file: /home/runner/work/puppet-foreman/puppet-foreman/spec/fixtures/modules/foreman/manifests/service.pp, line: 58) on node fv-az1380-906.0iobsfatwvhuvgmqxjqze0bk2d.ex.internal.cloudapp.net

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

foreman::providers on centos-9-x86_64 with foreman is expected to compile into a catalogue without dependency cycles Failure/Error: it { is_expected.to compile.with_all_deps } error during compilation: 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: /home/runner/work/puppet-foreman/puppet-foreman/spec/fixtures/modules/foreman/manifests/service.pp, line: 47); cannot redeclare (file: /home/runner/work/puppet-foreman/puppet-foreman/spec/fixtures/modules/podman/manifests/quadlet.pp, line: 114) (file: /home/runner/work/puppet-foreman/puppet-foreman/spec/fixtures/modules/podman/manifests/quadlet.pp, line: 114, column: 7) (file: /home/runner/work/puppet-foreman/puppet-foreman/spec/fixtures/modules/foreman/manifests/service.pp, line: 58) on node fv-az1380-906.0iobsfatwvhuvgmqxjqze0bk2d.ex.internal.cloudapp.net

foreman on ubuntu-22.04-x86_64 with db_manage set to false is expected not to contain Class[foreman::database::postgresql] Failure/Error: it { should_not contain_class('foreman::database::postgresql') } Puppet::PreformattedError: 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: /home/runner/work/puppet-foreman/puppet-foreman/spec/fixtures/modules/foreman/manifests/service.pp, line: 47); cannot redeclare (file: /home/runner/work/puppet-foreman/puppet-foreman/spec/fixtures/modules/podman/manifests/quadlet.pp, line: 114) (file: /home/runner/work/puppet-foreman/puppet-foreman/spec/fixtures/modules/podman/manifests/quadlet.pp, line: 114, column: 7) (file: /home/runner/work/puppet-foreman/puppet-foreman/spec/fixtures/modules/foreman/manifests/service.pp, line: 58) on node fv-az1788-468.v003jhcb0gbebhi3eudo0jipka.bx.internal.cloudapp.net

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') } Puppet::PreformattedError: 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: /home/runner/work/puppet-foreman/puppet-foreman/spec/fixtures/modules/foreman/manifests/service.pp, line: 47); cannot redeclare (file: /home/runner/work/puppet-foreman/puppet-foreman/spec/fixtures/modules/podman/manifests/quadlet.pp, line: 114) (file: /home/runner/work/puppet-foreman/puppet-foreman/spec/fixtures/modules/podman/manifests/quadlet.pp, line: 114, column: 7) (file: /home/runner/work/puppet-foreman/puppet-foreman/spec/fixtures/modules/foreman/manifests/service.pp, line: 58) on node fv-az1380-906.0iobsfatwvhuvgmqxjqze0bk2d.ex.internal.cloudapp.net

foreman::providers on ubuntu-22.04-x86_64 with foreman is expected to compile into a catalogue without dependency cycles Failure/Error: it { is_expected.to compile.with_all_deps } error during compilation: 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: /home/runner/work/puppet-foreman/puppet-foreman/spec/fixtures/modules/foreman/manifests/service.pp, line: 47); cannot redeclare (file: /home/runner/work/puppet-foreman/puppet-foreman/spec/fixtures/modules/podman/manifests/quadlet.pp, line: 114) (file: /home/runner/work/puppet-foreman/puppet-foreman/spec/fixtures/modules/podman/manifests/quadlet.pp, line: 114, column: 7) (file: /home/runner/work/puppet-foreman/puppet-foreman/spec/fixtures/modules/foreman/manifests/service.pp, line: 58) on node fv-az1788-468.v003jhcb0gbebhi3eudo0jipka.bx.internal.cloudapp.net

foreman::cli on centos-8-x86_64 with settings from foreman should contain settings in /etc from foreman Failure/Error: is_expected.to contain_file('/etc/hammer/cli.modules.d/foreman.yml') .with_content( <<~CONFIG :foreman: # Enable/disable foreman commands :enable_module: true # Your foreman server address :host: 'https://foreman.example.com' Puppet::PreformattedError: 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: /home/runner/work/puppet-foreman/puppet-foreman/spec/fixtures/modules/foreman/manifests/service.pp, line: 47); cannot redeclare (file: /home/runner/work/puppet-foreman/puppet-foreman/spec/fixtures/modules/podman/manifests/quadlet.pp, line: 114) (file: /home/runner/work/puppet-foreman/puppet-foreman/spec/fixtures/modules/podman/manifests/quadlet.pp, line: 114, column: 7) (file: /home/runner/work/puppet-foreman/puppet-foreman/spec/fixtures/modules/foreman/manifests/service.pp, line: 58) on node fv-az1380-906.0iobsfatwvhuvgmqxjqze0bk2d.ex.internal.cloudapp.net

foreman::cli on ubuntu-22.04-x86_64 with settings from foreman is expected to compile into a catalogue without dependency cycles Failure/Error: it { is_expected.to compile.with_all_deps } error during compilation: 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: /home/runner/work/puppet-foreman/puppet-foreman/spec/fixtures/modules/foreman/manifests/service.pp, line: 47); cannot redeclare (file: /home/runner/work/puppet-foreman/puppet-foreman/spec/fixtures/modules/podman/manifests/quadlet.pp, line: 114) (file: /home/runner/work/puppet-foreman/puppet-foreman/spec/fixtures/modules/podman/manifests/quadlet.pp, line: 114, column: 7) (file: /home/runner/work/puppet-foreman/puppet-foreman/spec/fixtures/modules/foreman/manifests/service.pp, line: 58) on node fv-az1788-468.v003jhcb0gbebhi3eudo0jipka.bx.internal.cloudapp.net

foreman on ubuntu-22.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') } Puppet::PreformattedError: 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: /home/runner/work/puppet-foreman/puppet-foreman/spec/fixtures/modules/foreman/manifests/service.pp, line: 47); cannot redeclare (file: /home/runner/work/puppet-foreman/puppet-foreman/spec/fixtures/modules/podman/manifests/quadlet.pp, line: 114) (file: /home/runner/work/puppet-foreman/puppet-foreman/spec/fixtures/modules/podman/manifests/quadlet.pp, line: 114, column: 7) (file: /home/runner/work/puppet-foreman/puppet-foreman/spec/fixtures/modules/foreman/manifests/service.pp, line: 58) on node fv-az1788-468.v003jhcb0gbebhi3eudo0jipka.bx.internal.cloudapp.net

foreman::providers on ubuntu-22.04-x86_64 with foreman is expected to contain Package[puppet-agent-oauth] that comes before Class[foreman] Failure/Error: it { should contain_package(oauth_os).that_comes_before('Class[foreman]') } Puppet::PreformattedError: 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: /home/runner/work/puppet-foreman/puppet-foreman/spec/fixtures/modules/foreman/manifests/service.pp, line: 47); cannot redeclare (file: /home/runner/work/puppet-foreman/puppet-foreman/spec/fixtures/modules/podman/manifests/quadlet.pp, line: 114) (file: /home/runner/work/puppet-foreman/puppet-foreman/spec/fixtures/modules/podman/manifests/quadlet.pp, line: 114, column: 7) (file: /home/runner/work/puppet-foreman/puppet-foreman/spec/fixtures/modules/foreman/manifests/service.pp, line: 58) on node fv-az1788-468.v003jhcb0gbebhi3eudo0jipka.bx.internal.cloudapp.net

foreman::cli on ubuntu-22.04-x86_64 with settings from foreman is expected to contain Package[foreman-cli] with ensure => "installed" Failure/Error: should contain_package('foreman-cli') .with_ensure('installed') Puppet::PreformattedError: 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: /home/runner/work/puppet-foreman/puppet-foreman/spec/fixtures/modules/foreman/manifests/service.pp, line: 47); cannot redeclare (file: /home/runner/work/puppet-foreman/puppet-foreman/spec/fixtures/modules/podman/manifests/quadlet.pp, line: 114) (file: /home/runner/work/puppet-foreman/puppet-foreman/spec/fixtures/modules/podman/manifests/quadlet.pp, line: 114, column: 7) (file: /home/runner/work/puppet-foreman/puppet-foreman/spec/fixtures/modules/foreman/manifests/service.pp, line: 58) on node fv-az1788-468.v003jhcb0gbebhi3eudo0jipka.bx.internal.cloudapp.net

foreman on ubuntu-22.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') } Puppet::PreformattedError: 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: /home/runner/work/puppet-foreman/puppet-foreman/spec/fixtures/modules/foreman/manifests/service.pp, line: 47); cannot redeclare (file: /home/runner/work/puppet-foreman/puppet-foreman/spec/fixtures/modules/podman/manifests/quadlet.pp, line: 114) (file: /home/runner/work/puppet-foreman/puppet-foreman/spec/fixtures/modules/podman/manifests/quadlet.pp, line: 114, column: 7) (file: /home/runner/work/puppet-foreman/puppet-foreman/spec/fixtures/modules/foreman/manifests/service.pp, line: 58) on node fv-az1788-468.v003jhcb0gbebhi3eudo0jipka.bx.internal.cloudapp.net

foreman::providers on debian-11-x86_64 with foreman is expected to compile into a catalogue without dependency cycles Failure/Error: it { is_expected.to compile.with_all_deps } error during compilation: 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: /home/runner/work/puppet-foreman/puppet-foreman/spec/fixtures/modules/foreman/manifests/service.pp, line: 47); cannot redeclare (file: /home/runner/work/puppet-foreman/puppet-foreman/spec/fixtures/modules/podman/manifests/quadlet.pp, line: 114) (file: /home/runner/work/puppet-foreman/puppet-foreman/spec/fixtures/modules/podman/manifests/quadlet.pp, line: 114, column: 7) (file: /home/runner/work/puppet-foreman/puppet-foreman/spec/fixtures/modules/foreman/manifests/service.pp, line: 58) on node fv-az1788-468.v003jhcb0gbebhi3eudo0jipka.bx.internal.cloudapp.net

foreman on ubuntu-22.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') } Puppet::PreformattedError: 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: /home/runner/work/puppet-foreman/puppet-foreman/spec/fixtures/modules/foreman/manifests/service.pp, line: 47); cannot redeclare (file: /home/runner/work/puppet-foreman/puppet-foreman/spec/fixtures/modules/podman/manifests/quadlet.pp, line: 114) (file: /home/runner/work/puppet-foreman/puppet-foreman/spec/fixtures/modules/podman/manifests/quadlet.pp, line: 114, column: 7) (file: /home/runner/work/puppet-foreman/puppet-foreman/spec/fixtures/modules/foreman/manifests/service.pp, line: 58) on node fv-az1788-468.v003jhcb0gbebhi3eudo0jipka.bx.internal.cloudapp.net

foreman::cli on ubuntu-22.04-x86_64 with settings from foreman should contain settings in /etc from foreman Failure/Error: is_expected.to contain_file('/etc/hammer/cli.modules.d/foreman.yml') .with_content( <<~CONFIG :foreman: # Enable/disable foreman commands :enable_module: true # Your foreman server address :host: 'https://foreman.example.com' Puppet::PreformattedError: 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: /home/runner/work/puppet-foreman/puppet-foreman/spec/fixtures/modules/foreman/manifests/service.pp, line: 47); cannot redeclare (file: /home/runner/work/puppet-foreman/puppet-foreman/spec/fixtures/modules/podman/manifests/quadlet.pp, line: 114) (file: /home/runner/work/puppet-foreman/puppet-foreman/spec/fixtures/modules/podman/manifests/quadlet.pp, line: 114, column: 7) (file: /home/runner/work/puppet-foreman/puppet-foreman/spec/fixtures/modules/foreman/manifests/service.pp, line: 58) on node fv-az1788-468.v003jhcb0gbebhi3eudo0jipka.bx.internal.cloudapp.net

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 1 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_112657299.pp.hb8sEk 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 ubuntu2204-64-puppet7.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 'ubuntu2204-64-puppet7.example.com' exited with 1 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_112702646.pp.QFjAaF 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 ubuntu2204-64-puppet7.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

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

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