Skip to content

Fixes #38085 - Cap the number of Puma workers at 100 #1697

Fixes #38085 - Cap the number of Puma workers at 100

Fixes #38085 - Cap the number of Puma workers at 100 #1697

Triggered via push December 13, 2024 15:32
Status Failure
Total duration 27m 32s
Artifacts

ci.yml

on: push
Puppet  /  Static validations
33s
Puppet / Static validations
Matrix: Puppet / acceptance
Matrix: Puppet / unit
Puppet  /  Test suite
2s
Puppet / Test suite
Fit to window
Zoom out
Zoom in

Annotations

23 errors and 1 warning
Puppet / Puppet 7 - AlmaLinux 8
Process completed with exit code 1.
Puppet / Puppet 8 - AlmaLinux 8
Process completed with exit code 1.
Puppet / Puppet 7 - Ubuntu 20.04: vendor/bundle/ruby/3.2.0/gems/voxpupuli-acceptance-3.2.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_153446899.yOpC8S.pp Last 10 lines of output were: Warning: /Stage[main]/Foreman::Service/Foreman::Dynflow::Pool[worker]/Foreman::Dynflow::Worker[worker-2]/Service[dynflow-sidekiq@worker-2]: Skipping because of failed dependencies Info: /Stage[main]/Foreman::Service/Foreman::Dynflow::Pool[worker]/Foreman::Dynflow::Worker[worker-2]/Service[dynflow-sidekiq@worker-2]: Unscheduling all events on Service[dynflow-sidekiq@worker-2] 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-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] Error: Could not find a suitable provider for foreman_config_entry �[mNotice: Applied catalog in 37.44 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-3.2.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_153530694.40IzzD.pp Last 10 lines of output were: 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]/File[/etc/foreman/dynflow/worker-2.yml]: 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-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 Error: Could not find a suitable provider for foreman_config_entry �[mNotice: Applied catalog in 5.64 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#L10
Scenario: install foreman 2 workers behaves like the foreman application Service "apache2" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "apache2" to be running Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15
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#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 - 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#L15
Scenario: install foreman 2 workers behaves like the foreman application Port "80" is expected to be listening Failure/Error: it { is_expected.to be_listening } expected Port "80" to be listening Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15
Puppet / Puppet 8 - Ubuntu 20.04: vendor/bundle/ruby/3.2.0/gems/voxpupuli-acceptance-3.2.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_153508942.vuHmvR.pp Last 10 lines of output were: Warning: /Stage[main]/Foreman::Service/Foreman::Dynflow::Pool[worker]/Foreman::Dynflow::Worker[worker-2]/Service[dynflow-sidekiq@worker-2]: Skipping because of failed dependencies Info: /Stage[main]/Foreman::Service/Foreman::Dynflow::Pool[worker]/Foreman::Dynflow::Worker[worker-2]/Service[dynflow-sidekiq@worker-2]: Unscheduling all events on Service[dynflow-sidekiq@worker-2] 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-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] Error: Could not find a suitable provider for foreman_config_entry �[mNotice: Applied catalog in 38.80 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-3.2.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_153554328.esjokU.pp Last 10 lines of output were: 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]/File[/etc/foreman/dynflow/worker-2.yml]: 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-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 Error: Could not find a suitable provider for foreman_config_entry �[mNotice: Applied catalog in 5.86 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#L10
Scenario: install foreman 2 workers behaves like the foreman application Service "apache2" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "apache2" to be running Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15
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#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 - 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#L15
Scenario: install foreman 2 workers behaves like the foreman application Port "80" is expected to be listening Failure/Error: it { is_expected.to be_listening } expected Port "80" to be listening Shared Example Group: "the foreman application" called from ./spec/acceptance/dynflow_spec.rb:15
Puppet / Test suite
Process completed with exit code 1.
Puppet / Static validations: metadata.json#L1
Skipping EOL operating system CentOS 8