You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@airavata.apache.org by "Marcus Christie (JIRA)" <ji...@apache.org> on 2016/11/16 21:06:58 UTC
[jira] [Created] (AIRAVATA-2231) UserResourceProfileResource.save()
looks up existing UserResourceProfile by user_id instead of by (user_id,
gateway_id)
Marcus Christie created AIRAVATA-2231:
-----------------------------------------
Summary: UserResourceProfileResource.save() looks up existing UserResourceProfile by user_id instead of by (user_id, gateway_id)
Key: AIRAVATA-2231
URL: https://issues.apache.org/jira/browse/AIRAVATA-2231
Project: Airavata
Issue Type: Bug
Components: Registry API
Reporter: Marcus Christie
Fix For: 0.17-SNAPSHOT
From Hipchat:
{quote}
So here's what I think is happening. You have a UserResourceProfile in dev.scigap, username smarru. When dev.seagrid tries to create a UserResourceProfile for smarru, there is a bug in the backend code where it is finding and updating the smarru@dev.scigap record and updating it instead. Thus dev.seagrid is never able to create a dev.seagrid UserResourceProfile for you, leading to the errors.
{quote}
Here's the line where there is the look up by userId only
https://github.com/machristie/airavata/blob/dd319ce94ffb7db6729c724b0dbe3523bea0b338/modules/registry/registry-core/src/main/java/org/apache/airavata/registry/core/app/catalog/resources/UserResourceProfileResource.java#L358-L358
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)