[Nailgun] GET network_configuration throws error
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
High
|
Roman Prykhodchenko | ||
8.0.x |
Fix Released
|
High
|
Roman Prykhodchenko | ||
Mitaka |
Fix Released
|
High
|
Roman Prykhodchenko |
Bug Description
Well, the story is huge and requires some explanations.
We *do* have a network_
The problem occurs when we need to allocate VIPs more than we have free IPs in network pool. Since information how many VIPs we need is dynamic and is depended on plugins (since plugins may export network roles), we can't *validate* it on the first place. Moreover, it's depended on which network some netrole is assigned, so we can't and shouldn't forbid user to enable plugin.
Still, when new plugin is enabled, and we have not enough free IP addresses for VIPs the errors will be raised. If it's the case, the network_
Another way to hit this bug is to move controllers (or other roles that have VIP assigned to them) to different network node groups. In this case Nailgun will try to calculate common node group for VIPs allocation and throw an error because it will find more than 1 common group.
Unfortunately, there's no easy fix for UI.. since they don't know what's wrong.
I have no idea how to fix it. Perhaps we should start with removing VIP allocation code from serializing network settings for the API handler.
tags: |
added: feature-validation removed: feature-advanced-networking |
tags: | added: area-python |
tags: | added: team-bugfix |
Changed in fuel: | |
assignee: | Roman Prykhodchenko (romcheg) → Maciej Kwiek (maciej-iai) |
status: | Confirmed → In Progress |
Changed in fuel: | |
assignee: | Maciej Kwiek (maciej-iai) → Roman Prykhodchenko (romcheg) |
Changed in fuel: | |
milestone: | 8.0 → 9.0 |
Changed in fuel: | |
status: | In Progress → Fix Committed |
Changed in fuel: | |
status: | Fix Committed → In Progress |
description: | updated |
tags: | added: hit-hcf |
tags: | added: on-verification |
The discussion is here -
http:// lists.openstack .org/pipermail/ openstack- dev/2015- October/ 077258. html