cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Prasanna Santhanam (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (CLOUDSTACK-4082) vhd-utils download used by developers is stale
Date Fri, 09 Aug 2013 08:58:48 GMT

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

Prasanna Santhanam reassigned CLOUDSTACK-4082:
----------------------------------------------

    Assignee: Donal Lafferty  (was: Prasanna Santhanam)

Looking at your blogpost http://dlafferty.blogspot.co.uk/2013/08/using-cloudstacks-log-files-xenserver.html
and the scripts for copy_vhd_(to|from)_secondarystorage.sh the -S option is never utilized
in 4.2 in either scripts. 

>From the logs on your blogpost it appears that you are running with master. Does this
really affect 4.2? If so - can we have the full SMlog attached. I see you've snipped out operations
in the VMOps plugin that define the params for entry into vhd-util. Having those would help.
                
> vhd-utils download used by developers is stale
> ----------------------------------------------
>
>                 Key: CLOUDSTACK-4082
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4082
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: XenServer
>    Affects Versions: 4.1.1, 4.2.0
>         Environment: XenServer 6.0.2  (and possibly later versions)
>            Reporter: Donal Lafferty
>            Assignee: Donal Lafferty
>
> vhd-utils is downloaded separately to the Apache CloudStack source code base.
> See https://cwiki.apache.org/confluence/display/CLOUDSTACK/How+to+build+CloudStack#HowtobuildCloudStack-BuildingCloudStack
> This version of vhd-utils lacks the '-S' option used by XenServer 6.0.2 (and possibly
above).  As a consequence, it will not create VDIs

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message