Skip to content

Add Debian 11 and Ubuntu 22.04; drop EoL Ubuntu 18.04 and CentOS 8 #189

Add Debian 11 and Ubuntu 22.04; drop EoL Ubuntu 18.04 and CentOS 8

Add Debian 11 and Ubuntu 22.04; drop EoL Ubuntu 18.04 and CentOS 8 #189

Triggered via pull request September 3, 2023 22:50
@kenyonkenyon
synchronize #134
debian11
Status Failure
Total duration 4m 47s
Artifacts

ci.yml

on: pull_request
Puppet  /  Static validations
1m 6s
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
Puppet / 7 - Ubuntu 22.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 'ubuntu2204-64-puppet7.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_225250754.pp.OguXOl 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: -- 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.10 seconds
Puppet / 7 - Ubuntu 22.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 22.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 'ubuntu2204-64-puppet7.example.com' exited with 4 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_225258542.pp.OaZJZz Last 10 lines of output were: Info: Applying configuration version '1693781580' Error: Systemd start for chronyd failed! journalctl log for chronyd: -- 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: -- No entries -- �[mNotice: Applied catalog in 1.23 seconds
Puppet / 7 - Ubuntu 22.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 22.04
Process completed with exit code 1.
Puppet / 8 - Debian 11: 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 'debian11-64-puppet8.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_225258481.pp.CZA2Ae 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: -- Journal begins at Sun 2023-09-03 22:52:37 UTC, ends at Sun 2023-09-03 22:53:05 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 3.72 seconds
Puppet / 8 - Debian 11: 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 11: 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 'debian11-64-puppet8.example.com' exited with 4 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_225306654.pp.BWp1Hg Last 10 lines of output were: journalctl log for chronyd: -- Journal begins at Sun 2023-09-03 22:52:37 UTC, ends at Sun 2023-09-03 22:53:11 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: -- Journal begins at Sun 2023-09-03 22:52:37 UTC, ends at Sun 2023-09-03 22:53:11 UTC. -- -- No entries -- �[mNotice: Applied catalog in 0.81 seconds
Puppet / 8 - Debian 11: 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 11
Process completed with exit code 1.
Puppet / 7 - Debian 11: 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 'debian11-64-puppet7.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_225319337.pp.VzXRv1 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: -- Journal begins at Sun 2023-09-03 22:52:57 UTC, ends at Sun 2023-09-03 22:53:26 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.70 seconds
Puppet / 7 - Debian 11: 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 11: 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 'debian11-64-puppet7.example.com' exited with 4 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_225327235.pp.8mJ5XJ Last 10 lines of output were: journalctl log for chronyd: -- Journal begins at Sun 2023-09-03 22:52:57 UTC, ends at Sun 2023-09-03 22:53:30 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: -- Journal begins at Sun 2023-09-03 22:52:57 UTC, ends at Sun 2023-09-03 22:53:30 UTC. -- -- No entries -- �[mNotice: Applied catalog in 1.05 seconds
Puppet / 7 - Debian 11: 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 11
Process completed with exit code 1.
Puppet / 8 - Ubuntu 22.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 'ubuntu2204-64-puppet8.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_225312493.pp.Jb5bBI 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: -- 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.06 seconds
Puppet / 8 - Ubuntu 22.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 22.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 'ubuntu2204-64-puppet8.example.com' exited with 4 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_225324937.pp.0nPIYp Last 10 lines of output were: Info: Applying configuration version '1693781609' Error: Systemd start for chronyd failed! journalctl log for chronyd: -- 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: -- No entries -- �[mNotice: Applied catalog in 1.45 seconds
Puppet / 8 - Ubuntu 22.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 22.04
Process completed with exit code 1.