Add Debian hiera data to match package defaults #232
ci.yml
on: pull_request
Puppet
/
Static validations
24s
Matrix: Puppet / acceptance
Matrix: Puppet / unit
Puppet
/
Test suite
0s
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_212646509.pp.7PiCEz
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 Sun 2024-05-12 21:26:32 UTC, end at Sun 2024-05-12 21:26:50 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.61 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_212652023.pp.GN2ZCg
Last 10 lines of output were:
journalctl log for chronyd:
-- Logs begin at Sun 2024-05-12 21:26:32 UTC, end at Sun 2024-05-12 21:26:54 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 Sun 2024-05-12 21:26:32 UTC, end at Sun 2024-05-12 21:26:54 UTC. --
-- No entries --
�[mNotice: Applied catalog in 0.63 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_212652248.pp.SuNgA8
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 Sun 2024-05-12 21:26:37 UTC, end at Sun 2024-05-12 21:26:56 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 - 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_212650426.pp.xGbOLv
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 Sun 2024-05-12 21:26:35 UTC, end at Sun 2024-05-12 21:26:56 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.19 seconds
|
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_212657799.pp.GUt5MJ
Last 10 lines of output were:
journalctl log for chronyd:
-- Logs begin at Sun 2024-05-12 21:26:37 UTC, end at Sun 2024-05-12 21:27:00 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 Sun 2024-05-12 21:26:37 UTC, end at Sun 2024-05-12 21:27:00 UTC. --
-- No entries --
�[mNotice: Applied catalog in 0.68 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 - 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 - 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_212657422.pp.DKYJqY
Last 10 lines of output were:
journalctl log for chronyd:
-- Logs begin at Sun 2024-05-12 21:26:35 UTC, end at Sun 2024-05-12 21:26:59 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 Sun 2024-05-12 21:26:35 UTC, end at Sun 2024-05-12 21:26:59 UTC. --
-- No entries --
�[mNotice: Applied catalog in 1.03 seconds
|
Puppet / Puppet 7 - Debian 10
Process completed with exit code 1.
|
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 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_212658350.pp.DRDyQf
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 Sun 2024-05-12 21:26:42 UTC, end at Sun 2024-05-12 21:27: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 6.03 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_212707304.pp.kmOXEL
Last 10 lines of output were:
journalctl log for chronyd:
-- Logs begin at Sun 2024-05-12 21:26:42 UTC, end at Sun 2024-05-12 21:27:10 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 Sun 2024-05-12 21:26:42 UTC, end at Sun 2024-05-12 21:27:10 UTC. --
-- No entries --
�[mNotice: Applied catalog in 1.18 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 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_212703873.pp.RbtVxs
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 Sun 2024-05-12 21:26:46 UTC, end at Sun 2024-05-12 21:27:10 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.51 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_212711429.pp.N5DNqn
Last 10 lines of output were:
journalctl log for chronyd:
-- Logs begin at Sun 2024-05-12 21:26:46 UTC, end at Sun 2024-05-12 21:27:14 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 Sun 2024-05-12 21:26:46 UTC, end at Sun 2024-05-12 21:27:14 UTC. --
-- No entries --
�[mNotice: Applied catalog in 1.06 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_212730568.pp.uS26ED
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 Sun 2024-05-12 21:27:14 UTC, end at Sun 2024-05-12 21:27: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.47 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_212739097.pp.ddfI82
Last 10 lines of output were:
journalctl log for chronyd:
-- Logs begin at Sun 2024-05-12 21:27:14 UTC, end at Sun 2024-05-12 21:27: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 Sun 2024-05-12 21:27:14 UTC, end at Sun 2024-05-12 21:27:42 UTC. --
-- No entries --
�[mNotice: Applied catalog in 1.18 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.
|