Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Thu, 16 Jan 2014 05:11:21 +0000 (UTC)
From: "prashant kumar mishra (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12686832.1388481548726.14123.1389849081754@arcas>
In-Reply-To: <JIRA.12686832.1388481548726@arcas>
References: <JIRA.12686832.1388481548726@arcas>
Subject: [jira] [Reopened] (CLOUDSTACK-5690) [Upgrade from 4.2.1->4.3]System
 VMs and Router VMs are not upgraded to new 64bit templates .
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/CLOUDSTACK-5690?page=3Dcom.atl=
assian.jira.plugin.system.issuetabpanels:all-tabpanel ]

prashant kumar mishra reopened CLOUDSTACK-5690:
-----------------------------------------------


> [Upgrade from 4.2.1->4.3]System VMs and Router VMs are not upgraded to ne=
w 64bit templates .
> -------------------------------------------------------------------------=
-------------------
>
>                 Key: CLOUDSTACK-5690
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-569=
0
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the defa=
ult.)=20
>          Components: Upgrade
>    Affects Versions: 4.3.0
>         Environment: upgrade from 4.2.1 to 4.3
>            Reporter: manasaveloori
>            Assignee: Harikrishna Patnala
>            Priority: Critical
>             Fix For: 4.3.0
>
>         Attachments: mysqldump421.dmp, mysqldump43.dmp
>
>
> Steps:
> 1.=09Deploy CS 4.2.1 .Use 32 bit templates.
> 2.=09Deploy some VRs.
> 3.=09Register 64bit templates.
> 4.=09Upgrade to 4.3.
> 5.=09Now stop and start(or destroy) the system VMs so that they get upgra=
ded to new 64 bit templates.
> Observation:
> The system VMs are not upgraded to new 64 bit template:
> mysql> select * from volumes where instance_id=3D5\G;----before destroyin=
g
> *************************** 1. row ***************************
>                         id: 7
>                 account_id: 1
>                  domain_id: 1
>                    pool_id: 2
>               last_pool_id: NULL
>                instance_id: 5
>                  device_id: 0
>                       name: ROOT-5
>                       uuid: 6f324474-5fa5-44cb-8950-d0aced23f334
>                       size: 0
>                     folder: NULL
>                       path: ROOT-5
>                     pod_id: NULL
>             data_center_id: 2
>                 iscsi_name: NULL
>                    host_ip: NULL
>                volume_type: ROOT
>                  pool_type: NULL
>           disk_offering_id: 9
>                template_id: 8
> first_snapshot_backup_uuid: NULL
>                recreatable: 1
>                    created: 2013-12-30 17:22:48
>                   attached: NULL
>                    updated: 2013-12-31 13:24:33
>                    removed: 2013-12-31 13:24:33
>                      state: Expunged
>                 chain_info: {"diskDeviceBusName":"scsi0:0","diskChain":["=
[f672eae0b4003767808fb787a5c04d5f] s-5-VM/ROOT-5.vmdk"]}
>               update_count: 6
>                  disk_type: NULL
>     vm_snapshot_chain_size: NULL
>                     iso_id: NULL
>             display_volume: 1
>                     format: OVA
>                   min_iops: NULL
>                   max_iops: NULL
>              hv_ss_reserve: NULL
> 1 row in set (0.00 sec)
> ERROR:
> No query specified
> mysql> select * from volumes where instance_id=3D14\G;--after destroying.
> *************************** 1. row ***************************
>                         id: 17
>                 account_id: 1
>                  domain_id: 1
>                    pool_id: 2
>               last_pool_id: NULL
>                instance_id: 14
>                  device_id: 0
>                       name: ROOT-14
>                       uuid: d4e8a55a-0cdc-4bbb-bfba-a18f16e29ff9
>                       size: 2097152000
>                     folder: NULL
>                       path: ROOT-14
>                     pod_id: NULL
>             data_center_id: 2
>                 iscsi_name: NULL
>                    host_ip: NULL
>                volume_type: ROOT
>                  pool_type: NULL
>           disk_offering_id: 9
>                template_id: 8
> first_snapshot_backup_uuid: NULL
>                recreatable: 1
>                    created: 2013-12-31 13:24:33
>                   attached: NULL
>                    updated: 2013-12-31 13:26:13
>                    removed: NULL
>                      state: Ready
>                 chain_info: {"diskDeviceBusName":"ide0:1","diskChain":["[=
f672eae0b4003767808fb787a5c04d5f] s-14-VM/ROOT-14.vmdk"]}
>               update_count: 2
>                  disk_type: NULL
>     vm_snapshot_chain_size: NULL
>                     iso_id: NULL
>             display_volume: 1
>                     format: OVA
>                   min_iops: NULL
>                   max_iops: NULL
>              hv_ss_reserve: NULL
> 1 row in set (0.00 sec)
> ERROR:
> No query specified
> Note:
> For Router VMs the field requires upgrade is set to =E2=80=9C No=E2=80=9D=
. So there is no option to upgrade the VR to new 64 bit template.
> Even after stop and start of the VR the template is not upgraded to 64 bi=
t.
> Attaching the mysql dumps.


--
This message was sent by Atlassian JIRA
(v6.1.5#6160)