systemd with manage_resolved true configure systemd resolved works idempotently with no errors Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'oracle7-64-puppet7.example.com' exited with 4 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_173231764.pp.GNCoRt Last 10 lines of output were: systemd = 219-78.0.7.el7_9.3 Available: systemd-219-78.0.7.el7_9.5.x86_64 (ol7_latest) systemd = 219-78.0.7.el7_9.5 Available: systemd-219-78.0.9.el7_9.5.x86_64 (ol7_latest) systemd = 219-78.0.9.el7_9.5 Available: systemd-219-78.0.9.el7_9.7.x86_64 (ol7_latest) systemd = 219-78.0.9.el7_9.7 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest �[mNotice: Applied catalog in 1.36 seconds

systemd with manage_resolved true configure systemd resolved Service "systemd-resolved" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "systemd-resolved" to be running

systemd with manage_resolved true configure systemd resolved Service "systemd-resolved" is expected to be enabled Failure/Error: it { is_expected.to be_enabled } expected Service "systemd-resolved" to be enabled

systemd with manage_resolved true configure systemd stopped works idempotently with no errors Failure/Error: apply_manifest(pp, catch_failures: true) Beaker::Host::CommandFailure: Host 'oracle7-64-puppet7.example.com' exited with 4 running: puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_173236411.pp.B4FWt0 Last 10 lines of output were: systemd = 219-78.0.7.el7_9.3 Available: systemd-219-78.0.7.el7_9.5.x86_64 (ol7_latest) systemd = 219-78.0.7.el7_9.5 Available: systemd-219-78.0.9.el7_9.5.x86_64 (ol7_latest) systemd = 219-78.0.9.el7_9.5 Available: systemd-219-78.0.9.el7_9.7.x86_64 (ol7_latest) systemd = 219-78.0.9.el7_9.7 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest �[mNotice: Applied catalog in 1.36 seconds