[
https://issues.apache.org/jira/browse/CLOUDSTACK-9022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15035664#comment-15035664
]
ASF GitHub Bot commented on CLOUDSTACK-9022:
--------------------------------------------
Github user wilderrodrigues commented on the pull request:
https://github.com/apache/cloudstack/pull/1145#issuecomment-161266056
@remibergsma @DaanHoogland @wido @bhaisaab @ustcweizhou @karuturi @runseb
@borisroman @jburwell
If test_vm_life_cycle.py is failing because the current 4.6 and/or master
is broken/unstable, we have to get it working again before any other PR gets
merged.
We cannot, for any imaginable reason, get into the situation we were at few
months ago.
I will run tests against current 4.6 branch and Master to see if that's
actually broken. Who can help me on testing as well?
Cheers,
Wilder
> We should keep Destroyed volumes for some time
> ----------------------------------------------
>
> Key: CLOUDSTACK-9022
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9022
> Project: CloudStack
> Issue Type: Improvement
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Reporter: Wei Zhou
> Assignee: Wei Zhou
>
> for now, the Destroyed volumes will be expunged in Storage cleanup thread, no
> matter when they are destroyed.
> In Expunging vm, we only clean the Destroyed vms which have been destroyed at
> least 'expunge.delay' seconds.
> We need to add the similar configuration for volumes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
