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

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

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

Commit 06aa0641f1f86a39e7224e84766f9374482e7c8c in airavata's branch refs/heads/develop from
Marcus Christie
[ https://gitbox.apache.org/repos/asf?p=airavata.git;h=06aa064 ]

AIRAVATA-3358 Synchronize creating gateway groups to prevent multiple request threads from
creating duplicates


> 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