Skip to content

Add Debian hiera data to match package defaults #201

Add Debian hiera data to match package defaults

Add Debian hiera data to match package defaults #201

Triggered via pull request January 31, 2024 00:33
Status Failure
Total duration 3m 14s
Artifacts

ci.yml

on: pull_request
Puppet  /  Static validations
28s
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 / 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_003614276.pp.X6rH6i 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 Wed 2024-01-31 00:35:37 UTC, end at Wed 2024-01-31 00:36:18 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 3.11 seconds
Puppet / 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 / 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_003620347.pp.O19cjT Last 10 lines of output were: journalctl log for chronyd: -- Logs begin at Wed 2024-01-31 00:35:37 UTC, end at Wed 2024-01-31 00:36:22 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 Wed 2024-01-31 00:35:37 UTC, end at Wed 2024-01-31 00:36:22 UTC. -- -- No entries -- �[mNotice: Applied catalog in 0.74 seconds
Puppet / 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 / Puppet 7 - Debian 10
Process completed with exit code 1.
Puppet / 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_003613892.pp.3gvwyL 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 Wed 2024-01-31 00:35:40 UTC, end at Wed 2024-01-31 00:36:20 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 4.74 seconds
Puppet / 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 / 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_003621494.pp.ijwiER Last 10 lines of output were: journalctl log for chronyd: -- Logs begin at Wed 2024-01-31 00:35:40 UTC, end at Wed 2024-01-31 00:36:24 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 Wed 2024-01-31 00:35:40 UTC, end at Wed 2024-01-31 00:36:24 UTC. -- -- No entries -- �[mNotice: Applied catalog in 1.12 seconds
Puppet / 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 / Puppet 7 - Ubuntu 18.04
Process completed with exit code 1.
Puppet / 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_003617168.pp.CmyMNT 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 Wed 2024-01-31 00:35:38 UTC, end at Wed 2024-01-31 00:36:23 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 2.96 seconds
Puppet / 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 / 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_003624434.pp.QYLnDr Last 10 lines of output were: journalctl log for chronyd: -- Logs begin at Wed 2024-01-31 00:35:38 UTC, end at Wed 2024-01-31 00:36:28 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 Wed 2024-01-31 00:35:38 UTC, end at Wed 2024-01-31 00:36:28 UTC. -- -- No entries -- �[mNotice: Applied catalog in 0.70 seconds
Puppet / 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 / Puppet 8 - Debian 10
Process completed with exit code 1.
Puppet / 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_003617287.pp.HImp1c 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 Wed 2024-01-31 00:35:39 UTC, end at Wed 2024-01-31 00:36:25 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.67 seconds
Puppet / 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 / 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_003627125.pp.dcG9Mq Last 10 lines of output were: journalctl log for chronyd: -- Logs begin at Wed 2024-01-31 00:35:39 UTC, end at Wed 2024-01-31 00:36:31 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 Wed 2024-01-31 00:35:39 UTC, end at Wed 2024-01-31 00:36:31 UTC. -- -- No entries -- �[mNotice: Applied catalog in 1.12 seconds
Puppet / 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 / Puppet 8 - Ubuntu 18.04
Process completed with exit code 1.
Puppet / 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_003627659.pp.M7d4su 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 Wed 2024-01-31 00:35:52 UTC, end at Wed 2024-01-31 00:36:35 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.88 seconds
Puppet / 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 / 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_003636573.pp.vu2wEN Last 10 lines of output were: journalctl log for chronyd: -- Logs begin at Wed 2024-01-31 00:35:52 UTC, end at Wed 2024-01-31 00:36:39 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 Wed 2024-01-31 00:35:52 UTC, end at Wed 2024-01-31 00:36:39 UTC. -- -- No entries -- �[mNotice: Applied catalog in 1.15 seconds
Puppet / 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 / Puppet 7 - Ubuntu 20.04
Process completed with exit code 1.
Puppet / 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_003631369.pp.IVDYYW 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 Wed 2024-01-31 00:35:46 UTC, end at Wed 2024-01-31 00:36:38 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 4.51 seconds
Puppet / 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 / 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_003639910.pp.FCnDQj Last 10 lines of output were: journalctl log for chronyd: -- Logs begin at Wed 2024-01-31 00:35:46 UTC, end at Wed 2024-01-31 00:36:43 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 Wed 2024-01-31 00:35:46 UTC, end at Wed 2024-01-31 00:36:43 UTC. -- -- No entries -- �[mNotice: Applied catalog in 0.99 seconds
Puppet / 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 / Puppet 8 - Ubuntu 20.04
Process completed with exit code 1.