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

[Callisto13]

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):

[Callisto13]

Actually this is fine, just really really slow. Will be less of a problem when we get #310 in.

[Callisto13]

Actually this is a problem. Minor, but still.

When I call delete and the current plan is sat waiting for the next retry attempt, the delete will not be registered until the next reschedule. When you are near the end of attempts (like on 9) this can be a really long time.

Ideally a delete should be able to cancel that wait.

[github-actions]

This issue is stale because it has been open 60 days with no activity.

[github-actions]

This issue is stale because it has been open 60 days with no activity.

[github-actions]

This issue was closed because it has been stalled for 365 days with no activity.