Bug #24644
open
Respect subnet range boundries
Description
I wonder if this one works https://github.com/theforeman/smart-proxy/pull/148 or if it is a different use-case from my issue.
I have a subnet in foreman 10.3.20.0/22, and I have set Start and End of ip range to 10.3.20.30 - 10.3.23.149.
And in dhcpd I have "range 10.3.23.150 10.3.23.254;"
So discovered nodes get IPs between 10.3.23.150-10.3.23.254
And when I provision the nodes. If I don't press the suggest new address button when customizing the node that I provision, it keeps the out of "foreman" range IP.
Updated by Lukas Zapletal over 6 years ago
- Subject changed from respect subnet range boundries to Respect subnet range boundries
Hello, which version did you upgraded from and to?
Updated by Lukas Zapletal over 6 years ago
Wait do you see this for discovery only or for non-discovery workflow (basic PXE)?
Because there is this well known issue which is huge pain: #16143 and this smells like duplicate of this.
Updated by Elias Abacioglu about 6 years ago
I've had this for as long as i can remember, so not sure it's a new thing. At least same problem on 1.16, 1.17, 1.18 and probably earlier.
We didn't have this before we started using discovery workflow. We used to create nodes manually in foreman, adding mac-address manually and it always got an IP for it within the subnet ranges set in foreman as there was nothing pre-filled.