Inconsistent implementation of setting networks ranges
Bug #1480846 reported by
Ilya Kharin
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Fuel for OpenStack |
Confirmed
|
Medium
|
Fuel Sustaining | ||
| Mitaka |
Won't Fix
|
Medium
|
Fuel Python (Deprecated) | ||
| Newton |
Confirmed
|
Medium
|
Fuel Sustaining | ||
Bug Description
In the networking part there are two similar blocks of code that responsible for setting IP ranges for network groups. The logic of these two method a few differs that described in the bug report [3]. So, the duplication of the code should be removed.
[1] NetworkManager.
[2] NetworkManager.
[3] https:/
| Changed in fuel: | |
| milestone: | none → 7.0 |
| assignee: | nobody → Fuel Python Team (fuel-python) |
| Changed in fuel: | |
| status: | New → Confirmed |
| importance: | Undecided → Medium |
| tags: | added: module-nailgun tech-debt |
| Changed in fuel: | |
| milestone: | 7.0 → 8.0 |
| tags: | added: module-networks |
| summary: |
- inconsistent implementation of setting networks ranges + Inconsistent implementation of setting networks ranges |
| tags: | added: area-python |
Revision history for this message
| Dmitry Pyzhov (dpyzhov) wrote | #1 |
| Changed in fuel: | |
| milestone: | 8.0 → 9.0 |
To post a comment you must log in.
Moving medium bug to 9.0 because we have SCF in action for 8.0