yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #49878
[Bug 1572593] Re: Impossible attach detached port to another instance
Reviewed: https://review.openstack.org/308389
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=fc66e7eb411eb8e99767c062ab8d0263738d5558
Submitter: Jenkins
Branch: master
commit fc66e7eb411eb8e99767c062ab8d0263738d5558
Author: Timofey Durakov <tdurakov@xxxxxxxxxxxx>
Date: Wed Apr 20 17:58:23 2016 +0300
Clean port dns_name in case of port detach
In case of port detach dns_name should be also
updated in Neutron
Change-Id: I65edb33b955a91d1701fc91cb9fae0a5f26d4e46
Closes-Bug: #1572593
** Changed in: nova
Status: In Progress => Fix Released
--
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
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
References