Thank you Slavka,
The template is already named that way: https://imgur.com/aVQLpSY
From the screenshot you can see 2 entries - first one is the old 4.15
template and the second one is the new 4.15.1 template set with proper name.
Is there any other place the name should be changed?
Best regards,
Jordan
-----Original Message-----
From: Slavka Peleva <slav...@storpool.com.INVALID>
Sent: Monday, October 18, 2021 12:38 PM
To: users@cloudstack.apache.org
Subject: Re: Cloudstack 4.15.2 upgrade fail
[X] This message came from outside your organization
Hi Yordan,
During the upgrade, CloudStack is looking for a specific template name -
"systemvm-xenserver-4.15.1". You can rename the uploaded template directly in
the DB, or I think you have to set for template's name -
"systemvm-xenserver-4.15.1" while uploading it.
Best regards,
Slavka
On Mon, Oct 18, 2021 at 12:12 PM Yordan Kostov <yord...@nsogroup.com> wrote:
> Hello everyone,
>
> Environment is 4.15.0 ACS on Centos 7 in HA setup on
> 3 node galera cluster managing XCP-NG hosts.
> Today I performed upgrade of ACS from to 4.15.2 as per
> this guide
> https://urldefense.com/v3/__http://docs.cloudstack.apache.org/en/lates
> t/upgrading/upgrade/upgrade-4.15.html__;!!A6UyJA!1XHKwiVUKxx9w1MZaZS2G
> n9gPDucxWw1w3wUXtx5wMFBlhYesJ5XbhTbeMakyy3EhaJ2P4styS-H$
>
> After upgrade the management service is running but GUI gives this error:
> HTTP ERROR 503 Service Unavailable
> URI:
>
> /client/
>
> STATUS:
>
> 503
>
> MESSAGE:
>
> Service Unavailable
>
> SERVLET:
>
> -
>
>
> In management-server.log I see this error pops after starting the service:
> 2021-10-18 11:04:55,142 ERROR [c.c.u.DatabaseUpgradeChecker]
> (main:null)
> (logid:) Unable to upgrade the database
> com.cloud.utils.exception.CloudRuntimeException: 4.15.1.0XenServer
> SystemVm template not found. Cannot upgrade system Vms
>
> I do registered the template upload as per the guide steps.
>
> Any advice?
>
> Best regards,
> Jordan
>
