workspace pod never reached Running state: cannot schedule pod due to out of resources, reason: OutOfcpu
Open
Nobody has claimed this yet.
meta: never-stale
team: workspace
type: bug
- Dominant language
- TypeScript
- Stars
- 13.8k
- Forks
- 1.4k
- Avg merge
- 17h 58m
- Merged PRs (30d)
- 5
Description
Bug description
From the tracing, the us60 cluster reports
workspace pod never reached Running state: cannot schedule pod due to out of resources, reason: OutOfcpu
which we did not see at previous clusters.
Descript pod
status:
message: 'Pod Node didn''t have enough resource: cpu, requested: 2000, used: 15190,
capacity: 15900'
phase: Failed
reason: OutOfcpu
Steps to reproduce
We don't know for now.
Workspace affected
No response
Expected behavior
No response
Example repository
No response
Anything else?
We only saw this with literally one workspace in us60.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the tracing output and the pod status message showing phase Failed and reason OutOfcpu. Investigate why the us60 cluster could not schedule the workspace pod with the reported CPU request and capacity, then establish reproduction steps and an expected behavior; the issue is complete when the scheduling failure is diagnosed and addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100