liquidmetal-dev / liquidmetal-dev/flintlock

I should be able to delete an mvm even if it has not finished creating yet

Open
#314 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

good first issue kind/bug lifecycle/stale
Dominant language
Go
Stars
1.5k
Forks
73
Avg merge
17h 24m
Merged PRs (30d)
30

Description

What happened:
I created an MVM and it failed to start properly and was on its 6th attempt of the reconciliation loop.
I tried to delete it, but the delete only went through after the 10th create attempt had been made.

What did you expect to happen:
A delete should delete regardless of the created state of the mvm, or what stage of the process it is in.

How to reproduce it:
Make reconciliation fail any old how (messing up IfaceCreate is a good one), call create, then delete before recons get to 10/10.

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

Environment:

  • flintlock version:
  • containerd version:
  • OS (e.g. from /etc/os-release):

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the issue with a failed reconciliation, such as disrupting IfaceCreate, then trace the MVM create and delete lifecycle while retries are still in progress. Done means an MVM can be deleted before reconciliation reaches the tenth create attempt, regardless of its creation stage.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.