0/1 nodes are available: 1 Insufficient memory
See original GitHub issueDescribe the bug
Error when starting workspace:
Unified Che Plugin Broker
Starting VS Code and Theia plugins processing
Starting Che plugins and editor processing
Downloading VS Code extension for plugin 'ms-python/python/latest'
List of plugins and editors to install
- ms-python/python/latest - Linting, Debugging (multi-threaded, remote), Intellisense, code formatting, refactoring, unit tests, snippets, and more.
- eclipse/che-machine-exec-plugin/0.0.1 - Che Plug-in with che-machine-exec service to provide creation terminal or tasks for Eclipse CHE workspace machines.
- eclipse/che-theia/7.0.0-next - Eclipse Theia, get the latest release each day.
All plugins have been successfully processed
0/1 nodes are available: 1 Insufficient memory.
Error: Failed to run the workspace: "Unrecoverable event occurred: 'FailedScheduling', '0/1 nodes are available: 1 Insufficient memory.', 'workspacell2g2kpcqi40b7ww.python-5d87d587d8-7lct5'"
Che version
- 7.0.0-rc-5.0-SNAPSHOT
Steps to reproduce
- Open Dashboard
- Click ‘Create Workspace’
- Select ‘Python’ (Stack with Python 3.6)
- Add project ‘python-hello-world’
- Add plugin ‘Che machine-exec Service latest’
- Add plugin ‘Eclipse IDE (ws-skeleton publisher) latest’
- Click ‘Create & Open’
Expected behavior
Workspace should start
Runtime
docker --version
Docker version 18.03.0-ce, build 0520e24
docker-compose --version
docker-compose version 1.20.1, build 5d8c71b
docker-machine --version
docker-machine version 0.14.0, build 89b8332
minikube version
minikube version: v1.2.0
kubectl version --client
Client Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.1", GitCommit:"4485c6f18cee9a5d3c3b4e523bd27972b1b53892", GitTreeState:"clean", BuildDate:"2019-07-18T14:25:20Z", GoVersion:"go1.12.7", Compiler:"gc", Platform:"darwin/amd64"}
helm version
Client: &version.Version{SemVer:"v2.14.2", GitCommit:"a8b13cc5ab6a7dbef0a58f5061bcc7c0c61598e7", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.14.2", GitCommit:"a8b13cc5ab6a7dbef0a58f5061bcc7c0c61598e7", GitTreeState:"clean"}
chectl --version
chectl/0.0.2-a74ad81 darwin-x64 node-v10.4.1
minikube status
host: Running
kubelet: Running
apiserver: Running
kubectl: Correctly Configured: pointing to minikube-vm at 192.168.99.100
minikube start --memory=10240
😄 minikube v1.2.0 on darwin (amd64)
💡 Tip: Use 'minikube start -p <name>' to create a new cluster, or 'minikube delete' to delete this one.
🔄 Restarting existing virtualbox VM for "minikube" ...
⌛ Waiting for SSH access ...
🐳 Configuring environment for Kubernetes v1.15.0 on Docker 18.09.6
🔄 Relaunching Kubernetes v1.15.0 using kubeadm ...
⌛ Verifying: apiserver proxy etcd scheduler controller dns
🏄 Done! kubectl is now configured to use "minikube"
kubectl get nodes
NAME STATUS ROLES AGE VERSION
minikube Ready master 13h v1.15.0
kubectl get services
kubernetes ClusterIP 10.96.0.1 <none> 443/TCP 13h
kubectl get pod --namespace ch
che-54f4459fb4-jtfms 1/1 Running 0 37m
devfile-registry-549b9bbd5b-jg7h6 1/1 Running 1 12h
plugin-registry-75478b67dd-bnvf2 1/1 Running 1 12h
chectl --help server
control Che server
chectl workspace:list
› Warning: Not implemented yet
› Warning: Not implemented yet
› Warning: Not implemented yet
TypeError: Expected property `task` to be of type `function`, got `undefined`
at new Task (/snapshot/chectl/node_modules/listr/lib/task.js:25:10)
at Listr.add (/snapshot/chectl/node_modules/listr/index.js:71:21)
at new Listr (/snapshot/chectl/node_modules/listr/index.js:50:8)
at List.<anonymous> (/snapshot/chectl/lib/commands/workspace/list.js:0:0)
at Generator.next (<anonymous>)
at __awaiter (/snapshot/chectl/node_modules/tslib/tslib.js:110:75)
at new Promise (<anonymous>)
at Object.__awaiter (/snapshot/chectl/node_modules/tslib/tslib.js:106:16)
at List.run (/snapshot/chectl/lib/commands/workspace/list.js:0:0)
at List._run (/snapshot/chectl/node_modules/@oclif/command/lib/command.js:44:31)
Screenshots
Installation method
- chectl
Environment
OS: macOS Mojave 10.14.6 Browser: Google Chrome Version 75.0.3770.142 (Official Build) (64-bit) Running Eclipse Che locally
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (3 by maintainers)
Top GitHub Comments
Yeah, the issue is you need to
minikube delete
and thenminikube start --memory=10240Mi
. In the output you can seeI’ve been bitten by this before.
Deleting
minikube
and starting withminikube start --memory=8192
solved the issue.Thank you all for your quick support!