README VERSION               : 1.1
README CREATION DATE         : 2022-02-23
PATCH-ID                     : vom-HF0742600 
PATCH NAME                   : Veritas Operations Manager 7.4.2 Patch 600
BASE PACKAGE NAME            : VRTSfmh
BASE PACKAGE VERSION         : Veritas Operations Manager 7.4.2.0
SUPERSEDED PATCHES           : vom-HF0742500
REQUIRED PATCHES             : NONE
INCOMPATIBLE PATCHES         : NONE
SUPPORTED PADV               : aix,aix71,aix72,rhel7_x86_64,rhel8_x86_64,sles12_x86_64,sles15_x86_64,sol11_sparc,sol11_x86,w2k12r2X64,w2k16X64,w2k19X64
(P-PLATFORM , A-ARCHITECTURE , D-DISTRIBUTION , V-VERSION)
PATCH CATEGORY               :  MH
PATCH CRITICALITY            : RECOMMENDED
HAS KERNEL COMPONENT         : NO
ID                           : vom-HF0742600
REBOOT REQUIRED              : NO
REQUIRE APPLICATION DOWNTIME : NO

PATCH INSTALLATION INSTRUCTIONS:
--------------------------------
IMPORTANT NOTE : Please take a backup of the database using the instructions given in the Admin guide before installing this Hotfix.

This Hotfix is applicable for VOM 7.4.2 Managed Hosts as well as VOM 7.4.2 Management Server.

1. Download the file vom-7.4.2.600.sfa
2. Launch a browser and login to the VIOM management server.
3. Navigate to Settings ->  Deployment Icon.
4. Upload the Hotfix to the VIOM CMS using the Upload Solutions button.
The Hotfix vom-7.4.2.600 should be visible in the Hot Fixes tree node.
5. Please install this Hotfix on CS using the following instructions:
- Go to Settings ->  Deployment ->  Hot Fixes ->  Veritas Infoscale Operations Manager Managed Host.
- Click on Hot Fixes Tab. Click on Applicable Hosts Tab.
- Right click on CS Name and click on Install.

PATCH UNINSTALLATION INSTRUCTIONS:
----------------------------------
NONE

SPECIAL INSTRUCTIONS:
-----------------------------
NONE

SUMMARY OF FIXED ISSUES:
-----------------------------------------

 PATCH ID:vom-HF0742600

4067034 (4067033)  Product Enhancement - InfoScale licensing reconciliation tool 
4067041 (4067040)  log4j2 vulnerabilities fixes 
4067046 (4067045)  Apache Tomcat vulnerability issue CVE-2022-23181 in versions below 9.0.58. 
4067050 (4067049)  'Per Core License Information' report displays incorrect License information. 
4067058 (4067057)  Product Enhancement - Discovers FULLFSCK flag on VxFS file system and generates fault on file system corruption. 
4067130 (4067129)  'Infoscale version' shows N/A for some of the InfoScale servers. 
4067133 (4067132)  Security fix - A reflected cross-site scripting (XSS) vulnerability allows a malicious VIOM user to inject malicious script into another users browser (CWE-79). 
4067136 (4067135)  Security fix - An absolute path transversal vulnerability allows a user to gain unauthorized access to resources on the server (CWE-36). 

 PATCH ID:vom-HF0742500

4049488 (4049487)  Product Enhancement - Core Plus Licensing for InfoScale deployment. 
4049494 (4049492)  Not able to save VIOM report in csv format. 
4049505 (4049504)  Not able to configure LDAP/AD of length more than 32 characters. 
4049509 (4049507)  Product Enhancement - VIOM Audit Logs Forwarding. 
4049515 (4049514)  Tomcat version 9.0.52 and Java version 1.8.0_302.b08 upgrade 
4049639 (4049637)  Product Enhancement - New fault for VxVM DCLI vxlist error 

 PATCH ID:vom-HF0742400

4032937 (4032936)  Upgrade tomcat to 9.0.45 
4032940 (4032939)  Search on Replications tab does not work 
4032946 (4032947)  Product Enhancement - Global reports to create custom and centralized reports over multiple VIOM Management Servers. 
4032953 (4032950)  Product enhancement - vxdclid plugin compatibility should not break while doing MH upgrade from VIOM GUI. 
4033084 (4033081)  Product Enhancement - InfoScale licensing service enhancement. 
4042366 (4042365)  V-16-25-30068 reported when trying to do VCS service group online/offline using VBS policy using VIOM GUI 
4042371 (4042370)  Use of 'had' command instead of 'hastart' command in sfmh-discovery.pl script. 
4042478 (4042477)  Duplicate Virtual Machine ID found in database and not able to add MH to VIOM CMS 
4042481 (4042480)  Some of the binaries in VRTSsfmh package are using older openssl version. 
4042486 (4042485)  Product Enhancement - Display a warning message in VIOM GUI if VIOM CMS is running in maintenance mode. 

 PATCH ID:vom-HF0742300

4028854 (4028853)  Discrepancy between ncore license report and Excel version. 
4028872 (4028869)  Product Enhancement - VIOM Web API to remove/unconfigure Agent from Management Server. 
4028955 (4028954)  VCS Service Groups status not showing intermittently for all hosts in a cluster in VIOM GUI. 
4028959 (4028958)  VIOM email notification does not mention the faulted resource name for VCS resource faulted alert. 
4028969 (4028968)  Product Enhancement - Support of third party certificate for xprtld process running on port 5634. 
4028998 (4028997)  Veritas InfoScale Operations Manager on Windows allows an attacker to run arbitrary code with administrator privilege. 
4029001 (4028983)  Upgrade tomcat to 9.0.41 and java to Amazon Corretto java 8.275.01.1 

 PATCH ID:vom-HF0742200

4017417 (4017414)  Host family discovery fail due to json error in Task.pm 
4017420 (4017419)  VIOM Web Server does not start at the end of VIOM CMS patch upgrade. 
4017423 (4017422)  While adding VIOM Agent to VIOM CMS, getting error "Host is already part of the domain". 
4017437 (4017435)  Not able to generate email alert for VCS cluster down from Availability perspective. 
4017442 (4017440)  VIOM does report no valid SFHA license for version 5.1 on Windows servers. 
4017453 (4017444)  Tomcat upgrade to 9.0.37.0 
4017461 (4017460)  Product Enhancement - New reports for Veritas Volume Replicator. 
4017472 (4017463)  Product Enhancement: CLI to configure LDAP in VIOM. 

 PATCH ID:vom-HF0742100

4009452 (4009454)  Can not expand VVR volume on Windows InfoScale Node from VIOM GUI. 
4009466 (4009463)  MH patch install on Solaris 11 hosts does not unset the Veritas publisher. 
4009469 (4009472)  Some other fixes and security upgrades. 
4009471 (4009470)  VIOM patch shows Not installed though it is installed. 
4009475 (4009474)  Windows MH agent showing disconnected in VIOM even after refresh/reboot 

SUMMARY OF KNOWN ISSUES:
-----------------------------------------
NONE 

KNOWN ISSUES : 
--------------
NONE

FIXED INCIDENTS: 
----------------

 PATCH ID:vom-HF0742600

 * INCIDENT NO:4067034     TRACKING ID:4067033

SYMPTOM: N/A 

DESCRIPTION: The License Reconciliation is a feature that provides an effortless solution to compare InfoScale license usage data against each entitlement and includes a facility to view the effective license position summary of an organization. Refer below technotes for more details https://www.veritas.com/support/en_US/doc/viom_technote_7.4.2.600 - VIOM version 7.4.2
https://www.veritas.com/support/en_US/doc/viom_technote_8.0.0.100 - VIOM version 8.0 

RESOLUTION: N/A 

 * INCIDENT NO:4067041     TRACKING ID:4067040

SYMPTOM: log4j2 vulnerabilities fixes 

DESCRIPTION: This patch upgrade log4j2 version to 2.17.1 on VIOM Management Servers to fix below mentioned vulnerabilities.
CVE-2021-44228, CVE-2021-45046, CVE-2021-45105, CVE-2021-4104, CVE-2021-44832, CVE-2019-17571

This hotfix is mandatory for VIOM Management Servers and Managed Hosts/Agents to fix the log4j2 vulnerabilities. This hotfix upgrades log4j component to version 2.17.1 on VIOM Management Servers and removes log4j jars from Windows Managed Hosts. Removal of log4j jars from Managed Hosts/Agents does not impact any VIOM functionality. 

RESOLUTION: Upgraded log4j2 to 2.17.1 

 * INCIDENT NO:4067046     TRACKING ID:4067045

SYMPTOM: Apache Tomcat vulnerability issue CVE-2022-23181 in versions below 9.0.58. 

DESCRIPTION: This patch upgrade Apache Tomcat to version 9.0.58 to fix vulnerability CVE-2022-23181. 

RESOLUTION: Upgraded tomcat to version 9.0.58 in VIOM patch. 

 * INCIDENT NO:4067050     TRACKING ID:4067049

SYMPTOM: 'Per Core License Information' report does not show correct 'Core to License' value. 

DESCRIPTION: VIOM GUI -> Licensing perspective -> Report -> 'Per Core License Information' displays incorrect number of 'Core to License' w.r.t. InfoScale version. 

RESOLUTION: Fixed DB schema to get correct numbers of Core to License. 

 * INCIDENT NO:4067058     TRACKING ID:4067057

SYMPTOM: N/A 

DESCRIPTION: Veritas InfoScale Operations Manager discovers FULLFSCK flag on a VxFS file system every 24 hours. If the file system is corrupted, a fault 'SF_FILESYSTEM_CORRUPTED' is raised. For more information, refer technotes below.
https://www.veritas.com/support/en_US/doc/viom_technote_7.4.2.600 - VIOM version 7.4.2
https://www.veritas.com/support/en_US/doc/viom_technote_8.0.0.100 - VIOM version 8.0 

RESOLUTION: N/A 

 * INCIDENT NO:4067130     TRACKING ID:4067129

SYMPTOM: InfoScale deployment details or some reports under Licensing perspective show InfoScale versions as N/A. 

DESCRIPTION: While checking InfoScale version under some of the Licensing reports or 'Deployment details' tab, you may see that InfoScale versions are getting displayed as N/A. You may see this issue on the InfoScale servers where only InfoScale Availability is installed. 

RESOLUTION: Added a fix to get the InfoScale version when only InfoScale Availability is installed. 

 * INCIDENT NO:4067133     TRACKING ID:4067132

SYMPTOM: An authenticated remote attacker (administrative/root role) can inject arbitrary web script or HTML into HTTP/GET parameter which reflect the user input without sanitization. 

DESCRIPTION: Cross-site scripting Reflected (XSS) vulnerability affects the Veritas Operations Manager application, which allows authenticated remote attackers to inject arbitrary web script or HTML into HTTP/GET parameter which reflect the user input without sanitization.
It is required to have access to the web application as a user with administrative/root role.
Severity : Medium

Refer technote for more details.
https://www.veritas.com/support/en_US/doc/viom_technote_7.4.2.600 - VIOM version 7.4.2
https://www.veritas.com/support/en_US/doc/viom_technote_8.0.0.100 - VIOM version 8.0 

RESOLUTION: Fixed the affected endpoint. 

 * INCIDENT NO:4067136     TRACKING ID:4067135

SYMPTOM: An authenticated remote attacker (administrative/root role) can manipulate the resource name in the GET requests referring to files with absolute paths, it is possible to access arbitrary files stored on the filesystem. 

DESCRIPTION: The web server fails to sanitize the input data allowing a remote authenticated attacker to read files on the filesystem arbitrarily.
By manipulating the resource name in the GET requests referring to files with absolute paths, it is possible to access arbitrary files stored on the filesystem.
It is required to have access to the web application as a user with administrative/root role.
Severity : Medium

Refer technote for more details.
https://www.veritas.com/support/en_US/doc/viom_technote_7.4.2.600 - VIOM version 7.4.2
https://www.veritas.com/support/en_US/doc/viom_technote_8.0.0.100 - VIOM version 8.0 

RESOLUTION: Fixed the affected endpoint. 

 PATCH ID:vom-HF0742500

 * INCIDENT NO:4049488     TRACKING ID:4049487

SYMPTOM: N/A 

DESCRIPTION: Details on Core Plus Licensing for InfoScale deployment are available in technote https://www.veritas.com/support/en_US/doc/viom_technote_7.4.2.500 

RESOLUTION: N/A 

 * INCIDENT NO:4049494     TRACKING ID:4049492

SYMPTOM: Not able to save VIOM report in csv format while running on organization in data center, it leads to HTTP 400 error. 

DESCRIPTION: Web server rejects request for some characters due to different encoding and URI standard than most browsers. 

RESOLUTION: Handled request to save report in csv format on OE. 

 * INCIDENT NO:4049505     TRACKING ID:4049504

SYMPTOM: Not able to configure LDAP/AD of length more than 32 characters. 

DESCRIPTION: According to RFC1034 standard domain name length must be 63 characters or less so increased LDAP/AD length limit to 63 characters. 

RESOLUTION: Increased LDAP/AD length limit to 63 characters. 

 * INCIDENT NO:4049509     TRACKING ID:4049507

SYMPTOM: N/A 

DESCRIPTION: Details on VIOM Audit Logs Forwarding feature are available in technote https://www.veritas.com/support/en_US/doc/viom_technote_7.4.2.500 

RESOLUTION: N/A 

 * INCIDENT NO:4049515     TRACKING ID:4049514

SYMPTOM: Tomcat and Java security updates. 

DESCRIPTION: Tomcat upgraded to version 9.0.52 and Java upgraded to version 1.8.0_302.b08 

RESOLUTION: Upgraded tomcat and java to latest version available. 

 * INCIDENT NO:4049639     TRACKING ID:4049637

SYMPTOM: N/A 

DESCRIPTION: This update has a new fault topic "event.alert.vom.dclid.vxlist.error". This fault will be generated for InfoScale servers where "/opt/VRTSsfmh/bin/vxlist" command does not work properly. "vxlist" command output contains error like "vxdclid process cannot connect to vxconfigd". 

RESOLUTION: N/A 

 PATCH ID:vom-HF0742400

 * INCIDENT NO:4032937     TRACKING ID:4032936

SYMPTOM: Tomcat security updates. 

DESCRIPTION: Tomcat upgraded to 9.0.45 

RESOLUTION: Upgraded tomcat to latest version available. 

 * INCIDENT NO:4032940     TRACKING ID:4032939

SYMPTOM: Not able to filter/search RVGs. 

DESCRIPTION: Under Replication tab, you can not search or filter out the RVGs. 

RESOLUTION: Added search functionality on the replication tab. 

 * INCIDENT NO:4032946     TRACKING ID:4032947

SYMPTOM: N/A 

DESCRIPTION: Details on using Global reports are available in technote https://www.veritas.com/support/en_US/doc/viom_technote_7.4.2.400 

RESOLUTION: N/A 

 * INCIDENT NO:4032953     TRACKING ID:4032950

SYMPTOM: N/A 

DESCRIPTION: Earlier, while doing MH upgrade on InfoScale hosts used to break the vxdclid plugin compatibility with VxVM. Now, we have enhance the MH upgrade procedure to avoid the vxdclid plugin compatibility. 
Upgrading MH through VIOM GUI on InfoScale hosts will retain the vxdclid plugin compatibility with VxVM version.

NOTE: After patch upgrade, SFMH 7.4.2 Managed Host bundle will be removed from VIOM CMS. You need to re-upload the 7.4.2 Managed Host bundle when you want to do MH upgrade from VIOM GUI. You may download Veritas_InfoScale_Operations_Manager_Managed_Host_Bundle_7.4.2 from Veritas Download Center. 

RESOLUTION: N/A 

 * INCIDENT NO:4033084     TRACKING ID:4033081

SYMPTOM: N/A 

DESCRIPTION: For more details, please refer technote https://www.veritas.com/support/en_US/doc/viom_technote_7.4.2.400 

RESOLUTION: N/A 

 * INCIDENT NO:4042366     TRACKING ID:4042365

SYMPTOM: Unable to online/offline VCS service groups using VBS 

DESCRIPTION: If a service group is part of VBS policy then using VBS start/stop operation, you can not online/offline service group. 

RESOLUTION: One flag value was not being handled correctly. 

 * INCIDENT NO:4042371     TRACKING ID:4042370

SYMPTOM: May cause issue with systemctl start/stop of VCS service. 

DESCRIPTION: Use of 'had' command instead of 'hastart' command in sfmh-discovery.pl script. 

RESOLUTION: Changed command from had to hastart. 

 * INCIDENT NO:4042478     TRACKING ID:4042477

SYMPTOM: Can not add MHs to VIOM CMS due to error duplicate id already present in db. 

DESCRIPTION: While adding MH using gendeploy script, you may see that MH is not getting added to CMS. You may see error like duplicate host id is already present in db. To re-add the MH, you need to remove the MH from VIOM CMS first. If you are using vomadm command to remove the MH, it may not work.
The fix is for removing the MH using vomadm cli. 

RESOLUTION: Checking the MH entry in configuration as well as in db. 

 * INCIDENT NO:4042481     TRACKING ID:4042480

SYMPTOM: Some of the binaries in VRTSsfmh package are using older openssl version. 

DESCRIPTION: You may find that few of the binaries in VRTSsfmh package are using older openssl version. 

RESOLUTION: Upgraded openssl version. 

 * INCIDENT NO:4042486     TRACKING ID:4042485

SYMPTOM: N/A 

DESCRIPTION: Terminating VIOM CMS upgrade or VIOM backup/restore procedure in middle can result VIOM CMS running in maintenance mode and VIOM admin may not know about this.
This product enhancement will pop-up a warning message whenever a VIOM user logs in GUI to know if CMS is running in maintenance mode. 

RESOLUTION: N/A 

 PATCH ID:vom-HF0742300

 * INCIDENT NO:4028854     TRACKING ID:4028853

SYMPTOM: Data mismatch in Excel and license report. 

DESCRIPTION: Data of column ncore to license mismatch in Excel generated from Deployment details tab of licensing perspective and "Per core license information" report of licensing perspective. 

RESOLUTION: "Fixed db schema/view" 

 * INCIDENT NO:4028872     TRACKING ID:4028869

SYMPTOM: N/A 

DESCRIPTION: Details on using VIOM Web API are available in technote https://www.veritas.com/support/en_US/doc/viom_technote_7.4.2.300 

RESOLUTION: N/A 

 * INCIDENT NO:4028955     TRACKING ID:4028954

SYMPTOM: In Availability perspective, status of VCS service group was intermittently showing empty for some hosts or all hosts in a cluster. 

DESCRIPTION: VCS Service Groups status in VIOM GUI was intermittently showing empty for some hosts or all hosts in a cluster. 

RESOLUTION: Fix added in sfmh discovery -Triggered VCS rescan after 'hasys -add' operation. 

 * INCIDENT NO:4028959     TRACKING ID:4028958

SYMPTOM: VIOM email notification does not mention the faulted resource name for VCS resource faulted alert. 

DESCRIPTION: Email notification for faulted VCS resource do not mention resource name. 

RESOLUTION: Added the resource name while generating alert in VCS discovery and in alert definition of 'event.alert.vom.vcs.resource.faulted'. 

 * INCIDENT NO:4028969     TRACKING ID:4028968

SYMPTOM: N/A 

DESCRIPTION: You may import your own certificate for xprtld process running on port 5634 on Linux CMS and Linux, Solaris, AIX MHs.

Details on using third party certificate for xprtld process are available in technote https://www.veritas.com/support/en_US/doc/viom_technote_7.4.2.300 

RESOLUTION: N/A 

 * INCIDENT NO:4028998     TRACKING ID:4028997

SYMPTOM: A low privileged user on the Windows system without any privileges in VIOM can create a <drive>:\usr\local\ssl\openssl.cnf configuration file to load a malicious OpenSSL engine resulting in arbitrary code execution as SYSTEM when the service starts. 

DESCRIPTION: On start-up, the VIOM Agent loads the OpenSSL library from \usr\local\ssl. This library attempts to load the \usr\local\ssl\openssl.cnf configuration file which may not exist. On Windows systems, this path could translate to <drive>:\usr\local\ssl\openssl.cnf, where <drive> could be the default Windows installation drive such as C:\ or the current working directory from where the VIOM services / processes are running.  By default, on Windows systems, users can create directories under C:\.  A low privileged user on the Windows system without any privileges in VIOM can create a <drive>:\usr\local\ssl\openssl.cnf configuration file to load a malicious OpenSSL engine resulting in arbitrary code execution as SYSTEM when the service starts.  This gives the attacker administrator access on the system, allowing the attacker (by default) to access all data, to access all installed applications, etc.  
This vulnerability affects Veritas InfoScale Operations Manager (VIOM) and Agents. 

RESOLUTION: Upgraded openssl version. 

 * INCIDENT NO:4029001     TRACKING ID:4028983

SYMPTOM: Tomcat and java Security Updates. 

DESCRIPTION: Tomcat upgraded to 9.0.41 and java to Amazon Corretto java 8.275.01.1 

RESOLUTION: Upgraded tomcat and java to latest version available. 

 PATCH ID:vom-HF0742200

 * INCIDENT NO:4017417     TRACKING ID:4017414

SYMPTOM: json error in Task.pm is seen in log messages. 

DESCRIPTION: During Host family discovery on VIOM servers (CMS and Agents), you may see 'json error in Task.pm'. 

RESOLUTION: Fixed json error 

 * INCIDENT NO:4017420     TRACKING ID:4017419

SYMPTOM: VIOM Web Server does not start at the end of VIOM CMS patch upgrade. 

DESCRIPTION: If customer's own certificate is being used for VIOM web server and the keystore password is different from the default 'changeit', then you may see that VIOM web server is not getting started at the end of VIOM patch upgrade. 

RESOLUTION: Taking backup of server.xml and restoring it after patch upgrade. 

 * INCIDENT NO:4017423     TRACKING ID:4017422

SYMPTOM: You may see this issue on Linux Virtual Machines where VMs are cloned. 

DESCRIPTION: While adding VIOM Agent (Linux VM) to VIOM CMS, getting error "Host is already part of the domain". 

RESOLUTION: Created a unique ID for cloned Linux VMs based. 

 * INCIDENT NO:4017437     TRACKING ID:4017435

SYMPTOM: You are not receiving email alert for VCS cluster down if rule is created under Availability perspective. 

DESCRIPTION: You are not receiving email alert for VCS cluster down if rule is created under Availability perspective. 

RESOLUTION: Added support for sending email alert from Availability perspective for VCS cluster down. 

 * INCIDENT NO:4017442     TRACKING ID:4017440

SYMPTOM: VIOM GUI shows no valid license fault for SFHA 5.1 

DESCRIPTION: VIOM was not able to detect the SFHA 5.1 license key on Windows. 

RESOLUTION: Detected the license key, 

 * INCIDENT NO:4017453     TRACKING ID:4017444

SYMPTOM: Tomcat vulnerabilities reported. 

DESCRIPTION: Tomcat upgrade to 9.0.37.0 

RESOLUTION: Upgraded tomcat version. 

 * INCIDENT NO:4017461     TRACKING ID:4017460

SYMPTOM: N/A 

DESCRIPTION: VIOM does now have three new reports related to VVR in Server perspective.
- VVR replication data status
- Data Replication Status-Weekly
- Data Replication Status-Monthly

Details on new VVR reports are available in technote https://www.veritas.com/support/en_US/doc/viom_technote_7.4.2.200 

RESOLUTION: N/A 

 * INCIDENT NO:4017472     TRACKING ID:4017463

SYMPTOM: N/A 

DESCRIPTION: New CLI to allow VIOM user to -
- Configure LDAP
- Assign permissions
- Unconfigure LDAP
- Change bind user password for already configured LDAP. 

RESOLUTION: N/A 

 PATCH ID:vom-HF0742100

 * INCIDENT NO:4009452     TRACKING ID:4009454

SYMPTOM: "Resize Volume" operation fails for VVR volume, for windows MH. 

DESCRIPTION: VIOM GUI operation "Resize Volume" fails on Windows InfoScale Node when try to resize VVR volume. 

RESOLUTION: Removed the decimal from VVR volume size and round off. 

 * INCIDENT NO:4009466     TRACKING ID:4009463

SYMPTOM: After VIOM patch install on Solaris Agents, 'pkg publisher' command shows Veritas publisher. 

DESCRIPTION: After VIOM patch install on Solaris Agents, 'pkg publisher' command shows Veritas publisher. This publisher should be removed after patch install. 

RESOLUTION: Unsetting publisher once patch is installed. 

 * INCIDENT NO:4009469     TRACKING ID:4009472

SYMPTOM: N/A 

DESCRIPTION: - Java upgrade - Upgrade JAVA version to 1.8.0.252.

- Tomcat upgrade - Upgrade apache tomcat to 9.0.35 as mitigation to CVE-2020-9484 vulnerability.

- SmartIO related fixes 
  1) Cache state update in GUI.
  2) Impact Analysis Chart fix.
  3) Can not create multiple cache on same disk

- VCS Service Group related fixes 
  1) Not able to create link for Service group dependency 
  2) GUI shows firedrill task in RUNNING.

- xprtld service getting timed out after reboot because of slow network service start.

- vomsc status/start/stop command throwing error message.

- Policy signature scan report is giving exception when signature is registered.

- Storage Migration Solution fixes
  1) Multiple volume migration tasks not able to schedule in single operations using migrate by host method.
  2) Not able to do Volume Migration using Migrate Volume by Host method 

RESOLUTION: Fixed above all mentioned issues. 

 * INCIDENT NO:4009471     TRACKING ID:4009470

SYMPTOM: In Deployment, the patch shows as Not Installed though it is successfully installed. 

DESCRIPTION: Sometimes, you may see that VIOM patch installation is successful but when checking in Deployment, the patch shows as Not Installed and hence unable to apply the patch to other MH hosts. 

RESOLUTION: Handled the Json exception. 

 * INCIDENT NO:4009475     TRACKING ID:4009474

SYMPTOM: Sometimes after Windows MH agent reboot, host can be seen in disconnected state in  Settings->Host. 

DESCRIPTION: You can see agent in disconnected state if host has Microsoft Failover Cluster Virtual Adapter. 

RESOLUTION: Skipping the Microsoft Failover Cluster Virtual Adapter from the host GUID. 

INCIDENTS FROM OLD PATCHES:
---------------------------
NONE