Closed tserong closed 1 year ago
Yep, it's gotta be something to do with the localhost port forwards. If I retry using (in this case) cluster creation on node1 via http://192.168.121.155:1337/ and join on node2 via http://192.168.121.43:1337, it all works fine (although I still saw a red "500 Internal Server Error" box pop up once on node2's login screen). So I'm not sure if this is something that can/should be fixed, or just needs to be documented for those doing dev/test.
I have a similar issue when I forward my screen even outside of the vm box to my desktop when I was doing a demo presentation. The login screen didn't show up when accessing the dashboard page, but nothing work. So I have to manually going to the login page and then login and everything back to normal.
(although I still saw a red "500 Internal Server Error" box pop up once on node2's login screen)
Actually, that was a "401 Unauthorized", not a "500 Internal Server Error", and the fact that the user is unauthorized at that point in time probably makes sense. Still, I don't think that error should appear, given the user hasn't actually attempted to log in yet.
Describe the bug I used
aqrdev
to create a new deployment from the head of the main branch today, then went to http://localhost:1337/, created a new cluster, then went to http://localhost:1338/ to join the second node. This seems to have succeeded (the GUI on node1 lists both hosts), but http://localhost:1338/ remains stuck on the Join screen, with a 500 Internal server error visible.journalctl -fu aquarium
on node2 gives:To Reproduce 1) Use
aqrdev
to create a new deployment. 2) Go to http://localhost:1337/ and create a new cluster. Login to the dashboard and get the IP address and auth token from node1. 3) Go to http://localhost:1338/ and tell that node to join an existing cluster with the details from item 2. 4) Observe that you get stuck on the join screen with that 500 internal server errorExpected behavior The join succeeds and I'm able to access the dashboard on node2
Screenshots
Additional context I'm using Firefox on openSUSE Tumbleweed.
Could the problem here be something to do with using the localhost:1337 and localhost:1338 port forwards? Will this cause the browser to do something stupid/unexpected with session cookies?