modulesync 9.3.0 #243
ci.yml
on: pull_request
Puppet
/
Static validations
22s
Matrix: Puppet / acceptance
Matrix: Puppet / unit
Puppet
/
Test suite
4s
Annotations
11 errors and 5 warnings
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_233119331.ZyA0rv.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:31:01 UTC, end at Tue 2024-09-17 23:31:25 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.57 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_233127170.UepxI7.pp
Last 10 lines of output were:
journalctl log for chronyd:
-- Logs begin at Tue 2024-09-17 23:31:01 UTC, end at Tue 2024-09-17 23:31: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:
-- Logs begin at Tue 2024-09-17 23:31:01 UTC, end at Tue 2024-09-17 23:31:30 UTC. --
-- No entries --
�[mNotice: Applied catalog in 1.14 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_233126632.LNXGgt.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:31:09 UTC, end at Tue 2024-09-17 23:31:33 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.15 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_233134830.NBaK2e.pp
Last 10 lines of output were:
journalctl log for chronyd:
-- Logs begin at Tue 2024-09-17 23:31:09 UTC, end at Tue 2024-09-17 23:31:37 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:31:09 UTC, end at Tue 2024-09-17 23:31:37 UTC. --
-- No entries --
�[mNotice: Applied catalog in 1.12 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 / Test suite
Process completed with exit code 1.
|
Puppet / Static validations:
metadata.json#L1
Skipping EOL operating system RedHat 7
|
Puppet / Static validations:
metadata.json#L1
Skipping EOL operating system CentOS 7
|
Puppet / Static validations:
metadata.json#L1
Skipping EOL operating system CentOS 8
|
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
|