Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Thu, 30 Mar 2017 12:06:41 +0000 (UTC)
From: "ASF GitHub Bot (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.13047309.1488374382000.164304.1490875601687@Atlassian.JIRA>
In-Reply-To: <JIRA.13047309.1488374382000@Atlassian.JIRA>
References: <JIRA.13047309.1488374382000@Atlassian.JIRA> <JIRA.13047309.1488374382634@jira-lw-us.apache.org>
Subject: [jira] [Commented] (CLOUDSTACK-9808) 4.9->4.10 upgrade does not
 upgrade global settings to point to new template
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Thu, 30 Mar 2017 12:06:45 -0000


    [ https://issues.apache.org/jira/browse/CLOUDSTACK-9808?page=3Dcom.atla=
ssian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=
=3D15948937#comment-15948937 ]=20

ASF GitHub Bot commented on CLOUDSTACK-9808:
--------------------------------------------

Github user DaanHoogland commented on the issue:

    https://github.com/apache/cloudstack/pull/2023
 =20
    LGTM
    @kishankavala did you check what went wrong with the kvm template. @kar=
uturi reported that and it was probably some auto-conflict-resolution.


> 4.9->4.10 upgrade does not upgrade global settings to point to new templa=
te
> -------------------------------------------------------------------------=
--
>
>                 Key: CLOUDSTACK-9808
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-980=
8
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the defa=
ult.)=20
>          Components: Upgrade
>    Affects Versions: 4.10.0.0
>            Reporter: Boris Stoyanov
>            Assignee: Kishan Kavala
>            Priority: Blocker
>
> Following the same source of information (http://docs.cloudstack.apache.o=
rg/projects/cloudstack-release-notes/en/4.10/upgrade/upgrade-4.9.html)
> I=E2=80=99ve registered the template with the right naming: "systemvm-kvm=
-4.10=E2=80=9D, waited until it was in Ready status.
> Then upgraded management and the cloudstack-agent on all hosts.=20
> Upon starting the management, the DB upgrade was successful. I=E2=80=99ve=
 logged in the system and observed that it was still using 4.6.0 ssvm templ=
ates. The option to upgrade the VR wasn=E2=80=99t available as well. Checki=
ng global settings it turns out minreq.sysvmtemplate.version =3D 4.6.0 and =
router.template.kvm was pointing to the original ssmv template (not systemv=
m-kvm-4.10). The original ssvm template is still in active state but it sho=
uld be in InActive.=20
> This basically leaves the user unable to upgrade ssvm (which are not work=
ing btw) without hacking the DB and global settings=20


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)