Public bug reported:
When reassigning floating IP from one VM to another on the same host, it
stops responding. This happens due to l3 agent just checks that IP
address is configured on the interface and does not update ip rules to
reflect new fixed IP.
Reassignment works if disassociate floating IP first and then associate it with
another fixed IP.
However API allows reassignment without disassociation so it should work as
well.
** Affects: neutron
Importance: Undecided
Assignee: Oleg Bondarev (obondarev)
Status: New
** Tags: l3-dvr-backlog liberty-backport-potential mitaka-backport-potential
** Tags added: mitaka-backport-potential
** Tags added: liberty-backport-potential
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1599089
Title:
DVR: floating ip stops working after reassignment
Status in neutron:
New
Bug description:
When reassigning floating IP from one VM to another on the same host,
it stops responding. This happens due to l3 agent just checks that IP
address is configured on the interface and does not update ip rules to
reflect new fixed IP.
Reassignment works if disassociate floating IP first and then associate it
with another fixed IP.
However API allows reassignment without disassociation so it should work as
well.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1599089/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
