[
https://issues.apache.org/jira/browse/AIRAVATA-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eroma closed AIRAVATA-2339.
---------------------------
tested and verified in
http://149.165.156.11/ (seagrid PGA in JS)
submitted bigred2 jobs with user account using default key and also with a key
generated by the user.
Both cases passed.
While having user account set in the gateway also tried submitting jobs with
the community account by unchecking the checkbox, that also successfully
launched.
> Default ssh key use for individual user accounts failing. Cannot ssh to
> compute resource
> ----------------------------------------------------------------------------------------
>
> Key: AIRAVATA-2339
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2339
> Project: Airavata
> Issue Type: Bug
> Components: GFac, PGA PHP Web Gateway
> Affects Versions: 0.17
> Reporter: Eroma
> Assignee: Marcus Christie
> Fix For: 0.17
>
>
> For individual user settings we can assign the default generated key.
> When it is assigned USER_RESOURCE_PROFILE table gets updated with the
> relevant token.
> When tried to use it to ssh it is failing.
> But if a new key is generated and assigned then ssh to resource work. When a
> new key is generated it get saved in to USER_COMPUTE_RESOURCE_PREFERENCE.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
