Neutron port fixed_ips backwards incompatible change wrt "[]"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Heat |
Fix Released
|
High
|
Rabi Mishra |
Bug Description
Since this change, we're seeing different behaviour in existing tripleo templates:
https:/
The problem is that we wire in a parameter, which relies on the existing behavior where an empty list is treated the same as not passing any fixed_ips:
https:/
https:/
ControlFixedIPs has a default of an empty list, which used to mean neutron assigned the IPs, but now it means we literally get an empty list, e.g no IPs
This breaks TripleO, and despite being more technically correct from a neutron interface perspective, it's a backwards incompatible change.
I think we have to work out a way to not break existing templates, even if the new behaviour has to be introduced via a new property or something.
tags: | added: tripleo |
Changed in heat: | |
assignee: | nobody → Rabi Mishra (rabi) |
Changed in heat: | |
status: | New → Triaged |
importance: | Undecided → High |
Fix proposed to branch: master /review. openstack. org/272983
Review: https:/