Running App Volumes v2.16.0.62.
I have created a custom Writable_Template and uploaded it to the "cloudvolumes\writable_templates" folder. After that i was able to create several Writable volumes for a few test users based on the new template, and all seems to work like a charm.
For the second time now i have noticed that my custom template has been deleted automatically overnight, it is not selectable as tamplate while creating a new Writable Volume and when browsing the datastore i can see that de actual .vmdk file had been deleted from the "cloudvolumes\writable_templates" folder.
Why is this happening and how can i stop this behaviour? It is killing my setup and planning atm...
We are using another template as well and are also using 2.16 manager so it does not seems to be a bug (not 100% sure though).
Is there anything you can find in the server log? Normally I would suggest that, even if it is a cleanup action, it should be stored in the log file on the manager.
Forgot to mention that i indeed checked the manager logs and was not able to find any relevant entries.
If there is no logging in the manager my guess is that it might a storage action, might that be the case?
Is there a machine that the template is still attached to and that machine is being refreshed or deleted and thus deleting the writable as well?
In the past we have seen writables being deleted when a user logged out and the VDI machine was being deleted before Appvolumes could reconfigure the machine and detach the writable.
As far as i am aware of, no the is not machine this template is attached to.
Just to make sure i followed the right procedure. I made a filecopy of an existing template, attached the copy to a clean windows machine, made my alterations and copied the new template to the templates folder.
I am in the process of recreating the template so lets see..
Seems legit yeah.. If you can use the template to create a writable the process worked..