airavata-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus Christie (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AIRAVATA-2470) When existing gateway provider tries to update the second part of the gateway reqest
Date Mon, 03 Jul 2017 00:59:00 GMT

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

Marcus Christie commented on AIRAVATA-2470:
-------------------------------------------

I'll take this one and fix it on the backend.  The frontend code is correct, it is passing
the internal gateway id but the backend needs to be updated to search by the internal gateway
id.

> When existing gateway provider tries to update the second part of the gateway reqest
> ------------------------------------------------------------------------------------
>
>                 Key: AIRAVATA-2470
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-2470
>             Project: Airavata
>          Issue Type: Bug
>          Components: PGA PHP Web Gateway
>    Affects Versions: 0.17
>         Environment: https://dev.scigap.org
>            Reporter: Eroma
>            Assignee: Marcus Christie
>             Fix For: 0.18
>
>         Attachments: Screen Shot 2017-07-02 at 10.40.54 AM.png
>
>
> 1. Existing gateway provider creates a gateway request
> 2. SciGaP admin gets notification
> 3. SciGaP admin approves the request
> 4. Gateway provider gets notified about the gateway request update
> 5. Logs in to portal, and clicks Update request
> 6. Exception thrown  - Error getting gateway-profile, reason: Could not find Gateway
with ID: f37a6727-bb6d-4e69-a213-0f55386ec90b



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message