Patch Update for vRealize Suite Lifecycle Manager 2.0

Products

• VMware Aria Suite

Issue/Introduction

Symptoms:

This article contains a list of known issues that are resolved in the latest patch available for vRealize Suite Lifecycle Manager 2.0.

Patch Version: Patch 1

List of issues resolved in this patch:

Resolved Issue/ Added features	Symptoms (or related KB Article)
Disable TLS 1.0 on vROPs	Provide option to disable TLS 1.0 on vROps as part of vROps Deploy / Cluster Expand workflows.
Enable Automatic Failover on vRA Manager Service	LCM should include steps "to enable Automatic Manager Service Fail-over" after installation of vRA product.
vRA deployment manager service VM fails because IIS is not required.	vRA deployment manager service VM fails because IIS is not required.
vRO Package Merge Features.	Merge a custom package directly to the uber package in source control.
Deploy subset of vRO packages to Endpoints	Ability to deploy a subset of vRO Package files to an endpoint.
Capture latest Orchestrator-package from source control.	Latest orchestrator-package capture directly from source control
Domain Name fields to be changed to Hostname to avaoid confusion.	"Domain Name" in vRSLCM Add Certificate task misleads as domain name
Cannot add content endpoint.	Error thrown is 'SyntaxError: Unexpected token will come during performing any operation for content management features.
vRA Install precheck failing with 'Admin role permissions' error.	vRA 7.5 installation precheck in vRSLCM 2.0 fails with "Admin role permission check for the cluster in the given vcenter and data center" even after user is given required privileges. Product deployment fails on VC 6.7 when the custom VC user has used with LCM specific privileges
vRA precheck for IaaS compnoent fails due to ping failure.	Precheck for reachability/existense of IaaS VMs & DNS servers fail in LCM while performing vRA deployment with precheck, if ICMP is disabled for the target VMs causing entire precheck to fail.
vCenter templates deployed to incorrect datastore	Deploy the LCM to a particular data store. Deployment happens to different data store because of the linked vCenter
vRA appliance certificates imported from json overrides UI provided certificate.	Export Configuration of an Environment has certificate details at the node level which overwrites the certificate provided in UI when using that config file in another LCM and makes the deployment fail.
vRA upgrade from 7.4 to 7.5 fails with NULL Pointer Exception.	Case mismatch between the IaaS hostname returned by vRA and the hostname stored in the inventory or it has provided by the user during the deployment, In this case vRA upgrade fails while fetching the VC details specific to that IaaS host and hence the NullPointerException.
vRBC 7.5 standalone install fails.	vRBC standalone deployment is failing because of disabling SSH connectivity in LCM for vRBC, at time of deployment
Deploying a template with the same name to a vCenter results in the same name with appended characters.	if VM template with certain name <Template A> exists in the target VM folder (or as powered off VM with the same name still) and newer version with same name being deployed by vRLCM pipeline – that version *should not* override the original template or rename it to say <Template A _bak> but rather fail the pipeline
Increased Character limit in UI for Certificate/ CSR generation.	Character Length in Certificate generation for CN and certificate alias cannot exceed 20 characters
Component Profile fails to deploy and breaks release process of vRA Blueprints.	This only happens when the "component profile" already exists on the target system we are trying to deploy.
vRA vSphere Agents status is Down due to untrusted SAN Self Signed Certificate deployed by LCM 2.0	VC Endpoint data-collection in vRA fails with untrusted certificate exception when the vRA is deployed through LCM-2.0
vROPs upgrades fail when more than 2 vCenters need to be added for an upgrade.	LCM is extracting data regarding the VM's only from the first two vCenters.
vROPs upgrade from 6.7 to 7.0 fails.	vROps upgrade from 6.7 to 7.0 failed using LCM 2.0. Error "UpgradeVropsValidationTask -  -- Exception encountered java.lang.NullPointerException: null"

Environment

VMware vRealize Suite Lifecycle Manager 2.x

Resolution

To deploy this patch directly from the vRealize Suite Lifecycle Manager appliance, you will want to follow these steps:

1. Snapshot or backup the vRealize Suite Lifecycle Manager instance you intend to upgrade.
2. Log into vRealize Suite Lifecycle Manager.
3. Navigate to Settings > Update.
4. Click on 'Install Patch'. 
5. In the pop up screen, select 'Check Patches Online'.
6. Download the available patch.
7. Click on the Next button to review. 
8. Click Submit to initiate the installation.
9. During patch deployment, UI maintenance page will appear which is the expected behavior.
10. Once install is complete and product is validated as working, remove any snapshots created as best practice.

To deploy this patch from an offline patch, following these steps:

1. Download the patch from https://customerconnect.vmware.com/group/vmware/patch (select vRealize Suite Lifecycle Manager and the 2.0 version).
2. Snapshot or backup the vRealize Suite Lifecycle Manager instance you intend to upgrade.
3. Log into vRealize Suite Lifecycle Manager.
4. Navigate to Settings > Update.
5. Click on 'Install Patch'.
6. Upload the patch you downloaded.
7. Click on the Next button to review.
8. Click Submit to initiate the installation.
9. During patch deployment, UI maintenance page will appear which is the expected behavior.
10. Once install is complete and product is validated as working, remove any snapshots created as best practice.