[ws-daemon] Stops on SIGINT + restarts, leaves workspace pods in "terminating"
Open
Nobody has claimed this yet.
component: ws-daemon
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
ws-daemon seems to:
- receive SIGNIT (why, from whom? node in bad state?)
- restart right after
- leaves workspaces in "terminating"
- PD alert (1st one): https://gitpod.slack.com/archives/C01TNS8EVQT/p1652164161037079
- pod name:
ws-daemon-qhcfc - node name:
workspace-ws-us44-pool-xc2k - GCloud logs
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 ws-daemon pod logs and the linked Google Cloud and Slack reports, then trace how SIGINT causes the daemon to restart. Investigate why workspace pods remain in "terminating" and verify that a daemon restart no longer leaves them in that state.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- google-cloud, kubernetes, typescript
- Domain
- backend, cloud, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100