[
https://issues.apache.org/jira/browse/CLOUDSTACK-7959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14234267#comment-14234267
]
Will Stevens commented on CLOUDSTACK-7959:
------------------------------------------
[~rohit.ya...@shapeblue.com] Ok perfect... Ya I just had a look at the code in
4.3 and I think that it is a good idea to make the change in that branch as
well (which will get added to 4.4 with your merge). Since we are more likely
to have some updated build systems now that we are getting more resources from
other places (like CloudOps) for jenkins build slaves, I think it is a good
idea to get this change in now...
Thanks for doing that... Side note (since you are going to have a merge
conflict on this going into 4.4). Is there a reason we keep changing the way
the system vms are named between branches? I know this was frustrating for me
previously when I was trying to find the system vms for different branches. Is
there a reason we keep changing the format between branches? We can't really
change it on previously released branches (without updating all the docs and
such), but going forward we should try to keep a consistent naming system.
> 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)
