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-3358) Multiple sets of "gateway groups" created for dev-delta tenant
Date Mon, 31 Aug 2020 20:57:00 GMT

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

Marcus Christie commented on AIRAVATA-3358:
-------------------------------------------

I've added what I think will fix this. I think what happened is that multiple API requests
came in at the same time and each one triggered the creation of the gateway groups in the
Sharing Catalog, but the IDs of those groups were saved as the GatewayGroups entity in the
Registry only once.  I've made the initializeGatewayGroups method synchronized to prevent
multiple threads from calling it at once.

I also added some error logging in case this happens again.

Since I'm not 100% sure how this error happened and I don't know how to replicate it, I'm
going to go ahead and resolve this issue. If it occurs again hopefully the error logging will
help determine the source of the issue. Also hopefully we catch it sooner -- we didn't catch
this error until months later and we no longer had the logs available.

> Multiple sets of "gateway groups" created for dev-delta tenant
> --------------------------------------------------------------
>
>                 Key: AIRAVATA-3358
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-3358
>             Project: Airavata
>          Issue Type: Bug
>            Reporter: Marcus Christie
>            Assignee: Marcus Christie
>            Priority: Major
>
> ~100 "Admins" groups, "Gateway Users" groups, "Read-only admins" groups were created.
Appears that maybe the groups were created in the *sharing catalog* but the ids weren't saved
in the *registry catalog*, but that's just a guess. I'm not sure how all of these duplicate
groups were created.
> The workaround is I deleted the groups for the tenant that weren't listed in app_catalog.GATEWAY_GROUPS.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Mime
View raw message