Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Patch 1 update for vRealize Suite Lifecycle Manager 2.1 (68067)

Last Updated: 6/6/2019Categories: InformationalTotal Views: 5875Language:
English

2 like this article

Subscribe to get an email
newsletter with new updates

2 people found this helpful Please provide article feedback:

Symptoms

Refer the below table for the issues resolved in this patch for vRealize Suite Lifecycle Manager 2.1

Patch Version: Patch 1

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

4

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

Make sure the snapshot of LCM VA is taken

Login inside the LCM VA

Go to setting page-> Customer Connect

Download the patch i.e vRealize Suite, version 2.1.0 Patch 1. Make sure the patch is downloaded.

Navigate to setting tab->update.Click on install patch

Upload the patch from the local drive. Click on radio button once the patch uploaded is successful.

Click on next->next and the submit button. Success message will come for triggering Patch Install.

Once the patch install gets triggered successfully, UI maintenance page will appear which is the expected behavior.

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.

Make sure the snapshot of LCM VA is taken.

Login inside the LCM VA.

Go to setting page->update tab.

Check for patches online.

Click for downloading the patch.

Once the patch is downloaded, select the radio button and click on next-next.

Click on Submit. Success message will come for triggering Patch Install.

Once the patch install gets triggered successfully, UI maintenance page will appear which is the expected behavior.

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.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
执行与 IPMI 相关的操作时，ESXi 进入无响应状态，且日志报告 IpmiIfcSdrReadRecordId: retry expired (78124)

KB
•
パワーオン状態の仮想マシンへのストレージ ポリシーの適用が、「試みられた操作は、現在の状態（「パワーオン」）では実行できません (The attempted operation cannot be performed in the current state ("Powered on"))」というエラーで失敗する (68164)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

Take Our Survey

Support Assistant