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_111859962.pp.iTL7ix 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: 45); 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: 55) 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_111902860.pp.AXdj0Y 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: 45); 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: 55) 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

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_111912151.pp.HgkwvF 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: 45); 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: 55) 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_111914886.pp.qWsAJS 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: 45); 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: 55) 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 'centos8-64-puppet7.example.com' exited with 1 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_111907684.pp.sWNkaN 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: 45); 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: 55) 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_111910501.pp.cGvzWP 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: 45); 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: 55) 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

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_111909116.pp.OMP5nw 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: 45); 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: 55) 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_111912932.pp.lrzT23 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: 45); 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: 55) 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

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_111917055.pp.ISbabH 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: 45); 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: 55) 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_111919961.pp.2Cq9uX 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: 45); 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: 55) 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

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_111902201.pp.YlnqsB 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: 45); 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: 55) 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_111906435.pp.LnhBfQ 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: 45); 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: 55) 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

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_111913421.pp.M6887B 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: 45); 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: 55) 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_111917670.pp.NmcEVv 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: 45); 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: 55) 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

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 'debian12-64-puppet8.example.com' exited with 1 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_111911526.pp.SZluSz 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: 45); 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: 55) 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_111916231.pp.cRtSs6 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: 45); 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: 55) 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

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_111914487.pp.eYSbQm 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: 45); 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: 55) 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_111919215.pp.tkUGxr 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: 45); 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: 55) 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

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_111913380.pp.BzDBcO 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: 45); 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: 55) 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_111918486.pp.ckbKNI 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: 45); 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: 55) 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

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_111915821.pp.oyqfOY 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: 45); 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: 55) 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_111921076.pp.S5XwfI 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: 45); 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: 55) 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

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_111930517.pp.6WV8jD 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: 45); 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: 55) 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_111935959.pp.TLRgZI 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: 45); 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: 55) 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

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: 45); 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: 55) 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: 45); 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: 55) 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: 45); 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: 55) 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 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: 45); 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: 55) on node fv-az1380-906.0iobsfatwvhuvgmqxjqze0bk2d.ex.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: 45); 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: 55) 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 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: 45); 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: 55) 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 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: 45); 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: 55) on node fv-az1380-906.0iobsfatwvhuvgmqxjqze0bk2d.ex.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: 45); 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: 55) 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 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: 45); 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: 55) on node fv-az1380-906.0iobsfatwvhuvgmqxjqze0bk2d.ex.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: 45); 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: 55) on node fv-az1380-906.0iobsfatwvhuvgmqxjqze0bk2d.ex.internal.cloudapp.net

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: 45); 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: 55) 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: 45); 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: 55) 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: 45); 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: 55) 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: 45); 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: 55) 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: 45); 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: 55) 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: 45); 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: 55) 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: 45); 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: 55) 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: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: 45); 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: 55) on node fv-az1380-906.0iobsfatwvhuvgmqxjqze0bk2d.ex.internal.cloudapp.net

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: 45); 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: 55) on node fv-az1380-906.0iobsfatwvhuvgmqxjqze0bk2d.ex.internal.cloudapp.net