[Fuel UI] Multiple floating ranges are not supported when using Neutron
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Triaged
|
Medium
|
Fuel Sustaining | ||
Newton |
Triaged
|
Medium
|
Fuel Sustaining |
Bug Description
Steps to reproduce:
1. Create an environment using Neutron
2. In the Network settings define multiple floating ranges for floating ips
3. Deploy the environment
Current result:
Deployment succeeds but only a single allocation_pool gets allocated to the floating subnet
Expected result:
For all releases of Neutron that do not support fragmented floating ip ranges in a single subnet, disable this functionality from the UI. Or fix multiple floating allocation_pools in a single subnet
There are 2 fixes, for having fragmented floating IPs in a single subnet:
1. Divide them into different subnets, where every subnet has 1 allocation_pool
2. Bypass API and directly manipulate mysql db, seems risky! For more info see: http://
See related discussion:
https://<email address hidden>
Changed in fuel: | |
milestone: | none → 6.0 |
summary: |
- [Fuel UI] Multiple floating ranges not supported when using Neutron + [Fuel UI] Multiple floating ranges not working when using Neutron |
Changed in fuel: | |
assignee: | Sam Stoelinga (sammiestoel) → nobody |
Changed in fuel: | |
importance: | Wishlist → Medium |
milestone: | 6.0 → 6.1 |
assignee: | nobody → Fuel Python Team (fuel-python) |
importance: | Medium → Low |
summary: |
- [Fuel UI] Multiple floating ranges not working when using Neutron + [Fuel UI] Multiple floating ranges are not supported when using Neutron |
tags: | added: feature |
Changed in fuel: | |
milestone: | 6.1 → 7.0 |
milestone: | 7.0 → 6.1 |
tags: | added: module-networks |
Changed in fuel: | |
milestone: | 7.0 → 8.0 |
Changed in fuel: | |
importance: | Low → Medium |
Changed in fuel: | |
status: | Confirmed → Triaged |
tags: | added: area-python |
Changed in fuel: | |
milestone: | 8.0 → 9.0 |
tags: | added: area-ui |
Changed in fuel: | |
assignee: | Fuel Python (Deprecated) (fuel-python) → Fuel Sustaining (fuel-sustaining-team) |
Changed in fuel: | |
milestone: | 10.0 → 10.1 |
Changed in fuel: | |
milestone: | 10.1 → 11.0 |
Should this be included into Release Notes?
Can 2 abovementioned fixed be described as a possible workaround?