Skip to content

Drop pidfile_workaround from Beaker testing #217

Drop pidfile_workaround from Beaker testing

Drop pidfile_workaround from Beaker testing #217

Triggered via pull request February 26, 2024 01:41
Status Failure
Total duration 5m 55s
Artifacts

ci.yml

on: pull_request
Puppet  /  Static validations
15s
Puppet / Static validations
Matrix: Puppet / acceptance
Matrix: Puppet / unit
Puppet  /  Test suite
0s
Puppet / Test suite
Fit to window
Zoom out
Zoom in

Annotations

8 errors
Puppet / Puppet 8 - CentOS 8: 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 'centos8-64-puppet8.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_014344834.pp.1tW1i9 Last 10 lines of output were: Feb 26 01:43:47 centos8-64-puppet8.example.com systemd[1]: chronyd.service: Control process exited, code=exited status=1 Feb 26 01:43:47 centos8-64-puppet8.example.com systemd[1]: chronyd.service: Failed with result 'exit-code'. Feb 26 01:43:47 centos8-64-puppet8.example.com systemd[1]: Failed to start NTP client/server. �[mNotice: /Stage[main]/Chrony::Service/Service[chronyd]: Triggered 'refresh' from 1 event �[mNotice: /Stage[main]/Chrony::Service/Service[chrony-wait.service]: 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 0.19 seconds
Puppet / Puppet 8 - CentOS 8: spec/acceptance/class_spec.rb#L23
chrony class: Service "chronyd" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "chronyd" to be running
Puppet / Puppet 8 - CentOS 8: 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 'centos8-64-puppet8.example.com' exited with 4 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_014348509.pp.uDnsJG Last 10 lines of output were: Feb 26 01:43:51 centos8-64-puppet8.example.com systemd[1]: Dependency failed for Wait for chrony to synchronize system clock. Feb 26 01:43:51 centos8-64-puppet8.example.com systemd[1]: chrony-wait.service: Job chrony-wait.service/start failed with result 'dependency'. Error: /Stage[main]/Chrony::Service/Service[chrony-wait.service]/ensure: change from 'stopped' to 'running' failed: Systemd start for chrony-wait.service failed! journalctl log for chrony-wait.service: -- Logs begin at Mon 2024-02-26 01:43:27 UTC, end at Mon 2024-02-26 01:43:51 UTC. -- Feb 26 01:43:51 centos8-64-puppet8.example.com systemd[1]: Dependency failed for Wait for chrony to synchronize system clock. Feb 26 01:43:51 centos8-64-puppet8.example.com systemd[1]: chrony-wait.service: Job chrony-wait.service/start failed with result 'dependency'. �[mNotice: Applied catalog in 0.30 seconds
Puppet / Puppet 8 - CentOS 8: spec/acceptance/class_spec.rb#L59
chrony class: with chrony-wait service enabled Service "chronyd" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "chronyd" to be running
Puppet / Puppet 8 - CentOS 8: spec/acceptance/class_spec.rb#L63
chrony class: with chrony-wait service enabled Service "chrony-wait.service" is expected to be enabled Failure/Error: it { is_expected.to be_enabled } expected Service "chrony-wait.service" to be enabled
Puppet / Puppet 8 - CentOS 8: spec/acceptance/class_spec.rb#L64
chrony class: with chrony-wait service enabled Service "chrony-wait.service" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "chrony-wait.service" to be running
Puppet / Puppet 8 - CentOS 8
Process completed with exit code 1.
Puppet / Puppet 7 - CentOS 8
Process completed with exit code 1.