getsentry / getsentry/self-hosted

No Organization Access -- after upgrade to 23.11.2

Open
#2,654 9 comments 3 reactions 0 assignees View on GitHub
Bug
Dominant language
Shell
Stars
9.6k
Forks
2k
Avg merge
1d 3h
Merged PRs (30d)
12

Description

### Self-Hosted Version

23.11.2

### CPU Architecture

x86_64

### Docker Version

24.0.7

### Docker Compose Version

2.23.3

### Steps to Reproduce

1. Existing 23.4.0 installation (upgraded from previous versions)
2. Upgrade to 23.6.2
3. Upgrade to 23.11.2

### Expected Result

Everything works.

### Actual Result

Met with the following error upon logging in. Clicking the circled link does get me in, but unsure of what changes need to be made as I am the owner of the only Organization on the instance.

![image](https://github.com/getsentry/self-hosted/assets/1904577/1c143c66-85c1-4f85-88fe-496f56392e61)

### Event ID

_No response_

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the documented upgrade path from 23.4.0 through 23.6.2 to 23.11.2 and inspect the login error shown in the issue. Trace organization access during authentication and authorization, then verify that the sole organization owner can log in normally after the upgrade without using the workaround link.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, docker-compose, shell
Domain
authentication, authorization, devops
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.