Yes we have the exact same issue, it's a known issue for as far as I'm aware. Just make sure to raise a ticket with VMware, they are aware.
I reconized that this happens after rebooting the vcenter server.
Why are these "known issues" are not public documented?
Indeed restarting the Vcenter triggers it. Strange thing is that we, at first sight, could not reproduce it on our acceptance environment.
The current workaround for this is:
1:- set env variable AVM_DISABLE_VCENTER_SSL_VALIDATION with value 1 on Management servers
2:- restart the manager service.
can you please describe how to set this value on the appvolumes managers?
I open a command prompt and typed in....
"set env variable AVM_DISABLE_VCENTER_SSL_VALIDATION=1"
Is there an option to check this setting?
- Open Control Panel
- Select System
- Click the Advanced system settings link.
- Click Environment Variables. In the section System Variables, Click
- In the New System Variable window, specify the value of Variable Name as AVM_DISABLE_VCENTER_SSL_VALIDATION and specify the Variable Value as 1
- Click OK. Close all remaining windows by clicking OK.
Had same issue.. this is even more fun when running multiple vCenters under the same SSO...
Then you get the intermediate cert presented instead of the vCenter certs. Causing duplicate cert entry in the database.
This even causes that only one vCenter will work and the others will fail to even mount App Stacks.
Thankfully this quick bypass solves it and will be patched in 2.13
Thanks a lot techguy129! This seems to solve the issue.
I just heard from VMware that this is indeed a know bug.
A hot patch is available, but needs to be requested separately from VMware Global Support.
The issue will be resolved in a future version of App Volumes
If it is the 184.108.40.206 hotfix no need to ask for it. We tested it on our managers but still see this specific error message popping up.
We are now running 220.127.116.11 agent (which works quite well just not with all 2.9 appstacks) and 18.104.22.168 manager. For me it seems to be the most stable and quickest combination until now. And believe me I have seen a few .
This issue has been addressed and deploying the most recent version of App Volumes would provide a more secure option.
Senior Product Manager, App Volumes