As part of my analysis on this issue, the scenario is the limitation of the current neutron code regarding raising an exception whenever a floatingip is attached to an instance whose subnet's gateway-ip is not connected to the current router, but the router has an interface in that subnet. I am attaching a Patch regarding the issue, which contains the implementation of:
1) Throwing a Warning in the Logs in neutron server regarding the scenario
2) Displaying a Warning message in the horizon conditionally
So that we are able to to attach a floatingip to an instance whose subnet is connected to the router(otherthan the gateway-ip of subnet) with a warning message which is not harmful. Could you please confirm whether the patch meets our need or need to have some changes.
Hi Zsolt Krenak, Mathew Taylor
As part of my analysis on this issue, the scenario is the limitation of the current neutron code regarding raising an exception whenever a floatingip is attached to an instance whose subnet's gateway-ip is not connected to the current router, but the router has an interface in that subnet. I am attaching a Patch regarding the issue, which contains the implementation of:
1) Throwing a Warning in the Logs in neutron server regarding the scenario
2) Displaying a Warning message in the horizon conditionally
So that we are able to to attach a floatingip to an instance whose subnet is connected to the router(otherthan the gateway-ip of subnet) with a warning message which is not harmful. Could you please confirm whether the patch meets our need or need to have some changes.