Skip to content

modulesync 9.3.0

modulesync 9.3.0 #249

Triggered via pull request September 17, 2024 23:41
@jhoblittjhoblitt
synchronize #200
modulesync
Status Failure
Total duration 3m 3s
Artifacts

ci.yml

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

Annotations

11 errors and 2 warnings
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_234328314.16gXAS.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 Tue 2024-09-17 23:43:10 UTC, end at Tue 2024-09-17 23:43: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.37 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_234336731.slOueo.pp Last 10 lines of output were: journalctl log for chronyd: -- Logs begin at Tue 2024-09-17 23:43:10 UTC, end at Tue 2024-09-17 23:43: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 Tue 2024-09-17 23:43:10 UTC, end at Tue 2024-09-17 23:43:39 UTC. -- -- No entries -- �[mNotice: Applied catalog in 1.10 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_234330199.avFcab.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 Tue 2024-09-17 23:43:12 UTC, end at Tue 2024-09-17 23:43:37 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 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_234338502.F3ZnEr.pp Last 10 lines of output were: journalctl log for chronyd: -- Logs begin at Tue 2024-09-17 23:43:12 UTC, end at Tue 2024-09-17 23:43: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 Tue 2024-09-17 23:43:12 UTC, end at Tue 2024-09-17 23:43:41 UTC. -- -- No entries -- �[mNotice: Applied catalog in 1.13 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 / Test suite
Process completed with exit code 1.
Puppet / Static validations: metadata.json#L1
Skipping EOL operating system Debian 10
Puppet / Static validations: metadata.json#L1
Skipping EOL operating system Ubuntu 18.04