Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Thu, 4 Dec 2014 15:08:12 +0000 (UTC)
From: "Will Stevens (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12756966.1416575034000.75999.1417705692731@Atlassian.JIRA>
In-Reply-To: <JIRA.12756966.1416575034000@Atlassian.JIRA>
References: <JIRA.12756966.1416575034000@Atlassian.JIRA>
 <JIRA.12756966.1416575034961@arcas>
Subject: [jira] [Commented] (CLOUDSTACK-7959) System VMs failing to build
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Will Stevens commented on CLOUDSTACK-7959:
------------------------------------------

[~rohit.yadav@shapeblue.com] To be honest, I have not looked into it.  I am going off the fact that those system vm builds did not break  with the initial change so I was assuming the fix was not needed.  When you made the change, was there a 'compat' option even specified (i doubt it).  I guess the change would be valid if the system vm build machines get upgraded to something that defaults to 1.1 for those builds.  

If we make this change in 4.3, I think we have to notify [~dahn] so he can make the equivalent change in 4.4.  I know he does not want to have changes in 4.3 that do not get pushed into 4.4 as well.

I will have a quick look at 4.3 and 4.4 this morning and see if I think this change should be in those branches...  I will post back in a bit...

> System VMs failing to build
> ---------------------------
>
>                 Key: CLOUDSTACK-7959
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7959
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>    Affects Versions: Future, 4.5.0
>            Reporter: Will Stevens
>            Assignee: edison su
>             Fix For: Future
>
>
> The system vm builds are failing on Jenkins for the '4.5' and 'master' branches.
> The reason they are failing is because of the following.
> In file: tools/appliance/build.sh b/tools/appliance/build.sh
> In function: kvm_export()
> The line: 
> qemu-img convert -o compat=0.10 -f raw -c -O qcow2 raw.img "${appliance_build_name}-kvm.qcow2"
> Is throwing an "unknown option 'compat'" error.
>   


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)