You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Stephen Turner (JIRA)" <ji...@apache.org> on 2014/10/31 18:19:34 UTC

[jira] [Commented] (CLOUDSTACK-6806) UI:API: If VM start is performed when createTemplate from Volume is in progress, user should be notified

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

Stephen Turner commented on CLOUDSTACK-6806:
--------------------------------------------

If the API returns an error, the UI will catch it, so removing UI component.

> UI:API: If VM start is performed when createTemplate from Volume is in progress, user should be notified
> --------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-6806
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6806
>             Project: CloudStack
>          Issue Type: Improvement
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: API
>    Affects Versions: 4.4.0
>            Reporter: Parth Jagirdar
>
> Perform following,
> create a VM,
> Create a Template from volume. (The pre-req is VM must be in stopped state)
> Verify that the newly listed template is listed on UI.
> click on template and check that ready=no. (Template creation still in progress)
> While status Ready=no is true, attempt to start the VM.
> Observe that upon VM start the template is no longer listed on UI and DB entry for this template is removed. (DB entry is entirely removed from table instead of marking removed field; this is by design)
> Proposal is to::
> Notify user upon VM start when Template creation is in progress Instead of removing/deleting template without notifying.
> If volume is big enough createTemplate can take a while and its very likely that user may attempt to start VM.



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