Today I was talking to one of our field folks and he asked if there was an issue with Tags in combination with vCLS VMs in 7.0 U2b specifically. I had tested assigning tags to vCLS VMs before, and it worked just fine. With 7.0 U2b unfortunately this has stopped working. The error you will see displayed in the vSphere Client is the following:
(vmodl.fault.SecurityError) {
faultCause = null,
faultMessage = null
}
Or as it shows in the UI:
So what can you do about it? Well, unfortunately not much right now, I filed a bug and uploaded the logs, engineers are looking at it as we speak, and hopefully, I will have an answer for those who need to use tags soon.
UPDATE: Engineering has found a workaround, customers who can’t wait for the fix can contact GSS to get the workaround implemented!
Hi Duncan,
What is a use case where one might need to tag these VMs?
Some people tag them for reporting/automation purposes, it makes it easier for them to identify/filter out these VMs.
We use tags to control the backup. Sometimes admins forget to set a tag for new machines. In this case we have a job “No tags” to warn the admins. Of course now all vcls VMs trigger this warning every day. Not a big problem, but annoying.
That’s interesting. I just notified Rob about an issue with vCLS VMs in RVTools after upgrading vCSA to 7.0 U2b, and he told me that this turned out to be a security issue. What I didn’t have the chance to do yet, is to test whether a user with admin rights on the vCSA will work.
I suspect that these will be some more minor issues popping up, as this appears to be a permission problem for the vCLS VMs.
Thanks for this. I have this issue right now! SR 21221505105 if you’re interested!
Thanks, will follow the SR!
I found the work around by powershell
Get-TagCategory -Name “XYZ” | New-Tag -Name “Deen Dayal”