This way, it seems that you have a bug in CS 4.3.0 when starting a machine that was created from a template that has been deleted.
There will happen a null pointer exception in: “858 - if (volTemplateId != null && volTemplateId.longValue() != template.getId())” The object, “template” is going to be null, because in: “811 - VirtualMachineTemplate template = _entityMgr.findById(VirtualMachineTemplate.class, vm.getTemplateId());” The findById, will add a where clause, looking for template that have the column removed that is null, therefore It will return a null object. On Mon, Jun 16, 2014 at 4:41 AM, Nux! <n...@li.nux.ro> wrote: > Hi, > > You can remove it from the UI, but not directly from the disk as it is > used (in many cases) as a backing file for the VMs spawned from it. > > HTH > Lucian > > -- > Sent from the Delta quadrant using Borg technology! > > Nux! > www.nux.ro > > ----- Original Message ----- > From: "Sanjeev Neelarapu" <sanjeev.neelar...@citrix.com> > To: dev@cloudstack.apache.org > Sent: Monday, 16 June, 2014 5:18:04 AM > Subject: RE: Can we delete a template after a VM is instantiated from it? > > We can delete template without any issues. > > -Sanjeev > > -----Original Message----- > From: Rafael Weingartner [mailto:rafaelweingart...@gmail.com] > Sent: Sunday, June 15, 2014 8:48 PM > To: dev@cloudstack.apache.org > Subject: Can we delete a template after a VM is instantiated from it? > > Hi, > > I was wondering if we can delete a template that has already been used to > instantiate some VMs. > > Would that cause any trouble? > > -- > Rafael Weingärtner > -- Rafael Weingärtner