Customer Fixed Issues and Known Issues Tahoe SP4

Owned by Enterprise IT
May 08, 2024

 | Previous Versions: << Sierra << Sierra HF01 << Sierra SP1 << Sierra SP1 HF01 << Sierra SP1 HF02 << Sierra SP1 HF03 << Denali << Denali HF01 << Denali HF02 << Denali HF03 << Denali SP1 << Denali SP1 HF01 << Tahoe << Tahoe SP1 << Tahoe SP3 HF01 << Tahoe SP3 HF01 (v1) << Tahoe SP3 HF02<< Tahoe SP3 HF03

What's New? | Customer Fixed Issues and Known Issues | Prerequisites | Installation, Configuration, and Upgrade

On this page: Customer Fixed Issues | Known Issues 

Customer Fixed Issues 

This section describes the issues reported by the customers and their fixes in Tahoe SP4 version.

Agentless Discovery

Issue ID

Issue Description

Scenario

Resolution

106631 User was facing an issue with Content Parser pop-up in Discovery Template page, as it was not fetching the data from hard disks of multiple sizes (GB and TB). 

Steps: 

  1. Navigate to Discovery & Monitoring > Discovery Template > Content parser. 
     
  2. On the Discovery Template page, Click the specific Template Name. 
     
  3. Click Actions for the specific Parameter Name. 
     
  4. Under the CONTENT PARSER pop-up, select Content Type, Output Type, Unit and check the Final output to make it as false for the multiple parsers to work. 
User is not facing issues while fetching data from multiple hard disks and is working properly after the resolution. 
107218User was facing an issue while fetching IP Address for Windows Management Instrumentation (WMI) discovery. 

Steps: 

  1. Navigate to Admin > Discovery & Monitoring > Discovery.

  2. On the Discovery page, Click View Jobs under LIST. The Subnet Details displays the IP ADDRESS of the scanned discovery. 
User is not facing issue while fetching IP Address for Windows Management Instrumentation Discovery (WMI) and it is displaying appropriately after the resolution. 
108161 While creating and submitting parser for any parameter, the Parent key value was displaying as zero under CONTENT PARSER pop-up. 

Steps: 

  1. Navigate to Discovery & Monitoring > Discovery Template  

  2. On the Discovery Template page, Click the specific Template Name. 
     
  3. Click Actions for the specific Parameter Name.

  4. Under the CONTENT PARSER pop-up select mandatory fields. and add to the list.
The Parent key value is displaying as empty for all parameters under CONTENT PARSER pop-up after saving the data. 

Platform

Issue ID

Issue Description

Scenario

Resolution

104971

All the report related data loaded when Power BI was connected to reporting API URL. 
It was difficult to filter out relevant data like last one year data or so. 

NA

To filter the relevant data, two filters are introduced in database level: Number of Months and Number of Records.  
These filters simplify the task of filtering the top relevant data and optimize the process which is helpful in building dashboards. 
 
To Build the dashboard under Power BI desktop tool use the below data keys in SUMMIT_AppConfigSettings table to make necessary configuration of filters. 

DataKeys: 

Reporting_GetAPI_MaxRecords.

Reporting_GetAPI_Months.


Known Issues 

This section describes the known issues detected by the SummitAI Dev and QA team in the release, Tahoe SP4 Release.

Issue ID

Issue Description

Scenario

Workaround

103951

Due to the change of Serial Number for Agent,  Agentless, Pseudo, and Root account, duplicate records are being added to the table.

Prerequisite:

Both Agent and Agentless should belong to the same IP.


Steps:

  1. Configure Linux Agent.

  2. Configure Agentless Discovery job.

  3. Data flows into Agent or Agentless table as per the configuration.

  4. Compare the Serial number fields of Agent/agentless and Widget_scan_details table.
N/A