[jira] [Reopened] (AIRAVATA-1952) When a deployment is no longer existing in a certain resource clone experiment launch crashes with error-exception

["Eroma (JIRA)" <ji...@apache.org>]

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

Eroma reopened AIRAVATA-1952:
-----------------------------

Steps:
1. Cloned an experiment where the deployment is no longer exists.
2. Upon opening the edit clone experiment page it gave messages such as no deployment available for the application and also an error message at the bottom saying user cannot proceed.
(So far so good)
3. So I closed the experiment.
4. In the background now i have the cloned experiment with the previous deployment and when launched it immediately turned the exp status to FAILED (Still acceptable)
5. But no reason is given to the user for the failure. Also since the deployment is no longer available ideally the cloned experiment should not have compute resource details as well.
6. Best solution would be to cloned experiment not to have any resource details and also not to let user launch it.

> When a deployment is no longer existing in a certain resource clone experiment launch crashes with error-exception
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: AIRAVATA-1952
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-1952
>             Project: Airavata
>          Issue Type: Bug
>          Components: PGA PHP Web Gateway
>    Affects Versions: 0.16
>         Environment: https://dev.seagrid.org
>            Reporter: Eroma
>            Assignee: Nipurn Doshi
>         Attachments: Screen Shot 2016-04-13 at 4.26.11 PM.png
>
>
> When a deployment is no longer existing in a certain resource clone experiment launch crashes with error-exception
> Steps
> 1. Selected an old experiment
> 2. Cloned and changed the queue
> 3. Clicked launch
> 4. Gives the attached error.
> This was because in the present the application is not deployed anywhere. In cases like this cloning should be restricted or handled with a proper message to the user.



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