Well after some testing i noticed a few things. If i configure my pools to automatically Delete after logoff, the attached appstack, the .vmdk, GETS DELETED AS WELL! If i set to Refresh after logoff, the appstack stays attached to the linked clone and of course won't attach to another VM when i log in again!
I'm hoping i'm an idiot and some config is totally wrong. Any ideas?
After changing the hypervisor config in Appvolumes Manager to mount over the vCenter (instead of on the hosts) i have the following problem when logging off my view session, when the linked clone is supposed to delete.
VIEW ADMIN:
VCENTER:
VMWARE-VIEWCOMPOSER.LOG
2015-05-13 13:18:24,383 | VC thread | | FATAL | CommonLib.VcSubsystem.LroVcTask - Got VcFault: VMware.Sim.CommonLib.Exception.SimVcSubsystemException: Ein allgemeiner Systemfehler ist aufgetreten: Error deleting disk The disk cannot be deleted. ---> System.Web.Services.Protocols.SoapException: Ein allgemeiner Systemfehler ist aufgetreten: Error deleting disk The disk cannot be deleted. |
--- Ende der internen Ausnahmestapel��wachung ---, Machine Name: vcenter.domain.local, Timestamp: 13.05.2015 11:18:24, App Domain Name: SviWebService.exe, Thread Identity: , Windows Identity: NT-AUTORITŔ\SYSTEM, OS Version: Microsoft Windows NT 6.1.7601 Service Pack 1, vcFaultName: vcFaultDetails: System.Xml.XmlElement for task: task-297041
2015-05-13 13:18:24,383 | VC thread | | FATAL | ServiceCore.Action.VcAction - The VC Operation failed with error: VMware.Sim.CommonLib.Exception.SimVcSubsystemException: Ein allgemeiner Systemfehler ist aufgetreten: Error deleting disk The disk cannot be deleted. ---> System.Web.Services.Protocols.SoapException: Ein allgemeiner Systemfehler ist aufgetreten: Error deleting disk The disk cannot be deleted. |
--- Ende der internen Ausnahmestapel��wachung ---, Machine Name: vcenter.domain.local, Timestamp: 13.05.2015 11:18:24, App Domain Name: SviWebService.exe, Thread Identity: , Windows Identity: NT-AUTORITŔ\SYSTEM, OS Version: Microsoft Windows NT 6.1.7601 Service Pack 1, vcFaultName: vcFaultDetails: System.Xml.XmlElement
====================================================================================================================================
I'm having trouble with Appvolumes since updating to 2.7 (manager, agent and appstacks). Manager is configured for vCenter, the service account has the correct permissions.
Sporadically appstacks will not attach and i'm seeing the following messages in the activity log, any ideas? They appear every 2-5 minutes for different linked clones.
May 13 2015 08:54AM | Unable to find known VM with InstanceUUID "501e3386-14f4-41d2-5b08-09b137f4xxxx" (templates? false) |
May 13 2015 08:54AM | Unable to find "Machine <Appvol-003> (501e3386-14f4-41d2-5b08-09b137f4xxxx)" on "esxi-05.domain.local" -- Using default hypervisor instead |
May 13 2015 08:54AM | Unable to find known VM with InstanceUUID "501e3386-14f4-41d2-5b08-09b137f4xxxx" (templates? false) |
May 13 2015 08:54AM | Unable to find known VM with InstanceUUID "501e3386-14f4-41d2-5b08-09b137f4xxxx" (templates? false) |
May 13 2015 08:54AM | Unable to find "Machine <Appvol-003> (501e3386-14f4-41d2-5b08-09b137f4xxxx)" on "esxi-05.domain.local" -- Using default hypervisor instead |
The agent logfiles are not to be found VMware KB: Location of VMware App Volumes log files in C:\Windows.
Running a Horizon View 6.0.1 environment with linked-clones.
Thanks.
I just recieved an answer from VMware Technical Support:
This issue is resolved in the upcoming release version of AppVolumes 2.9.
I can confirm this issue is fixed in Appvolumes v2.9 (23.06.2015)
Hello,
I had the same problem, all my appstacks deleted with the linked clone. I created different vcenter users for view and for AppVolumes, and I removed all rights for the view vcenter user on the Appvolumes datastores.
this solved it for me.
Kind regards
Cristiano
My guess is a configuration issue of some sort. Are you utilizing Storage Groups? If so, how are they setup?
Hmmm well it was working well before the upgrade.
After re-installing Appvolumes Manager on a fresh DB and not creating any storage groups, everything is working fine again. Very strange...
After configuring Storage groups, the problem occured again!
I've opened a support request.
I'm having the exact same issue. Were you able to get an answer from VMware support?
My posting:
Well after recreating the issue for technical support over webex and lots of analyzing on their side, a PR was opened and engineering is working on a solution.
Last i heard from them was on 29.05.2015, but i can update this thread as soon as i get an answer if you want.
That would be awesome. I appreciate it.
I just recieved an answer from VMware Technical Support:
This issue is resolved in the upcoming release version of AppVolumes 2.9.
I can confirm this issue is fixed in Appvolumes v2.9 (23.06.2015)
Did they give you a good work around until then?
Nope... Thank god we aren't using Appvolumes in production yet (although we were planning on implementing it over a month ago).
App Volumes 2.9 is available, or will be later this evening/tomorrow:
App Volumes 2.9 Now Available! | VMware End-User Computing Blog - VMware Blogs
Great. Just downloaded the new release and will test my scenario on this version.
The following issues were resolved in this release:
Likewise I was also seeing this issue and have been working with support over the last week to try and resolve this. I am in the process of upgrading one of our affected sites and will report back to see if the new version (2.9) has fixed the issues for us.