Public bug reported: Devstack 2015.1, single box.
Trying to get floating ips to work across 2 /24 blocks (on a /16 subnet) Localrc: HOST_IP=10.100.130.8 # public ip of host, 10.100.0.0/16 subnet FLAT_INTERFACE=eth0 FIXED_RANGE=10.140.129.0/24 # private FIXED_NETWORK_SIZE=255 FLOATING_RANGE=10.100.129.0/16 #publicly reachable network for vms, also in 10.100.0.0/16, but only 10.100.129.X block MULTI_HOST=0 LOGFILE=/opt/stack/logs/stack.sh.log ADMIN_PASSWORD=* MYSQL_PASSWORD=* RABBIT_PASSWORD=* SERVICE_PASSWORD=* SERVICE_TOKEN=* Creating a guest : assigned ips private=10.140.129.3, 10.100.129.2 On the host itself (ip a l) inet 10.100.129.2/32 scope global br100 valid_lft forever preferred_lft forever Address is not accessible from the outside (because it's a /32, expected a /16) Initial pool was created with range 10.100.0.0 - 10.100.255.255 and then started assigning ips from 10.100.0.1 conflicting with the router, and also ips were assigned /32 I deleted the pool and created a new one: 10.100.129.0 - 10.100.129.255 but ips are still /32. ** Affects: nova Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1404817 Title: On a /16 range floating ip is assigned /32 - cannot connect Status in OpenStack Compute (Nova): New Bug description: Devstack 2015.1, single box. Trying to get floating ips to work across 2 /24 blocks (on a /16 subnet) Localrc: HOST_IP=10.100.130.8 # public ip of host, 10.100.0.0/16 subnet FLAT_INTERFACE=eth0 FIXED_RANGE=10.140.129.0/24 # private FIXED_NETWORK_SIZE=255 FLOATING_RANGE=10.100.129.0/16 #publicly reachable network for vms, also in 10.100.0.0/16, but only 10.100.129.X block MULTI_HOST=0 LOGFILE=/opt/stack/logs/stack.sh.log ADMIN_PASSWORD=* MYSQL_PASSWORD=* RABBIT_PASSWORD=* SERVICE_PASSWORD=* SERVICE_TOKEN=* Creating a guest : assigned ips private=10.140.129.3, 10.100.129.2 On the host itself (ip a l) inet 10.100.129.2/32 scope global br100 valid_lft forever preferred_lft forever Address is not accessible from the outside (because it's a /32, expected a /16) Initial pool was created with range 10.100.0.0 - 10.100.255.255 and then started assigning ips from 10.100.0.1 conflicting with the router, and also ips were assigned /32 I deleted the pool and created a new one: 10.100.129.0 - 10.100.129.255 but ips are still /32. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1404817/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp