VMware Cloud Community
WuGeDe
Enthusiast
Enthusiast
Jump to solution

vCLS VM setting tag fails with error

Hi guys
I need to tag my vCLS VMs.
But if i try to it fails with error.
I recently updated the vcsa from 7.0.1 to 7.0.2.00200.
With the old version I had no problem tagging that VMs.

Error message:

Operation failed!

(vmodl.fault.SecurityError) {
faultCause = null,
faultMessage = null
}

 

 

Whats wrong?

Tags (1)
0 Kudos
1 Solution

Accepted Solutions
depping
Leadership
Leadership
Jump to solution

this is a known issue, fix is being worked on. if you need this solved, please contact GSS.

https://www.yellow-bricks.com/2021/06/01/issue-adding-tags-to-the-vcls-vms-with-vcenter-server-7-0-u...

View solution in original post

12 Replies
depping
Leadership
Leadership
Jump to solution

this is a known issue, fix is being worked on. if you need this solved, please contact GSS.

https://www.yellow-bricks.com/2021/06/01/issue-adding-tags-to-the-vcls-vms-with-vcenter-server-7-0-u...

WuGeDe
Enthusiast
Enthusiast
Jump to solution

Thank you for your reply.

But that really sucks. 

Another customer has already a case number SR 21221505105
I will open a case too at vmware global support services and point on the mentioned SR.

0 Kudos
depping
Leadership
Leadership
Jump to solution

I spoke with the engineering team and they have a work-around, so GSS should be able to solve it.

WuGeDe
Enthusiast
Enthusiast
Jump to solution

That is good news. Thanks again! 👍

0 Kudos
depping
Leadership
Leadership
Jump to solution

I can send you the internal reference so you can point GSS to it... will send you a DM.

WuGeDe
Enthusiast
Enthusiast
Jump to solution

I appreciate your help! Thank you!

I added that to the support request.

0 Kudos
WuGeDe
Enthusiast
Enthusiast
Jump to solution

@depping I had a Zoom call with the support today and we fixed the issue pretty quick with the help of your information.
It is a pretty straight forward fix. It is temporary for now.
They said the issue will be solved in the next release / vcsa update in July.
Thank you for your help again! 👍

0 Kudos
depping
Leadership
Leadership
Jump to solution

Yeah the fix is easy indeed. thanks for reporting back!

0 Kudos
alissonvaz
Contributor
Contributor
Jump to solution

hello guys,

I was facing this same issue using vCenter on release 7.0.2.00400 (current).

Recently, we've configured vCenter Linked Mode, and I think the issue started to be shown after that.

I tried a lot of things to solve, but the one that really work, was just disconnect the host, remove from inventory and connect again!

I found this solution based on logs, (/var/log/vmware ]# tail -f messages)

Regards!

0 Kudos
gallaghermi
Contributor
Contributor
Jump to solution

I still have this issue even after upgrading to vCenter 7.0 Updates 3c. Do the hosts need to be upgraded as well?

 

I opened case and support told me he knew nothing about this and your not supposed to tag the vCLS VMs.

0 Kudos
WuGeDe
Enthusiast
Enthusiast
Jump to solution

@gallaghermi & @alissonvaz if it helps you could mention my support request. SR#21232457206

0 Kudos
DMWayne
Contributor
Contributor
Jump to solution

Has this actually been fix in the more recent releases yet?

0 Kudos