[
https://issues.apache.org/jira/browse/CLOUDSTACK-8651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14645479#comment-14645479
]
ASF GitHub Bot commented on CLOUDSTACK-8651:
--------------------------------------------
Github user koushik-das commented on the pull request:
https://github.com/apache/cloudstack/pull/607#issuecomment-125849581
Moved the test to a new file test_browse_templates2.py. This is the command
to run it
nosetests-2.7 --with-marvin --marvin-config=setup/dev/advanced.cfg
--with-xunit --xunit-file=test_output.xml
test/integration/component/test_browse_templates2.py -a required_hardware=false
--zone=Sandbox-simulator --hypervisor=simulator
> [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)
