Bug 1284493 - Delete instance should veify instance is deleted before returning
Summary: Delete instance should veify instance is deleted before returning
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-novaclient
Version: 8.0 (Liberty)
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 8.0 (Liberty)
Assignee: Eoghan Glynn
QA Contact: nlevinki
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-11-23 13:33 UTC by yfried
Modified: 2023-09-14 03:13 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-11-24 17:05:30 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description yfried 2015-11-23 13:33:41 UTC
Description of problem:
Nova operations are async and return before they are done. This is problematic during cleanup scripts and automation (Tempest, Khaleesi, etc...) where VM deletion returns before the VM is deleted and subsequent resource deletions will fail because VM is still alive on the system

As a result each script needs to implement a waiter to handle nova resources

Please add a flag that will force nova operations to become sync like other clients and return only when operation is actually done.

How reproducible:
$ nova delete <vm> && nova show <vm>

Actual results:
VM is shown in "deleting" state

Expected results:
404 error - VM doesn't exist.

Comment 2 Eoghan Glynn 2015-11-24 17:05:30 UTC
This aynchrony is intended behavior in the nova API and realistically-speaking will not be changed upstream.

Comment 3 yfried 2015-11-25 17:58:08 UTC
Can't we ADD a sync mode where we wait for actions to complete?

Comment 4 Red Hat Bugzilla 2023-09-14 03:13:32 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days


Note You need to log in before you can comment on or make changes to this bug.