Foreman in a Container in a Container 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_123817165.pp.yhSm4R Last 10 lines of output were: 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]/Service[dynflow-sidekiq@worker]: Triggered 'refresh' from 1 event �[mNotice: /Stage[main]/Foreman::Service/Foreman::Dynflow::Pool[worker]/Foreman::Dynflow::Worker[worker]/File[/etc/foreman/dynflow/worker.yml]/ensure: removed Error: /Stage[main]/Foreman::Register/Foreman_host[foreman-ubuntu2204-64-puppet7.example.com]: Could not evaluate: Error making GET request to Foreman at https://ubuntu2204-64-puppet7.example.com/api/v2/hosts: Response: 503 Service Unavailable: The webserver was unable to reach the backend service. Is Foreman running at ubuntu2204-64-puppet7.example.com? �[mNotice: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-ubuntu2204-64-puppet7.example.com]: Dependency Foreman_host[foreman-ubuntu2204-64-puppet7.example.com] has failures: true 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 77.44 seconds Shared Example Group: "an idempotent resource" called from ./spec/acceptance/foreman_basic_spec.rb:63

Foreman in a Container in a Container 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 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_123940691.pp.4ccG7F Last 10 lines of output were: �[mNotice: /Stage[main]/Foreman::Service/Service[foreman.socket]/ensure: ensure changed 'running' to 'stopped' �[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] Error: /Stage[main]/Foreman::Register/Foreman_host[foreman-ubuntu2204-64-puppet7.example.com]: Could not evaluate: Error making GET request to Foreman at https://ubuntu2204-64-puppet7.example.com/api/v2/hosts: Response: 503 Service Unavailable: The webserver was unable to reach the backend service. Is Foreman running at ubuntu2204-64-puppet7.example.com? �[mNotice: /Stage[main]/Foreman::Register/Foreman_instance_host[foreman-ubuntu2204-64-puppet7.example.com]: Dependency Foreman_host[foreman-ubuntu2204-64-puppet7.example.com] has failures: true 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 24.24 seconds Shared Example Group: "an idempotent resource" called from ./spec/acceptance/foreman_basic_spec.rb:63

Foreman in a Container in a Container 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/foreman_basic_spec.rb:75

Foreman in a Container in a Container 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/foreman_basic_spec.rb:75