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
detecting state #6778
Comments
This issue does exactly occur to me now randomly. I'm working around this by stopping the workspace and starting it again. |
Just to clarify: it happens only when you run docker in Gitpod? |
@akosyakov for me, we run everything inside docker, so I can confirm that it happened with something that runs inside docker, but no other assumptions around that |
@csweichel I looked at supervisor logs when it happens and gitpod/components/supervisor/pkg/ports/ports.go Lines 486 to 495 in bb1349f
auto-exposing port . There was not changes in exposed ports service besides removing global port, so it seems it blocks on control port request to server. I am not sure. Can we see traces?
|
Unfortunately we don't trace this interface 🤦 That said, auto-exposure is only neccesary in the "public exposure" case since we've moved away from Kubernetes services. Hence we could make this part be a bit more "tolerant" towards auto-exposure failure. |
I am not sure what do you mean? It does not fail, it hangs forever. |
/assign |
@akosyakov Do you have a workspace ID or a link to the logs for your case? I had a look in the logs of the workspace |
I actually was able to reproduce it with new workspaces today. I think the workspace id was It was opened for this context: trusktr/solid-lume-starter@35c3426 and start a server with |
Here is an update of my findings so far:
|
I think you are right, I overlooked something by mistake. I could not see them hanging right now. Actually all returns successfully. |
@iQQBot you can follow internal investigation here: https://gitpod.slack.com/archives/C01KGM9BH54/p1638873457412200 |
Relevant update: #7054 (comment) |
@iQQBot supervisor reconnects to the server each 10 mins, during such reconnect we can miss some events, so let's add a mitigation which sync with server on reconnect. Do you need some code pointers? |
Why reconnects to server each 10min? |
I'm having this "detecting..." problem. |
Yeah, it sounds exactly like a problem of missing events. If you forward another port a new event is issued which delivers proper state for first port too. |
should be fixed by #7621 |
@akosyakov the issue is reproducing again after my account was migrated to the new Gitpod version. Port 300 is not opening when I run a Docker container on it. Could this issue be reproduced in the new release? |
Hi @olleyt, is this still happening? |
yes, it is still happening for example this workspace : xcymr2gwvy0.ws-us96b.gitpod.io or this one ny59rvseewn.ws-us96b.gitpod.io timestamp: Mon 01 May 2023 10:11:20 AM UTC as a workaround we used |
This was resolved yesterday. See https://www.gitpodstatus.com/incidents/6h1gd447lk7b. |
Bug description
like you see in this picture this service runs perfectly and can be accessed with the browser, but
it is marked with a detecting state.
Steps to reproduce
I don't know if you can reproduce it.
We have this situation that the port detection works perfect for node services that are running in docker containers,
but not for the pgadmin that is also running inside a docker container.
Workspace affected
workspace: apricot-scorpion-yeo25j03
Expected behavior
No response
Example repository
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: