If we backport the fix for this in nova we also have to backport the fix for the bug that it introduced:
https://review.openstack.org/#/c/310474/ ** Also affects: nova/mitaka Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1572593 Title: Impossible attach detached port to another instance Status in heat: Invalid Status in neutron: Invalid Status in OpenStack Compute (nova): Fix Released Status in OpenStack Compute (nova) mitaka series: In Progress Bug description: The follow scenario leads to error: - create independent port in neutron - boot VM in nova - attach port to VM via nova interface-attach. As result dns_name of port will be updated and port be attached to VM - detach port from VM via nova interface-detach. As result port will be detached, BUT dns_name will be still as name of VM. if you try to attach this port to another VM you will get error, that it's not possible to attach port. The same issue happens for Heat stack, when we have VM+port and execute update replace for Server. To manage notifications about this bug go to: https://bugs.launchpad.net/heat/+bug/1572593/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
