Quantcast
Channel: VMware Communities : All Content - All Communities
Viewing all articles
Browse latest Browse all 175326

Weird Get-TagAssignment bug

$
0
0

I've got two VCSAs at 6.5 build 5705665. When I run the following, I get the error noted below:

 

Commads:

Connect-VIServer vcsa1.blah.local

Connect-VIServer vcsa2.blah.local

$VCTags = Get-TagAssignment -Server vcsa1.blah.local

 

Output:

Name                           Port  User                         

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

vcsa1.blah.local  443   BLAH\user           

vcsa2.blah.local  443   BLAH\user           

Get-TagAssignment : 6/22/2017 1:55:51 PM Get-TagAssignment Sequence contains more than one matching element

At line:4 char:12

+ $VCBTags = Get-TagAssignment -Server vcsa1.blah.local

+            ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    + CategoryInfo          : NotSpecified: (:) [Get-TagAssignment], CisException

    + FullyQualifiedErrorId : VMware.VimAutomation.ViCore.Impl.V1.Service.Tagging.Cis.TaggingServiceCisImpl.GetTagAssignment.Error,VMware.VimAutomation.ViCore.Cmdlets.C

   ommands.Tagging.GetTagAssignment

 

 

I can disconnect from vcsa2 and run the Get-TagAssignment cmdlet successfully against vcsa1. The error only occurs when simultaneously connected to these two servers. I have one other 6.5 build 5705665 VCSA and any combination with it and the other two doesn't result in the error. I also have some 5.5 vCenters on Windows and can't reproduce the error with any combination of those and 6.5 servers.

 

I've reproduced from Windows Server 2012 R2 (PowerShell 4.0, PowerCLI 6.5R1) and Windows Server 2016 (PowerShell 5.1, PowerCLI 6.5.1).

 

Can anyone else reproduce this?

 

Message was edited by: dbailey12


Viewing all articles
Browse latest Browse all 175326

Trending Articles