-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Restart workspace fail (OpenShift Dedicated, minishift) #16512
Comments
@vparfonov could you clarify how you deployed eclipse che on OSD? |
here script that I used for deploy https://gist.github.com/vparfonov/dcdd1c4ec30604d9b957737cebffb4bb |
Reproduced on multi-user installation with original old fashion
|
@ericwill any ideas? looks like an issue with ssh plugin cc: @vinokurig |
Looks like it is related to #14950, @vzhukovskii any ideas? |
Will take a look asap |
FYI, I reproduced it on
|
As far as I understand, changes related to storing private keys in secrets should not broke the flow of starting two dedicated workspaces. What situation with the only one workspace, does it start successfully? |
Looks like single workspace starts successfully |
I suppose, then, it shouldn't be related to #14950 |
More logs.
Might be related to |
It is not related to the SSH plugin as well, because the plugin hadn't been started before the error. |
@skabashnyuk so this is likely related to the k8s client lib update right? |
I don't know yet. |
Deploy script is deprecated and removed. |
@tolusha the custom script was used for OSD deployment (there is no way to deploy on OSD any other way atm) for the record, it looks like I can not reproduce on Hosted Che against 7.11 Snapshot redhat-developer/rh-che#1828 |
I faced the same issue today on the minikube + chectl + operator, but the error message was about self-signed-cert secret. |
I can't reproduce this issue anymore when I use an image from #16540 |
Me to, works well with #16540 |
I can't reproduce on minishift with chectl and operator... |
k8s client 4.9.0
kubernetes client 4.1.0
See more fabric8io/kubernetes-client#1840 PR #16540
|
@skabashnyuk am I correct that this issue is not severe e.g. even if the initial restart failed one of the subsequent should pass once the k8s-resources are finally deleted? So far we were not able to reproduce it on staging against 7.11.0 upstream and do not treat it as a blocker for production update |
I would say it could. Without any guarantee of course. |
thanks, so our plan is to promote 7.11.0 and request 7.11.1 if this issue will become a problem. On the staging, we were not able to reproduce the issue so far #16475 (comment) |
Describe the bug
Got error message during restarting early created workspaces. This reproduced not each time need to repeat restarting several times.
Che version
Steps to reproduce
Got this error log:
Expected behavior
Runtime
kubectl version
)oc version
)minikube version
andkubectl version
)minishift version
andoc version
)docker version
andkubectl version
)Screenshots
Installation method
Environment
Eclipse Che Logs
che-2-5kqgc-che.log
Additional context
Could not reproduce before this commit: db46ad4
The text was updated successfully, but these errors were encountered: