VMware Cloud Community
internetrush
Contributor
Contributor

New-ResourcePool Broken

Tried to create a resourcepool as seen below:

Get-PowerCLIVersion

PowerCLI Version

----------------

   VMware vSphere PowerCLI 5.8 Release 1 build 2057893


$CLuster | gm

   TypeName: VMware.VimAutomation.ViCore.Impl.V1.Inventory.ClusterImpl

New-ResourcePool -Confirm:$false -Location $Cluster -Name $name

New-ResourcePool : 12/12/2014 1:24:00 PM    New-ResourcePool        The operation is not supported on the

object.   

At line:1 char:17

+ New-ResourcePool <<<<  -Confirm:$false -Location $Cluster -Name $name

    + CategoryInfo          : NotSpecified: (:) [New-ResourcePool], NotSupported

    + FullyQualifiedErrorId : Client20_ComputeResourceServiceImpl_NewResourcePool_ViError,VMware.VimAutom

   ation.ViCore.Cmdlets.Commands.NewResourcePool

According to this it should accept base resource pool hosts or clusters:

vSphere 5.5 Documentation Center 

Ive tried all 3 and nothing. Also only connected to only one vCenter as ive seen that problem as well.

Any suggestions?

0 Kudos
6 Replies
internetrush
Contributor
Contributor

Also: PS:

PS C:\temp>>> $name

GeneralPop

0 Kudos
LucD
Leadership
Leadership

Is DRS activated on the cluster ?


Blog: lucd.info  Twitter: @LucD22  Co-author PowerCLI Reference

0 Kudos
internetrush
Contributor
Contributor

Yes DRS is enabled.

0 Kudos
LucD
Leadership
Leadership

Is your default connection perhaps to an ESXi instead of a vCenter ?

Do a

$global:defaultviserver

and

$global:defaultviservers


Blog: lucd.info  Twitter: @LucD22  Co-author PowerCLI Reference

0 Kudos
internetrush
Contributor
Contributor

Hey Luc,

I had sumilar thoughts, was only attached to one and only one vcenter server.

$global:defaultviserver

Name                           Port  User                     

----                           ----  ----                     

vcentertest                    443       - Edited user.

Here we go...

$Global:DefaultVIservers

Name                           Port  User                      

----                           ----  ----                      

vcentertest                    443                 

vcentervsfrk                   443          

vcentervsmke                   443                  

For some reason it is connecting me to all 3 even though im only saying to connect to one. Is there any way to force it not to connect to all of them?

connect-viserver -Server 'vcentertest' -Credential $admin -AllLinked:$false

Yields the same results.

EDIT:

Got it to only one vi server by ensuring that it is only one that is connected to manually:

Hit Line breakpoint on 'C:\temp\test.ps1:206'

New-ResourcePool : 12/15/2014 7:20:06 AM    New-ResourcePool        The operation is not supported on the obje

ct.  

At C:\temp\test.ps1:87 char:31

+             $newPool = New-ResourcePool <<<<  -Confirm:$false -Location $Cluster -Name $name

    + CategoryInfo          : NotSpecified: (:) [New-ResourcePool], NotSupported

    + FullyQualifiedErrorId : Client20_ComputeResourceServiceImpl_NewResourcePool_ViError,VMware.VimAutomatio

   n.ViCore.Cmdlets.Commands.NewResourcePool

[DBG]: PS C:\temp>>> $global:DefaultVIServer

Name                           Port  User                        

----                           ----  ----                        

vcentertest                    443      

___________________________________________________________________________________________________________

[DBG]: PS C:\temp>>> $global:DefaultVIServers

Name                           Port  User                        

----                           ----  ----                        

vcentertest                    443                       

Still get the same problem.

0 Kudos
LucD
Leadership
Leadership

I already asked about DRS, but I assume the license is ok as well.

See KB1004098


Blog: lucd.info  Twitter: @LucD22  Co-author PowerCLI Reference

0 Kudos