instance.delete notification is missing for unscheduled instance
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
Matt Riedemann | ||
Ocata |
Fix Committed
|
High
|
Matt Riedemann |
Bug Description
Description
===========
It seems that the Move instance creation to conductor commit [1] changed when and how the instance.delete notification is emitted for an unscheduled instance. Unfortunately the legacy notification doesn't have test coverage and the versioned notification coverage are still on review [2] for this case.
Before [1] the instance.delete for an unscheduled instance is emitted from here [3]. But after [1] the execution of the same delete operation goes to a new direction [4] and never reaches [3].
Before [1] the new test coverage in [2] was passing but now after [1] is merged the test_create_
[1] https:/
[2] https:/
[3] https:/
[4] https:/
Steps to reproduce
==================
Run the nova functional test in patch [2] before and after commit [1]. The test_create_
Environment
===========
Nova functional test env with based on commit f9d7b383a7cb12b
Logs & Configs
==============
Changed in nova: | |
assignee: | nobody → Balazs Gibizer (balazs-gibizer) |
tags: | added: ocata-backport-potential |
Changed in nova: | |
status: | New → Confirmed |
importance: | Undecided → High |
Changed in nova: | |
assignee: | Balazs Gibizer (balazs-gibizer) → Dan Smith (danms) |
Changed in nova: | |
assignee: | Dan Smith (danms) → Matt Riedemann (mriedem) |
Changed in nova: | |
assignee: | Matt Riedemann (mriedem) → Balazs Gibizer (balazs-gibizer) |
Changed in nova: | |
assignee: | Balazs Gibizer (balazs-gibizer) → Matt Riedemann (mriedem) |
Fix proposed to branch: master /review. openstack. org/437222
Review: https:/