airavata-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AIRAVATA-2339) Default ssh key use for individual user accounts failing. Cannot ssh to compute resource
Date Sun, 26 Mar 2017 00:31:41 GMT

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

ASF subversion and git services commented on AIRAVATA-2339:
-----------------------------------------------------------

Commit 41cc92057c603fb21fc3f1c719d525fbbc7ab281 in airavata's branch refs/heads/develop from
[~marcuschristie]
[ https://git-wip-us.apache.org/repos/asf?p=airavata.git;h=41cc920 ]

AIRAVATA-2339 Attempting to fix data staging with individual account

In ProcessContext I removed use of isUseUserCRPref() in methods related to
getting gateway storage information. Whether the current experiment is submitted
with user's compute resource preferences or not should not affect gateway
storage information. How to specify user's storage preferences is not yet
implemented and must be implemented with something other than isUseUserCRPref().

In SCPDataStageTask, I changed the construction of the sshSession for the SCP
connection to the compute resource to use
getComputerResourceSSHKeyAuthentication() instead of
getStorageSSHKeyAuthentication(), which would not be correct, if I understand
the code correctly.


> 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)

Mime
View raw message