Ensure compatibility with Splunk 9.2.0.1 and 9.0.0 #146
Annotations
5 errors
|
Run tests:
spec/acceptance/splunk_enterprise_spec.rb#L26
splunk enterprise class Splunk version 8.2.9 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_120145522.pp.6lWjBV
Last 10 lines of output were:
Mar 18 12:02:05 centos9-64-puppet8.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 12:02:05 centos9-64-puppet8.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 12:02:05 centos9-64-puppet8.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 12:02:05 centos9-64-puppet8.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 18.19 seconds
|
|
Run tests:
spec/acceptance/splunk_enterprise_spec.rb#L53
splunk enterprise class Splunk version 8.2.9 Service "Splunkd" is expected to be running
Failure/Error: it { is_expected.to be_running }
expected Service "Splunkd" to be running
|
|
Run tests:
spec/acceptance/splunk_forwarder_spec.rb#L26
splunk::forwarder class Splunk forwarder version 8.2.9 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_120524202.pp.mK2aiP
Last 10 lines of output were:
Mar 18 12:05:27 centos9-64-puppet8.example.com systemd[1]: SplunkForwarder.service: Control process exited, code=exited, status=1/FAILURE
Mar 18 12:05:27 centos9-64-puppet8.example.com systemd[1]: SplunkForwarder.service: Killing process 7392 (splunkd) with signal SIGKILL.
Mar 18 12:05:27 centos9-64-puppet8.example.com systemd[1]: SplunkForwarder.service: Failed with result 'exit-code'.
Mar 18 12:05:27 centos9-64-puppet8.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.58 seconds
|
|
Run tests:
spec/acceptance/splunk_forwarder_spec.rb#L45
splunk::forwarder class Splunk forwarder version 8.2.9 Service "SplunkForwarder" is expected to be running
Failure/Error: it { is_expected.to be_running }
expected Service "SplunkForwarder" to be running
|
|
Run tests
Process completed with exit code 1.
|
Loading