Skip to content

Add Debian hiera data to match package defaults #233

Add Debian hiera data to match package defaults

Add Debian hiera data to match package defaults #233

Triggered via pull request May 13, 2024 20:06
Status Failure
Total duration 2m 51s
Artifacts

ci.yml

on: pull_request
Puppet  /  Static validations
24s
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 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_200756645.pp.oZfzA2 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 Mon 2024-05-13 20:07:41 UTC, end at Mon 2024-05-13 20:08:00 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.56 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_200802083.pp.Yj55Uf Last 10 lines of output were: journalctl log for chronyd: -- Logs begin at Mon 2024-05-13 20:07:41 UTC, end at Mon 2024-05-13 20:08:04 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 Mon 2024-05-13 20:07:41 UTC, end at Mon 2024-05-13 20:08:04 UTC. -- -- No entries -- �[mNotice: Applied catalog in 0.62 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 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_200758237.pp.qcSNNv 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 Mon 2024-05-13 20:07:42 UTC, end at Mon 2024-05-13 20:08:02 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.06 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_200804259.pp.pmLNRQ Last 10 lines of output were: journalctl log for chronyd: -- Logs begin at Mon 2024-05-13 20:07:42 UTC, end at Mon 2024-05-13 20:08:06 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 Mon 2024-05-13 20:07:42 UTC, end at Mon 2024-05-13 20:08:06 UTC. -- -- No entries -- �[mNotice: Applied catalog in 0.80 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 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_200806522.pp.1r9IzS 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 Mon 2024-05-13 20:07:49 UTC, end at Mon 2024-05-13 20:08:12 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.36 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_200813877.pp.z1vPkl Last 10 lines of output were: journalctl log for chronyd: -- Logs begin at Mon 2024-05-13 20:07:49 UTC, end at Mon 2024-05-13 20:08:16 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 Mon 2024-05-13 20:07:49 UTC, end at Mon 2024-05-13 20:08:16 UTC. -- -- No entries -- �[mNotice: Applied catalog in 1.16 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.
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_200823074.pp.W9owJ5 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 Mon 2024-05-13 20:08:05 UTC, end at Mon 2024-05-13 20:08:31 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.09 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_200833211.pp.pBCf8t Last 10 lines of output were: journalctl log for chronyd: -- Logs begin at Mon 2024-05-13 20:08:05 UTC, end at Mon 2024-05-13 20:08:36 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 Mon 2024-05-13 20:08:05 UTC, end at Mon 2024-05-13 20:08:36 UTC. -- -- No entries -- �[mNotice: Applied catalog in 1.17 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 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_200846986.pp.FDp66U 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 Mon 2024-05-13 20:08:30 UTC, end at Mon 2024-05-13 20:08: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 5.11 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_200854879.pp.VHk3TI Last 10 lines of output were: journalctl log for chronyd: -- Logs begin at Mon 2024-05-13 20:08:30 UTC, end at Mon 2024-05-13 20:08:57 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 Mon 2024-05-13 20:08:30 UTC, end at Mon 2024-05-13 20:08:57 UTC. -- -- No entries -- �[mNotice: Applied catalog in 1.15 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 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_200854033.pp.t8uTE7 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 Mon 2024-05-13 20:08:36 UTC, end at Mon 2024-05-13 20:09:00 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.03 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_200901967.pp.yzrPyM Last 10 lines of output were: journalctl log for chronyd: -- Logs begin at Mon 2024-05-13 20:08:36 UTC, end at Mon 2024-05-13 20:09:04 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 Mon 2024-05-13 20:08:36 UTC, end at Mon 2024-05-13 20:09:04 UTC. -- -- No entries -- �[mNotice: Applied catalog in 1.08 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.