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

vRealize Automation 8.1 deployment fails with "client-secrets" does not exist (79609)

Last Updated: 8/18/2023Categories: TroubleshootingTotal Views: 8016Language:
Chinese (Simplified)JapaneseEnglish

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

The issue is present when VMware Identity Manager (vIDM) nodes are configured behind an VMware NSX load balancer

vRealize Automation 8.1 deployment or patch fails with

0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
100 620 100 92 100 528 368 2112 --:--:-- --:--:-- --:--:-- 2489
{"refLink":"/csp/gateway/slc/api/definitions/external/<UUID>"}Error: getting deployed release "client-secrets": release: "client-secrets" not found
sleeping for 8 before upstalling client-secrets
running: helm upgrade --install --timeout=1800 --wait --namespace prelude --set-string

The /services-logs/csp-clients-fixture/csp-clients-fixture.log contains the below entries

"500: Failed to register client with id XXX"

Note: Where XXX refers to a service OAuth2 client ID. This will often be a different client ID on each run.

The identity-service.log contains below entries

"reactor.netty.http.client.PrematureCloseException: Connection prematurely closed BEFORE response"

Cause

By default, NSX-v is closing inactive connections after one second, this causes the Identity service pod HTTP connection to vIDM to be closed while the Identity services' session to remain open and alive.

Resolution

Note: If the Workaround section was implemented previously, remove the workaround described when applying the below fix.

Before proceeding ensure sufficient resources are also assigned to the vIDM nodes as insufficient resourcing on vIDM nodes can produce similar symptoms. For clustered setups minimum recommended resources for vidm nodes is 4CPU 16 GB RAM.

To resolve this issue apply the below settings to the Workspace ONE / vIDM NSX load balancer configuration:

Create a new Add an application rule to the NSX configuration: Add an Application Rule

Set the HTTP Keep-alive to 300s

timeout http-keep-alive 300s

Note: See, Load Balancer HTTP Connection Mode.  You can set a value lesser than 300 due to other application(s) using the NSX load balancer. The Identity service timeout is 15 seconds and vIDM timeout is 20 seconds. Picking a value under 15 seconds will not resolve the issue, and a value between 15 and 20 seconds may prove unstable. If such values are necessary, you may need to apply the workaround described below to completely disable the identity connection pool or fine-tune the identity service keep-alive time.

Workaround

NOTE: The below workaround will not persist through upgrades or patches. Should you wish to upgrade or patch vRealize Automation 8.x after implementing this workaround either follow this article for further updates to the resolution section or alternatively raise a support request to confirm the latest fix by information.

To increase vIDM resources see vRSLCM documentation

Open the deployment configuration file using preferred text editor

vi /opt/charts/identity-service/templates/deployment.yaml

Search for the line

-Dlogging.level.com.zaxxer.hikari.HikariConfig=DEBUG

Below the above entry add the following additional line

-Didentity.rest.max_idle_time=PT0S

Note:  In PT0S it is a zero, not the letter o.  When editing the file use spaces not tabs.  The file is sensitive to text alignment so ensure the lines are aligned correctly.

Confirm the file is configured as below

-Dlogging.level.com.zaxxer.hikari.HikariConfig=DEBUG
-Didentity.rest.max_idle_time=PT0S

Perform this change on each vRealize Automation node.

Re-deploy vRealize Automation by running the deploy.sh script manually or by triggering a retry in the vRealize Suite Lifecycle Manager UI

/opt/scripts/deploy.sh

Related Information

vRealize Automation 8.1 Load Balancing Guide
Deploying the VMware Identity Manager Machine Behind a Load Balancer

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
VMware AirWatch MDM Agent 6.5.11 for Windows Mobile/CE リリースのお知らせ (79610)

KB
•
Workspace ONE Intelligence 2020/06/17 リリースのお知らせ (79631)

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

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Aria Automation

Related Versions:

VMware vRealize Automation 8.1.x

Take Our Survey

Support Assistant