cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-9808) 4.9->4.10 upgrade does not upgrade global settings to point to new template
Date Wed, 08 Mar 2017 10:49:38 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-9808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15901068#comment-15901068
] 

ASF subversion and git services commented on CLOUDSTACK-9808:
-------------------------------------------------------------

Commit 40e49a626fd3266432b6cdaecd54f92ec540f4de in cloudstack's branch refs/heads/master from
[~rajanik]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=40e49a6 ]

Merge pull request #1982 from Accelerite/CLOUDSTACK-9807

CLOUDSTACK-9807/CLOUDSTACK-9808 - Added upgrade changes for 4.10 system vm templateRemoved
systemvm template upgrade code in 4.6 upgrade. Added 4.10 system vm template upgrade changes
with new urls and md5sum

Manual testing results:
Updated min req version:
mysql> select name, value from configuration where name = 'minreq.sysvmtemplate.version';
+------------------------------+----------+
| name                         | value    |
+------------------------------+----------+
| minreq.sysvmtemplate.version | 4.10.0.0 |
+------------------------------+----------+
1 row in set (0.00 sec)

Update template for KVM:
mysql> select * from vm_template where name = 'systemvm-kvm-4.10'\G
*************************** 1. row ***************************
                  id: 201
         unique_name: 201-2-badc363a-507d-3802-942f-205d35c3b575
                name: systemvm-kvm-4.10
                uuid: 3526258d-d9a4-4c3d-8f15-3137eb5d7ab8
              public: 0
            featured: 0
                type: SYSTEM
                 hvm: 1
                bits: 64
                 url: http://packages.shapeblue.com/systemvmtemplate/4.10/systemvm64template-4.10-kvm.qcow2.bz2
              format: QCOW2
             created: 2017-03-02 11:35:06
             removed: NULL
          account_id: 2
            checksum: NULL
        display_text: systemvm-kvm-4.10
     enable_password: 0
       enable_sshkey: 0
         guest_os_id: 184
            bootable: 1
         prepopulate: 0
         cross_zones: 1
         extractable: 0
     hypervisor_type: KVM
  source_template_id: NULL
        template_tag: NULL
            sort_key: 0
                size: 5242880
               state: Active
        update_count: 0
             updated: NULL
dynamically_scalable: 0
1 row in set (0.00 sec)

* pr/1982:
  Bug-ID: CLOUDSTACK-9807: 4.10.0.0 systemvm template upgrade.

Signed-off-by: Rajani Karuturi <rajani.karuturi@accelerite.com>


> 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)

Mime
View raw message