Skip to content

Add Debian hiera data to match package defaults #188

Add Debian hiera data to match package defaults

Add Debian hiera data to match package defaults #188

Triggered via pull request September 3, 2023 00:58
Status Failure
Total duration 4m 5s
Artifacts

ci.yml

on: pull_request
Puppet  /  Static validations
38s
Puppet / Static validations
Matrix: Puppet / acceptance
Matrix: Puppet / unit
Puppet  /  Test suite
0s
Puppet / Test suite
Fit to window
Zoom out
Zoom in

Annotations

30 errors
Puppet / 7 - Ubuntu 18.04: spec/acceptance/class_spec.rb#L6
chrony class: works idempotently with no errors Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'ubuntu1804-64-puppet7.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_010049900.pp.OqG3rB Last 10 lines of output were: Error: /Stage[main]/Chrony::Service/Service[chronyd]/ensure: change from 'stopped' to 'running' failed: Systemd start for chronyd failed! journalctl log for chronyd: -- Logs begin at Sun 2023-09-03 01:00:29 UTC, end at Sun 2023-09-03 01:00:57 UTC. -- -- No entries -- �[mNotice: /Stage[main]/Chrony::Service/Service[chronyd]: Triggered 'refresh' from 1 event Info: Class[Chrony::Service]: Unscheduling all events on Class[Chrony::Service] Info: Class[Chrony]: Unscheduling all events on Class[Chrony] Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 5.93 seconds
Puppet / 7 - Ubuntu 18.04: spec/acceptance/class_spec.rb#L33
chrony class: Service "chrony" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "chrony" to be running
Puppet / 7 - Ubuntu 18.04: spec/acceptance/class_spec.rb#L43
chrony class: with chrony-wait service enabled works idempotently with no errors Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'ubuntu1804-64-puppet7.example.com' exited with 4 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_010058516.pp.FctJpx Last 10 lines of output were: journalctl log for chronyd: -- Logs begin at Sun 2023-09-03 01:00:29 UTC, end at Sun 2023-09-03 01:01:02 UTC. -- -- No entries -- Error: /Stage[main]/Chrony::Service/Service[chronyd]/ensure: change from 'stopped' to 'running' failed: Systemd start for chronyd failed! journalctl log for chronyd: -- Logs begin at Sun 2023-09-03 01:00:29 UTC, end at Sun 2023-09-03 01:01:02 UTC. -- -- No entries -- �[mNotice: Applied catalog in 1.54 seconds
Puppet / 7 - Ubuntu 18.04: spec/acceptance/class_spec.rb#L69
chrony class: with chrony-wait service enabled Service "chrony" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "chrony" to be running
Puppet / 7 - Ubuntu 18.04
Process completed with exit code 1.
Puppet / 7 - Debian 10: spec/acceptance/class_spec.rb#L6
chrony class: works idempotently with no errors Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'debian10-64-puppet7.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_010110103.pp.luPWVu Last 10 lines of output were: -- No entries -- Info: Class[Chrony]: Unscheduling all events on Class[Chrony] Info: Stage[main]: Unscheduling all events on Stage[main] Error: /Stage[main]/Chrony::Service/Service[chronyd]: Systemd restart for chronyd failed! journalctl log for chronyd: -- Logs begin at Sun 2023-09-03 01:00:48 UTC, end at Sun 2023-09-03 01:01:17 UTC. -- -- No entries -- �[mNotice: Applied catalog in 4.64 seconds
Puppet / 7 - Debian 10: spec/acceptance/class_spec.rb#L33
chrony class: Service "chrony" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "chrony" to be running
Puppet / 7 - Debian 10: spec/acceptance/class_spec.rb#L43
chrony class: with chrony-wait service enabled works idempotently with no errors Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'debian10-64-puppet7.example.com' exited with 4 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_010117779.pp.kiyUs1 Last 10 lines of output were: journalctl log for chronyd: -- Logs begin at Sun 2023-09-03 01:00:48 UTC, end at Sun 2023-09-03 01:01:21 UTC. -- -- No entries -- Error: /Stage[main]/Chrony::Service/Service[chronyd]/ensure: change from 'stopped' to 'running' failed: Systemd start for chronyd failed! journalctl log for chronyd: -- Logs begin at Sun 2023-09-03 01:00:48 UTC, end at Sun 2023-09-03 01:01:21 UTC. -- -- No entries -- �[mNotice: Applied catalog in 1.13 seconds
Puppet / 7 - Debian 10: spec/acceptance/class_spec.rb#L69
chrony class: with chrony-wait service enabled Service "chrony" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "chrony" to be running
Puppet / 7 - Debian 10
Process completed with exit code 1.
Puppet / 8 - Ubuntu 18.04: spec/acceptance/class_spec.rb#L6
chrony class: works idempotently with no errors Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'ubuntu1804-64-puppet8.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_010123284.pp.vPyqpX Last 10 lines of output were: Error: /Stage[main]/Chrony::Service/Service[chronyd]/ensure: change from 'stopped' to 'running' failed: Systemd start for chronyd failed! journalctl log for chronyd: -- Logs begin at Sun 2023-09-03 01:00:52 UTC, end at Sun 2023-09-03 01:01:34 UTC. -- -- No entries -- �[mNotice: /Stage[main]/Chrony::Service/Service[chronyd]: Triggered 'refresh' from 1 event Info: Class[Chrony::Service]: Unscheduling all events on Class[Chrony::Service] Info: Class[Chrony]: Unscheduling all events on Class[Chrony] Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 7.18 seconds
Puppet / 8 - Ubuntu 18.04: spec/acceptance/class_spec.rb#L33
chrony class: Service "chrony" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "chrony" to be running
Puppet / 8 - Ubuntu 18.04: spec/acceptance/class_spec.rb#L43
chrony class: with chrony-wait service enabled works idempotently with no errors Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'ubuntu1804-64-puppet8.example.com' exited with 4 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_010135330.pp.kFK1Cd Last 10 lines of output were: journalctl log for chronyd: -- Logs begin at Sun 2023-09-03 01:00:52 UTC, end at Sun 2023-09-03 01:01:41 UTC. -- -- No entries -- Error: /Stage[main]/Chrony::Service/Service[chronyd]/ensure: change from 'stopped' to 'running' failed: Systemd start for chronyd failed! journalctl log for chronyd: -- Logs begin at Sun 2023-09-03 01:00:52 UTC, end at Sun 2023-09-03 01:01:41 UTC. -- -- No entries -- �[mNotice: Applied catalog in 1.70 seconds
Puppet / 8 - Ubuntu 18.04: spec/acceptance/class_spec.rb#L69
chrony class: with chrony-wait service enabled Service "chrony" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "chrony" to be running
Puppet / 8 - Ubuntu 18.04
Process completed with exit code 1.
Puppet / 8 - Ubuntu 20.04: spec/acceptance/class_spec.rb#L6
chrony class: works idempotently with no errors Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'ubuntu2004-64-puppet8.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_010131477.pp.wtZSIM Last 10 lines of output were: Error: /Stage[main]/Chrony::Service/Service[chronyd]/ensure: change from 'stopped' to 'running' failed: Systemd start for chronyd failed! journalctl log for chronyd: -- Logs begin at Sun 2023-09-03 01:01:04 UTC, end at Sun 2023-09-03 01:01:43 UTC. -- -- No entries -- �[mNotice: /Stage[main]/Chrony::Service/Service[chronyd]: Triggered 'refresh' from 1 event Info: Class[Chrony::Service]: Unscheduling all events on Class[Chrony::Service] Info: Class[Chrony]: Unscheduling all events on Class[Chrony] Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 7.05 seconds
Puppet / 8 - Ubuntu 20.04: spec/acceptance/class_spec.rb#L33
chrony class: Service "chrony" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "chrony" to be running
Puppet / 8 - Ubuntu 20.04: spec/acceptance/class_spec.rb#L43
chrony class: with chrony-wait service enabled works idempotently with no errors Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'ubuntu2004-64-puppet8.example.com' exited with 4 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_010143827.pp.57AWFq Last 10 lines of output were: journalctl log for chronyd: -- Logs begin at Sun 2023-09-03 01:01:04 UTC, end at Sun 2023-09-03 01:01:49 UTC. -- -- No entries -- Error: /Stage[main]/Chrony::Service/Service[chronyd]/ensure: change from 'stopped' to 'running' failed: Systemd start for chronyd failed! journalctl log for chronyd: -- Logs begin at Sun 2023-09-03 01:01:04 UTC, end at Sun 2023-09-03 01:01:49 UTC. -- -- No entries -- �[mNotice: Applied catalog in 1.61 seconds
Puppet / 8 - Ubuntu 20.04: spec/acceptance/class_spec.rb#L69
chrony class: with chrony-wait service enabled Service "chrony" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "chrony" to be running
Puppet / 8 - Ubuntu 20.04
Process completed with exit code 1.
Puppet / 8 - Debian 10: spec/acceptance/class_spec.rb#L6
chrony class: works idempotently with no errors Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'debian10-64-puppet8.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_010136470.pp.iHewU1 Last 10 lines of output were: -- No entries -- Error: /Stage[main]/Chrony::Service/Service[chronyd]: Systemd restart for chronyd failed! journalctl log for chronyd: -- Logs begin at Sun 2023-09-03 01:01:10 UTC, end at Sun 2023-09-03 01:01:46 UTC. -- -- No entries -- Info: Class[Chrony]: Unscheduling all events on Class[Chrony] Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 5.09 seconds
Puppet / 8 - Debian 10: spec/acceptance/class_spec.rb#L33
chrony class: Service "chrony" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "chrony" to be running
Puppet / 8 - Debian 10: spec/acceptance/class_spec.rb#L43
chrony class: with chrony-wait service enabled works idempotently with no errors Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'debian10-64-puppet8.example.com' exited with 4 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_010147218.pp.qIIsBA Last 10 lines of output were: journalctl log for chronyd: -- Logs begin at Sun 2023-09-03 01:01:10 UTC, end at Sun 2023-09-03 01:01:53 UTC. -- -- No entries -- Error: /Stage[main]/Chrony::Service/Service[chronyd]/ensure: change from 'stopped' to 'running' failed: Systemd start for chronyd failed! journalctl log for chronyd: -- Logs begin at Sun 2023-09-03 01:01:10 UTC, end at Sun 2023-09-03 01:01:53 UTC. -- -- No entries -- �[mNotice: Applied catalog in 1.22 seconds
Puppet / 8 - Debian 10: spec/acceptance/class_spec.rb#L69
chrony class: with chrony-wait service enabled Service "chrony" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "chrony" to be running
Puppet / 8 - Debian 10
Process completed with exit code 1.
Puppet / 7 - Ubuntu 20.04: spec/acceptance/class_spec.rb#L6
chrony class: works idempotently with no errors Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'ubuntu2004-64-puppet7.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_010144206.pp.MdY0YJ Last 10 lines of output were: Error: /Stage[main]/Chrony::Service/Service[chronyd]/ensure: change from 'stopped' to 'running' failed: Systemd start for chronyd failed! journalctl log for chronyd: -- Logs begin at Sun 2023-09-03 01:01:15 UTC, end at Sun 2023-09-03 01:01:53 UTC. -- -- No entries -- �[mNotice: /Stage[main]/Chrony::Service/Service[chronyd]: Triggered 'refresh' from 1 event Info: Class[Chrony::Service]: Unscheduling all events on Class[Chrony::Service] Info: Class[Chrony]: Unscheduling all events on Class[Chrony] Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 7.28 seconds
Puppet / 7 - Ubuntu 20.04: spec/acceptance/class_spec.rb#L33
chrony class: Service "chrony" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "chrony" to be running
Puppet / 7 - Ubuntu 20.04: spec/acceptance/class_spec.rb#L43
chrony class: with chrony-wait service enabled works idempotently with no errors Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'ubuntu2004-64-puppet7.example.com' exited with 4 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_010154506.pp.Q185Nv Last 10 lines of output were: journalctl log for chronyd: -- Logs begin at Sun 2023-09-03 01:01:15 UTC, end at Sun 2023-09-03 01:01:58 UTC. -- -- No entries -- Error: /Stage[main]/Chrony::Service/Service[chronyd]/ensure: change from 'stopped' to 'running' failed: Systemd start for chronyd failed! journalctl log for chronyd: -- Logs begin at Sun 2023-09-03 01:01:15 UTC, end at Sun 2023-09-03 01:01:58 UTC. -- -- No entries -- �[mNotice: Applied catalog in 1.58 seconds
Puppet / 7 - Ubuntu 20.04: spec/acceptance/class_spec.rb#L69
chrony class: with chrony-wait service enabled Service "chrony" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "chrony" to be running
Puppet / 7 - Ubuntu 20.04
Process completed with exit code 1.