You have been subscribed to a public bug:
osp10
We crated:
External network.
2 internal networks- net1 and net2.
Port from each network - port1 and port2.
Trunk, configured with port1.
Trunk sub-port configured with port2.
Floating ip.
We booted a VM with port1 port and configured on the VM eth0 with
eth0.VLAN sub interface, matches port2 configuration.
We assigned FIP to port2 - no connectivity to VM via port 2.
Cause:
Due to 1 GW on the VM via eth0 ( untagged ), all tagged requests that need GW
go to the untagged GW- which fails the connectivity.
This behavior is correct.
So there is no meaning to assign fip to neutron port which was configured as
trunk subport.
We should block this option.
** Affects: neutron
Importance: Undecided
Status: Invalid
** Tags: neutron
--
Vlan aware VM - assign FIP to port which configured as "subport" is irrelevant.
https://bugs.launchpad.net/bugs/1636483
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
--
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
