Comment 1 for bug 1959699
Revision history for this message
| Rodolfo Alonso (rodolfo-alonso-hernandez) wrote | #1 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0f7b58d
(Get the code!)
Hello Sebastian:
First of all, let me pointing out that [1] was not the same problem as in this bug. In [1], the router port had an IP address outside the subnet CIDR; that was an error. This is not the case here, were the FIP receives an IP address in this range.
IMO, we should allow this. The GW IP is not a Neutron resource (an IP allocation, associated to a port). This is a parameter of the subnet. We could write a warning message in the logs, that's all. The user should be able to assign this IP to a FIP (for whatever use case I can't image now). Of course, that's my own opinion only.
Regards.
[1]https:/