cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-8651) [Browser Based Upload Template] Partially uploaded templates doesn't get cleaned up after the SSVM handling it is destroyed
Date Wed, 29 Jul 2015 08:12:04 GMT

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

ASF subversion and git services commented on CLOUDSTACK-8651:
-------------------------------------------------------------

Commit 3be278ed5e4e83c1f8024adaa7056629973e0151 in cloudstack's branch refs/heads/master from
[~koushikd]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=3be278e ]

CLOUDSTACK-8651: [Browser Based Upload Template] Partially uploaded templates doesn't get
cleaned up after the SSVM handling it is destroyed
Fixed template sync code to include templates in 'NotUploaded' and 'UploadInProgress' states
along with 'Active'.


> [Browser Based Upload Template] Partially uploaded templates doesn't get cleaned up after
the SSVM handling it is destroyed
> ---------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-8651
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8651
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.6.0
>            Reporter: Koushik Das
>            Assignee: Koushik Das
>             Fix For: 4.6.0
>
>
> Repro steps:
> 1. Make a call to getuploadparamsfortemplate, don't start actual upload to SSVM or make
sure that the upload is in partially completed state.
> 2. Destroy SSVM (when template state is NotUploaded or UploadInProgress).
> 3. After a new SSVM comes up, these templates continue to remain in the same state and
cannot be removed/cleaned-up.
> The issue is happening as the original SSVM is destroyed and no longer able to monitor
the template. The fix is to clean-up the partially uploaded templates as part of template
sync-up when the new SSVM comes up.



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

Mime
View raw message