-
Notifications
You must be signed in to change notification settings - Fork 274
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
proxy routes broken with multiple realm roles #1971
Comments
Here is a super basic crossbar config for a proxy worker, enough to reproduce the bug described above
|
Since the code runs as a roundrobin, it "succeeds" on first attempt and fails on the other
|
Here are the relevant Crossbar logs. NOTE: the connection refused is expected as I am not running a backend.
|
Luckily this issue can be fixed with a one-liner
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If a realm route has only one role, everything works fine. However if there are multiple roles for a realm and the route is configured, the round robin logic is broken
crossbar/crossbar/worker/proxy.py
Lines 1386 to 1388 in fa0e418
In the current implementation, a new realm route is started for each role
crossbar/crossbar/node/node.py
Lines 962 to 978 in fa0e418
However, the round robin logic above doesn't check if a route has the specific role and tries to access it, resulting in a KeyError.
The text was updated successfully, but these errors were encountered: