Description of problem:
provisioningDHCPRange can be an empty string in the Provisioning CR if provisioningDHCPExternal is true, but MAO is still trying to fall back to the config map. It should not do that.
IMHO, it is 100% OK to assume the installer creates the Provisioning CR, there's no need for backwards compatibility here, and ideally we'd just remove all of this config map stuff, but if we don't want to do that in 4.5, this case needs to get handled.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Set provisioningDHCPExternal: true, and provisioningDHCPRange to ""
message: couldn't find key dhcp_range in ConfigMap
I would like to see the provisioning CR generated by the installer. That can be gathered by "oc get provisioning -o yaml".
After https://github.com/openshift/installer/pull/3496 lands, the template will look like this:
rendered template* I meant, of course
proposed fix : https://github.com/openshift/machine-api-operator/pull/568
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, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.