[
https://issues.apache.org/jira/browse/AIRAVATA-3125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16885608#comment-16885608
]
Marcus Christie commented on AIRAVATA-3125:
-------------------------------------------
The problem is that user profile for "rquick@seagrid" didn't get replicated to
the sharing registry (nor did it get replicated to the experiment registry).
There are 928 such accounts in staging:
{code:sql}
select up.* from profile_service.USER_PROFILE up
where not exists (
select 1 from sharing_catalog.SHARING_USER
where USER_ID = up.AIRAVATA_INTERNAL_USER_ID
);
{code}
We might need a way to trigger replication. My guess is that a bug or something
caused the replication to fail at some point but if it were triggered again it
would complete.
> Cannot add a new user in to the gateway-user group
> --------------------------------------------------
>
> Key: AIRAVATA-3125
> URL: https://issues.apache.org/jira/browse/AIRAVATA-3125
> Project: Airavata
> Issue Type: Sub-task
> Components: Django Portal
> Affects Versions: 0.18
> Environment: https://django.staging.seagrid.org
> Reporter: Eroma
> Assignee: Marcus Christie
> Priority: Critical
> Attachments: Screen Shot 2019-07-15 at 1.38.54 PM.png
>
>
> # An existing user in Admin group was removed from the group
> # Then the same user was queried and tried to save in gateway-user group as
> an admin
> # When clicked on submit an exception was thrown.
> # Then tried to add the same user again as an admin.
> # Still the same exception is thrownÂ
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
