In fuelmenu, if you set IP for master, static pool starts from same IP
Bug #1283805 reported by
Mike Scherbakov
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Committed
|
High
|
Matthew Mosesohn |
Bug Description
In fuelmenu dialog, if you set IP address for master node different from default one (in my case that was 10.20.0.10), click Apply, and then go to PXE setup - you will observe that Static Pool Start is 10.20.0.10. It means that first node for deployment will be allocated with same IP address as master node, and it leads to error during deployment. Namely, system installs, but node goes into offline state and becomes unreachable from master node.
The fix should be pretty easy - [Static Pool Start, Static Pool End] should not intersect with master node IP address.
ISO #180, "nailgun_sha": "f786786894acc3
Changed in fuel: | |
assignee: | Dima Shulyak (dshulyak) → Matthew Mosesohn (raytrac3r) |
tags: | added: release-notes |
Changed in fuel: | |
status: | In Progress → Fix Committed |
To post a comment you must log in.
Mike, ideally, I would love to see a workaround where we exclude the IP of the Fuel master interface, but I believe nailgun doesn't have any awareness of its own IP address. Regrettably, neither does dnsmasq care if it gives out its own IP address as a lease and cause problems.
I would like to see an alternative solution exist where you can set a range of 10.20.0.2 -> 10.20.0.128 for the static pool, and automatically exclude 10.20.0.10 if that's my IP on the admin interface. That's a longer workaround, so the error really is the best option right now.
I'll get it ready for tomorrow.