Add Debian 11 and Ubuntu 22.04; drop EoL Ubuntu 18.04 and CentOS 8 #187
ci.yml
on: pull_request
Puppet
/
Static validations
38s
Matrix: Puppet / acceptance
Matrix: Puppet / unit
Puppet
/
Test suite
0s
Annotations
10 errors
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_005429483.pp.bYa2Iw
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 00:54:06 UTC, ends at Sun 2023-09-03 00:54: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 3.90 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_005437926.pp.tYfZSY
Last 10 lines of output were:
journalctl log for chronyd:
-- Journal begins at Sun 2023-09-03 00:54:06 UTC, ends at Sun 2023-09-03 00:54: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:
-- Journal begins at Sun 2023-09-03 00:54:06 UTC, ends at Sun 2023-09-03 00:54:42 UTC. --
-- No entries --
�[mNotice: Applied catalog in 0.88 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_005436296.pp.vELu7H
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 00:54:16 UTC, ends at Sun 2023-09-03 00:54:42 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.15 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_005443104.pp.iSb8Ic
Last 10 lines of output were:
journalctl log for chronyd:
-- Journal begins at Sun 2023-09-03 00:54:16 UTC, ends at Sun 2023-09-03 00:54:46 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 00:54:16 UTC, ends at Sun 2023-09-03 00:54:46 UTC. --
-- No entries --
�[mNotice: Applied catalog in 0.92 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.
|