The ClusterProvisioningIP field in the baremetal platform had an incorrect JSON annotation for serialization/deserialization, using "provisioningHostIP" instead of "clusterProvisioningIP." This name is incorrect and doesn't adequately reflect it's purpose. This field is the IP used in the cluster for provisioning. We should deprecate the old name and move to the new one to prevent confusion.
When configuring the install-config.yaml to include both clusterProvisioningIP and provisioningHostIP, this message appear (as expected): [kni@provisionhost-0-0 ~]$ ./openshift-baremetal-install --dir ~/ocp create manifests FATAL failed to fetch Master Machines: failed to load asset "Install Config": failed to upconvert install config: platform.baremetal.provisioningHostIP: Invalid value: "172.23.0.3": provisioningHostIP is deprecated; only clusterProvisioningIP needs to be specified But when specifying only the provisioningHostIP field in the install-config.yaml, it is actually continuing with no problem - so if the field is deprecated shouldn't the manifests command show an alert here also?
It's working as designed, the installer team asked us to deprecate it this way and it's consistent with how other things are upconverted silently.
OK. so I'm verifying it as described in comment 9 .
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 (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2020:5633