Remove-TagAssignment not workig but no error appears

[Torrent007]

Hi all !

I'm trying to clean up some tag assignement with PowerCLI on VM but I'm in front of a misterious behaviour

This behaviour appears on a lot of VM (not all) and I did not find a common point between them...

In more, when I clean tag assignement in web client, that's work...

Have you any idea on it guys ?

Thanks in advance !

Fabien

[LucD]

Which PowerCLI version are you using?

[Torrent007]

Hi LucD,

From Get-PowerCLIVersion command:

My vCenter version:

6.5.0.10964411

[LucD]

I can't recreate what you are seeing.

For me the Tag assignment removal works like expected.

Did you stop/start your PS/PowerCLI session before doing a test?

[Torrent007]

Yes I tried, and a vCenter restart, but no effect

If you've no idea, I will open an official case to VMware about it so.

That's a strange behaviour...

[Torrent007]

I tried with a colleague with a PowerCLI version of  VMware PowerCLI 11.2.0 and that's works.

I'try to donwgrade from VMware PowerCLI 11.5.0 to VMware PowerCLI 11.2.0 and come back with result.

[LucD · Accepted solution]

The PowerCLI Change Log mentions that in 11.5.0 the Remove-TagAssignment cmdlet was changed for a performance improvement.
That might have broken something (in some situations).

[Torrent007]

Hi,

I tried since 2 hours to uninstall/reinstall right version of PowerCLI but no way to delete completely 11.5...

I tried:

(Get-Module VMware.PowerCLI -ListAvailable).RequiredModules | Uninstall-Module -Force
Get-Module VMware.PowerCLI -ListAvailable | Uninstall-Module -Force

Then:

Install-Module -Name VMware.PowerCLI -RequiredVersion 11.2.0.12483598

I also tried to cleanup directories without more success

Still on it

EDIT: Just saw this script you worked on:

Obtaining Specific PowerCLI Versions from the PowerShell Gallery - VMware PowerCLI Blog - VMware Blo...

Will try it and come back asap

Thanks,

F.

[LucD]

First check where the PowerCLI modules are located with

Get-Module -Name VMware* -ListAvailable

If they are in any of the Program Files or Windows folders, not your personal folders, you would probably need to use a PowerShell session started as Administrator.
But just deleting the PowerCLI folders (make sure you have all of them, also the ones in different paths) should be sufficient.

[Torrent007]

I tried (I'm not bad in powershell) but no effect.

Issue may be at installation, as mentionned on a script you worked on:

Obtaining Specific PowerCLI Versions from the PowerShell Gallery - VMware PowerCLI Blog - VMware Blo...

I'm trying this script and come back asap

Thanks for your constant help

F.

[LucD]

An alternative is to use the ZIP file for 11.2.0.

[Torrent007]

Your script resolved my version issue.

And this 11.2 version resolve my tag assignment issue !

Thanks for your help, it's OK for me.

Last question, have you any access to a bug reporter VMware to alert on it LucD ?

[LucD]

I'm afraid not.

You have a couple of options,

1. Open a SR with VMware.
   They might say that you a Developer Support contract, but that is not true if the issue is really a PowerCLI bug. Refer to PowerCLI Support Breakdown​
2. Launch a PowerCLI Idea. And though not really intended for reporting bugs, I have it has been used for that before. A good idea would be to ask VMware to launch a Bug Reporting site (or vote for Online repository with known issues (and fixes) for | VMware PowerCLI )
3. Contact one or more VMware persons that revolve around PowerCLI. A good way is to use the VMware Slack channel that has a PowerCLI channel. You can ask an invite here.
4. Use social media and put one of the PowerCLI powers-that-be in Cc. For example tweet with @PowerCLI, @kmruddy (or @kyleruddybeard) or @jakerobinson in Cc

[Torrent007]

Okay, I'll tweet them so

[greedj1]

I am also seeing this bug with the same version of powercli.

[LucD]

Do you have the option to upgrade to PowerCLI 12.0?