yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #29317
[Bug 1431480] [NEW] When displaying the number of floating ips available for allocation, the number of actually available floating ips is not considered
Public bug reported:
The neutron CLI command reports of 8 floating IPs available for
allocation in the whole cluster,
root@node-4:~# neutron subnet-show 8c41a617-ac07-4fdb-b79e-0103f3b59b51
+-------------------+--------------------------------------------------+
| Field | Value |
+-------------------+--------------------------------------------------+
| allocation_pools | {"start": "172.16.57.87", "end": "172.16.57.94"} |
| cidr | 172.16.57.80/28 |
| dns_nameservers | |
| enable_dhcp | False |
| gateway_ip | 172.16.57.81 |
| host_routes | |
| id | 8c41a617-ac07-4fdb-b79e-0103f3b59b51 |
| ip_version | 4 |
| ipv6_address_mode | |
| ipv6_ra_mode | |
| name | net04_ext__subnet |
| network_id | 2525c40a-3b89-44e7-8f54-5a1d4d351a13 |
| tenant_id | fa5d1de1eb824bceb511867509b8bce4 |
+-------------------+--------------------------------------------------+
yet in the Horizon the default quota value for 'floating_ips' is shown
(equal to 50).
This is confusing because once 7 floating ips are allocated, all
subsequent allocations fail, yet User doesn't understand that this is
caused by pool exhaustion since he relies on <Default FIP Quota> -
<Number of allocated FIPs>
The minimum between the FIP Quota value and the Quantity of actually
available FIPs should be shown in Allocate FIP form.
** Affects: horizon
Importance: Medium
Assignee: Timur Sufiev (tsufiev-x)
Status: New
** Tags: neutron
** Changed in: horizon
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1431480
Title:
When displaying the number of floating ips available for allocation,
the number of actually available floating ips is not considered
Status in OpenStack Dashboard (Horizon):
New
Bug description:
The neutron CLI command reports of 8 floating IPs available for
allocation in the whole cluster,
root@node-4:~# neutron subnet-show 8c41a617-ac07-4fdb-b79e-0103f3b59b51
+-------------------+--------------------------------------------------+
| Field | Value |
+-------------------+--------------------------------------------------+
| allocation_pools | {"start": "172.16.57.87", "end": "172.16.57.94"} |
| cidr | 172.16.57.80/28 |
| dns_nameservers | |
| enable_dhcp | False |
| gateway_ip | 172.16.57.81 |
| host_routes | |
| id | 8c41a617-ac07-4fdb-b79e-0103f3b59b51 |
| ip_version | 4 |
| ipv6_address_mode | |
| ipv6_ra_mode | |
| name | net04_ext__subnet |
| network_id | 2525c40a-3b89-44e7-8f54-5a1d4d351a13 |
| tenant_id | fa5d1de1eb824bceb511867509b8bce4 |
+-------------------+--------------------------------------------------+
yet in the Horizon the default quota value for 'floating_ips' is shown
(equal to 50).
This is confusing because once 7 floating ips are allocated, all
subsequent allocations fail, yet User doesn't understand that this is
caused by pool exhaustion since he relies on <Default FIP Quota> -
<Number of allocated FIPs>
The minimum between the FIP Quota value and the Quantity of actually
available FIPs should be shown in Allocate FIP form.
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1431480/+subscriptions
Follow ups
References
