-
-
Notifications
You must be signed in to change notification settings - Fork 4.4k
Description
Environment
self-hosted (https://develop.sentry.dev/self-hosted/)
Steps to Reproduce
Open Releases and select any release with same version number a few projects share. ( in our case 1.123.1, but there are more cases )
OR alternatively open Issue of the release with ID, that a few projects share.
Expected Result
All Releases and all Issues open without errors.
Actual Result
We get the following error when opening Issues or Releases with duplicate ID:
Logs from web-1 container:
sentry.models.release.Release.MultipleObjectsReturned: get() returned more than one Release -- it returned 2!
14:21:40 [INFO] sentry.access.api: api.access (method='GET' view='sentry.api.endpoints.organization_release_meta.OrganizationReleaseMetaEndpoint' response=500 user_id='19' is_app='False' token_type='None' is_frontend_request='True' organization_id='1' auth_id='None' path='/api/0/organizations/company/releases/1.123.1/meta/' caller_ip='141.101.99.15' user_agent='Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/125.0.0.0 Safari/537.36' rate_limited='False' rate_limit_category='None' request_duration_seconds=0.04949188232421875 rate_limit_type='DNE' concurrent_limit='None' concurrent_requests='None' reset_time='None' group='None' limit='None' remaining='None')
14:21:40 [ERROR] django.request: Internal Server Error: /api/0/organizations/company/releases/1.123.1/meta/ (status_code=500 request=<WSGIRequest: GET '/api/0/organizations/company/releases/1.123.1/meta/'>)
Is there any way to prevent and fix this? Perhaps our setup is incorrect, causing versioning across different projects to not work together correctly? We have over 140 projects, so it is normal that by using semantic versioning some projects eventually get same version number.
Thank you.
Product Area
Releases
Link
No response
DSN
No response
Version
24.5.0
Metadata
Metadata
Assignees
Labels
Type
Projects
Status