Did you delete the template? "template 212 is not in store:2"

On Sun, Mar 24, 2024 at 12:47 AM Jimmy Huybrechts <ji...@linservers.com>
wrote:

> Hi Wei,
>
>
>
> See attached error log from when trying to migrate a vm that was migrated
> before from the standalone host.
>
>
>
> --
>
> Jimmy
>
>
>
> *Van: *Wei ZHOU <ustcweiz...@gmail.com>
> *Datum: *zaterdag, 23 maart 2024 om 10:14
> *Aan: *users@cloudstack.apache.org <users@cloudstack.apache.org>
> *Onderwerp: *Re: Migrate migrated instance to another host
>
> Hi,
>
> /var/log/cloudstack/management/management-server.log
> please note the log file is rotated everyday.
>
> -Wei
>
> On Sat, Mar 23, 2024 at 9:34 AM Jimmy Huybrechts <ji...@linservers.com>
> wrote:
> >
> > Hi Wei,
> >
> > I can, if you tell me where to look as I couldn’t find anything on them
> in the logs.
> >
> > --
> > Jimmy
> >
> > Van: Wei ZHOU <ustcweiz...@gmail.com>
> > Datum: vrijdag, 22 maart 2024 om 16:15
> > Aan: users@cloudstack.apache.org <users@cloudstack.apache.org>
> > Onderwerp: Re: Migrate migrated instance to another host
> > Can you share the logs of vm migration and vm import ?
> >
> >
> > On Fri, Mar 22, 2024 at 3:55 PM Jimmy Huybrechts <ji...@linservers.com>
> wrote:
> > >
> > > I’ve migrated vm’s from a remote KVM host which worked fine and they
> run on Cloudstack now.
> > >
> > > However, I just tried migrating one from one cloudstack host to
> another, just like with instances made from a cloudstack host and it’s not
> moving but ending up with an error.
> > >
> > > This is displayed in the webgui:
> > > Failed to migrate VM [VM instance
> {"id":109,"instanceName":"i-8-108-VM","type":"User","uuid":"2fbb0d84-7ea2-4092-aa5d-25a53eb3cda2"}]
> along with its volumes due to [java.lang.NullPointerException].
> > >
> > > Now I’m trying to see in what log the complete error would be but I’m
> coming up blank on which log I need.
> > >
> > > Instances created natively in Cloudstack are migrating just fine, it’s
> only the ones that came from the remote KVM host before.
> > >
> > > --
> > > Jimmy
>

Reply via email to