55db0a565c
The 1.2.0 release broke the API methods to set and unset flavor extra specs because we need the raw object, as returned from the nova client, to make method calls to change those values. As a result, a new 'raw' parameter was added to the submitTask() method of TaskManager to allow us to get these raw objects back. Additionally, we were never displaying the 'extra_specs' for a flavor. This, too, requires a raw object method call. Flavors are now normalized to remove client cruft and make sure that 'extra_specs' is always an attribute. As if that weren't enough, we now do functional tests for these things! What more could one ask for??? Change-Id: Ie5c132317392cf26df2c8f43e9f07d040119eca0
8 lines
257 B
YAML
8 lines
257 B
YAML
---
|
|
features:
|
|
- Flavors will always contain an 'extra_specs' attribute. Client cruft,
|
|
such as 'links', 'HUMAN_ID', etc. has been removed.
|
|
fixes:
|
|
- Setting and unsetting flavor extra specs now works. This had
|
|
been broken since the 1.2.0 release.
|