VMware Cloud Community
dionrowney
Contributor
Contributor

Get-Tag breaks New-VM exceeding http.response.maxSize ?

We have submitted ticket SR 23431262705 but they have not ngot back to us with anything helpful yet.  Has anyone see this problem before?:

We have encountered an issue where we cannot create a new VM in powershell if we have run the Get-Tag commandlet first.

We see this problem in production environment (1500VMs) but not in test (15 VMs).

Example to replicate:

PS C:\Users\> New-VM -Server vcenter.domain.ca -Template linux-rhel-9.2-9 -Name dcimdev96 -ResourcePool VMwareMgtPoolName PowerState Num CPUs MemoryGB
---- ---------- -------- --------
dcimdev96 PoweredOff 2 4.000

PS C:\Users> Get-Tag -Name "No App-Aware Proc"
Name Category Description
---- -------- -----------
No App-Aware Proc Backup Processing Exclude VM from all Application aware processing

PS C:\Users> New-VM -Server vcenter.domain.ca -Template linux-rhel-9.2-9 -Name dcimdev97 -ResourcePool VMwareMgtPool
New-VM : 2023-05-12 2:25:28 PM New-VM One or more errors occurred.
At line:1 char:1
+ New-VM -Server vcenter.domain.ca -Template linux-rhel-9.2-9 -Name dcim ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: ( [New-VM], VimException
+ FullyQualifiedErrorId : Core_BaseCmdlet_UnknownError,VMware.VimAutomation.ViCore.Cmdlets.Commands.NewVM

{code}

We see the following in the lofile: /var/log/vmware/vapi/endpoint/endpoint.log :

2023-05-12T11:50:18.489-06:00 | ERROR | vAPI-I/O dispatcher-1 | SessionFacade | Unexpected error occurred while executing the call with session user@domain.CA (internal id a1a5848b-e788-483d-a4d7-cfad3c930ea8, token
af91b...) for method com.vmware.cis.tasks.list with uuid 01724a48-5ed9-4d59-862b-72919fe323de.
com.vmware.vapi.endpoint.common.UnacceptableResponseException: Response size 7695352b is greater than allowed 7000000b

We thing this may be resolved by setting a value found in: /etc/vmware-vapi/endpoint.properties

http.response.maxSize=7000000

to something larger

but we do not know if this is correct or supported.

The problem occurs to users: Administrator@vsphere.local, other full administrators but not to users who have slightly more limited permissions.

regards.

0 Kudos
0 Replies