Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Slow pvc binding: Che workspace fails to start because of pod has unbound PersistentVolumeClaims #11848

Closed
ghost opened this issue Nov 6, 2018 · 1 comment
Closed

Slow pvc binding: Che workspace fails to start because of pod has unbound PersistentVolumeClaims #11848

ghost opened this issue Nov 6, 2018 · 1 comment
Assignees
@sleshchenko
Labels
kind/bug Outline of a bug - must adhere to the bug report template. severity/blocker Causes system to crash and be non-recoverable or prevents Che developers from working on Che code.

Comments

@ghost
Copy link

ghost commented Nov 6, 2018 •
edited by ghost
Loading

Description

When Che is deployed to an OpenShift cluster that is rather slow (namely pvc binding), the initial workspace start fails with an error:

2018-11-06 16:09:47,621[aceSharedPool-0]  [WARN ] [.i.k.KubernetesInternalRuntime 226]  - Failed to start Kubernetes runtime of workspace workspacedn0abvgbmahcwujf. Cause: Unrecoverable event occurred: 'FailedScheduling', 'pod has unbound PersistentVolumeClaims (repeated 5 times)', 'workspacedn0abvgbmahcwujf.dockerimage-74f4445d89-pstgk'

image

It happens because pvcs are in pending state.

image

I wonder if it's possible to track status of pvs before creating deployment.

This cannot be fixed by removing this event from unrecoverable events in Che conf, since the error happens on k8s level - Che is attempting to create a deployment with a pod spec that uses unbound pvc.
@ghost ghost added kind/bug Outline of a bug - must adhere to the bug report template. severity/P1 Has a major impact to usage or development of the system. labels Nov 6, 2018
@sleshchenko
Copy link
Member

I also faced the same issue on local minikube instance.

@dmytro-ndp dmytro-ndp added severity/blocker Causes system to crash and be non-recoverable or prevents Che developers from working on Che code. and removed severity/P1 Has a major impact to usage or development of the system. labels Nov 9, 2018
@sleshchenko sleshchenko self-assigned this Nov 12, 2018
@sleshchenko sleshchenko added the status/in-progress This issue has been taken by an engineer and is under active development. label Nov 12, 2018
@sleshchenko sleshchenko mentioned this issue Nov 13, 2018
Merged
@skabashnyuk skabashnyuk mentioned this issue Nov 15, 2018
Closed
10 tasks
@dmytro-ndp dmytro-ndp removed the status/in-progress This issue has been taken by an engineer and is under active development. label Nov 18, 2018
@sleshchenko sleshchenko mentioned this issue May 27, 2019
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sleshchenko sleshchenko

Labels
kind/bug Outline of a bug - must adhere to the bug report template. severity/blocker Causes system to crash and be non-recoverable or prevents Che developers from working on Che code.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@dmytro-ndp @skabashnyuk @sleshchenko