Skip to content

Add Debian hiera data to match package defaults #236

Add Debian hiera data to match package defaults

Add Debian hiera data to match package defaults #236

Triggered via pull request June 7, 2024 04:58
Status Failure
Total duration 5m 7s
Artifacts

ci.yml

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

Annotations

20 errors and 2 warnings
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_045959480.NV1IJc.pp 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 Fri 2024-06-07 04:59:44 UTC, end at Fri 2024-06-07 05:00:03 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.70 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_050005114.HNpuKj.pp Last 10 lines of output were: journalctl log for chronyd: -- Logs begin at Fri 2024-06-07 04:59:44 UTC, end at Fri 2024-06-07 05:00:07 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 Fri 2024-06-07 04:59:44 UTC, end at Fri 2024-06-07 05:00:07 UTC. -- -- No entries -- �[mNotice: Applied catalog in 0.64 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_045958958.ORGhh2.pp 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 Fri 2024-06-07 04:59:43 UTC, end at Fri 2024-06-07 05:00:03 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.67 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_050004495.jlzJXe.pp Last 10 lines of output were: journalctl log for chronyd: -- Logs begin at Fri 2024-06-07 04:59:43 UTC, end at Fri 2024-06-07 05:00: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 Fri 2024-06-07 04:59:43 UTC, end at Fri 2024-06-07 05:00:06 UTC. -- -- No entries -- �[mNotice: Applied catalog in 0.63 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_050031853.wIDCEI.pp 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 Fri 2024-06-07 05:00:11 UTC, end at Fri 2024-06-07 05:00: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.68 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_050039479.6Bp7Lx.pp Last 10 lines of output were: journalctl log for chronyd: -- Logs begin at Fri 2024-06-07 05:00:11 UTC, end at Fri 2024-06-07 05:00:42 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 Fri 2024-06-07 05:00:11 UTC, end at Fri 2024-06-07 05:00:42 UTC. -- -- No entries -- �[mNotice: Applied catalog in 1.12 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 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_050306752.Mo6fDZ.pp 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 Fri 2024-06-07 05:02:50 UTC, end at Fri 2024-06-07 05:03: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.61 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_050314202.SugPuT.pp Last 10 lines of output were: journalctl log for chronyd: -- Logs begin at Fri 2024-06-07 05:02:50 UTC, end at Fri 2024-06-07 05:03: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 Fri 2024-06-07 05:02:50 UTC, end at Fri 2024-06-07 05:03:16 UTC. -- -- No entries -- �[mNotice: Applied catalog in 1.03 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 / Static validations: metadata.json#L1
Skipping EOL operating system CentOS 8
Puppet / Static validations: metadata.json#L1
Skipping EOL operating system Ubuntu 18.04