yahoo-eng-team team mailing list archive

[Boden R <bodenvmw@xxxxxxxxx>]

As long as the FIP given via --floating-ip-address is within the CIDR of
the external net it's valid. The allocation pool is for automatic
allocations.

Try your scenario above and pass a --floating-ip-address that's not in the external net CIDR.
You should get something like this:

InvalidIpForNetworkClient: IP address 11.11.1.119 is not a valid IP for
any of the subnets on the specified network.

** Changed in: neutron
       Status: New => Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1654958

Title:
  Foaltingip can apply for to limit beyond the range of the IP

Status in neutron:
  Invalid

Bug description:
  Limit range for 172.30.0.130 to 172.30.0.254 floatingip address
  [root@node-1 ~]# neutron subnet-show c3dfb7a9-4526-4a12-aec5-34bf22b1926f
  +-------------------+--------------------------------------------------+
  | Field             | Value                                            |
  +-------------------+--------------------------------------------------+
  | allocation_pools  | {"start": "172.30.0.130", "end": "172.30.0.254"} |
  | cidr              | 172.30.0.0/24                                    |
  | dns_nameservers   |                                                  |
  | enable_dhcp       | False                                            |
  | gateway_ip        | 172.30.0.1                                       |
  | host_routes       |                                                  |
  | id                | c3dfb7a9-4526-4a12-aec5-34bf22b1926f             |
  | ip_version        | 4                                                |
  | ipv6_address_mode |                                                  |
  | ipv6_ra_mode      |                                                  |
  | name              | public_net__subnet                               |
  | network_id        | e9434edd-3402-4de1-aa36-ad8899f6a203             |
  | subnetpool_id     |                                                  |
  | tenant_id         | 57364a142e3e4b7187aaf89f054a85bd                 |
  +-------------------+--------------------------------------------------+
  But creating floatingip outside of this range or can create success
  [root@node-1 ~]# neutron floatingip-create --floating-ip-address 172.30.0.127 public_net
  Created a new floatingip:
  +---------------------+--------------------------------------+
  | Field               | Value                                |
  +---------------------+--------------------------------------+
  | bandwidth           | 4                                    |
  | fixed_ip_address    |                                      |
  | floating_ip_address | 172.30.0.127                         |
  | floating_network_id | e9434edd-3402-4de1-aa36-ad8899f6a203 |
  | id                  | cffcd4a5-4239-4947-a1f7-4fddc9413ec1 |
  | port_id             |                                      |
  | router_id           |                                      |
  | status              | DOWN                                 |
  | tenant_id           | e8cf9c9245f24f209263465bcb2cc8c4     |
  +---------------------+--------------------------------------+

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1654958/+subscriptions