Ensure compatibility with Splunk 9.2.0.1 and 9.0.0 #140
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 'ubuntu2204-64-puppet7.example.com' exited with 6 running:
puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_222100455.pp.lu5f8W
Last 10 lines of output were:
Mar 17 22:20:44 ubuntu2204-64-puppet7.example.com splunk[1179]: unable to write 'random state'
Mar 17 22:20:44 ubuntu2204-64-puppet7.example.com splunk[1180]: writing RSA key
�[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]
�[mNotice: /Stage[main]/Main/File_line[file_locking]: Dependency Service[Splunkd] has failures: true
Warning: /Stage[main]/Main/File_line[file_locking]: Skipping because of failed dependencies
Info: Stage[main]: Unscheduling all events on Stage[main]
�[mNotice: Applied catalog in 28.04 seconds
|
Run tests:
spec/acceptance/splunk_enterprise_spec.rb#L52
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#L25
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 'ubuntu2204-64-puppet7.example.com' exited with 6 running:
puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_222531960.pp.6Y1uR1
Last 10 lines of output were:
Mar 17 22:25:35 ubuntu2204-64-puppet7.example.com systemd[1]: SplunkForwarder.service: Killing process 27304 (sh) with signal SIGKILL.
Mar 17 22:25:35 ubuntu2204-64-puppet7.example.com systemd[1]: SplunkForwarder.service: Killing process 27305 (splunkd) with signal SIGKILL.
Mar 17 22:25:35 ubuntu2204-64-puppet7.example.com systemd[1]: SplunkForwarder.service: Failed with result 'exit-code'.
Mar 17 22:25:35 ubuntu2204-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 2.31 seconds
|
Run tests:
spec/acceptance/splunk_forwarder_spec.rb#L44
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