Known issues in Splunk App for VMWare 3.1.2

Publication date	Defect number	Description
2014-11-21	TAG-8650	Errors when installing indexer without SA-Utils and SA-Hydra. On a distributed deployment, you must install SA-Utils and SA-Hydra on indexers to avoid producing benign error messages.
2014-10-27	SOLNVMW-3906	If a perpetual license and a trial license exist on the same server at the same time, Splunk App for VMware license status shows the trial expiration date instead of the perpetual one.
2014-10-27	-	Upon upgrading from a previous version of Splunk App for VMware, you must walk through the setup page and delete the old add-ons. However, the setup page does not automatically appear after upgrading the app. By default, the value of the is_configured key in the app.conf is 1. Change the value to 0 so that the setup page appears when first running the app after upgrade. The app.conf file exists in $SPLUNK_HOME/etc/apps/splunk_for_vmware/local.
2014-10-27	SOLNVMW-3858, SOLNVMW-3874	If the license master is remote, the App Data Volume page on a slave does not list the _size_ of app licenses. The App Data Volume page does indicate the existence of a license.
2014-10-27	SPL-91339	On the App License Status page, remote license masters always report the expiration date of app licenses as ∞ (infinite), although it may actually be less.
2014-10-27	SOLNVMW-3748	yslog data from syslog server not getting indexed. Syslog data sent from a syslog server, with a line breaking issue, in the following format is not indexed (by Splunk_TA_esxilogs). 0-dd6d170cebd6 ' opID=SWI-7f741cda-80] [VpxLRO] -- FINISH task-internal-157304 -- -- vpxapi.VpxaService.fetchQuickStats -- 52bfdd7d-118e-3345-58e0-dd6d170cebd6 ete (processed 29730 bytes)
2014-10-27	SOLNVMW-3360	For a search head pooled environment, in the App Install Health dashboard, the panel displaying the data collection node does not populate.
2014-10-27	SOLNVMW-3294	Error when user skips configuration of collection nodes.You must configure data collection to get data into the app.
2014-10-27	SOLNVWM-3257	In certain cases, ESXi logs coming via Syslog are assigned an incorrect sourcetype.
2014-10-27	SOLNVMW-3245	If you configure Syslog using intermediate forwarders and loghost values are not returned, the ESXi host becomes unresponsive to the API and no error message is displayed.
2014-10-27	SOLNVMW-3168	On IE9, the Threshold Configuration view's height increases unexpectedly as you enter text in the textbox.
2014-10-27	SOLNVMW-3083	A powered off vm cannot lookup datastore information from time based lookup TimeDatastoreSummary.
2014-10-27	SOLNVMW-2186	The VM Detail view (that shows the performance of a VM across migrations) is not displayed correctly when the TimeHierarchyVM lookup is missing migration data for the virtual machines. When the lookup is not updated correctly the summary data can not be correctly tied to the hierarchy. This breaks views such as VM Detail that show the performance of a VM across migrations.
2015-1-27	TAG-8879	Autocomplete text box is empty and not populating data in views on Windows due to failing to run generateIIT.py. (Note: SH on Windows is not QA-tested in this version)
2015-1-30	TAG-8961	For License Status check, it requires to clicks refresh button every several hours to list as valid due to missing ModularInput scheme in inputs.conf.spec. Workaround Add the following contents in $SPLUNK_HOME/etc/apps/splunk_for_vmware/README/inputs.conf.spec [vmware_licensecheck://<name>] log_level = <value> * log level of modular inputs from "DEBUG", "INFO", "WARN","WARNING", "ERROR"
2015-3-6	TAG-8211	In Collection Configurations, vCenter authentication fails when special characters are used in password
2015-06-22	TAG-9416 / SPL-86606	The tsidx_retention.py script that grooms search head pool shared namespaces for TSIDX files fails to clean up the files because of a bug in the /services/data/indexes endpoint that it references. This endpoint outputs a blank value for the tsidxstatshomepath attribute on Splunk Enterprise versions v6.1.1 through 6.1.4 and 6.2.0. The bug has been fixed in versions v6.1.5 and v6.2.1. If you run any of the affected versions, you must delete the TSIDX files manually from the shared namespace. Doing so does not result in data loss.