-
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
Failure executing: POST sshconfigmap or gitconfig configmaps already exists #15904
Comments
Same error is seen in #15900 |
From my observation configmaps has some delay in the deletion process. I would suggest trying to use random names for config map names like https://github.com/eclipse/che/blob/master/infrastructures/kubernetes/src/main/java/org/eclipse/che/workspace/infrastructure/kubernetes/wsplugins/brokerphases/BrokerEnvironmentFactory.java#L138-L139 CC @vinokurig |
@skabashnyuk I believe (but not 100% sure) it may be caused by incorrect workspace k8s resources cleaning up... I mean when workspace is idled but k8s resources are not clean up. Next workspace start will show an error message and object already exists, and maybe config map is just a first object we try to create. |
I thought about that as well but didn't found any confirmation about that.
I got this error somehow by continuously starting/stopping two workspaces in parallel. |
There are objects where we are not able to generate names, like some services... |
@sleshchenko you probably right. @metlos has the same vision that naming should not be a reason for the problem. It might be related to https://github.com/eclipse/che/blob/master/infrastructures/kubernetes/src/main/java/org/eclipse/che/workspace/infrastructure/kubernetes/provision/UniqueNamesProvisioner.java. We will take care of it. |
I was able to reproduce the state when config maps were not deleted with such a case
|
Duplicate #14859 |
Describe the bug
Noticed during an inspection of che-server logs.
Che version
Steps to reproduce
Unknown
Expected behavior
This error should not happen.
Runtime
kubectl version
)oc version
)minikube version
andkubectl version
)minishift version
andoc version
)docker version
andkubectl version
)Screenshots
Installation method
Environment
Additional context
n/a
The text was updated successfully, but these errors were encountered: