You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@airavata.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2016/04/15 21:34:25 UTC
[jira] [Commented] (AIRAVATA-1952) When a deployment is no longer
existing in a certain resource clone experiment launch crashes with
error-exception
[ https://issues.apache.org/jira/browse/AIRAVATA-1952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15243471#comment-15243471 ]
ASF subversion and git services commented on AIRAVATA-1952:
-----------------------------------------------------------
Commit f5092180881422d2cbe59e5f2df518135c49cc31 in airavata-php-gateway's branch refs/heads/develop from [~ndoshi]
[ https://git-wip-us.apache.org/repos/asf?p=airavata-php-gateway.git;h=f509218 ]
fixes added for connected issues - AIRAVATA-1952 + AIRAVATA-1951 + AIRAVATA-1926
> 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
> Fix For: 0.16
>
> 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)