cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Harikrishna Patnala (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CLOUDSTACK-5690) [Upgrade from 4.2.1->4.3]System VMs and Router VMs are not upgraded to new 64bit templates .
Date Wed, 08 Jan 2014 12:12:52 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-5690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Harikrishna Patnala resolved CLOUDSTACK-5690.
---------------------------------------------

    Resolution: Not A Problem

In 4.3 64 bit system template is used only for routers, this can be done after upgrade using
the configuration parameter router.template.* (xen/vmware/kvm/lxc/hyperv) in zone/Global.

> [Upgrade from 4.2.1->4.3]System VMs and Router VMs are not upgraded to new 64bit templates
.
> --------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-5690
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5690
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          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.	Deploy CS 4.2.1 .Use 32 bit templates.
> 2.	Deploy some VRs.
> 3.	Register 64bit templates.
> 4.	Upgrade to 4.3.
> 5.	Now stop and start(or destroy) the system VMs so that they get upgraded to new 64
bit templates.
> Observation:
> The system VMs are not upgraded to new 64 bit template:
> mysql> select * from volumes where instance_id=5\G;----before destroying
> *************************** 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=14\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 “ No”. 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 bit.
> Attaching the mysql dumps.



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

Mime
View raw message