Hello all,
we have an issue with the Get-TagAssignment command using the new PowerCLI 6.5R1 and a vCenter 6.5
While executing the command, the powershell windows will freeze without any option to cancel the command.
Only possible solution is kill the powershell and restart all over.
What I'm doing is the following:
- connect the vCenter server "Connect-viserver XXXXXXXXX"
- get-vm as a test to see if there is a connection
- $VM = get-vm YYYYYYYYY
- Get-TagAssignment -Entity $VM
FREEZE
Anybody else got some issues with this Get-TagAssignment command?
Tx!
This is most likely due to an expired certificate on the VC you're connecting to. We've seen this happening before.
Try setting your InvalidCertificateAction to Ignore: VMware PowerCLI – Suppress vCenter Certificate warnings – Pragmatic IO
It's a bug that we'll be addressing soon (hopefully with the next release already). Until then - use the configuration to ignore these warnings as a workaround
Cheers,
Alex
Hello Akolev,
tx a lot for the response!
I've tried your solution and it didn't solve the issue.
what I had to do was use the FQDN of the vcenter instead of the hostname itself.
Then it works.
Tx!
Tim
Out of curiosity, isn't that indicating a DNS resolution/suffix issue or a certificate friendly name issue?
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference
Yeap, got the same senario vsphere 6.5 and powercli 6.5 release 1
Get-Tag hangs unless I connect the vCenter with FQDN...
Just as an extra confirmation, using the FQDN instead of the hostname will indeed solve the problem.
Try to use this as workaround :
1. do: Set-PowerCLIConfiguration -InvalidCertificateAction Ignore -Scope User
2. restart powercli
3. try get-tag again
Paul