Bug #799
Handle OpPreReq failures of OP_INSTANCE_CREATE gracefully
| Status: | Closed | Start date: | 07/11/2011 | |
|---|---|---|---|---|
| Priority: | Medium | Due date: | ||
| Assignee: | Vangelis Koukis | % Done: | 0% |
|
| Category: | Cyclades API | Spent time: | - | |
| Target version: | v0.5.1 |
Description
If instance creation fails at the PreReq phase, no machine is created at the Ganeti backend. The event daemon picks up OP_INSTANCE_CREATE failing, and the creates the relevant notification and Synnefo instance is marked in ERROR.
However, it can never be removed: DELETE /servers/id issues OP_INSTANCE_REMOVE at the backend, which cannot complete successfully,
since the logic layer requires notification of successful execution of OP_INSTANCE_REMOVE to mark an instance as deleted in the DB,
after the changes made in #721.
Possible fix: if an OP_INSTANCE_REMOVE fails with ECODE_NOENT = "unknown_entity", the Ganeti instance is no longer there, and the Synnefo instance should be marked as deleted.
Associated revisions
Handle removing machines in ERROR properly
Set the VM deleted flag when receiving a failure notification for a Ganeti
OP_INSTANCE_REMOVE operation, if the server is in ERROR state, since no
corresponding Ganeti instance backend exists in this case. Fixes #799.
History
#1 Updated by Vangelis Koukis almost 13 years ago
- Status changed from Assigned to Closed
093f9c53b merged into master fixes handling failed OP_INSTANCE_REMOVE when a machine is in ERROR and no Ganeti instance exists at the backend, this ticket may close.