ec2 api doesn't respect reclaim_instance_interval from nova.conf
Bug #1212581 reported by
Sam Stoelinga
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Compute (nova) |
Won't Fix
|
Wishlist
|
Unassigned | ||
Bug Description
When a user, uses the ec2 api to delete an instance the check whether the instance should be soft-deleted isn't done. This logic is current in api/nova/ and not in api/ec2.
I expected the ec2 api to have the same behavior. We currently lost user data because of this.
Would be nice to have compute/api.y only a contain a single delete function which does the checking whether to soft-delete or not instead of doing it in the api level.
Impact: High
| Changed in nova: | |
| assignee: | nobody → Sam Stoelinga (sammiestoel) |
| tags: | added: api ec2 |
| Changed in nova: | |
| status: | New → Confirmed |
| importance: | Undecided → Wishlist |
| Changed in nova: | |
| assignee: | Sam Stoelinga (sammiestoel) → nobody |
| Changed in nova: | |
| status: | Confirmed → Won't Fix |
To post a comment you must log in.
standalone ec2-api project doesn't have such bug because it works through piblic Nova API.