You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "adam wojnarski (JIRA)" <ji...@apache.org> on 2013/12/02 15:12:35 UTC

[jira] [Commented] (CLOUDSTACK-5294) showing wrong template size 755.64 TB as in CLOUDSTACK-4249

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

adam wojnarski commented on CLOUDSTACK-5294:
--------------------------------------------

any chance for this to be fixed?

> showing wrong template size 755.64 TB as in CLOUDSTACK-4249
> -----------------------------------------------------------
>
>                 Key: CLOUDSTACK-5294
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5294
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Install and Setup, Management Server
>    Affects Versions: 4.2.0
>            Reporter: adam wojnarski
>            Priority: Critical
>              Labels: secondary, storage, template
>
> CLOUDSTACK-4249 is reported to be fixed. It is not! I installed the newest available version (rpms built from source) and the bug is still present. I fallowed the instalation steps precisely and everything else is ok. I tried contacting the resolver via mail but got no responce.
> I have my template disk in raw, converted with qemu-img convert -f raw -O qcow2, works ok with a  regular KVM hypervisor.
> I noticed that in the install manual the command to download the system template is /usr/lib64/cloud/common/scripts/storage/secondary/cloud-install-sys-tmplt -m /mnt/secondary -u http://d21ifhcun6b1t2.cloudfront.net/templates/4.2/systemvmtemplate-2013-06-12-master-kvm.qcow2.bz2 -h kvm -s <optional-management-server-secret-key> -F so as far as i understand the secondary storage vm used is prior to this bug fix so it may still be affected by issue 4249. 2013-06-12 is prior to the date of this ticket resolution. 



--
This message was sent by Atlassian JIRA
(v6.1#6144)