Plugin Broker failed to start if userID contains :
See original GitHub issueDescribe the bug
When starting workspace, workspace fails with error message:
Error: Failed to run the workspace: "Plugins installation process timed out"
In minikube cluster, che-plugin-broker is seen in status Init:Error.
Logs from container eclipse-che-init-plugin-broker-v0-22 say:
2019/10/29 12:12:46 Expected runtime id to be in format 'workspace:env:ownerId'
che-plugin-broker pod description shows this:
-runtime-id workspace9sf22yxtjmr71u75:default:f:a78d3304-d12b-4c40-ab27-b54ec3a4f143:fk633080
which obviously does not conform to the mentioned expected format
Che version
- other: 7.3.0
Steps to reproduce
See additional context
Expected behavior
Expected is normal workspace startup.
Runtime
- minikube (include output of
minikube version
andkubectl version
)
minikube version: v1.4.0
commit: 7969c25a98a018b94ea87d949350f3271e9d64b6
kubectl version
Client Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.2", GitCommit:"c97fe5036ef3df2967d086711e6c0c405941e14b", GitTreeState:"clean", BuildDate:"2019-10-15T19:18:23Z", GoVersion:"go1.12.10", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.0", GitCommit:"2bd9643cee5b3b3a5ecbd3af49d09018f0773c77", GitTreeState:"clean", BuildDate:"2019-09-18T14:27:17Z", GoVersion:"go1.12.9", Compiler:"gc", Platform:"linux/amd64"}
Installation method
- chectl
$ chectl server:start --multiuser --platform=minikube`
$ chectl version
chectl/7.3.0 linux-x64 node-v10.16.3
Environment
Custom server running on VM - CentOS Linux release 7.7.1908 (Core)
Additional context
Problem started to appear after adding new custom devfile stack into devfile-registry following this guide. Since this moment, no workspace can be started, does not matter if it comes from predefined stacks of using external devfile with factory.
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (2 by maintainers)
Top GitHub Comments
Will test this in LDAP environment as soon as che-plugin-metadata-broker version is bumped to 3.1.2 in che-operator.
I have now Keycloak with LDAP setup on two minikube based Che instances, since plugin broker 3.1.2 everything works as expected. Thank you.