oxidecomputer / oxidecomputer/omicron
Instance stuck in `starting` later stuck in `stopping`
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
On dogfood, created the instance through Terraform, got stuck in starting. Later after trying to stop the instance through the CLI, it switches to being stuck in stopping.
Also I found whilst it cannot be deleted in these states, it did manage to delete the network interfaces. Should this be prevented since the network interface cannot be edited on a stopped instance.
You can find the log at:
/net/catacomb/data/staff/dogfood/jun-29/38b7d88a-02a8-402a-9088-8d6dd6896a65-stuck-starting.log
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 by reviewing the supplied log at /net/catacomb/data/staff/dogfood/jun-29/38b7d88a-02a8-402a-9088-8d6dd6896a65-stuck-starting.log and tracing the instance lifecycle exercised through Terraform and the CLI. Done should include identifying why the instance remains in starting or stopping and clarifying whether network-interface deletion must be prevented in those states.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, terraform
- Domain
- backend, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100