Build notification in conductor fails to send due to InstanceNotFound
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
| OpenStack Compute (nova) |
High
|
melanie witt | ||
| Ocata |
High
|
melanie witt | ||
| Pike |
High
|
melanie witt |
Bug Description
I found this issue while working on improving the CellDatabases fixture by defaulting untargeted DB access to 'cell0' instead of 'cell1'.
While building an instance in conductor, it sends a notification about the changed state using notifications.
We need to target the context in case the notification call needs to load something from the instance's cell database.
Changed in nova: | |
status: | New → In Progress |
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit 54cf9f5a90d7458
Author: melanie witt <email address hidden>
Date: Thu Oct 5 23:55:58 2017 +0000
Target context for build notification in conductor
When sending notifications about an instance, it's possible the
notification payload will have attributes not already loaded on
the instance. In this case, a lazy-load will happen and if the
load method needs to lookup the instance (example: in the
_check_
InstanceNot
will fail to be sent.
This targets the instance context to the instance's cell when
calling the send notification method.
Closes-Bug: #1721670
Change-Id: I6b9eb120b6e7fc
Changed in nova: | |
status: | In Progress → Fix Released |
Fix proposed to branch: stable/pike
Review: https:/
Changed in nova: | |
importance: | Undecided → High |
Changed in nova: | |
importance: | High → Medium |
tags: | added: notifications |
Fix proposed to branch: stable/ocata
Review: https:/
Changed in nova: | |
importance: | Medium → High |
Reviewed: https:/
Committed: https:/
Submitter: Zuul
Branch: stable/pike
commit 594b33469bc1621
Author: melanie witt <email address hidden>
Date: Thu Oct 5 23:55:58 2017 +0000
Target context for build notification in conductor
When sending notifications about an instance, it's possible the
notification payload will have attributes not already loaded on
the instance. In this case, a lazy-load will happen and if the
load method needs to lookup the instance (example: in the
_check_
InstanceNot
will fail to be sent.
This targets the instance context to the instance's cell when
calling the send notification method.
Closes-Bug: #1721670
Change-Id: I6b9eb120b6e7fc
(cherry picked from commit 54cf9f5a90d7458
Reviewed: https:/
Committed: https:/
Submitter: Zuul
Branch: stable/ocata
commit d7a60f8a1c51070
Author: melanie witt <email address hidden>
Date: Thu Oct 5 23:55:58 2017 +0000
Target context for build notification in conductor
When sending notifications about an instance, it's possible the
notification payload will have attributes not already loaded on
the instance. In this case, a lazy-load will happen and if the
load method needs to lookup the instance (example: in the
_check_
InstanceNot
will fail to be sent.
This targets the instance context to the instance's cell when
calling the send notification method.
Closes-Bug: #1721670
Conflicts:
nova/
nova/
NOTE(melwitt): Conflict was due to the older version of target_cell
not yielding a new RequestContext, the absence of set_target_cell,
and an older version of the unit test in Ocata.
Change-Id: I6b9eb120b6e7fc
(cherry picked from commit 54cf9f5a90d7458
This issue was fixed in the openstack/nova 17.0.0.0b1 development milestone.
This issue was fixed in the openstack/nova 16.0.2 release.
This issue was fixed in the openstack/nova 15.0.8 release.
Fix proposed to branch: master /review. openstack. org/509967
Review: https:/