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 'almalinux8-64-puppet7.example.com' exited with 6 running:
puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_222209579.pp.u3gnLw
Last 10 lines of output were:
Mar 17 22:20:25 almalinux8-64-puppet7.example.com splunk[1075]: Getting CA Private Key
Mar 17 22:20:25 almalinux8-64-puppet7.example.com splunk[1075]: unable to write 'random state'
�[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 20.37 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 'almalinux8-64-puppet7.example.com' exited with 6 running:
puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest_222548999.pp.O7D2JL
Last 10 lines of output were:
-- Logs begin at Sun 2024-03-17 22:19:49 UTC, end at Sun 2024-03-17 22:31:52 UTC. --
Mar 17 22:31:52 almalinux8-64-puppet7.example.com systemd[1]: SplunkForwarder.service: Processes still around after final SIGKILL. Entering failed mode.
Mar 17 22:31:52 almalinux8-64-puppet7.example.com systemd[1]: SplunkForwarder.service: Failed with result 'exit-code'.
Mar 17 22:31:52 almalinux8-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 361.74 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