Updated on:  25 June 2019

vRealize Suite Lifecycle Manager 2.1 |  May 14, 2019 

Check for additions and updates to these release notes.

Patches in vRealize Suite Lifecycle Manager

This section contains information about patch 1 in vRealize Suite Lifecycle Manager 2.1. 

Symptoms

This section discussed prerequisites, download instructions, and other things a user should know before installing the software.

List of issues resolved in this patch: 

Row Summary Symptom
1 vRA upgrade pre-check ignores the Iaas VM where only management agent is installed Upgrade pre-check fails with error vRA inventory and vRSLCM inventory mismatch if the Iaas VM has only management agent installed. This is not true for any of the components installed in Iaas VM other than management agent
2 Java version precheck is not done during upgrade precheck via vRSLCM as the precheck and remediation will be taken care by vRA Upgrading vRA from vRSLCM pre-check fails with Java 8 update 201 or later must be installed.
3 If shortname is used for accessing vRSLCM, user were hitting authentication issue to login Authentication issue while using the short host name to access vRSLCM UI
LCM UI freezes and has issue when engine is not running LCM UI looks distorted with several tabs collapsed when engine is not running
5 Scale out of vRLI is failing, if it is imported with load balancer vRLI imported with cluster VIP, on scaling out fails with membershipApplicationCannotJoinThroughVirtualAddress
6 Test and release of the content will fail if the content is deleted from VRA endpoint

Whenever an end user deleted any BP and trying to release the same BP from LCM again. Below error will appear

optimistic locking failed; nested exception is org.hibernate.StaleObjectStateException: Row was updated or deleted by another transaction (or unsaved-value mapping was incorrect) : [com.vmware.vcac.composition.domain.CompositeBlueprint#vSphereEmptyVM]","moreInfoUrl":null}]} verify if the dependencies of the content are released successfully or already available in the endpoint

7 Behavior change in post and pre stubs in content pipeline page from 2.0 to 2.1 Extensible of pipeline using the "packageVersionLink" input is in a different format in each pipeline stub. In post-capture it has ", " in front of the url, in post-release it has square brackets around the URL.
8 LCM 2.1 / Can't deploy vRO content to any endpoints / Error While parsing dunes-meta-inf.xml file Whenever we will release the vro content to any of the vro endpoint. We will see the below error in the log.{"timestamp":"2019-04-30T06:10:56.844+0000","status":500,"error":"Internal Server Error","message":"[Error While parsing dunes-meta-inf.xml file : java.net.ConnectException: Connection timed out 
9 Failed to deploy the content whose name contain the special character as "&" When the Composite Blueprint Name contains special characer like "&" then the capture is failing with the following error Content Capture failed for [Automation-CompositeBlueprint/AD&M Win2012R2 Server] [v2] from end-point"XYZ" with error 400 400, Error : {"errors":[{"code":10101,"source":null,"message":"Invalid argument.","systemMessage":"System request parameter $filter=(name eq 'AD is not properly formatted. Details: String index out of range: 12.","moreInfoUrl":null}]}
10 When you perform capture and test, the endpoint(staging environment) listing is not considering the policy 'sourceControlEnvironment' Whenever any endpoint is marked as Source controlled. It will not be considered during the listing of an endpoint during the add content page
11 Issues identified on backend while running unit tests
  1. Pipeline status is updated based on the success/failure of the last unit test workflow
  2. Stop on first failure flag is not considering on unit test
  3. A version should be marked as tested only if there no test failures
  4. Activity log on the parent is showing as completed even if there are test failures
12 VIDM AD over IWA directory addition is failing from LCM when Windows Connector is used. VIDM AD over IWA directory addition is failing from LCM when Windows Connector is used.
Connector Configuration:
  1. Windows and Embedded Linux connector is supported.
  2. Windows Connector support is limited to the following scenarios
  Supported:
  1.  Import vIDM having AD configured with windows connector and then add the AD from vRLCM.
  2.  vIDM with multiple windows connectors configured to different AD's.
  3.  Edit/Delete of AD configured on windows connector from vRLCM
   Not Supported:
  1.      Configuration(new) of AD on windows connector from vRLCM not supported
  2.      Clustered Windows Connectors not Supported.
  3.      Installation of windows connector from vRLCM.
  4.      Upgrade of Windows connector
  5.      Replace certificate on windows connector from vRLCM
  6.      Connector Selection from vRLCM.

Resolution

For vRealize Suite Lifecycle Manager Virtual Appliances

Download Filename vrlcm-2.1.0-PATCH1.patch
Build 13664521
Download Size  623 MB
Checksums
md5sum: e2e156d44900dd70e95f37dc8f84a161  
sha1sum: 9c5dff36f3d8440b0a04c5e825d05fd9e46cdab1 
sha256sum: 4d7c27536811e3e4be037d6d3e21c8b9d4ba0329c61b0d92d610b4788832d220

 

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-> MyVmware
  4. Download the patch i.e vRealize Suite, version 2.1.0 Patch 1. 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, 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 instruction 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, 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.

check-circle-line exclamation-circle-line close-line
Scroll to top icon