You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@airavata.apache.org by "Eroma (JIRA)" <ji...@apache.org> on 2017/05/22 17:15:04 UTC

[jira] [Comment Edited] (AIRAVATA-2358) Without gateway preference setting for compute resources, experiment stuck in CREATED

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

Eroma edited comment on AIRAVATA-2358 at 5/22/17 5:14 PM:
----------------------------------------------------------

Same error is in api-orch server log when the login username is empty in gateway preferences. Experiment in CREATED but error in log. This launch failure need to be reflected in the UI for the user.

Same issue exists with individual user settings. User settings per compute cluster can be saved without username. Login username and scratch location should be made mandatory to avoid individual user level data entry issues.



was (Author: eroma_a):
Same error is in api-orch server log when the login username is empty in gateway preferences. Experiment in CREATED but error in log. This launch failure need to be reflected in the UI for the user.

Same issue exists with individual user settings. User settings per compute cluster can be saved without username.

> Without gateway preference setting for compute resources, experiment stuck in CREATED
> -------------------------------------------------------------------------------------
>
>                 Key: AIRAVATA-2358
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-2358
>             Project: Airavata
>          Issue Type: Bug
>          Components: Airavata Orchestrator, PGA PHP Web Gateway
>    Affects Versions: 0.17
>         Environment: http://149.165.156.11/
>            Reporter: Eroma
>            Assignee: Marcus Christie
>             Fix For: 0.18
>
>
> When experiment is saved and launched prior to configuring the gateway preferences for the relevant compute resource in PGA experiment is in CREATED. No errors, messages or experiment FAILED.
> But in api-orchestrator log already the experiment has failed with errors. it has errors [1]
> This should be reflected in PGA, by either changing the status to FAILED or by notifying the user and gateway admin of the issue in hand and once the preferences are set it should get launched.
> This way user doesn't have to create another one due to gateway admin level configuration issue.
> [1]
> 2017-04-03 20:11:00 [pool-15-thread-6] INFO o.a.a.m.c.impl.ExperimentConsumer -  Message Received with message id 'LAUNCH.EXP-2b62c33f-8fd5-486b-8f79-daafebc32b74' and with message type 'EXPERIMENT'  for experimentId: Lammps_Test1_b4352c5a-3e8c-497b-9b17-7d7915c4e273
> 2017-04-03 20:11:00 [pool-15-thread-6] INFO o.a.a.o.s.OrchestratorServerHandler - Launching experiment with experimentId: Lammps_Test1_b4352c5a-3e8c-497b-9b17-7d7915c4e273 gateway Id: seagrid
> 2017-04-03 20:11:00 [pool-15-thread-6] ERROR o.a.a.o.s.OrchestratorServerHandler - Experiment launch failed due to Thrift conversion error, experimentId: Lammps_Test1_b4352c5a-3e8c-497b-9b17-7d7915c4e273, gatewayId: seagrid
> org.apache.thrift.TException: Experiment 'Lammps_Test1_b4352c5a-3e8c-497b-9b17-7d7915c4e273' launch failed. Unable to figureout execution type for application Test_Lammps_7e68727f-b0ca-4895-81af-4527a9c1183d
>         at org.apache.airavata.orchestrator.server.OrchestratorServerHandler.launchExperiment(OrchestratorServerHandler.java:253)
>         at org.apache.airavata.orchestrator.server.OrchestratorServerHandler.launchExperiment(OrchestratorServerHandler.java:668)
>         at org.apache.airavata.orchestrator.server.OrchestratorServerHandler.access$500(OrchestratorServerHandler.java:78)
>         at org.apache.airavata.orchestrator.server.OrchestratorServerHandler$ExperimentHandler.onMessage(OrchestratorServerHan



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)