splunk enterprise class Splunk version 8.2.12 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_142643420.pp.VcqWwo Last 10 lines of output were: Mar 18 14:27:04 centos9-64-puppet7.example.com systemd[1]: /etc/systemd/system/Splunkd.service:24: Unit uses MemoryLimit=; please use MemoryMax= instead. Support for MemoryLimit= will be removed soon. Mar 18 14:27:05 centos9-64-puppet7.example.com systemd[1]: /etc/systemd/system/Splunkd.service:23: Unit uses CPUShares=; please use CPUWeight= instead. Support for CPUShares= will be removed soon. Mar 18 14:27:05 centos9-64-puppet7.example.com systemd[1]: /etc/systemd/system/Splunkd.service:24: Unit uses MemoryLimit=; please use MemoryMax= instead. Support for MemoryLimit= will be removed soon. Mar 18 14:27:05 centos9-64-puppet7.example.com systemd[1]: Starting Systemd service file for Splunk, generated by 'splunk enable boot-start'... �[mNotice: /Stage[main]/Splunk::Enterprise::Service/Service[Splunkd]: Triggered 'refresh' from 1 event Info: Class[Splunk::Enterprise::Service]: Unscheduling all events on Class[Splunk::Enterprise::Service] Info: Class[Splunk::Enterprise]: Unscheduling all events on Class[Splunk::Enterprise] Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 19.84 seconds

splunk enterprise class Splunk version 8.2.12 Service "Splunkd" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "Splunkd" to be running

splunk::forwarder class Splunk forwarder version 8.2.12 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_143023027.pp.pXcgJj Last 10 lines of output were: Mar 18 14:30:26 centos9-64-puppet7.example.com systemd[1]: SplunkForwarder.service: Control process exited, code=exited, status=1/FAILURE Mar 18 14:30:26 centos9-64-puppet7.example.com systemd[1]: SplunkForwarder.service: Killing process 7379 (splunkd) with signal SIGKILL. Mar 18 14:30:26 centos9-64-puppet7.example.com systemd[1]: SplunkForwarder.service: Failed with result 'exit-code'. Mar 18 14:30:26 centos9-64-puppet7.example.com systemd[1]: Failed to start Systemd service file for Splunk, generated by 'splunk enable boot-start'. �[mNotice: /Stage[main]/Splunk::Forwarder::Service/Service[SplunkForwarder]: Triggered 'refresh' from 1 event Info: Class[Splunk::Forwarder::Service]: Unscheduling all events on Class[Splunk::Forwarder::Service] Info: Class[Splunk::Forwarder]: Unscheduling all events on Class[Splunk::Forwarder] Info: Stage[main]: Unscheduling all events on Stage[main] �[mNotice: Applied catalog in 1.82 seconds

splunk::forwarder class Splunk forwarder version 8.2.12 Service "SplunkForwarder" is expected to be running Failure/Error: it { is_expected.to be_running } expected Service "SplunkForwarder" to be running