[
https://issues.apache.org/jira/browse/AIRAVATA-3616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17534037#comment-17534037
]
Marcus Christie commented on AIRAVATA-3616:
-------------------------------------------
I noticed that the name of the seagrid-elastic.jetstream-cloud.org compute
resource wasn't reflected in the GRP editor. This is because it wasn't actually
loading the compute resource names and was only truncating the compute resource
id. I've fixed that too as part of this issue since that can cause confusion.
> Disabled compute resources should be filtered out of app deployment/compute
> resource selection
> ----------------------------------------------------------------------------------------------
>
> Key: AIRAVATA-3616
> URL: https://issues.apache.org/jira/browse/AIRAVATA-3616
> Project: Airavata
> Issue Type: Bug
> Reporter: Marcus Christie
> Priority: Major
>
> h3. Steps to reproduce
> 1. Login to seagrid.org
> 2. Click on Quantum_Espresso
> 3. Select Allocation Default
> 4. Select seagrid-elastic.jetstream-cloud.org
> h3. Expected Results
> seagrid-elastic.jetstream-cloud.org is disabled as a compute resource. It
> shouldn't be selectable or even in the list.
> h3. Actual Results
> seagrid-elastic.jetstream-cloud.org is in the and selectable as a compute
> resource like any other.
> h3. Workaround
> Also remove the disabled compute resource from the Group Resource Profile.
> h3. Airavata error
> {code}
> AiravataSystemException(airavataErrorType=2, message='Error while creating
> the experiment. More info : Error while creating the experiment. More info :
> Compute Resource is not enabled by the Admin!')
> {code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
