Description of problem: default provisioning DHCP range is too low for large scale BM deploys. Can we set it at .10 to $subnet_max instead of .10 to .100?
Version-Release number of selected component (if applicable): 4.4
How reproducible: 100%
Steps to Reproduce:
1. Deploy > 90 BM nodes
Actual results: Node will not get DHCP offer on pxe due to 90 max leases
Expected results: Node pxe's and provisions
The DHCP range is configurable to be as large as a user likes. There's no limitation there. A user can set provisioningDHCPRange in the install-platform, so I think this is much lower priority than currently indicated.
In general we expect the provisioning subnet to be dedicated and owned by the cluster, so updating the default to be $SUBNET_MAX may be a reasonable thing to do. It needs a bit more discussion, but I think we can leave this open to have a look at it in the 4.6 cycle.
I do not think we should backport it, as it would be quite surprising if you're used to deploying 4.4 and made assumptions about the provisioning network that suddenly become untrue in a z-Stream.
Description of problem: default provisioning DHCP range is too low for large scale BM deploys.
Version-Release number the fix was verified on: 4.6.0-0.nightly-2020-07-15-065024.
Steps to verify fix:
1. Run this on the provisionhost for both IPV4 and IPV6
oc get provisioning -o yaml | grep provisioningDHCPRange
Expected results: wide range for IP addresses, as seen above.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (OpenShift Container Platform 4.6 GA Images), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.