+++ This bug was initially created as a clone of Bug #1417686 +++ 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 --- Additional comment from Stephen Gordon on 2017-01-30 11:42:09 EST --- 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.
This bugzilla has been removed from the release and needs to be reviewed and Triaged for another Target Release.
The fix, which is really a workaround, is to have the client modify the version being sent depending on what kind of device tagging, if any, has been requested. This works in all cases except bdm tagging + auto network, because the former needs ==2.32 and the latter needs >=2.37.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2017:1595