yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #19901
[Bug 1356464] Re: Assigning a FIP to a VIP port does not work, if the VIP resides in a subnet that is associated with a DVR router residing in a service node with no default gateway.
** Changed in: neutron
Status: Fix Committed => 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/1356464
Title:
Assigning a FIP to a VIP port does not work, if the VIP resides in a
subnet that is associated with a DVR router residing in a service node
with no default gateway.
Status in OpenStack Neutron (virtual network service):
Fix Released
Bug description:
With DVR routers for FIP to work, there has to be a FIP Namespace that should be created and an IR Namespace.
But when a LBaaS VIP port is created on a Subnet that is part of the DVR router, the IR Namespace is not created for the VIP port since that port is not a Compute Port.
There are some corner cases here, when there are VMs in a node then
the IR's for that subnet is already created and so the FIP namespace
also will be created.
The issue will only be seen if the compute and the VIP ports are
separated apart.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1356464/+subscriptions
References