[
https://issues.apache.org/jira/browse/AIRAVATA-2322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Christie updated AIRAVATA-2322:
--------------------------------------
Attachment: Screen Shot 2017-02-15 at 08.34.06-fullpage.png
I've verified this on dev.seagrid.org. What I did was I manipulated the queue
dropdown and added a "dummy" queue option. When I submit this experiment the
status becomes FAILED and the Experiment has the following Errors:
{quote}
Validation failed refer the validationResults list for detail error. Validation
errors : Validation Errors : The specified queue dummy does not exist. If you
believe this is an error, contact the administrator to verify App-Catalog
Configurations
{quote}
Screenshot:
!Screen Shot 2017-02-15 at 08.34.06-fullpage.png|thumbnail!
> Orchestrator doesn't update experiment status to FAILED when validation fails
> -----------------------------------------------------------------------------
>
> Key: AIRAVATA-2322
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2322
> Project: Airavata
> Issue Type: Bug
> Reporter: Marcus Christie
> Assignee: Marcus Christie
> Attachments: Screen Shot 2017-02-15 at 08.34.06-fullpage.png
>
>
> For the dREG gateway, the queue name is hard coded to {{GPU}}. However, that
> queue doesn't exist on bridges.psc.edu. During validation, the
> SimpleOrchestratorImpl finds that the queue doesn't exist and throws a
> LaunchValidationException. However, the OrchestratorServerHandler didn't mark
> the experiment as failed so the experiment was still in CREATED state and
> never updates to another state.
> I think what we want to do is catch the LaunchValidationException in
> OrchestratorServerHandler.launchException and mark the experiment as FAILED
> if vaildation fails. It would be good too to put the validation error
> message in there somewhere so that the user or an admin can know what went
> wrong.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
