run foreman in a container #1608
ci.yml
on: pull_request
Puppet
/
Static validations
2m 19s
Matrix: Puppet / acceptance
Matrix: Puppet / unit
Puppet
/
Test suite
0s
Annotations
140 errors
Puppet / 7 (Ruby 2.7):
spec/classes/foreman_database_spec.rb#L14
foreman on redhat-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') }
expected that the catalogue would contain Foreman::Rake[db:migrate]
|
Puppet / 7 (Ruby 2.7):
spec/classes/foreman_database_spec.rb#L15
foreman on redhat-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') }
expected that the catalogue would contain Foreman_config_entry[db_pending_seed]
|
Puppet / 7 (Ruby 2.7):
spec/classes/foreman_database_spec.rb#L16
foreman on redhat-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') }
expected that the catalogue would contain Foreman::Rake[db:seed]
|
Puppet / 7 (Ruby 2.7):
spec/classes/foreman_database_spec.rb#L38
foreman on redhat-8-x86_64 with seed parameters is expected to contain Foreman::Rake[db:seed] with environment => {"SEED_ADMIN_USER"=>"joe", "SEED_ADMIN_PASSWORD"=>"secret"}
Failure/Error:
should contain_foreman__rake('db:seed')
.with_environment(
'SEED_ADMIN_USER' => 'joe',
'SEED_ADMIN_PASSWORD' => 'secret'
)
expected that the catalogue would contain Foreman::Rake[db:seed]
|
Puppet / 7 (Ruby 2.7):
spec/classes/foreman_database_spec.rb#L14
foreman on ubuntu-20.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') }
expected that the catalogue would contain Foreman::Rake[db:migrate]
|
Puppet / 7 (Ruby 2.7):
spec/classes/foreman_database_spec.rb#L15
foreman on ubuntu-20.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') }
expected that the catalogue would contain Foreman_config_entry[db_pending_seed]
|
Puppet / 7 (Ruby 2.7):
spec/classes/foreman_database_spec.rb#L16
foreman on ubuntu-20.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') }
expected that the catalogue would contain Foreman::Rake[db:seed]
|
Puppet / 7 (Ruby 2.7):
spec/classes/foreman_database_spec.rb#L38
foreman on ubuntu-20.04-x86_64 with seed parameters is expected to contain Foreman::Rake[db:seed] with environment => {"SEED_ADMIN_USER"=>"joe", "SEED_ADMIN_PASSWORD"=>"secret"}
Failure/Error:
should contain_foreman__rake('db:seed')
.with_environment(
'SEED_ADMIN_USER' => 'joe',
'SEED_ADMIN_PASSWORD' => 'secret'
)
expected that the catalogue would contain Foreman::Rake[db:seed]
|
Puppet / 7 (Ruby 2.7):
spec/classes/foreman_database_spec.rb#L14
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') }
expected that the catalogue would contain Foreman::Rake[db:migrate]
|
Puppet / 7 (Ruby 2.7):
spec/classes/foreman_database_spec.rb#L15
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') }
expected that the catalogue would contain Foreman_config_entry[db_pending_seed]
|
Puppet / 8 (Ruby 3.2):
spec/classes/foreman_database_spec.rb#L14
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') }
expected that the catalogue would contain Foreman::Rake[db:migrate]
|
Puppet / 8 (Ruby 3.2):
spec/classes/foreman_database_spec.rb#L15
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') }
expected that the catalogue would contain Foreman_config_entry[db_pending_seed]
|
Puppet / 8 (Ruby 3.2):
spec/classes/foreman_database_spec.rb#L16
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') }
expected that the catalogue would contain Foreman::Rake[db:seed]
|
Puppet / 8 (Ruby 3.2):
spec/classes/foreman_database_spec.rb#L38
foreman on centos-8-x86_64 with seed parameters is expected to contain Foreman::Rake[db:seed] with environment => {"SEED_ADMIN_USER"=>"joe", "SEED_ADMIN_PASSWORD"=>"secret"}
Failure/Error:
should contain_foreman__rake('db:seed')
.with_environment(
'SEED_ADMIN_USER' => 'joe',
'SEED_ADMIN_PASSWORD' => 'secret'
)
expected that the catalogue would contain Foreman::Rake[db:seed]
|
Puppet / 8 (Ruby 3.2):
spec/classes/foreman_database_spec.rb#L14
foreman on centos-9-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') }
expected that the catalogue would contain Foreman::Rake[db:migrate]
|
Puppet / 8 (Ruby 3.2):
spec/classes/foreman_database_spec.rb#L15
foreman on centos-9-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') }
expected that the catalogue would contain Foreman_config_entry[db_pending_seed]
|
Puppet / 8 (Ruby 3.2):
spec/classes/foreman_database_spec.rb#L16
foreman on centos-9-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') }
expected that the catalogue would contain Foreman::Rake[db:seed]
|
Puppet / 8 (Ruby 3.2):
spec/classes/foreman_database_spec.rb#L38
foreman on centos-9-x86_64 with seed parameters is expected to contain Foreman::Rake[db:seed] with environment => {"SEED_ADMIN_USER"=>"joe", "SEED_ADMIN_PASSWORD"=>"secret"}
Failure/Error:
should contain_foreman__rake('db:seed')
.with_environment(
'SEED_ADMIN_USER' => 'joe',
'SEED_ADMIN_PASSWORD' => 'secret'
)
expected that the catalogue would contain Foreman::Rake[db:seed]
|
Puppet / 8 (Ruby 3.2):
spec/classes/foreman_database_spec.rb#L14
foreman on debian-11-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') }
expected that the catalogue would contain Foreman::Rake[db:migrate]
|
Puppet / 8 (Ruby 3.2):
spec/classes/foreman_database_spec.rb#L15
foreman on debian-11-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') }
expected that the catalogue would contain Foreman_config_entry[db_pending_seed]
|
Puppet / Puppet 8 - CentOS 9:
vendor/bundle/ruby/3.2.0/gems/voxpupuli-acceptance-2.4.0/lib/voxpupuli/acceptance/examples.rb#L4
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 6 running:
puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_125807231.pp.qteZ4j
Last 10 lines of output were:
Info: /Stage[main]/Foreman::Service/Podman::Quadlet[foreman.container]/Service[foreman.service]: Unscheduling refresh on Service[foreman.service]
Info: Class[Foreman::Service]: Unscheduling all events on Class[Foreman::Service]
�[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@orchestrator] has failures: true
�[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@worker-1] has failures: true
�[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@worker-2] has failures: true
Warning: /Stage[main]/Foreman/Anchor[foreman::service]: Skipping because of failed dependencies
Warning: /Stage[main]/Foreman::Register/Foreman_host[foreman-centos9-64-puppet8.example.com]: Skipping because of failed dependencies
Warning: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-centos9-64-puppet8.example.com]: Skipping because of failed dependencies
Info: Stage[main]: Unscheduling all events on Stage[main]
�[mNotice: Applied catalog in 114.47 seconds
Shared Example Group: "an idempotent resource" called from ./spec/acceptance/dynflow_spec.rb:5
|
Puppet / Puppet 8 - CentOS 9:
vendor/bundle/ruby/3.2.0/gems/voxpupuli-acceptance-2.4.0/lib/voxpupuli/acceptance/examples.rb#L8
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 6 running:
puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_130005922.pp.XECHtc
Last 10 lines of output were:
�[mNotice: /Stage[main]/Foreman::Service/Foreman::Dynflow::Pool[worker]/Foreman::Dynflow::Worker[worker-1]/Service[dynflow-sidekiq@worker-1]/ensure: ensure changed 'stopped' to 'running'
Info: /Stage[main]/Foreman::Service/Foreman::Dynflow::Pool[worker]/Foreman::Dynflow::Worker[worker-1]/Service[dynflow-sidekiq@worker-1]: Unscheduling refresh on Service[dynflow-sidekiq@worker-1]
�[mNotice: /Stage[main]/Foreman::Service/Foreman::Dynflow::Pool[worker]/Foreman::Dynflow::Worker[worker-2]/Service[dynflow-sidekiq@worker-2]/enable: enable changed 'false' to 'true'
Info: Class[Foreman::Service]: Unscheduling all events on Class[Foreman::Service]
�[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@orchestrator] has failures: true
Warning: /Stage[main]/Foreman/Anchor[foreman::service]: Skipping because of failed dependencies
Warning: /Stage[main]/Foreman::Register/Foreman_host[foreman-centos9-64-puppet8.example.com]: Skipping because of failed dependencies
Warning: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-centos9-64-puppet8.example.com]: Skipping because of failed dependencies
�[mNotice: Applied catalog in 15.41 seconds
Shared Example Group: "an idempotent resource" called from ./spec/acceptance/dynflow_spec.rb:5
|
Puppet / Puppet 8 - CentOS 9:
spec/support/acceptance/examples.rb#L9
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
|
Puppet / Puppet 8 - CentOS 9:
spec/support/acceptance/examples.rb#L10
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
|
Puppet / Puppet 8 - CentOS 9:
spec/support/acceptance/examples.rb#L23
Scenario: install foreman 2 workers behaves like the foreman application File "/run/foreman.sock" is expected to be socket
Failure/Error: it { should be_socket }
expected `File "/run/foreman.sock".socket?` to be truthy, got false
Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15
|
Puppet / Puppet 8 - CentOS 9:
spec/support/acceptance/examples.rb#L27
Scenario: install foreman 2 workers behaves like the foreman application Command "curl -s --cacert /etc/foreman-certs/certificate.pem https://centos9-64-puppet8.example.com -w '%{redirect_url}' -o /dev/null" stdout is expected to eq "https://centos9-64-puppet8.example.com/users/login"
Failure/Error: its(:stdout) { is_expected.to eq("https://#{host_inventory['fqdn']}#{params.fetch(:expected_login_url_path, '/users/login')}") }
expected: #<Encoding:UTF-8> "https://centos9-64-puppet8.example.com/users/login"
got: #<Encoding:US-ASCII> ""
(compared using ==)
Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15
|
Puppet / Puppet 8 - CentOS 9:
vendor/bundle/ruby/3.2.0/gems/voxpupuli-acceptance-2.4.0/lib/voxpupuli/acceptance/examples.rb#L4
Scenario: install foreman 1 worker 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 6 running:
puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_130030484.pp.TSovYQ
Last 10 lines of output were:
Info: Using environment 'production'
Info: Applying configuration version '1715691632'
�[mNotice: /Stage[main]/Foreman::Service/Foreman::Dynflow::Worker[orchestrator]/Service[dynflow-sidekiq@orchestrator]/enable: enable changed 'false' to 'true'
�[mNotice: /Stage[main]/Foreman::Service/Foreman::Dynflow::Pool[worker]/Foreman::Dynflow::Worker[worker-2]/Service[dynflow-sidekiq@worker-2]/ensure: ensure changed 'running' to 'stopped'
�[mNotice: /Stage[main]/Foreman::Service/Foreman::Dynflow::Pool[worker]/Foreman::Dynflow::Worker[worker-2]/File[/etc/foreman/dynflow/worker-2.yml]/ensure: removed
Error: /Stage[main]/Foreman::Register/Foreman_host[foreman-centos9-64-puppet8.example.com]: Could not evaluate: Error making GET request to Foreman at https://centos9-64-puppet8.example.com/api/v2/hosts: Response: 502 Proxy Error: The webserver received an invalid response from the backend service. Was Foreman at centos9-64-puppet8.example.com unable to handle the request?
�[mNotice: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-centos9-64-puppet8.example.com]: Dependency Foreman_host[foreman-centos9-64-puppet8.example.com] has failures: true
Warning: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-centos9-64-puppet8.example.com]: Skipping because of failed dependencies
Info: Stage[main]: Unscheduling all events on Stage[main]
�[mNotice: Applied catalog in 2.89 seconds
Shared Example Group: "an idempotent resource" called from ./spec/acceptance/dynflow_spec.rb:46
|
Puppet / Puppet 8 - CentOS 9:
vendor/bundle/ruby/3.2.0/gems/voxpupuli-acceptance-2.4.0/lib/voxpupuli/acceptance/examples.rb#L8
Scenario: install foreman 1 worker 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 4 running:
puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_130037525.pp.QohrhV
Last 10 lines of output were:
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)
�[mNotice: Compiled catalog for centos9-64-puppet8.example.com in environment production in 1.28 seconds
Info: Using environment 'production'
Info: Applying configuration version '1715691639'
Error: /Stage[main]/Foreman::Register/Foreman_host[foreman-centos9-64-puppet8.example.com]: Could not evaluate: Error making GET request to Foreman at https://centos9-64-puppet8.example.com/api/v2/hosts: Response: 502 Proxy Error: The webserver received an invalid response from the backend service. Was Foreman at centos9-64-puppet8.example.com unable to handle the request?
�[mNotice: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-centos9-64-puppet8.example.com]: Dependency Foreman_host[foreman-centos9-64-puppet8.example.com] has failures: true
Warning: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-centos9-64-puppet8.example.com]: Skipping because of failed dependencies
�[mNotice: Applied catalog in 0.61 seconds
Shared Example Group: "an idempotent resource" called from ./spec/acceptance/dynflow_spec.rb:46
|
Puppet / Puppet 8 - CentOS 9:
spec/support/acceptance/examples.rb#L23
Scenario: install foreman 1 worker behaves like the foreman application File "/run/foreman.sock" is expected to be socket
Failure/Error: it { should be_socket }
expected `File "/run/foreman.sock".socket?` to be truthy, got false
Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:56
|
Puppet / Puppet 8 - CentOS 9:
spec/support/acceptance/examples.rb#L27
Scenario: install foreman 1 worker behaves like the foreman application Command "curl -s --cacert /etc/foreman-certs/certificate.pem https://centos9-64-puppet8.example.com -w '%{redirect_url}' -o /dev/null" stdout is expected to eq "https://centos9-64-puppet8.example.com/users/login"
Failure/Error: its(:stdout) { is_expected.to eq("https://#{host_inventory['fqdn']}#{params.fetch(:expected_login_url_path, '/users/login')}") }
expected: #<Encoding:UTF-8> "https://centos9-64-puppet8.example.com/users/login"
got: #<Encoding:US-ASCII> ""
(compared using ==)
Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:56
|
Puppet / Puppet 7 - CentOS 9:
vendor/bundle/ruby/3.2.0/gems/voxpupuli-acceptance-2.4.0/lib/voxpupuli/acceptance/examples.rb#L4
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 6 running:
puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_125742014.pp.iR6pWN
Last 10 lines of output were:
Info: /Stage[main]/Foreman::Service/Podman::Quadlet[foreman.container]/Service[foreman.service]: Unscheduling refresh on Service[foreman.service]
Info: Class[Foreman::Service]: Unscheduling all events on Class[Foreman::Service]
�[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@orchestrator] has failures: true
�[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@worker-1] has failures: true
�[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@worker-2] has failures: true
Warning: /Stage[main]/Foreman/Anchor[foreman::service]: Skipping because of failed dependencies
Warning: /Stage[main]/Foreman::Register/Foreman_host[foreman-centos9-64-puppet7.example.com]: Skipping because of failed dependencies
Warning: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-centos9-64-puppet7.example.com]: Skipping because of failed dependencies
Info: Stage[main]: Unscheduling all events on Stage[main]
�[mNotice: Applied catalog in 124.04 seconds
Shared Example Group: "an idempotent resource" called from ./spec/acceptance/dynflow_spec.rb:5
|
Puppet / Puppet 7 - CentOS 9:
vendor/bundle/ruby/3.2.0/gems/voxpupuli-acceptance-2.4.0/lib/voxpupuli/acceptance/examples.rb#L8
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 6 running:
puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_125950273.pp.gQqiy4
Last 10 lines of output were:
Info: Applying configuration version '1715691594'
�[mNotice: /Stage[main]/Foreman::Service/Foreman::Dynflow::Worker[orchestrator]/Service[dynflow-sidekiq@orchestrator]/ensure: ensure changed 'stopped' to 'running'
Info: /Stage[main]/Foreman::Service/Foreman::Dynflow::Worker[orchestrator]/Service[dynflow-sidekiq@orchestrator]: Unscheduling refresh on Service[dynflow-sidekiq@orchestrator]
�[mNotice: /Stage[main]/Foreman::Service/Foreman::Dynflow::Pool[worker]/Foreman::Dynflow::Worker[worker-1]/Service[dynflow-sidekiq@worker-1]/enable: enable changed 'false' to 'true'
�[mNotice: /Stage[main]/Foreman::Service/Foreman::Dynflow::Pool[worker]/Foreman::Dynflow::Worker[worker-2]/Service[dynflow-sidekiq@worker-2]/enable: enable changed 'false' to 'true'
Error: /Stage[main]/Foreman::Register/Foreman_host[foreman-centos9-64-puppet7.example.com]: Could not evaluate: Error making GET request to Foreman at https://centos9-64-puppet7.example.com/api/v2/hosts: Response: 502 Proxy Error: The webserver received an invalid response from the backend service. Was Foreman at centos9-64-puppet7.example.com unable to handle the request?
�[mNotice: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-centos9-64-puppet7.example.com]: Dependency Foreman_host[foreman-centos9-64-puppet7.example.com] has failures: true
Warning: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-centos9-64-puppet7.example.com]: Skipping because of failed dependencies
Info: Stage[main]: Unscheduling all events on Stage[main]
�[mNotice: Applied catalog in 23.87 seconds
Shared Example Group: "an idempotent resource" called from ./spec/acceptance/dynflow_spec.rb:5
|
Puppet / Puppet 7 - CentOS 9:
spec/support/acceptance/examples.rb#L23
Scenario: install foreman 2 workers behaves like the foreman application File "/run/foreman.sock" is expected to be socket
Failure/Error: it { should be_socket }
expected `File "/run/foreman.sock".socket?` to be truthy, got false
Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15
|
Puppet / Puppet 7 - CentOS 9:
spec/support/acceptance/examples.rb#L27
Scenario: install foreman 2 workers behaves like the foreman application Command "curl -s --cacert /etc/foreman-certs/certificate.pem https://centos9-64-puppet7.example.com -w '%{redirect_url}' -o /dev/null" stdout is expected to eq "https://centos9-64-puppet7.example.com/users/login"
Failure/Error: its(:stdout) { is_expected.to eq("https://#{host_inventory['fqdn']}#{params.fetch(:expected_login_url_path, '/users/login')}") }
expected: #<Encoding:UTF-8> "https://centos9-64-puppet7.example.com/users/login"
got: #<Encoding:US-ASCII> ""
(compared using ==)
Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15
|
Puppet / Puppet 7 - CentOS 9:
vendor/bundle/ruby/3.2.0/gems/voxpupuli-acceptance-2.4.0/lib/voxpupuli/acceptance/examples.rb#L4
Scenario: install foreman 1 worker 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 6 running:
puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_130022438.pp.mVIIzP
Last 10 lines of output were:
�[mNotice: Compiled catalog for centos9-64-puppet7.example.com in environment production in 1.50 seconds
Info: Using environment 'production'
Info: Applying configuration version '1715691624'
�[mNotice: /Stage[main]/Foreman::Service/Foreman::Dynflow::Pool[worker]/Foreman::Dynflow::Worker[worker-2]/Service[dynflow-sidekiq@worker-2]/ensure: ensure changed 'running' to 'stopped'
�[mNotice: /Stage[main]/Foreman::Service/Foreman::Dynflow::Pool[worker]/Foreman::Dynflow::Worker[worker-2]/File[/etc/foreman/dynflow/worker-2.yml]/ensure: removed
Error: /Stage[main]/Foreman::Register/Foreman_host[foreman-centos9-64-puppet7.example.com]: Could not evaluate: Error making GET request to Foreman at https://centos9-64-puppet7.example.com/api/v2/hosts: Response: 502 Proxy Error: The webserver received an invalid response from the backend service. Was Foreman at centos9-64-puppet7.example.com unable to handle the request?
�[mNotice: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-centos9-64-puppet7.example.com]: Dependency Foreman_host[foreman-centos9-64-puppet7.example.com] has failures: true
Warning: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-centos9-64-puppet7.example.com]: Skipping because of failed dependencies
Info: Stage[main]: Unscheduling all events on Stage[main]
�[mNotice: Applied catalog in 2.77 seconds
Shared Example Group: "an idempotent resource" called from ./spec/acceptance/dynflow_spec.rb:46
|
Puppet / Puppet 7 - CentOS 9:
vendor/bundle/ruby/3.2.0/gems/voxpupuli-acceptance-2.4.0/lib/voxpupuli/acceptance/examples.rb#L8
Scenario: install foreman 1 worker 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 4 running:
puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_130028970.pp.OCyHKF
Last 10 lines of output were:
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)
�[mNotice: Compiled catalog for centos9-64-puppet7.example.com in environment production in 1.44 seconds
Info: Using environment 'production'
Info: Applying configuration version '1715691630'
Error: /Stage[main]/Foreman::Register/Foreman_host[foreman-centos9-64-puppet7.example.com]: Could not evaluate: Error making GET request to Foreman at https://centos9-64-puppet7.example.com/api/v2/hosts: Response: 502 Proxy Error: The webserver received an invalid response from the backend service. Was Foreman at centos9-64-puppet7.example.com unable to handle the request?
�[mNotice: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-centos9-64-puppet7.example.com]: Dependency Foreman_host[foreman-centos9-64-puppet7.example.com] has failures: true
Warning: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-centos9-64-puppet7.example.com]: Skipping because of failed dependencies
�[mNotice: Applied catalog in 0.60 seconds
Shared Example Group: "an idempotent resource" called from ./spec/acceptance/dynflow_spec.rb:46
|
Puppet / Puppet 7 - CentOS 9:
spec/support/acceptance/examples.rb#L23
Scenario: install foreman 1 worker behaves like the foreman application File "/run/foreman.sock" is expected to be socket
Failure/Error: it { should be_socket }
expected `File "/run/foreman.sock".socket?` to be truthy, got false
Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:56
|
Puppet / Puppet 7 - CentOS 9:
vendor/bundle/ruby/3.2.0/gems/voxpupuli-acceptance-2.4.0/lib/voxpupuli/acceptance/examples.rb#L4
Foreman with default options 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 6 running:
puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_130038308.pp.SSB0GH
Last 10 lines of output were:
�[mNotice: /Stage[main]/Foreman::Service/Foreman::Dynflow::Pool[worker]/Foreman::Dynflow::Worker[worker]/File[/etc/foreman/dynflow/worker.yml]/ensure: removed
�[mNotice: /Stage[main]/Foreman::Service/Podman::Quadlet[foreman.container]/Systemd::Daemon_reload[foreman.container]/Exec[systemd-foreman.container-systemctl-daemon-reload]: Triggered 'refresh' from 1 event
Info: Systemd::Daemon_reload[foreman.container]: Scheduling refresh of Service[foreman.service]
�[mNotice: /Stage[main]/Foreman::Service/Podman::Quadlet[foreman.container]/Service[foreman.service]/ensure: ensure changed 'stopped' to 'running'
Info: /Stage[main]/Foreman::Service/Podman::Quadlet[foreman.container]/Service[foreman.service]: Unscheduling refresh on Service[foreman.service]
Error: /Stage[main]/Foreman::Register/Foreman_host[foreman-centos9-64-puppet7.example.com]: Could not evaluate: Error making GET request to Foreman at https://centos9-64-puppet7.example.com/api/v2/hosts: Response: 502 Proxy Error: The webserver received an invalid response from the backend service. Was Foreman at centos9-64-puppet7.example.com unable to handle the request?
�[mNotice: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-centos9-64-puppet7.example.com]: Dependency Foreman_host[foreman-centos9-64-puppet7.example.com] has failures: true
Warning: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-centos9-64-puppet7.example.com]: Skipping because of failed dependencies
Info: Stage[main]: Unscheduling all events on Stage[main]
�[mNotice: Applied catalog in 50.69 seconds
Shared Example Group: "an idempotent resource" called from ./spec/acceptance/foreman_basic_spec.rb:7
|
Puppet / Puppet 7 - CentOS 9:
vendor/bundle/ruby/3.2.0/gems/voxpupuli-acceptance-2.4.0/lib/voxpupuli/acceptance/examples.rb#L8
Foreman with default options 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 4 running:
puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_130132466.pp.XBwVBq
Last 10 lines of output were:
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)
�[mNotice: Compiled catalog for centos9-64-puppet7.example.com in environment production in 1.47 seconds
Info: Using environment 'production'
Info: Applying configuration version '1715691694'
Error: /Stage[main]/Foreman::Register/Foreman_host[foreman-centos9-64-puppet7.example.com]: Could not evaluate: Error making GET request to Foreman at https://centos9-64-puppet7.example.com/api/v2/hosts: Response: 502 Proxy Error: The webserver received an invalid response from the backend service. Was Foreman at centos9-64-puppet7.example.com unable to handle the request?
�[mNotice: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-centos9-64-puppet7.example.com]: Dependency Foreman_host[foreman-centos9-64-puppet7.example.com] has failures: true
Warning: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-centos9-64-puppet7.example.com]: Skipping because of failed dependencies
�[mNotice: Applied catalog in 0.58 seconds
Shared Example Group: "an idempotent resource" called from ./spec/acceptance/foreman_basic_spec.rb:7
|
Puppet / Puppet 7 - CentOS 9:
spec/support/acceptance/examples.rb#L23
Foreman with default options behaves like the foreman application File "/run/foreman.sock" is expected to be socket
Failure/Error: it { should be_socket }
expected `File "/run/foreman.sock".socket?` to be truthy, got false
Shared Example Group: "the foreman application" called from ./spec/acceptance/foreman_basic_spec.rb:11
|
Puppet / Puppet 8 - CentOS 8:
vendor/bundle/ruby/3.2.0/gems/voxpupuli-acceptance-2.4.0/lib/voxpupuli/acceptance/examples.rb#L4
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 6 running:
puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_125643187.pp.gJG7yA
Last 10 lines of output were:
Info: /Stage[main]/Foreman::Service/Podman::Quadlet[foreman.container]/Service[foreman.service]: Unscheduling refresh on Service[foreman.service]
Info: Class[Foreman::Service]: Unscheduling all events on Class[Foreman::Service]
�[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@orchestrator] has failures: true
�[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@worker-1] has failures: true
�[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@worker-2] has failures: true
Warning: /Stage[main]/Foreman/Anchor[foreman::service]: Skipping because of failed dependencies
Warning: /Stage[main]/Foreman::Register/Foreman_host[foreman-centos8-64-puppet8.example.com]: Skipping because of failed dependencies
Warning: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-centos8-64-puppet8.example.com]: Skipping because of failed dependencies
Info: Stage[main]: Unscheduling all events on Stage[main]
�[mNotice: Applied catalog in 126.13 seconds
Shared Example Group: "an idempotent resource" called from ./spec/acceptance/dynflow_spec.rb:5
|
Puppet / Puppet 8 - CentOS 8:
vendor/bundle/ruby/3.2.0/gems/voxpupuli-acceptance-2.4.0/lib/voxpupuli/acceptance/examples.rb#L8
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 6 running:
puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_125853026.pp.gTcqv9
Last 10 lines of output were:
�[mNotice: /Stage[main]/Foreman::Service/Foreman::Dynflow::Worker[orchestrator]/Service[dynflow-sidekiq@orchestrator]/ensure: ensure changed 'stopped' to 'running'
Info: /Stage[main]/Foreman::Service/Foreman::Dynflow::Worker[orchestrator]/Service[dynflow-sidekiq@orchestrator]: Unscheduling refresh on Service[dynflow-sidekiq@orchestrator]
�[mNotice: /Stage[main]/Foreman::Service/Foreman::Dynflow::Pool[worker]/Foreman::Dynflow::Worker[worker-1]/Service[dynflow-sidekiq@worker-1]/ensure: ensure changed 'stopped' to 'running'
Info: /Stage[main]/Foreman::Service/Foreman::Dynflow::Pool[worker]/Foreman::Dynflow::Worker[worker-1]/Service[dynflow-sidekiq@worker-1]: Unscheduling refresh on Service[dynflow-sidekiq@worker-1]
�[mNotice: /Stage[main]/Foreman::Service/Foreman::Dynflow::Pool[worker]/Foreman::Dynflow::Worker[worker-2]/Service[dynflow-sidekiq@worker-2]/enable: enable changed 'false' to 'true'
Error: /Stage[main]/Foreman::Register/Foreman_host[foreman-centos8-64-puppet8.example.com]: Could not evaluate: Error making GET request to Foreman at https://centos8-64-puppet8.example.com/api/v2/hosts: Response: 502 Proxy Error: The webserver received an invalid response from the backend service. Was Foreman at centos8-64-puppet8.example.com unable to handle the request?
�[mNotice: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-centos8-64-puppet8.example.com]: Dependency Foreman_host[foreman-centos8-64-puppet8.example.com] has failures: true
Warning: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-centos8-64-puppet8.example.com]: Skipping because of failed dependencies
Info: Stage[main]: Unscheduling all events on Stage[main]
�[mNotice: Applied catalog in 19.88 seconds
Shared Example Group: "an idempotent resource" called from ./spec/acceptance/dynflow_spec.rb:5
|
Puppet / Puppet 8 - CentOS 8:
spec/support/acceptance/examples.rb#L23
Scenario: install foreman 2 workers behaves like the foreman application File "/run/foreman.sock" is expected to be socket
Failure/Error: it { should be_socket }
expected `File "/run/foreman.sock".socket?` to be truthy, got false
Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15
|
Puppet / Puppet 8 - CentOS 8:
spec/support/acceptance/examples.rb#L27
Scenario: install foreman 2 workers behaves like the foreman application Command "curl -s --cacert /etc/foreman-certs/certificate.pem https://centos8-64-puppet8.example.com -w '%{redirect_url}' -o /dev/null" stdout is expected to eq "https://centos8-64-puppet8.example.com/users/login"
Failure/Error: its(:stdout) { is_expected.to eq("https://#{host_inventory['fqdn']}#{params.fetch(:expected_login_url_path, '/users/login')}") }
expected: #<Encoding:UTF-8> "https://centos8-64-puppet8.example.com/users/login"
got: #<Encoding:US-ASCII> ""
(compared using ==)
Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15
|
Puppet / Puppet 8 - CentOS 8:
vendor/bundle/ruby/3.2.0/gems/voxpupuli-acceptance-2.4.0/lib/voxpupuli/acceptance/examples.rb#L4
Scenario: install foreman 1 worker 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 6 running:
puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_125919590.pp.ACkINv
Last 10 lines of output were:
�[mNotice: Compiled catalog for centos8-64-puppet8.example.com in environment production in 1.46 seconds
Info: Using environment 'production'
Info: Applying configuration version '1715691561'
�[mNotice: /Stage[main]/Foreman::Service/Foreman::Dynflow::Pool[worker]/Foreman::Dynflow::Worker[worker-2]/Service[dynflow-sidekiq@worker-2]/ensure: ensure changed 'running' to 'stopped'
�[mNotice: /Stage[main]/Foreman::Service/Foreman::Dynflow::Pool[worker]/Foreman::Dynflow::Worker[worker-2]/File[/etc/foreman/dynflow/worker-2.yml]/ensure: removed
Error: /Stage[main]/Foreman::Register/Foreman_host[foreman-centos8-64-puppet8.example.com]: Could not evaluate: Error making GET request to Foreman at https://centos8-64-puppet8.example.com/api/v2/hosts: Response: 502 Proxy Error: The webserver received an invalid response from the backend service. Was Foreman at centos8-64-puppet8.example.com unable to handle the request?
�[mNotice: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-centos8-64-puppet8.example.com]: Dependency Foreman_host[foreman-centos8-64-puppet8.example.com] has failures: true
Warning: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-centos8-64-puppet8.example.com]: Skipping because of failed dependencies
Info: Stage[main]: Unscheduling all events on Stage[main]
�[mNotice: Applied catalog in 2.25 seconds
Shared Example Group: "an idempotent resource" called from ./spec/acceptance/dynflow_spec.rb:46
|
Puppet / Puppet 8 - CentOS 8:
vendor/bundle/ruby/3.2.0/gems/voxpupuli-acceptance-2.4.0/lib/voxpupuli/acceptance/examples.rb#L8
Scenario: install foreman 1 worker 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 4 running:
puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_125925591.pp.rh1rQV
Last 10 lines of output were:
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)
�[mNotice: Compiled catalog for centos8-64-puppet8.example.com in environment production in 1.19 seconds
Info: Using environment 'production'
Info: Applying configuration version '1715691567'
Error: /Stage[main]/Foreman::Register/Foreman_host[foreman-centos8-64-puppet8.example.com]: Could not evaluate: Error making GET request to Foreman at https://centos8-64-puppet8.example.com/api/v2/hosts: Response: 502 Proxy Error: The webserver received an invalid response from the backend service. Was Foreman at centos8-64-puppet8.example.com unable to handle the request?
�[mNotice: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-centos8-64-puppet8.example.com]: Dependency Foreman_host[foreman-centos8-64-puppet8.example.com] has failures: true
Warning: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-centos8-64-puppet8.example.com]: Skipping because of failed dependencies
�[mNotice: Applied catalog in 0.52 seconds
Shared Example Group: "an idempotent resource" called from ./spec/acceptance/dynflow_spec.rb:46
|
Puppet / Puppet 8 - CentOS 8:
spec/support/acceptance/examples.rb#L23
Scenario: install foreman 1 worker behaves like the foreman application File "/run/foreman.sock" is expected to be socket
Failure/Error: it { should be_socket }
expected `File "/run/foreman.sock".socket?` to be truthy, got false
Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:56
|
Puppet / Puppet 8 - CentOS 8:
vendor/bundle/ruby/3.2.0/gems/voxpupuli-acceptance-2.4.0/lib/voxpupuli/acceptance/examples.rb#L4
Foreman with default options 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 6 running:
puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_125949155.pp.xiawMy
Last 10 lines of output were:
�[mNotice: /Stage[main]/Foreman::Service/Foreman::Dynflow::Pool[worker]/Foreman::Dynflow::Worker[worker]/File[/etc/foreman/dynflow/worker.yml]/ensure: removed
�[mNotice: /Stage[main]/Foreman::Service/Podman::Quadlet[foreman.container]/Systemd::Daemon_reload[foreman.container]/Exec[systemd-foreman.container-systemctl-daemon-reload]: Triggered 'refresh' from 1 event
Info: Systemd::Daemon_reload[foreman.container]: Scheduling refresh of Service[foreman.service]
�[mNotice: /Stage[main]/Foreman::Service/Podman::Quadlet[foreman.container]/Service[foreman.service]/ensure: ensure changed 'stopped' to 'running'
Info: /Stage[main]/Foreman::Service/Podman::Quadlet[foreman.container]/Service[foreman.service]: Unscheduling refresh on Service[foreman.service]
Error: /Stage[main]/Foreman::Register/Foreman_host[foreman-centos8-64-puppet8.example.com]: Could not evaluate: Error making GET request to Foreman at https://centos8-64-puppet8.example.com/api/v2/hosts: Response: 502 Proxy Error: The webserver received an invalid response from the backend service. Was Foreman at centos8-64-puppet8.example.com unable to handle the request?
�[mNotice: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-centos8-64-puppet8.example.com]: Dependency Foreman_host[foreman-centos8-64-puppet8.example.com] has failures: true
Warning: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-centos8-64-puppet8.example.com]: Skipping because of failed dependencies
Info: Stage[main]: Unscheduling all events on Stage[main]
�[mNotice: Applied catalog in 49.23 seconds
Shared Example Group: "an idempotent resource" called from ./spec/acceptance/foreman_basic_spec.rb:7
|
Puppet / Puppet 8 - CentOS 8:
vendor/bundle/ruby/3.2.0/gems/voxpupuli-acceptance-2.4.0/lib/voxpupuli/acceptance/examples.rb#L8
Foreman with default options 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 4 running:
puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_130041746.pp.y14yA1
Last 10 lines of output were:
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)
�[mNotice: Compiled catalog for centos8-64-puppet8.example.com in environment production in 1.43 seconds
Info: Using environment 'production'
Info: Applying configuration version '1715691643'
Error: /Stage[main]/Foreman::Register/Foreman_host[foreman-centos8-64-puppet8.example.com]: Could not evaluate: Error making GET request to Foreman at https://centos8-64-puppet8.example.com/api/v2/hosts: Response: 502 Proxy Error: The webserver received an invalid response from the backend service. Was Foreman at centos8-64-puppet8.example.com unable to handle the request?
�[mNotice: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-centos8-64-puppet8.example.com]: Dependency Foreman_host[foreman-centos8-64-puppet8.example.com] has failures: true
Warning: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-centos8-64-puppet8.example.com]: Skipping because of failed dependencies
�[mNotice: Applied catalog in 0.61 seconds
Shared Example Group: "an idempotent resource" called from ./spec/acceptance/foreman_basic_spec.rb:7
|
Puppet / Puppet 8 - CentOS 8:
spec/support/acceptance/examples.rb#L23
Foreman with default options behaves like the foreman application File "/run/foreman.sock" is expected to be socket
Failure/Error: it { should be_socket }
expected `File "/run/foreman.sock".socket?` to be truthy, got false
Shared Example Group: "the foreman application" called from ./spec/acceptance/foreman_basic_spec.rb:11
|
Puppet / Puppet 7 - CentOS 8:
vendor/bundle/ruby/3.2.0/gems/voxpupuli-acceptance-2.4.0/lib/voxpupuli/acceptance/examples.rb#L4
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 6 running:
puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_125654225.pp.MtmslV
Last 10 lines of output were:
Info: /Stage[main]/Foreman::Service/Podman::Quadlet[foreman.container]/Service[foreman.service]: Unscheduling refresh on Service[foreman.service]
Info: Class[Foreman::Service]: Unscheduling all events on Class[Foreman::Service]
�[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@orchestrator] has failures: true
�[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@worker-1] has failures: true
�[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@worker-2] has failures: true
Warning: /Stage[main]/Foreman/Anchor[foreman::service]: Skipping because of failed dependencies
Warning: /Stage[main]/Foreman::Register/Foreman_host[foreman-centos8-64-puppet7.example.com]: Skipping because of failed dependencies
Warning: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-centos8-64-puppet7.example.com]: Skipping because of failed dependencies
Info: Stage[main]: Unscheduling all events on Stage[main]
�[mNotice: Applied catalog in 131.39 seconds
Shared Example Group: "an idempotent resource" called from ./spec/acceptance/dynflow_spec.rb:5
|
Puppet / Puppet 7 - CentOS 8:
vendor/bundle/ruby/3.2.0/gems/voxpupuli-acceptance-2.4.0/lib/voxpupuli/acceptance/examples.rb#L8
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 6 running:
puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_125909445.pp.rUjfR1
Last 10 lines of output were:
Info: Applying configuration version '1715691552'
�[mNotice: /Stage[main]/Foreman::Service/Foreman::Dynflow::Worker[orchestrator]/Service[dynflow-sidekiq@orchestrator]/ensure: ensure changed 'stopped' to 'running'
Info: /Stage[main]/Foreman::Service/Foreman::Dynflow::Worker[orchestrator]/Service[dynflow-sidekiq@orchestrator]: Unscheduling refresh on Service[dynflow-sidekiq@orchestrator]
�[mNotice: /Stage[main]/Foreman::Service/Foreman::Dynflow::Pool[worker]/Foreman::Dynflow::Worker[worker-1]/Service[dynflow-sidekiq@worker-1]/enable: enable changed 'false' to 'true'
�[mNotice: /Stage[main]/Foreman::Service/Foreman::Dynflow::Pool[worker]/Foreman::Dynflow::Worker[worker-2]/Service[dynflow-sidekiq@worker-2]/enable: enable changed 'false' to 'true'
Error: /Stage[main]/Foreman::Register/Foreman_host[foreman-centos8-64-puppet7.example.com]: Could not evaluate: Error making GET request to Foreman at https://centos8-64-puppet7.example.com/api/v2/hosts: Response: 502 Proxy Error: The webserver received an invalid response from the backend service. Was Foreman at centos8-64-puppet7.example.com unable to handle the request?
�[mNotice: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-centos8-64-puppet7.example.com]: Dependency Foreman_host[foreman-centos8-64-puppet7.example.com] has failures: true
Info: Stage[main]: Unscheduling all events on Stage[main]
Warning: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-centos8-64-puppet7.example.com]: Skipping because of failed dependencies
�[mNotice: Applied catalog in 10.13 seconds
Shared Example Group: "an idempotent resource" called from ./spec/acceptance/dynflow_spec.rb:5
|
Puppet / Puppet 7 - CentOS 8:
spec/support/acceptance/examples.rb#L23
Scenario: install foreman 2 workers behaves like the foreman application File "/run/foreman.sock" is expected to be socket
Failure/Error: it { should be_socket }
expected `File "/run/foreman.sock".socket?` to be truthy, got false
Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15
|
Puppet / Puppet 7 - CentOS 8:
spec/support/acceptance/examples.rb#L27
Scenario: install foreman 2 workers behaves like the foreman application Command "curl -s --cacert /etc/foreman-certs/certificate.pem https://centos8-64-puppet7.example.com -w '%{redirect_url}' -o /dev/null" stdout is expected to eq "https://centos8-64-puppet7.example.com/users/login"
Failure/Error: its(:stdout) { is_expected.to eq("https://#{host_inventory['fqdn']}#{params.fetch(:expected_login_url_path, '/users/login')}") }
expected: #<Encoding:UTF-8> "https://centos8-64-puppet7.example.com/users/login"
got: #<Encoding:US-ASCII> ""
(compared using ==)
Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15
|
Puppet / Puppet 7 - CentOS 8:
vendor/bundle/ruby/3.2.0/gems/voxpupuli-acceptance-2.4.0/lib/voxpupuli/acceptance/examples.rb#L4
Scenario: install foreman 1 worker 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 6 running:
puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_125926532.pp.RDBTuq
Last 10 lines of output were:
�[mNotice: Compiled catalog for centos8-64-puppet7.example.com in environment production in 1.31 seconds
Info: Using environment 'production'
Info: Applying configuration version '1715691568'
�[mNotice: /Stage[main]/Foreman::Service/Foreman::Dynflow::Pool[worker]/Foreman::Dynflow::Worker[worker-2]/Service[dynflow-sidekiq@worker-2]/ensure: ensure changed 'running' to 'stopped'
�[mNotice: /Stage[main]/Foreman::Service/Foreman::Dynflow::Pool[worker]/Foreman::Dynflow::Worker[worker-2]/File[/etc/foreman/dynflow/worker-2.yml]/ensure: removed
Error: /Stage[main]/Foreman::Register/Foreman_host[foreman-centos8-64-puppet7.example.com]: Could not evaluate: Error making GET request to Foreman at https://centos8-64-puppet7.example.com/api/v2/hosts: Response: 502 Proxy Error: The webserver received an invalid response from the backend service. Was Foreman at centos8-64-puppet7.example.com unable to handle the request?
�[mNotice: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-centos8-64-puppet7.example.com]: Dependency Foreman_host[foreman-centos8-64-puppet7.example.com] has failures: true
Warning: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-centos8-64-puppet7.example.com]: Skipping because of failed dependencies
Info: Stage[main]: Unscheduling all events on Stage[main]
�[mNotice: Applied catalog in 2.26 seconds
Shared Example Group: "an idempotent resource" called from ./spec/acceptance/dynflow_spec.rb:46
|
Puppet / Puppet 7 - CentOS 8:
vendor/bundle/ruby/3.2.0/gems/voxpupuli-acceptance-2.4.0/lib/voxpupuli/acceptance/examples.rb#L8
Scenario: install foreman 1 worker 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 4 running:
puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_125932457.pp.6f9OT8
Last 10 lines of output were:
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)
�[mNotice: Compiled catalog for centos8-64-puppet7.example.com in environment production in 1.32 seconds
Info: Using environment 'production'
Info: Applying configuration version '1715691574'
Error: /Stage[main]/Foreman::Register/Foreman_host[foreman-centos8-64-puppet7.example.com]: Could not evaluate: Error making GET request to Foreman at https://centos8-64-puppet7.example.com/api/v2/hosts: Response: 502 Proxy Error: The webserver received an invalid response from the backend service. Was Foreman at centos8-64-puppet7.example.com unable to handle the request?
�[mNotice: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-centos8-64-puppet7.example.com]: Dependency Foreman_host[foreman-centos8-64-puppet7.example.com] has failures: true
Warning: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-centos8-64-puppet7.example.com]: Skipping because of failed dependencies
�[mNotice: Applied catalog in 0.58 seconds
Shared Example Group: "an idempotent resource" called from ./spec/acceptance/dynflow_spec.rb:46
|
Puppet / Puppet 7 - CentOS 8:
spec/support/acceptance/examples.rb#L23
Scenario: install foreman 1 worker behaves like the foreman application File "/run/foreman.sock" is expected to be socket
Failure/Error: it { should be_socket }
expected `File "/run/foreman.sock".socket?` to be truthy, got false
Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:56
|
Puppet / Puppet 7 - CentOS 8:
spec/support/acceptance/examples.rb#L27
Scenario: install foreman 1 worker behaves like the foreman application Command "curl -s --cacert /etc/foreman-certs/certificate.pem https://centos8-64-puppet7.example.com -w '%{redirect_url}' -o /dev/null" stdout is expected to eq "https://centos8-64-puppet7.example.com/users/login"
Failure/Error: its(:stdout) { is_expected.to eq("https://#{host_inventory['fqdn']}#{params.fetch(:expected_login_url_path, '/users/login')}") }
expected: #<Encoding:UTF-8> "https://centos8-64-puppet7.example.com/users/login"
got: #<Encoding:US-ASCII> ""
(compared using ==)
Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:56
|
Puppet / Puppet 7 - CentOS 8:
vendor/bundle/ruby/3.2.0/gems/voxpupuli-acceptance-2.4.0/lib/voxpupuli/acceptance/examples.rb#L4
Foreman with default options 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 6 running:
puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_125956901.pp.QrOXYk
Last 10 lines of output were:
�[mNotice: /Stage[main]/Foreman::Service/Foreman::Dynflow::Pool[worker]/Foreman::Dynflow::Worker[worker]/File[/etc/foreman/dynflow/worker.yml]/ensure: removed
�[mNotice: /Stage[main]/Foreman::Service/Podman::Quadlet[foreman.container]/Systemd::Daemon_reload[foreman.container]/Exec[systemd-foreman.container-systemctl-daemon-reload]: Triggered 'refresh' from 1 event
Info: Systemd::Daemon_reload[foreman.container]: Scheduling refresh of Service[foreman.service]
�[mNotice: /Stage[main]/Foreman::Service/Podman::Quadlet[foreman.container]/Service[foreman.service]/ensure: ensure changed 'stopped' to 'running'
Info: /Stage[main]/Foreman::Service/Podman::Quadlet[foreman.container]/Service[foreman.service]: Unscheduling refresh on Service[foreman.service]
Error: /Stage[main]/Foreman::Register/Foreman_host[foreman-centos8-64-puppet7.example.com]: Could not evaluate: Error making GET request to Foreman at https://centos8-64-puppet7.example.com/api/v2/hosts: Response: 502 Proxy Error: The webserver received an invalid response from the backend service. Was Foreman at centos8-64-puppet7.example.com unable to handle the request?
�[mNotice: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-centos8-64-puppet7.example.com]: Dependency Foreman_host[foreman-centos8-64-puppet7.example.com] has failures: true
Warning: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-centos8-64-puppet7.example.com]: Skipping because of failed dependencies
Info: Stage[main]: Unscheduling all events on Stage[main]
�[mNotice: Applied catalog in 77.08 seconds
Shared Example Group: "an idempotent resource" called from ./spec/acceptance/foreman_basic_spec.rb:7
|
Puppet / Puppet 7 - CentOS 8:
vendor/bundle/ruby/3.2.0/gems/voxpupuli-acceptance-2.4.0/lib/voxpupuli/acceptance/examples.rb#L8
Foreman with default options 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 4 running:
puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_130117334.pp.YVAnCY
Last 10 lines of output were:
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)
�[mNotice: Compiled catalog for centos8-64-puppet7.example.com in environment production in 1.38 seconds
Info: Using environment 'production'
Info: Applying configuration version '1715691679'
Error: /Stage[main]/Foreman::Register/Foreman_host[foreman-centos8-64-puppet7.example.com]: Could not evaluate: Error making GET request to Foreman at https://centos8-64-puppet7.example.com/api/v2/hosts: Response: 502 Proxy Error: The webserver received an invalid response from the backend service. Was Foreman at centos8-64-puppet7.example.com unable to handle the request?
�[mNotice: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-centos8-64-puppet7.example.com]: Dependency Foreman_host[foreman-centos8-64-puppet7.example.com] has failures: true
Warning: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-centos8-64-puppet7.example.com]: Skipping because of failed dependencies
�[mNotice: Applied catalog in 0.65 seconds
Shared Example Group: "an idempotent resource" called from ./spec/acceptance/foreman_basic_spec.rb:7
|
Puppet / Puppet 7 - Debian 12:
vendor/bundle/ruby/3.2.0/gems/voxpupuli-acceptance-2.4.0/lib/voxpupuli/acceptance/examples.rb#L4
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 6 running:
puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_125640144.pp.1YNwkD
Last 10 lines of output were:
Warning: /Stage[main]/Redis::Service/Service[redis-server]: Skipping because of failed dependencies
Warning: /Stage[main]/Foreman::Service/Foreman::Dynflow::Worker[orchestrator]/Service[dynflow-sidekiq@orchestrator]: Skipping because of failed dependencies
Warning: /Stage[main]/Foreman::Service/Foreman::Dynflow::Pool[worker]/Foreman::Dynflow::Worker[worker-1]/Service[dynflow-sidekiq@worker-1]: Skipping because of failed dependencies
Warning: /Stage[main]/Foreman::Service/Foreman::Dynflow::Pool[worker]/Foreman::Dynflow::Worker[worker-2]/Service[dynflow-sidekiq@worker-2]: Skipping because of failed dependencies
Warning: /Stage[main]/Foreman::Service/Foreman::Dynflow::Pool[worker]/Foreman::Dynflow::Worker[worker]/Service[dynflow-sidekiq@worker]: Skipping because of failed dependencies
Warning: /Stage[main]/Foreman::Service/Foreman::Dynflow::Pool[worker]/Foreman::Dynflow::Worker[worker]/File[/etc/foreman/dynflow/worker.yml]: Skipping because of failed dependencies
Warning: /Stage[main]/Foreman/Anchor[foreman::service]: Skipping because of failed dependencies
Warning: /Stage[main]/Foreman::Register/Foreman_host[foreman-debian12-64-puppet7.example.com]: Skipping because of failed dependencies
Warning: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-debian12-64-puppet7.example.com]: Skipping because of failed dependencies
�[mNotice: Applied catalog in 103.58 seconds
Shared Example Group: "an idempotent resource" called from ./spec/acceptance/dynflow_spec.rb:5
|
Puppet / Puppet 7 - Debian 12:
vendor/bundle/ruby/3.2.0/gems/voxpupuli-acceptance-2.4.0/lib/voxpupuli/acceptance/examples.rb#L8
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 6 running:
puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_125828613.pp.rXPvQX
Last 10 lines of output were:
Warning: /Stage[main]/Foreman::Service/Foreman::Dynflow::Worker[orchestrator]/Service[dynflow-sidekiq@orchestrator]: Skipping because of failed dependencies
Warning: /Stage[main]/Foreman::Service/Foreman::Dynflow::Pool[worker]/Foreman::Dynflow::Worker[worker-1]/Service[dynflow-sidekiq@worker-1]: Skipping because of failed dependencies
Warning: /Stage[main]/Foreman::Service/Foreman::Dynflow::Pool[worker]/Foreman::Dynflow::Worker[worker-2]/Service[dynflow-sidekiq@worker-2]: Skipping because of failed dependencies
Warning: /Stage[main]/Foreman::Service/Foreman::Dynflow::Pool[worker]/Foreman::Dynflow::Worker[worker]/Service[dynflow-sidekiq@worker]: Skipping because of failed dependencies
Warning: /Stage[main]/Foreman::Service/Foreman::Dynflow::Pool[worker]/Foreman::Dynflow::Worker[worker]/File[/etc/foreman/dynflow/worker.yml]: Skipping because of failed dependencies
Warning: /Stage[main]/Foreman/Anchor[foreman::service]: Skipping because of failed dependencies
Warning: /Stage[main]/Foreman::Register/Foreman_host[foreman-debian12-64-puppet7.example.com]: Skipping because of failed dependencies
Warning: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-debian12-64-puppet7.example.com]: Skipping because of failed dependencies
Info: Stage[main]: Unscheduling all events on Stage[main]
�[mNotice: Applied catalog in 11.36 seconds
Shared Example Group: "an idempotent resource" called from ./spec/acceptance/dynflow_spec.rb:5
|
Puppet / Puppet 7 - Debian 12:
spec/support/acceptance/examples.rb#L9
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
|
Puppet / Puppet 7 - Debian 12:
spec/support/acceptance/examples.rb#L10
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
|
Puppet / Puppet 7 - Debian 12:
spec/support/acceptance/examples.rb#L9
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
|
Puppet / Puppet 7 - Debian 12:
spec/support/acceptance/examples.rb#L10
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
|
Puppet / Puppet 7 - Debian 12:
spec/support/acceptance/examples.rb#L9
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
|
Puppet / Puppet 7 - Debian 12:
spec/support/acceptance/examples.rb#L10
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
|
Puppet / Puppet 7 - Debian 12:
spec/support/acceptance/examples.rb#L19
Scenario: install foreman 2 workers behaves like the foreman application Port "443" is expected to be listening
Failure/Error: it { is_expected.to be_listening }
expected Port "443" to be listening
Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15
|
Puppet / Puppet 7 - Debian 12:
spec/support/acceptance/examples.rb#L23
Scenario: install foreman 2 workers behaves like the foreman application File "/run/foreman.sock" is expected to be socket
Failure/Error: it { should be_socket }
expected `File "/run/foreman.sock".socket?` to be truthy, got false
Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15
|
Puppet / Puppet 8 - Debian 11:
vendor/bundle/ruby/3.2.0/gems/voxpupuli-acceptance-2.4.0/lib/voxpupuli/acceptance/examples.rb#L4
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 6 running:
puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_125641172.pp.mZKpxh
Last 10 lines of output were:
�[mNotice: /Stage[main]/Foreman::Service/Foreman::Dynflow::Pool[worker]/Foreman::Dynflow::Worker[worker]/File[/etc/foreman/dynflow/worker.yml]/ensure: removed
Info: Foreman::Dynflow::Pool[worker]: Unscheduling all events on Foreman::Dynflow::Pool[worker]
�[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@orchestrator] has failures: true
�[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@worker-1] has failures: true
�[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@worker-2] has failures: true
Warning: /Stage[main]/Foreman/Anchor[foreman::service]: Skipping because of failed dependencies
Warning: /Stage[main]/Foreman::Register/Foreman_host[foreman-debian11-64-puppet8.example.com]: Skipping because of failed dependencies
Warning: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-debian11-64-puppet8.example.com]: Skipping because of failed dependencies
Info: Stage[main]: Unscheduling all events on Stage[main]
�[mNotice: Applied catalog in 106.05 seconds
Shared Example Group: "an idempotent resource" called from ./spec/acceptance/dynflow_spec.rb:5
|
Puppet / Puppet 8 - Debian 11:
vendor/bundle/ruby/3.2.0/gems/voxpupuli-acceptance-2.4.0/lib/voxpupuli/acceptance/examples.rb#L8
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 4 running:
puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_125832123.pp.cIf59c
Last 10 lines of output were:
May 14 12:58:31 debian11-64-puppet8.example.com dynflow-sidekiq@worker-2[13055]: /usr/share/foreman/vendor/ruby/2.7.0/gems/apipie-rails-1.3.0/lib/apipie/validator.rb:330:in `new'
May 14 12:58:31 debian11-64-puppet8.example.com dynflow-sidekiq@worker-2[13055]: /usr/share/foreman/vendor/ruby/2.7.0/gems/apipie-rails-1.3.0/lib/apipie/validator.rb:330:in `build'
�[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@orchestrator] has failures: true
�[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@worker-1] has failures: true
�[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@worker-2] has failures: true
Warning: /Stage[main]/Foreman/Anchor[foreman::service]: Skipping because of failed dependencies
Warning: /Stage[main]/Foreman::Register/Foreman_host[foreman-debian11-64-puppet8.example.com]: Skipping because of failed dependencies
Warning: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-debian11-64-puppet8.example.com]: Skipping because of failed dependencies
�[mNotice: Applied catalog in 8.02 seconds
Shared Example Group: "an idempotent resource" called from ./spec/acceptance/dynflow_spec.rb:5
|
Puppet / Puppet 8 - Debian 11:
spec/support/acceptance/examples.rb#L9
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
|
Puppet / Puppet 8 - Debian 11:
spec/support/acceptance/examples.rb#L10
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
|
Puppet / Puppet 8 - Debian 11:
spec/support/acceptance/examples.rb#L9
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
|
Puppet / Puppet 8 - Debian 11:
spec/support/acceptance/examples.rb#L10
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
|
Puppet / Puppet 8 - Debian 11:
spec/support/acceptance/examples.rb#L10
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
|
Puppet / Puppet 8 - Debian 11:
spec/support/acceptance/examples.rb#L23
Scenario: install foreman 2 workers behaves like the foreman application File "/run/foreman.sock" is expected to be socket
Failure/Error: it { should be_socket }
expected `File "/run/foreman.sock".socket?` to be truthy, got false
Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15
|
Puppet / Puppet 8 - Debian 11:
spec/support/acceptance/examples.rb#L27
Scenario: install foreman 2 workers behaves like the foreman application Command "curl -s --cacert /etc/foreman-certs/certificate.pem https://debian11-64-puppet8.example.com -w '%{redirect_url}' -o /dev/null" stdout is expected to eq "https://debian11-64-puppet8.example.com/users/login"
Failure/Error: its(:stdout) { is_expected.to eq("https://#{host_inventory['fqdn']}#{params.fetch(:expected_login_url_path, '/users/login')}") }
expected: #<Encoding:UTF-8> "https://debian11-64-puppet8.example.com/users/login"
got: #<Encoding:US-ASCII> ""
(compared using ==)
Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15
|
Puppet / Puppet 8 - Debian 11:
spec/acceptance/dynflow_spec.rb#L31
Scenario: install foreman 2 workers 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
|
Puppet / Puppet 8 - Ubuntu 22.04:
vendor/bundle/ruby/3.2.0/gems/voxpupuli-acceptance-2.4.0/lib/voxpupuli/acceptance/examples.rb#L4
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 6 running:
puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_125647542.pp.BfPJoI
Last 10 lines of output were:
�[mNotice: /Stage[main]/Foreman::Service/Foreman::Dynflow::Pool[worker]/Foreman::Dynflow::Worker[worker]/File[/etc/foreman/dynflow/worker.yml]/ensure: removed
Info: Foreman::Dynflow::Pool[worker]: Unscheduling all events on Foreman::Dynflow::Pool[worker]
�[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@orchestrator] has failures: true
�[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@worker-1] has failures: true
�[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@worker-2] has failures: true
Warning: /Stage[main]/Foreman/Anchor[foreman::service]: Skipping because of failed dependencies
Warning: /Stage[main]/Foreman::Register/Foreman_host[foreman-ubuntu2204-64-puppet8.example.com]: Skipping because of failed dependencies
Warning: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-ubuntu2204-64-puppet8.example.com]: Skipping because of failed dependencies
Info: Stage[main]: Unscheduling all events on Stage[main]
�[mNotice: Applied catalog in 127.95 seconds
Shared Example Group: "an idempotent resource" called from ./spec/acceptance/dynflow_spec.rb:5
|
Puppet / Puppet 8 - Ubuntu 22.04:
vendor/bundle/ruby/3.2.0/gems/voxpupuli-acceptance-2.4.0/lib/voxpupuli/acceptance/examples.rb#L8
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 4 running:
puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_125900946.pp.SNUnr2
Last 10 lines of output were:
May 14 12:59:00 ubuntu2204-64-puppet8.example.com dynflow-sidekiq@worker-2[12039]: /usr/share/foreman/vendor/ruby/3.0.0/gems/apipie-rails-1.3.0/lib/apipie/validator.rb:330:in `new'
May 14 12:59:00 ubuntu2204-64-puppet8.example.com dynflow-sidekiq@worker-2[12039]: /usr/share/foreman/vendor/ruby/3.0.0/gems/apipie-rails-1.3.0/lib/apipie/validator.rb:330:in `build'
�[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@orchestrator] has failures: true
�[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@worker-1] has failures: true
�[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@worker-2] has failures: true
Warning: /Stage[main]/Foreman/Anchor[foreman::service]: Skipping because of failed dependencies
Warning: /Stage[main]/Foreman::Register/Foreman_host[foreman-ubuntu2204-64-puppet8.example.com]: Skipping because of failed dependencies
Warning: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-ubuntu2204-64-puppet8.example.com]: Skipping because of failed dependencies
�[mNotice: Applied catalog in 13.14 seconds
Shared Example Group: "an idempotent resource" called from ./spec/acceptance/dynflow_spec.rb:5
|
Puppet / Puppet 8 - Ubuntu 22.04:
spec/support/acceptance/examples.rb#L9
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
|
Puppet / Puppet 8 - Ubuntu 22.04:
spec/support/acceptance/examples.rb#L10
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
|
Puppet / Puppet 8 - Ubuntu 22.04:
spec/support/acceptance/examples.rb#L9
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
|
Puppet / Puppet 8 - Ubuntu 22.04:
spec/support/acceptance/examples.rb#L10
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
|
Puppet / Puppet 8 - Ubuntu 22.04:
spec/support/acceptance/examples.rb#L10
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
|
Puppet / Puppet 8 - Ubuntu 22.04:
spec/support/acceptance/examples.rb#L23
Scenario: install foreman 2 workers behaves like the foreman application File "/run/foreman.sock" is expected to be socket
Failure/Error: it { should be_socket }
expected `File "/run/foreman.sock".socket?` to be truthy, got false
Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15
|
Puppet / Puppet 8 - Ubuntu 22.04:
spec/support/acceptance/examples.rb#L27
Scenario: install foreman 2 workers behaves like the foreman application Command "curl -s --cacert /etc/foreman-certs/certificate.pem https://ubuntu2204-64-puppet8.example.com -w '%{redirect_url}' -o /dev/null" stdout is expected to eq "https://ubuntu2204-64-puppet8.example.com/users/login"
Failure/Error: its(:stdout) { is_expected.to eq("https://#{host_inventory['fqdn']}#{params.fetch(:expected_login_url_path, '/users/login')}") }
expected: #<Encoding:UTF-8> "https://ubuntu2204-64-puppet8.example.com/users/login"
got: #<Encoding:US-ASCII> ""
(compared using ==)
Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15
|
Puppet / Puppet 8 - Ubuntu 22.04:
spec/acceptance/dynflow_spec.rb#L31
Scenario: install foreman 2 workers 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
|
Puppet / Puppet 7 - Debian 11:
vendor/bundle/ruby/3.2.0/gems/voxpupuli-acceptance-2.4.0/lib/voxpupuli/acceptance/examples.rb#L4
Scenario: install foreman 2 workers behaves like an idempotent resource applies with no errors
Failure/Error: raise CommandFailure, "Host '#{self}' exited with #{result.exit_code} running:\n #{cmdline}\nLast #{@options[:trace_limit]} lines of output were:\n#{result.formatted_output(@options[:trace_limit])}"
Beaker::Host::CommandFailure:
Host 'debian11-64-puppet7.example.com' exited with 6 running:
puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_125640256.pp.xAHRRq
Last 10 lines of output were:
�[mNotice: /Stage[main]/Foreman::Service/Foreman::Dynflow::Pool[worker]/Foreman::Dynflow::Worker[worker]/File[/etc/foreman/dynflow/worker.yml]/ensure: removed
Info: Foreman::Dynflow::Pool[worker]: Unscheduling all events on Foreman::Dynflow::Pool[worker]
�[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@orchestrator] has failures: true
�[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@worker-1] has failures: true
�[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@worker-2] has failures: true
Warning: /Stage[main]/Foreman/Anchor[foreman::service]: Skipping because of failed dependencies
Warning: /Stage[main]/Foreman::Register/Foreman_host[foreman-debian11-64-puppet7.example.com]: Skipping because of failed dependencies
Warning: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-debian11-64-puppet7.example.com]: Skipping because of failed dependencies
Info: Stage[main]: Unscheduling all events on Stage[main]
�[mNotice: Applied catalog in 105.76 seconds
Shared Example Group: "an idempotent resource" called from ./spec/acceptance/dynflow_spec.rb:5
|
Puppet / Puppet 7 - Debian 11:
vendor/bundle/ruby/3.2.0/gems/voxpupuli-acceptance-2.4.0/lib/voxpupuli/acceptance/examples.rb#L8
Scenario: install foreman 2 workers behaves like an idempotent resource applies a second time without changes
Failure/Error: raise CommandFailure, "Host '#{self}' exited with #{result.exit_code} running:\n #{cmdline}\nLast #{@options[:trace_limit]} lines of output were:\n#{result.formatted_output(@options[:trace_limit])}"
Beaker::Host::CommandFailure:
Host 'debian11-64-puppet7.example.com' exited with 4 running:
puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_125830727.pp.GhNO9h
Last 10 lines of output were:
May 14 12:58:29 debian11-64-puppet7.example.com dynflow-sidekiq@worker-2[13061]: /usr/share/foreman/vendor/ruby/2.7.0/gems/apipie-rails-1.3.0/lib/apipie/validator.rb:330:in `new'
May 14 12:58:29 debian11-64-puppet7.example.com dynflow-sidekiq@worker-2[13061]: /usr/share/foreman/vendor/ruby/2.7.0/gems/apipie-rails-1.3.0/lib/apipie/validator.rb:330:in `build'
�[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@orchestrator] has failures: true
�[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@worker-1] has failures: true
�[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@worker-2] has failures: true
Warning: /Stage[main]/Foreman/Anchor[foreman::service]: Skipping because of failed dependencies
Warning: /Stage[main]/Foreman::Register/Foreman_host[foreman-debian11-64-puppet7.example.com]: Skipping because of failed dependencies
Warning: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-debian11-64-puppet7.example.com]: Skipping because of failed dependencies
�[mNotice: Applied catalog in 13.35 seconds
Shared Example Group: "an idempotent resource" called from ./spec/acceptance/dynflow_spec.rb:5
|
Puppet / Puppet 7 - Debian 11:
spec/support/acceptance/examples.rb#L9
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
|
Puppet / Puppet 7 - Debian 11:
spec/support/acceptance/examples.rb#L10
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
|
Puppet / Puppet 7 - Debian 11:
spec/support/acceptance/examples.rb#L9
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
|
Puppet / Puppet 7 - Debian 11:
spec/support/acceptance/examples.rb#L10
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
|
Puppet / Puppet 7 - Debian 11:
spec/support/acceptance/examples.rb#L10
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
|
Puppet / Puppet 7 - Debian 11:
spec/support/acceptance/examples.rb#L23
Scenario: install foreman 2 workers behaves like the foreman application File "/run/foreman.sock" is expected to be socket
Failure/Error: it { should be_socket }
expected `File "/run/foreman.sock".socket?` to be truthy, got false
Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15
|
Puppet / Puppet 7 - Debian 11:
spec/support/acceptance/examples.rb#L27
Scenario: install foreman 2 workers behaves like the foreman application Command "curl -s --cacert /etc/foreman-certs/certificate.pem https://debian11-64-puppet7.example.com -w '%{redirect_url}' -o /dev/null" stdout is expected to eq "https://debian11-64-puppet7.example.com/users/login"
Failure/Error: its(:stdout) { is_expected.to eq("https://#{host_inventory['fqdn']}#{params.fetch(:expected_login_url_path, '/users/login')}") }
expected: #<Encoding:UTF-8> "https://debian11-64-puppet7.example.com/users/login"
got: #<Encoding:US-ASCII> ""
(compared using ==)
Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15
|
Puppet / Puppet 7 - Debian 11:
spec/acceptance/dynflow_spec.rb#L31
Scenario: install foreman 2 workers 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
|
Puppet / Puppet 8 - Debian 12:
vendor/bundle/ruby/3.2.0/gems/voxpupuli-acceptance-2.4.0/lib/voxpupuli/acceptance/examples.rb#L4
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 6 running:
puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_130203518.pp.YFgpun
Last 10 lines of output were:
Warning: /Stage[main]/Redis::Service/Service[redis-server]: Skipping because of failed dependencies
Warning: /Stage[main]/Foreman::Service/Foreman::Dynflow::Worker[orchestrator]/Service[dynflow-sidekiq@orchestrator]: Skipping because of failed dependencies
Warning: /Stage[main]/Foreman::Service/Foreman::Dynflow::Pool[worker]/Foreman::Dynflow::Worker[worker-1]/Service[dynflow-sidekiq@worker-1]: Skipping because of failed dependencies
Warning: /Stage[main]/Foreman::Service/Foreman::Dynflow::Pool[worker]/Foreman::Dynflow::Worker[worker-2]/Service[dynflow-sidekiq@worker-2]: Skipping because of failed dependencies
Warning: /Stage[main]/Foreman::Service/Foreman::Dynflow::Pool[worker]/Foreman::Dynflow::Worker[worker]/Service[dynflow-sidekiq@worker]: Skipping because of failed dependencies
Warning: /Stage[main]/Foreman::Service/Foreman::Dynflow::Pool[worker]/Foreman::Dynflow::Worker[worker]/File[/etc/foreman/dynflow/worker.yml]: Skipping because of failed dependencies
Warning: /Stage[main]/Foreman/Anchor[foreman::service]: Skipping because of failed dependencies
Warning: /Stage[main]/Foreman::Register/Foreman_host[foreman-debian12-64-puppet8.example.com]: Skipping because of failed dependencies
Warning: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-debian12-64-puppet8.example.com]: Skipping because of failed dependencies
�[mNotice: Applied catalog in 187.11 seconds
Shared Example Group: "an idempotent resource" called from ./spec/acceptance/dynflow_spec.rb:5
|
Puppet / Puppet 8 - Debian 12:
vendor/bundle/ruby/3.2.0/gems/voxpupuli-acceptance-2.4.0/lib/voxpupuli/acceptance/examples.rb#L8
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 6 running:
puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_130515418.pp.DrniAI
Last 10 lines of output were:
Warning: /Stage[main]/Foreman::Service/Foreman::Dynflow::Worker[orchestrator]/Service[dynflow-sidekiq@orchestrator]: Skipping because of failed dependencies
Warning: /Stage[main]/Foreman::Service/Foreman::Dynflow::Pool[worker]/Foreman::Dynflow::Worker[worker-1]/Service[dynflow-sidekiq@worker-1]: Skipping because of failed dependencies
Warning: /Stage[main]/Foreman::Service/Foreman::Dynflow::Pool[worker]/Foreman::Dynflow::Worker[worker-2]/Service[dynflow-sidekiq@worker-2]: Skipping because of failed dependencies
Warning: /Stage[main]/Foreman::Service/Foreman::Dynflow::Pool[worker]/Foreman::Dynflow::Worker[worker]/Service[dynflow-sidekiq@worker]: Skipping because of failed dependencies
Warning: /Stage[main]/Foreman::Service/Foreman::Dynflow::Pool[worker]/Foreman::Dynflow::Worker[worker]/File[/etc/foreman/dynflow/worker.yml]: Skipping because of failed dependencies
Warning: /Stage[main]/Foreman/Anchor[foreman::service]: Skipping because of failed dependencies
Warning: /Stage[main]/Foreman::Register/Foreman_host[foreman-debian12-64-puppet8.example.com]: Skipping because of failed dependencies
Warning: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-debian12-64-puppet8.example.com]: Skipping because of failed dependencies
Info: Stage[main]: Unscheduling all events on Stage[main]
�[mNotice: Applied catalog in 10.59 seconds
Shared Example Group: "an idempotent resource" called from ./spec/acceptance/dynflow_spec.rb:5
|
Puppet / Puppet 8 - Debian 12:
spec/support/acceptance/examples.rb#L9
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
|
Puppet / Puppet 8 - Debian 12:
spec/support/acceptance/examples.rb#L10
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
|
Puppet / Puppet 8 - Debian 12:
spec/support/acceptance/examples.rb#L9
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
|
Puppet / Puppet 8 - Debian 12:
spec/support/acceptance/examples.rb#L10
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
|
Puppet / Puppet 8 - Debian 12:
spec/support/acceptance/examples.rb#L9
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
|
Puppet / Puppet 8 - Debian 12:
spec/support/acceptance/examples.rb#L10
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
|
Puppet / Puppet 8 - Debian 12:
spec/support/acceptance/examples.rb#L19
Scenario: install foreman 2 workers behaves like the foreman application Port "443" is expected to be listening
Failure/Error: it { is_expected.to be_listening }
expected Port "443" to be listening
Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15
|
Puppet / Puppet 8 - Debian 12:
spec/support/acceptance/examples.rb#L23
Scenario: install foreman 2 workers behaves like the foreman application File "/run/foreman.sock" is expected to be socket
Failure/Error: it { should be_socket }
expected `File "/run/foreman.sock".socket?` to be truthy, got false
Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15
|
Puppet / Puppet 7 - Ubuntu 22.04:
vendor/bundle/ruby/3.2.0/gems/voxpupuli-acceptance-2.4.0/lib/voxpupuli/acceptance/examples.rb#L4
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 6 running:
puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_125756754.pp.BuBIlW
Last 10 lines of output were:
�[mNotice: /Stage[main]/Foreman::Service/Foreman::Dynflow::Pool[worker]/Foreman::Dynflow::Worker[worker]/File[/etc/foreman/dynflow/worker.yml]/ensure: removed
Info: Foreman::Dynflow::Pool[worker]: Unscheduling all events on Foreman::Dynflow::Pool[worker]
�[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@orchestrator] has failures: true
�[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@worker-1] has failures: true
�[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@worker-2] has failures: true
Warning: /Stage[main]/Foreman/Anchor[foreman::service]: Skipping because of failed dependencies
Warning: /Stage[main]/Foreman::Register/Foreman_host[foreman-ubuntu2204-64-puppet7.example.com]: Skipping because of failed dependencies
Warning: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-ubuntu2204-64-puppet7.example.com]: Skipping because of failed dependencies
Info: Stage[main]: Unscheduling all events on Stage[main]
�[mNotice: Applied catalog in 245.24 seconds
Shared Example Group: "an idempotent resource" called from ./spec/acceptance/dynflow_spec.rb:5
|
Puppet / Puppet 7 - Ubuntu 22.04:
vendor/bundle/ruby/3.2.0/gems/voxpupuli-acceptance-2.4.0/lib/voxpupuli/acceptance/examples.rb#L8
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 4 running:
puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_130207636.pp.LxCEjo
Last 10 lines of output were:
May 14 13:02:06 ubuntu2204-64-puppet7.example.com dynflow-sidekiq@worker-2[12036]: /usr/share/foreman/vendor/ruby/3.0.0/gems/apipie-rails-1.3.0/lib/apipie/validator.rb:330:in `new'
May 14 13:02:06 ubuntu2204-64-puppet7.example.com dynflow-sidekiq@worker-2[12036]: /usr/share/foreman/vendor/ruby/3.0.0/gems/apipie-rails-1.3.0/lib/apipie/validator.rb:330:in `build'
�[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@orchestrator] has failures: true
�[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@worker-1] has failures: true
�[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@worker-2] has failures: true
Warning: /Stage[main]/Foreman/Anchor[foreman::service]: Skipping because of failed dependencies
Warning: /Stage[main]/Foreman::Register/Foreman_host[foreman-ubuntu2204-64-puppet7.example.com]: Skipping because of failed dependencies
Warning: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-ubuntu2204-64-puppet7.example.com]: Skipping because of failed dependencies
�[mNotice: Applied catalog in 14.87 seconds
Shared Example Group: "an idempotent resource" called from ./spec/acceptance/dynflow_spec.rb:5
|
Puppet / Puppet 7 - Ubuntu 22.04:
spec/support/acceptance/examples.rb#L9
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
|
Puppet / Puppet 7 - Ubuntu 22.04:
spec/support/acceptance/examples.rb#L10
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
|
Puppet / Puppet 7 - Ubuntu 22.04:
spec/support/acceptance/examples.rb#L9
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
|
Puppet / Puppet 7 - Ubuntu 22.04:
spec/support/acceptance/examples.rb#L10
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
|
Puppet / Puppet 7 - Ubuntu 22.04:
spec/support/acceptance/examples.rb#L10
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
|
Puppet / Puppet 7 - Ubuntu 22.04:
spec/support/acceptance/examples.rb#L23
Scenario: install foreman 2 workers behaves like the foreman application File "/run/foreman.sock" is expected to be socket
Failure/Error: it { should be_socket }
expected `File "/run/foreman.sock".socket?` to be truthy, got false
Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15
|
Puppet / Puppet 7 - Ubuntu 22.04:
spec/support/acceptance/examples.rb#L27
Scenario: install foreman 2 workers behaves like the foreman application Command "curl -s --cacert /etc/foreman-certs/certificate.pem https://ubuntu2204-64-puppet7.example.com -w '%{redirect_url}' -o /dev/null" stdout is expected to eq "https://ubuntu2204-64-puppet7.example.com/users/login"
Failure/Error: its(:stdout) { is_expected.to eq("https://#{host_inventory['fqdn']}#{params.fetch(:expected_login_url_path, '/users/login')}") }
expected: #<Encoding:UTF-8> "https://ubuntu2204-64-puppet7.example.com/users/login"
got: #<Encoding:US-ASCII> ""
(compared using ==)
Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15
|
Puppet / Puppet 7 - Ubuntu 22.04:
spec/acceptance/dynflow_spec.rb#L31
Scenario: install foreman 2 workers 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
|
Puppet / Puppet 8 - Ubuntu 20.04:
vendor/bundle/ruby/3.2.0/gems/voxpupuli-acceptance-2.4.0/lib/voxpupuli/acceptance/examples.rb#L4
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 6 running:
puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_125654851.pp.ytqh8z
Last 10 lines of output were:
�[mNotice: /Stage[main]/Foreman::Service/Foreman::Dynflow::Pool[worker]/Foreman::Dynflow::Worker[worker]/File[/etc/foreman/dynflow/worker.yml]/ensure: removed
Info: Foreman::Dynflow::Pool[worker]: Unscheduling all events on Foreman::Dynflow::Pool[worker]
�[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@orchestrator] has failures: true
�[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@worker-1] has failures: true
�[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@worker-2] has failures: true
Warning: /Stage[main]/Foreman/Anchor[foreman::service]: Skipping because of failed dependencies
Warning: /Stage[main]/Foreman::Register/Foreman_host[foreman-ubuntu2004-64-puppet8.example.com]: Skipping because of failed dependencies
Warning: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-ubuntu2004-64-puppet8.example.com]: Skipping because of failed dependencies
Info: Stage[main]: Unscheduling all events on Stage[main]
�[mNotice: Applied catalog in 141.24 seconds
Shared Example Group: "an idempotent resource" called from ./spec/acceptance/dynflow_spec.rb:5
|
Puppet / Puppet 8 - Ubuntu 20.04:
vendor/bundle/ruby/3.2.0/gems/voxpupuli-acceptance-2.4.0/lib/voxpupuli/acceptance/examples.rb#L8
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 4 running:
puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_125922288.pp.FeeRvv
Last 10 lines of output were:
May 14 12:59:21 ubuntu2004-64-puppet8.example.com dynflow-sidekiq@worker-2[11182]: /usr/share/foreman/vendor/ruby/2.7.0/gems/apipie-rails-1.3.0/lib/apipie/validator.rb:337:in `instance_exec'
May 14 12:59:21 ubuntu2004-64-puppet8.example.com dynflow-sidekiq@worker-2[11182]: /usr/share/foreman/vendor/ruby/2.7.0/gems/apipie-rails-1.3.0/lib/apipie/validator.rb:337:in `initialize'
�[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@orchestrator] has failures: true
�[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@worker-1] has failures: true
�[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@worker-2] has failures: true
Warning: /Stage[main]/Foreman/Anchor[foreman::service]: Skipping because of failed dependencies
Warning: /Stage[main]/Foreman::Register/Foreman_host[foreman-ubuntu2004-64-puppet8.example.com]: Skipping because of failed dependencies
Warning: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-ubuntu2004-64-puppet8.example.com]: Skipping because of failed dependencies
�[mNotice: Applied catalog in 13.97 seconds
Shared Example Group: "an idempotent resource" called from ./spec/acceptance/dynflow_spec.rb:5
|
Puppet / Puppet 8 - Ubuntu 20.04:
spec/support/acceptance/examples.rb#L9
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
|
Puppet / Puppet 8 - Ubuntu 20.04:
spec/support/acceptance/examples.rb#L10
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
|
Puppet / Puppet 8 - Ubuntu 20.04:
spec/support/acceptance/examples.rb#L9
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
|
Puppet / Puppet 8 - Ubuntu 20.04:
spec/support/acceptance/examples.rb#L10
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
|
Puppet / Puppet 8 - Ubuntu 20.04:
spec/support/acceptance/examples.rb#L10
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
|
Puppet / Puppet 8 - Ubuntu 20.04:
spec/support/acceptance/examples.rb#L23
Scenario: install foreman 2 workers behaves like the foreman application File "/run/foreman.sock" is expected to be socket
Failure/Error: it { should be_socket }
expected `File "/run/foreman.sock".socket?` to be truthy, got false
Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15
|
Puppet / Puppet 8 - Ubuntu 20.04:
spec/support/acceptance/examples.rb#L27
Scenario: install foreman 2 workers behaves like the foreman application Command "curl -s --cacert /etc/foreman-certs/certificate.pem https://ubuntu2004-64-puppet8.example.com -w '%{redirect_url}' -o /dev/null" stdout is expected to eq "https://ubuntu2004-64-puppet8.example.com/users/login"
Failure/Error: its(:stdout) { is_expected.to eq("https://#{host_inventory['fqdn']}#{params.fetch(:expected_login_url_path, '/users/login')}") }
expected: #<Encoding:UTF-8> "https://ubuntu2004-64-puppet8.example.com/users/login"
got: #<Encoding:US-ASCII> ""
(compared using ==)
Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15
|
Puppet / Puppet 8 - Ubuntu 20.04:
spec/acceptance/dynflow_spec.rb#L31
Scenario: install foreman 2 workers 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
|
Puppet / Puppet 7 - Ubuntu 20.04:
vendor/bundle/ruby/3.2.0/gems/voxpupuli-acceptance-2.4.0/lib/voxpupuli/acceptance/examples.rb#L4
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 6 running:
puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_125736911.pp.HzLZ5O
Last 10 lines of output were:
�[mNotice: /Stage[main]/Foreman::Service/Foreman::Dynflow::Pool[worker]/Foreman::Dynflow::Worker[worker]/File[/etc/foreman/dynflow/worker.yml]/ensure: removed
Info: Foreman::Dynflow::Pool[worker]: Unscheduling all events on Foreman::Dynflow::Pool[worker]
�[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@orchestrator] has failures: true
�[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@worker-1] has failures: true
�[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@worker-2] has failures: true
Warning: /Stage[main]/Foreman/Anchor[foreman::service]: Skipping because of failed dependencies
Warning: /Stage[main]/Foreman::Register/Foreman_host[foreman-ubuntu2004-64-puppet7.example.com]: Skipping because of failed dependencies
Warning: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-ubuntu2004-64-puppet7.example.com]: Skipping because of failed dependencies
Info: Stage[main]: Unscheduling all events on Stage[main]
�[mNotice: Applied catalog in 223.85 seconds
Shared Example Group: "an idempotent resource" called from ./spec/acceptance/dynflow_spec.rb:5
|
Puppet / Puppet 7 - Ubuntu 20.04:
vendor/bundle/ruby/3.2.0/gems/voxpupuli-acceptance-2.4.0/lib/voxpupuli/acceptance/examples.rb#L8
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 4 running:
puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_130127209.pp.n28pk9
Last 10 lines of output were:
May 14 13:01:26 ubuntu2004-64-puppet7.example.com dynflow-sidekiq@worker-2[11181]: /usr/share/foreman/vendor/ruby/2.7.0/gems/apipie-rails-1.3.0/lib/apipie/validator.rb:337:in `instance_exec'
May 14 13:01:26 ubuntu2004-64-puppet7.example.com dynflow-sidekiq@worker-2[11181]: /usr/share/foreman/vendor/ruby/2.7.0/gems/apipie-rails-1.3.0/lib/apipie/validator.rb:337:in `initialize'
�[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@orchestrator] has failures: true
�[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@worker-1] has failures: true
�[mNotice: /Stage[main]/Foreman/Anchor[foreman::service]: Dependency Service[dynflow-sidekiq@worker-2] has failures: true
Warning: /Stage[main]/Foreman/Anchor[foreman::service]: Skipping because of failed dependencies
Warning: /Stage[main]/Foreman::Register/Foreman_host[foreman-ubuntu2004-64-puppet7.example.com]: Skipping because of failed dependencies
Warning: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-ubuntu2004-64-puppet7.example.com]: Skipping because of failed dependencies
�[mNotice: Applied catalog in 20.83 seconds
Shared Example Group: "an idempotent resource" called from ./spec/acceptance/dynflow_spec.rb:5
|
Puppet / Puppet 7 - Ubuntu 20.04:
spec/support/acceptance/examples.rb#L9
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
|
Puppet / Puppet 7 - Ubuntu 20.04:
spec/support/acceptance/examples.rb#L10
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
|
Puppet / Puppet 7 - Ubuntu 20.04:
spec/support/acceptance/examples.rb#L9
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
|
Puppet / Puppet 7 - Ubuntu 20.04:
spec/support/acceptance/examples.rb#L10
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
|
Puppet / Puppet 7 - Ubuntu 20.04:
spec/support/acceptance/examples.rb#L10
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
|
Puppet / Puppet 7 - Ubuntu 20.04:
spec/support/acceptance/examples.rb#L23
Scenario: install foreman 2 workers behaves like the foreman application File "/run/foreman.sock" is expected to be socket
Failure/Error: it { should be_socket }
expected `File "/run/foreman.sock".socket?` to be truthy, got false
Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15
|
Puppet / Puppet 7 - Ubuntu 20.04:
spec/support/acceptance/examples.rb#L27
Scenario: install foreman 2 workers behaves like the foreman application Command "curl -s --cacert /etc/foreman-certs/certificate.pem https://ubuntu2004-64-puppet7.example.com -w '%{redirect_url}' -o /dev/null" stdout is expected to eq "https://ubuntu2004-64-puppet7.example.com/users/login"
Failure/Error: its(:stdout) { is_expected.to eq("https://#{host_inventory['fqdn']}#{params.fetch(:expected_login_url_path, '/users/login')}") }
expected: #<Encoding:UTF-8> "https://ubuntu2004-64-puppet7.example.com/users/login"
got: #<Encoding:US-ASCII> ""
(compared using ==)
Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15
|
Puppet / Puppet 7 - Ubuntu 20.04:
spec/acceptance/dynflow_spec.rb#L31
Scenario: install foreman 2 workers 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
|