afaik not, you can define the new one with the documented name and you're
done.
On Fri, Sep 27, 2013 at 5:49 AM, Indra Pramana in...@sg.or.id wrote:
Dear all,
Would like to confirm on this:
On Wed, Sep 25, 2013 at 7:40 PM, Indra Pramana in...@sg.or.id wrote:
2. Do I need to delete the
Dear all,
I scrutinized the CloudStack management logs during my failed upgrade
attempt from CloudStack 4.1.1 to 4.2.0 and found this on the log:
===
2013-09-24 02:53:56,029 DEBUG [cloud.storage.VolumeManagerImpl]
(secstorage-1:null) Checking if we need to prepare 1 volumes for
because system VM was created using old template?
Dear all,
I scrutinized the CloudStack management logs during my failed upgrade attempt
from CloudStack 4.1.1 to 4.2.0 and found this on the log:
===
2013-09-24 02:53:56,029 DEBUG [cloud.storage.VolumeManagerImpl]
(secstorage-1:null) Checking if we
: Wednesday, September 25, 2013 5:11 PM
To: d...@cloudstack.apache.org; users@cloudstack.apache.org
Subject: Upgrade failed because system VM was created using old template?
Dear all,
I scrutinized the CloudStack management logs during my failed upgrade
attempt from CloudStack 4.1.1 to 4.2.0
: Indra Pramana [mailto:in...@sg.or.id]
Sent: Wednesday, September 25, 2013 5:11 PM
To: d...@cloudstack.apache.org; users@cloudstack.apache.org
Subject: Upgrade failed because system VM was created using old template?
Dear all,
I scrutinized the CloudStack management logs during my failed upgrade
Hi Abhinav,
We are using KVM.
Thank you.
,
Abhinav
-Original Message-
From: Indra Pramana [mailto:in...@sg.or.id]
Sent: Wednesday, September 25, 2013 9:32 PM
To: users@cloudstack.apache.org
Cc: d...@cloudstack.apache.org
Subject: Re: Upgrade failed because system VM was created using old template?
Hi Abhinav,
We are using KVM
Pramana [mailto:in...@sg.or.id]
Sent: Wednesday, September 25, 2013 9:32 PM
To: users@cloudstack.apache.org
Cc: d...@cloudstack.apache.org
Subject: Re: Upgrade failed because system VM was created using old
template?
Hi Abhinav,
We are using KVM.
Thank you.