Skip to content
This repository has been archived by the owner on Jul 23, 2020. It is now read-only.

User blocked has tenant service still has entries for him #1415

Closed
xcoulon opened this issue Nov 20, 2017 · 4 comments
Closed

User blocked has tenant service still has entries for him #1415

xcoulon opened this issue Nov 20, 2017 · 4 comments

Comments

@xcoulon
Copy link
Collaborator

xcoulon commented Nov 20, 2017

user mmclane is blocked because the tenant service has entries for Che and Jenkins for his previous project. The env reset procedure did not reset all the data, and manually removing the projects was not enough.

@xcoulon xcoulon self-assigned this Nov 20, 2017
@xcoulon
Copy link
Collaborator Author

xcoulon commented Nov 20, 2017

Status for his account:
image pasted at 2017-11-20 14-58

@xyntrix
Copy link

xyntrix commented Nov 20, 2017

Created an empty project in OSO before initiating OSIO. Removed that project (learned that is a known issue: #1031). The OSIO projects are still active in OSO:

image

@pbergene
Copy link
Collaborator

Synced with @xcoulon - waiting for @mmclanerh to come on today and we'll walk through the steps required to clean out the tenant DB.

@xcoulon
Copy link
Collaborator Author

xcoulon commented Nov 21, 2017

The awesome @pbergene cleaned the tenant database with the remaining entries for @mmclanerh entries (1 entry in the tenants table and 4 entries in the namespaces table, for the -che, -jenkins, -stage and -run projects on OSO), then he deleted the corresponding projects on OSO using the devtools-sre-tools account, since those 4 remaining projects did belong to this SA user and not to @mmclanerh himself.

@xcoulon xcoulon closed this as completed Nov 21, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants