Splunk® Enterprise

Release Notes

Splunk Enterprise version 8.0 is no longer supported as of October 22, 2021. See the Splunk Software Support Policy for details. For information about upgrading to a supported version, see How to upgrade Splunk Enterprise.
This documentation does not apply to the most recent version of Splunk® Enterprise. For documentation on the most recent version, go to the latest release.

Fixed issues

Splunk Enterprise 8.0.8 was released on January 20, 2021. This release includes fixes for the following issues.

Issues are listed in all relevant sections. Some issues might appear more than once. To check for additional security issues related to this release, visit the Splunk Security Portal.

Authentication and authorization issues

Date resolved Issue number Description
2020-11-18 SPL-196712, SPL-196863, SPL-197658, SPL-197656 list_indexer_cluster cannot see the cluster info from the UI
2020-10-27 SPL-196620, SPL-195586 Linux 7.2.4.2 SHC + Duo Security 2FA - Authentication - login fails when using a custom root_endpint
2020-10-08 SPL-194288, SPL-190298 SAML - unable to update idpCerts via idpCertChain text box in SHC with replicate certificates enabled

Upgrade issues

Date resolved Issue number Description
2020-12-11 SPL-198237, SPL-196933 Settings removed from savedsearches.conf after upgrading from 7.3.3 to 7.3.7.1
2020-11-23 SPL-196903, SPL-195414 Custom Navigation Menus Lost When Upgrading Splunk from 7.3.6 to 7.3.7

Search issues

Date resolved Issue number Description
2021-01-04 SPL-193416, SPL-192132 The 'strict' argument of the 'rest' command produces incorrect results when used with an up-to-date SH and older indexers
2021-01-04 SPL-196222, SPL-193845 Bucket that rolled during search execution contained events missing from results
2021-01-04 SPL-198240, SPL-198094 srchTimeWin not effective if earliest= is used in query
2020-12-21 SPL-196346, SPL-196545, SPL-198275 The use of "usetime" and "earlier" arguements are causing a left join to behave as a inner join
2020-11-19 SPL-196588, SPL-194959 Using wildcards in conjunction with summary indexing reserved fields (psrsvd) yields incorrect search results.
2020-10-30 SPL-196484, SPL-194112 Cascading replication aborted for peer=Peer_URI:8089 with bundle status = bundle_initialized after a retry attempt
2020-10-14 SPL-195717, SPL-194016 search optimizer causing some search condition to be missing in remote search for searches including multiple wildcarded terms for the same field

Saved search, alerting, scheduling, and job management issues

Date resolved Issue number Description
2020-11-12 SPL-194596, SPL-194014 getMgmtUri shouldn't include stderr in the results.

Charting, reporting, and visualization issues

Date resolved Issue number Description
2020-12-10 SPL-198412, SPL-196313 Dashboard panel font size changes with browser zoom on v8.0.2

Indexer and indexer clustering issues

Date resolved Issue number Description
2020-10-19 SPL-196335, SPL-194863 During indexer cluster searchable rolling restart, indexer was stuck in ReassigningPrimaries

Distributed deployment, forwarder, deployment server issues

Date resolved Issue number Description
2020-11-24 SPL-196464, SPL-182933 Renaming server class creates multiple serverclass.conf files
2020-11-19 SPL-197228, SPL-196194 All App from Deployment Server UI show "Unchanged from state on deployment server"

Admin and CLI issues

Date resolved Issue number Description
2020-12-11 SPL-198237, SPL-196933 Settings removed from savedsearches.conf after upgrading from 7.3.3 to 7.3.7.1

Uncategorized issues

Date resolved Issue number Description
2020-12-15 SPL-198559, SPL-194635 smartstore start new upload jobs as soon as the current job failed no back off
2020-12-15 SPL-198571, SPL-190942 Enable Non-zero "max_cache_size" setting to account for local cached state on node restart
2020-11-10 SPL-197011, SPL-195826 splunkd.exe is constantly crashing by Access violation, cannot read at address
2020-10-30 SPL-196708, SPL-195411 Redundant absent summary cachemanager open calls
Last modified on 12 June, 2021
Timestamp recognition of dates with two-digit years fails beginning January 1, 2020   Deprecated and removed in version 8.0

This documentation applies to the following versions of Splunk® Enterprise: 8.0.8


Was this topic useful?







You must be logged into splunk.com in order to post comments. Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters