[nailgun] Instances created with wrong IP range on second cluster
Bug #1323965 reported by
Nicholas Chase
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Fuel for OpenStack |
Fix Committed
|
Medium
|
Aleksey Kasatkin | ||
Bug Description
I have today's 5.0 ISO of fuel, and created two clusters, each in Multi-Node (non-HA) with one controller and one compute.
Both use FlatDHCPManager, but I changed the IP ranges so they don't conflict. Specifically, in cluster1, under Nova network configuration, the Fixed Network CIDR is set to 10.0.0.0/16, while in cluster2 it's set to 10.0.3.0/16.
When I create a VM in cluster1 (though Horizon) it comes out with an IP of 10.0.0.2, as expected. However, when I create one in cluster2 (also through Horizon) it ALSO comes up as 10.0.0.2.
Revision history for this message
| Sergii Golovatiuk (sgolovatiuk) wrote | #1 |
| Changed in fuel: | |
| status: | New → Invalid |
Revision history for this message
| Andrew Woodward (xarses) wrote | #2 |
| Changed in fuel: | |
| status: | Invalid → Confirmed |
| importance: | Undecided → Medium |
| assignee: | nobody → Fuel Python Team (fuel-python) |
| milestone: | none → 5.1 |
| summary: |
- Instances created with wrong IP range on second cluster + [nailgun] Instances created with wrong IP range on second cluster |
Revision history for this message
| Mike Scherbakov (mihgen) wrote | #3 |
| tags: | added: nailgun-networking |
| Changed in fuel: | |
| assignee: | Fuel Python Team (fuel-python) → Kamil Sambor (ksambor) |
| Changed in fuel: | |
| assignee: | Kamil Sambor (ksambor) → Aleksey Kasatkin (alekseyk-ru) |
| status: | Confirmed → In Progress |
Revision history for this message
| Aleksey Kasatkin (alekseyk-ru) wrote | #4 |
| Changed in fuel: | |
| status: | In Progress → Confirmed |
| assignee: | Aleksey Kasatkin (alekseyk-ru) → Fuel Python Team (fuel-python) |
| tags: |
added: nailgun removed: nailgun-networking |
| Changed in fuel: | |
| milestone: | 5.1 → 6.0 |
| Changed in fuel: | |
| milestone: | 6.0 → 6.1 |
| tags: | added: feature |
| tags: |
added: module-networks removed: nailgun |
| Changed in fuel: | |
| assignee: | Fuel Python Team (fuel-python) → Aleksey Kasatkin (alekseyk-ru) |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Related fix proposed to fuel-web (master) | #5 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Related fix merged to fuel-web (master) | #6 |
Revision history for this message
| Aleksey Kasatkin (alekseyk-ru) wrote | #7 |
| Changed in fuel: | |
| milestone: | 6.1 → 7.0 |
| assignee: | Aleksey Kasatkin (alekseyk-ru) → Fuel Python Team (fuel-python) |
| no longer affects: | fuel/7.0.x |
| no longer affects: | fuel/6.1.x |
To post a comment you must log in.
The problem is in mask you used. It overlaps the range from first and second cluster. /16 means 10.0.X.X thus you had a problem. Please use /24 instead. If you still want /16 please use second octet as distinguishing attribute. 10.0.0.0/16 and 10.X.0.0/16 should work fine.