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

Partially successful scale-out requests causes subsequent requests to fail. (71000)

Last Updated: 8/17/2023Categories: TroubleshootingTotal Views: 21646Language:
Chinese (Simplified)JapaneseEnglish

2 like this article

Subscribe to get an email
newsletter with new updates

2 people found this helpful Please provide article feedback:

Symptoms

A scale-out request competes successfully,  but the additional machines are not created.  Subsequent requests will fail with a cluster size error.

A scale-out request fails with the error of

The data specified within the request is invalid.  Invalid cluster size (8) provided for component [machine-name] of blueprint [blueprint-name] during scale-out operation.  New value must be greater than current cluster size of (10)

Purpose

Cleanup a partially successful scale-out request.

Resolution

SSH to the vRealize Automation Primary Appliance

Login as root

Login to the the vPostgres database vcac as user postgres

su postgres

psql vcac

Run the below query to determine the gap in the cluster within the table comp_component_res

select id, name, cafe_resource_id, cluster_index from comp_component_res where dep_id= '<deployment_id>' and name = '<component_name>' order by name;

To find '<deployment_id>':

select * from cat_resource where name = '<deployment_name>' and parentresource_id is null;

Make sure you get one and only return; If yes, then below query:

select id from comp_deployment where name = '<deployment_name>';

The returned id is '<deployment_id>'.

To find '<component_name>':

You should be able to know the name from UI: Deployments - Components, pick the component name that the scale-out was applied to. See screenshot components.png

Example Output:
<UUID> | test00002947 | <UUID> | 0
<UUID> | test00002948 | <UUID> | 1
<UUID> | test00002949 | <UUID> | 2
<UUID> | test00002950 | <UUID> | 3
<UUID> | test00002951 | <UUID> | 4
<UUID> | test00002952 | <UUID> | 5
<UUID> | test00002953 | <UUID> | 6
<UUID> | test00002955 | <UUID> | 8
<UUID> | test00002960 | <UUID> | 9
<UUID> | test00002985 | <UUID> | 10

In the example output, the gap in the cluster starts with the number "7".

Request a scale-in to the cluster number that is missing in the table.

Using the example: Request a new scale-in request of "7" to destroy virtual machines 8, 9 and 10 fixing the gap.

Using the example:  Request a new scale-out to a value greater than 7 using the vRealize Automation UI.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
配置 pgAdmin 以连接到 vRealize Automation 实例 (71153)

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

KB
•
A solicitação de reconfiguração de máquina virtual é paralisada no estado "Reconfigurando" indefinidamente no vRealize Automation (71246)

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 7.x

Take Our Survey

Support Assistant