[Bug]: It is possible to create collections for a non-existent tenant #2884
Assignees
Labels
bug
Something isn't working
Comments
rohitcpbot
added a commit
that referenced
this issue
Oct 15, 2024
[BUG] Schema changes related to Issue#2884 and few other necessary constraints. ## Description of changes *Summarize the changes made by this PR.* - Improvements & Bug fixes - Fix for Issue #2884. - Added additional constraints to the schema to avoid future issues. - New functionality - n/a ## Test plan *How are these changes tested?* - [x] Tests pass locally with `make test` for golang ## Documentation Changes None
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What happened?
I have a tenant ID that, to all appearances is valid and works in the UI console. However, it does not in fact exist in the data layer, since staging was wiped.
In this situation, it is possible to create a collection, and to have the request return successfully and provide a new collection ID. However, subsequent attempts to use that collection ID fail with a "collection does not exist error."
Apparently, it is possible for the system to create collections even when the tenant ID does not exist, provided the tenant ID can pass auth.
Versions
Staging as of 2024-09-30
Relevant log output
No response
The text was updated successfully, but these errors were encountered: