Scenario: install foreman-proxy with ansible plugin 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_182218698.pp.nOe1MH Last 10 lines of output were: 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) Warning: This function is deprecated, please use stdlib::ensure_packages instead. at ["/etc/puppetlabs/code/environments/production/modules/foreman_proxy/manifests/plugin/ansible.pp", 62]:["/tmp/apply_manifest_182218698.pp.nOe1MH", 2] (location: /etc/puppetlabs/code/environments/production/modules/stdlib/lib/puppet/functions/deprecation.rb:35:in `deprecation') Error: Evaluation Error: Error while evaluating a Resource Statement, Evaluation Error: Error while evaluating a Function Call, deprecation. systemd::servicelimits - foreman-proxy.service. systemd::servicelimits is deprecated, use systemd::manage_dropin at ["/etc/puppetlabs/code/environments/production/modules/systemd/manifests/service_limits.pp", 77]: (file: /etc/puppetlabs/code/environments/production/modules/systemd/manifests/service_limits.pp, line: 77, column: 5) (file: /etc/puppetlabs/code/environments/production/modules/foreman_proxy/manifests/plugin/dynflow.pp, line: 48) on node centos9-64-puppet8.example.com Shared Example Group: "an idempotent resource" called from ./vendor/bundle/ruby/3.2.0/gems/voxpupuli-acceptance-2.4.0/lib/voxpupuli/acceptance/examples.rb:14 Shared Example Group: "the example" called from ./spec/acceptance/ansible_spec.rb:6

Scenario: install foreman-proxy with ansible plugin 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_182220857.pp.a4EfmR Last 10 lines of output were: 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) Warning: This function is deprecated, please use stdlib::ensure_packages instead. at ["/etc/puppetlabs/code/environments/production/modules/foreman_proxy/manifests/plugin/ansible.pp", 62]:["/tmp/apply_manifest_182220857.pp.a4EfmR", 2] (location: /etc/puppetlabs/code/environments/production/modules/stdlib/lib/puppet/functions/deprecation.rb:35:in `deprecation') Error: Evaluation Error: Error while evaluating a Resource Statement, Evaluation Error: Error while evaluating a Function Call, deprecation. systemd::servicelimits - foreman-proxy.service. systemd::servicelimits is deprecated, use systemd::manage_dropin at ["/etc/puppetlabs/code/environments/production/modules/systemd/manifests/service_limits.pp", 77]: (file: /etc/puppetlabs/code/environments/production/modules/systemd/manifests/service_limits.pp, line: 77, column: 5) (file: /etc/puppetlabs/code/environments/production/modules/foreman_proxy/manifests/plugin/dynflow.pp, line: 48) on node centos9-64-puppet8.example.com Shared Example Group: "an idempotent resource" called from ./vendor/bundle/ruby/3.2.0/gems/voxpupuli-acceptance-2.4.0/lib/voxpupuli/acceptance/examples.rb:14 Shared Example Group: "the example" called from ./spec/acceptance/ansible_spec.rb:6

Scenario: install foreman-proxy with ansible plugin behaves like the default foreman proxy application Service "foreman-proxy" is expected to be enabled Failure/Error: it { is_expected.to be_enabled } expected Service "foreman-proxy" to be enabled Shared Example Group: "the default foreman proxy application" called from ./spec/acceptance/ansible_spec.rb:8

Scenario: install foreman-proxy with ansible plugin behaves like the default foreman proxy application Service "foreman-proxy" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "foreman-proxy" to be running Shared Example Group: "the default foreman proxy application" called from ./spec/acceptance/ansible_spec.rb:8

Scenario: install foreman-proxy with ansible plugin behaves like the default foreman proxy application Port "8443" is expected to be listening Failure/Error: it { is_expected.to be_listening } expected Port "8443" to be listening Shared Example Group: "the default foreman proxy application" called from ./spec/acceptance/ansible_spec.rb:8

Scenario: install foreman-proxy with ansible plugin Package "ansible-collection-theforeman-foreman" is expected to be installed Failure/Error: it { is_expected.to be_installed } expected Package "ansible-collection-theforeman-foreman" to be installed

Scenario: install foreman-proxy with ansible plugin Package "ansible-runner" is expected to be installed Failure/Error: it { is_expected.to be_installed } expected Package "ansible-runner" to be installed

Scenario: install foreman-proxy with ansible plugin Command "ansible-runner --help" exit_status is expected to eq 0 Failure/Error: its(:exit_status) { should eq 0 } expected: 0 got: 127 (compared using ==)

Scenario: install foreman-proxy with ansible plugin Command "ansible-runner run --module ping --hosts localhost /tmp/ansible-runner-test" exit_status is expected to eq 0 Failure/Error: its(:exit_status) { should eq 0 } expected: 0 got: 127 (compared using ==)