BuildRequest ovo incorrectly assumes that IncompatibleObjectVersion exception has an objver field
Bug #1812177 reported by
Balazs Gibizer
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Low
|
Balazs Gibizer | ||
Ocata |
Fix Committed
|
Low
|
Matt Riedemann | ||
Pike |
Fix Committed
|
Low
|
Elod Illes | ||
Queens |
Fix Committed
|
Low
|
Elod Illes | ||
Rocky |
Fix Released
|
Low
|
Elod Illes |
Bug Description
BuildRequest ovo incorrectly assumes that IncompatibleObj
Changed in nova: | |
assignee: | nobody → Balazs Gibizer (balazs-gibizer) |
status: | New → In Progress |
Changed in nova: | |
importance: | Undecided → Low |
tags: | added: conductor |
no longer affects: | ubuntu |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/631179 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=975f0156137 e37f7a9139c0268 547d79dcc3c43c
Committed: https:/
Submitter: Zuul
Branch: master
commit 975f0156137e37f 7a9139c0268547d 79dcc3c43c
Author: Balazs Gibizer <email address hidden>
Date: Wed Jan 16 10:57:07 2019 +0100
Fix incompatible version handling in BuildRequest
The BuildRequest object code assumed that IncompatibleObj ectVersion
exception has a objver field that contains the object version. This
assumption is not true. The unit test made another mistake serializing
the function object obj_to_primitive instead of serializing the result
of the call of obj_to_primitive. This caused a false positive test
covering the error in the implementation as well.
Closes-Bug: #1812177
Change-Id: I1ef4a23aa2bf5c b46b481045f3d96 8f62f74606d