modulesync 9.3.0 #250
bastelfreakci.yml
on: pull_request
Puppet
/
Static validations
31s
Matrix: Puppet / acceptance
Matrix: Puppet / unit
Puppet
/
Test suite
2s
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_091336797.S3ooeu.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 Wed 2025-02-05 09:13:20 UTC, end at Wed 2025-02-05 09:13:43 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.04 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_091344343.8R1ZFt.pp
Last 10 lines of output were:
journalctl log for chronyd:
-- Logs begin at Wed 2025-02-05 09:13:20 UTC, end at Wed 2025-02-05 09:13:47 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 Wed 2025-02-05 09:13:20 UTC, end at Wed 2025-02-05 09:13:47 UTC. --
-- No entries --
�[mNotice: Applied catalog in 1.15 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_091356895.pqR8S5.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 Wed 2025-02-05 09:13:37 UTC, end at Wed 2025-02-05 09:14: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.33 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_091406262.sn1iH9.pp
Last 10 lines of output were:
journalctl log for chronyd:
-- Logs begin at Wed 2025-02-05 09:13:37 UTC, end at Wed 2025-02-05 09:14: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 Wed 2025-02-05 09:13:37 UTC, end at Wed 2025-02-05 09:14:10 UTC. --
-- No entries --
�[mNotice: Applied catalog in 1.46 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
|