run foreman in a container #1606
Annotations
10 errors
Run tests:
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_102444926.pp.KaMkWC
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 108.82 seconds
Shared Example Group: "an idempotent resource" called from ./spec/acceptance/dynflow_spec.rb:5
|
Run tests:
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_102638454.pp.6lKEpD
Last 10 lines of output were:
May 14 10:26:37 debian11-64-puppet8.example.com dynflow-sidekiq@worker-2[13075]: /usr/share/foreman/vendor/ruby/2.7.0/gems/apipie-rails-1.3.0/lib/apipie/validator.rb:330:in `new'
May 14 10:26:37 debian11-64-puppet8.example.com dynflow-sidekiq@worker-2[13075]: /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 16.91 seconds
Shared Example Group: "an idempotent resource" called from ./spec/acceptance/dynflow_spec.rb:5
|
Run tests:
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
|
Run tests:
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
|
Run tests:
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
|
Run tests:
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
|
Run tests:
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
|
Run tests:
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
|
Run tests:
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
|
Run tests:
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
|
Loading