[
https://issues.apache.org/jira/browse/CLOUDSTACK-9808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15948928#comment-15948928
]
ASF GitHub Bot commented on CLOUDSTACK-9808:
--------------------------------------------
GitHub user kishankavala opened a pull request:
https://github.com/apache/cloudstack/pull/2023
BUG-ID: CLOUDSTACK-9808 Added system Vm upgrade path for LXC and OVM
`mysql> select id,unique_name,name,type,url,updated,created from
vm_template where type='SYSTEM';
+----+-------------+-------------------------------+--------+-----------------------------------------------------------------------------------------------+---------+---------------------+
| id | unique_name | name | type | url
| updated | created |
+----+-------------+-------------------------------+--------+-----------------------------------------------------------------------------------------------+---------+---------------------+
| 1 | routing-1 | SystemVM Template (XenServer) | SYSTEM |
https://download.cloudstack.org/systemvm/4.10/systemvm64template-master-4.10.0-xen.vhd.bz2
| NULL | 2017-03-30 15:53:00 |
| 3 | routing-3 | SystemVM Template (KVM) | SYSTEM |
https://download.cloudstack.org/systemvm/4.10/systemvm64template-master-4.10.0-kvm.qcow2.bz2
| NULL | 2017-03-30 15:53:00 |
| 8 | routing-8 | SystemVM Template (vSphere) | SYSTEM |
https://download.cloudstack.org/systemvm/4.10/systemvm64template-master-4.10.0-vmware.ova
| NULL | 2017-03-30 15:53:00 |
| 9 | routing-9 | SystemVM Template (HyperV) | SYSTEM |
https://download.cloudstack.org/systemvm/4.10/systemvm64template-master-4.10.0-hyperv.vhd.zip
| NULL | 2017-03-30 15:53:00 |
| 10 | routing-10 | SystemVM Template (LXC) | SYSTEM |
https://download.cloudstack.org/systemvm/4.10/systemvm64template-master-4.10.0-kvm.qcow2.bz2
| NULL | 2017-03-30 15:54:13 |
| 12 | routing-12 | SystemVM Template (Ovm3) | SYSTEM |
https://download.cloudstack.org/systemvm/4.10/systemvm64template-master-4.10.0-ovm.raw.bz2
| NULL | 2017-03-30 15:55:58 |
+----+-------------+-------------------------------+--------+-----------------------------------------------------------------------------------------------+---------+---------------------+
6 rows in set (0.00 sec)
`
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Accelerite/cloudstack CLOUDSTACK-9808
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cloudstack/pull/2023.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2023
----
commit 4795cba0ec86c2e4ffd2da959414deeb15a2c532
Author: Kishan Kavala <[email protected]>
Date: 2017-03-30T11:45:46Z
BUG-ID: CLOUDSTACK-9808 Added system Vm upgrade path for LXC and OVM
----
> 4.9->4.10 upgrade does not upgrade global settings to point to new template
> ---------------------------------------------------------------------------
>
> Key: CLOUDSTACK-9808
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9808
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> 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.org/projects/cloudstack-release-notes/en/4.10/upgrade/upgrade-4.9.html)
> I’ve registered the template with the right naming: "systemvm-kvm-4.10”,
> waited until it was in Ready status.
> Then upgraded management and the cloudstack-agent on all hosts.
> Upon starting the management, the DB upgrade was successful. I’ve logged in
> the system and observed that it was still using 4.6.0 ssvm templates. The
> option to upgrade the VR wasn’t available as well. Checking global settings
> it turns out minreq.sysvmtemplate.version = 4.6.0 and router.template.kvm was
> pointing to the original ssmv template (not systemvm-kvm-4.10). The original
> ssvm template is still in active state but it should be in InActive.
> This basically leaves the user unable to upgrade ssvm (which are not working
> btw) without hacking the DB and global settings
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
