chrony class: works idempotently with no errors Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'centos9-64-puppet7.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_014454920.pp.zUvMnB Last 10 lines of output were: Feb 26 01:44:56 centos9-64-puppet7.example.com systemd[1]: chronyd.service: Control process exited, code=exited, status=1/FAILURE Feb 26 01:44:56 centos9-64-puppet7.example.com systemd[1]: chronyd.service: Failed with result 'exit-code'. Feb 26 01:44:56 centos9-64-puppet7.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.20 seconds

chrony class: Service "chronyd" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "chronyd" to be running

chrony class: with chrony-wait service enabled works idempotently with no errors Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'centos9-64-puppet7.example.com' exited with 4 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_014457502.pp.iFnsdg Last 10 lines of output were: journalctl log for chrony-wait.service: Feb 26 01:44:59 centos9-64-puppet7.example.com systemd[1]: Dependency failed for Wait for chrony to synchronize system clock. Feb 26 01:44:59 centos9-64-puppet7.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: Feb 26 01:44:59 centos9-64-puppet7.example.com systemd[1]: Dependency failed for Wait for chrony to synchronize system clock. Feb 26 01:44:59 centos9-64-puppet7.example.com systemd[1]: chrony-wait.service: Job chrony-wait.service/start failed with result 'dependency'. �[mNotice: Applied catalog in 0.31 seconds

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

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

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

Process completed with exit code 1.

chrony class: works idempotently with no errors Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'centos9-64-puppet8.example.com' exited with 6 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_014519891.pp.IzZZUK Last 10 lines of output were: Feb 26 01:45:22 centos9-64-puppet8.example.com systemd[1]: chronyd.service: Control process exited, code=exited, status=1/FAILURE Feb 26 01:45:22 centos9-64-puppet8.example.com systemd[1]: chronyd.service: Failed with result 'exit-code'. Feb 26 01:45:22 centos9-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.20 seconds

chrony class: Service "chronyd" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "chronyd" to be running

chrony class: with chrony-wait service enabled works idempotently with no errors Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'centos9-64-puppet8.example.com' exited with 4 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_014523427.pp.8GAvqj Last 10 lines of output were: journalctl log for chrony-wait.service: Feb 26 01:45:26 centos9-64-puppet8.example.com systemd[1]: Dependency failed for Wait for chrony to synchronize system clock. Feb 26 01:45:26 centos9-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: Feb 26 01:45:26 centos9-64-puppet8.example.com systemd[1]: Dependency failed for Wait for chrony to synchronize system clock. Feb 26 01:45:26 centos9-64-puppet8.example.com systemd[1]: chrony-wait.service: Job chrony-wait.service/start failed with result 'dependency'. �[mNotice: Applied catalog in 0.31 seconds

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

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

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