Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1417686

Summary: Microversion 2.37 break 2.32 usage
Product: Red Hat OpenStack Reporter: Stephen Gordon <sgordon>
Component: openstack-novaAssignee: Artom Lifshitz <alifshit>
Status: CLOSED NEXTRELEASE QA Contact: Prasanth Anbalagan <panbalag>
Severity: high Docs Contact:
Priority: high    
Version: 10.0 (Newton)CC: berrange, dasmith, eglynn, kchamart, sbauza, sferdjao, sgordon, srevivo, vromanso
Target Milestone: Upstream M1   
Target Release: 11.0 (Ocata)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1436266 (view as bug list) Environment:
Last Closed: 2017-03-27 14:32:00 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1416565, 1436266    

Description Stephen Gordon 2017-01-30 16:30:18 UTC 
Cloned from launchpad bug 1658571.

Description:

Device tagging support was added in microversion 2.32, as for
ports:
http://git.openstack.org/cgit/openstack/nova/tree/nova/api/openstack/compute/schemas/servers.py#n76
but in latter microversion 2.37 accidentally removed it:
http://git.openstack.org/cgit/openstack/nova/tree/nova/api/openstack/compute/schemas/servers.py#n82

And for bdms:
the schema is added by
https://github.com/openstack/nova/blob/master/nova/api/openstack/compute/block_device_mapping.py#L76
and it will only work for microversion 2.32

So this function is only usable from microversion 2.32 to 2.37 for
ports and only for 2.32 for bdms.

we should fix it and backport to Newton.

Specification URL (additional information):

https://bugs.launchpad.net/nova/+bug/1658571
Comment 1 Stephen Gordon 2017-01-30 16:42:09 UTC 
Discussing on the team call today we pondered whether it is feasible for RHOSP 10/11 to workaround this issue by patching the client to explicitly set the relevant microversion when calling `nova boot` with tags.

This would require analyzing the intersection with any microversions occuring after those that work with the feature.
Comment 2 Artom Lifshitz 2017-03-27 14:19:12 UTC 
A downstream client workaround has been done for bz1436266, in which the client sets the microversion according to what sort of tagging has been request to allow device tagging to work out of the box as much as possible without needing to pass the --os-compute-api-version flag. This is the best we can do in OSP10 - the real fix will come in OSP11 and microversion 2.42.