Symptoms:
Refer the below table for the issues resolved in this patch for vRealize Suite Lifecycle Manager 2.0
This is a cumulative Patch contains Patch1 and patch2 – Refer Patch Update for vRealize Suite Lifecycle Manager 2.0 (59658) and Patch 2 update for vRealize Suite Lifecycle Manager 2.0 (65098)
 
Patch Version:  Patch 3
 
List of issues resolved in this patch:
 

Row	Summary	Symptom
1	Import vROPS validation for SSH enablement and ROOT credential validation	vROPS any node SSH disabled and ROOT credential invalid for one of the node import was succeeding. We have resolved it in patch3 by failing the import request and asking user to enter correct ROOT credential on retry and enable SSH
2	vRNI deployment fails with vCenter version 6.7u1 and above	vRNI deployment fails with "Duplicate element 'InstanceID'" with vCenter version 6.7u1 and above.
3	Adding VMC NSX data Source to vRNI from vRSLCM	Adding VMC NSX data Source to vRNI from vRSLCM fails
4	Populate release status on post-release stub as part of multi-release	Currently, post-release pipeline running as part of multi-release is populating the request status instead of release status. Enabling post and pre-release, If the post-release is enabled and the background is disabled. We will be able to see the status as true or false in the content pipeline after applyinh the patch 3.
5	LCM is unable to import VROPS - blue Medora custom dashboards with super-metric as dependencies	Unable to capture the custom dashboard which contains super metric as dependencies.
6	Error capturing vRA Composite Blueprint with component profiles as dependencies by enabling includeDependencies	Capturing the composite blueprint with dependencies of automation component profile in the LCM environment will cause this issue.
7	Receiving an error when trying to merge changes to a blueprint	Merging the blueprint is returning an error 405 for PUT. id 405799925 message 405 Method Not Allowed
8	vRO package from a GitLab repository where a workflow name contains a hash "#"	Content checkout will fail when the package name contains "#" character
9	Periodic endpoint connection test, making the endpoint as inaccessible on failure	The endpoint status will be yellow whereas the endpoint is accessible
10	vROps upgrade cannot be completed because vRSLCM doesn't allow option to force re-installation of existing pak and override the initial update attempt	vROPS Upgrade will fail at uploading the .pak file, if the .pak is already uploaded.
11	Pre-check shows failure for vRealize Operations Validations during upgrade to vROps 7.0 but upgrade is successful	When user imports the vROPS which has different root password for each nodes, then the upgrade pre check for vROPS fails due to invalid credentials. Now we have fixed this issue during the import brownfield of vROPS, where the import brownfield of vROPS fails for each node which has different password and user has to provide the correct root password for each failed nodes as part of retry import brownfield request.
12	Importing vROps environment does not pick up all information for remote collectors in another data center, so upgrade fails	If product components are spread across multiple vCenters and if all of the vCenters are not registered in LCM then any subsequent action on the imported product, that concerns each of the product components (upgrade of product, snapshot of the product) fails.
13	Customer preparing for vRA upgrade to 7.5 - LCM incorrectly reporting Java version on IaaS nodes when running 7.5 pre-check	vRA upgrade pre-check does not consider major version of Java, so if minor version of the Java installed in iaaS VM is higher than that of the required Java version, upgrade pecheck shall pass but product upgrade shall fail.
14	vRLCM - Error during vROps upgrade validation with no useful info, does not say which validation check failed	vROps upgrade validation fails without providing any details on which validation step failed. This does not inform user where to look and what to troubleshoot. Here either SSH is disabled or vROps password is updated directly (i.e. not from vRSLCM)

For vRealize Suite Lifecycle Manager Virtual Appliances:
 

Download Filename	vrlcm-2.0.0-PATCH3.patch
Build	12518967
Download Size	654 MB
Checksums	md5sum: cb6e7ac63951cacd30b126e2eb8de38d  sha1sum: f6740a67ffd3db683f5e320dd3d246b684c12f87 sha256sum: 0a779aec9a6bc849d7a78c944b2ea2dd42c0a37b4d0263993432bd914693e1aa

Download and Installation:
If the vRSLCM VA is not connected to Internet, you can download this patch by going to the VMware Patch Download Center and choosing vRealize Suite Lifecycle Manager from the Search by Product drop down. 

If the vRSLCM VA is not connected to Internet, follow the instructions below:

1) Make sure the snapshot of LCM VA is taken 
2) Login inside the LCM VA 
3) Go to setting page->Customer Connect 
4) Download the patch i.e vRealize Suite, version 2.0.0 Patch 3. Make sure the patch is downloaded. 
5)  Navigate to setting tab->update. Click on install patch 
6)  Upload the patch from the local drive. Click on radio button once the patch uploaded is successful 
7) Click on next->next and the submit button. Success message will come for triggering Patch Install
8) Once the patch install gets triggered successfully, UI maintenance page will appear which is the expected behavior.
9) Wait for some time
10) The user will get navigated to LCM UI home page once the process gets completed.

Note: To confirm whether patch got applied successfully, visit LCM UI ‘settings page -> Update Tab’,
and check for System Information which will have applied patch details.
 
If the vRSLCM VA is connected to Internet, follow the instructions below:

1) Make sure the snapshot of LCM VA is taken 
2) Login inside the LCM VA 
3) Go to setting page->update tab 
4) Check for patches online 
5) Click for downloading the patch 
6) Once the patch is downloaded, select the radio button and click on next-next 
7) Click on Submit. Success message will come for triggering Patch Install
8) Once the patch install gets triggered successfully, UI maintenance page will appear which is the expected behavior. 
9) Wait for some time
10) The user will get navigated to LCM UI home page once the process gets completed.

Note: To confirm whether patch got applied successfully, visit LCM UI ‘settings page -> Update Tab’,
and check for System Information which will have applied patch details.