Summary of the issue as I understand it following some discussions: The baremetal hosts defined in the install-config is a list, where each host can have either `role: master` or `role: worker` The installer uses terraform to deploy the master hosts, the number of hosts is defined via the controlPlane replicas value. We generate a terraform variable containing these hosts, but AFAICS we just add all of them, without filtering on `role: master` https://github.com/openshift/installer/blob/master/pkg/tfvars/baremetal/baremetal.go#L46 Consequently we end up consuming the first N hosts from that list, even if they're workers: https://github.com/openshift/installer/blob/master/data/data/baremetal/masters/main.tf#L3 So, I think at a minimum we need to filter the tfvars hosts list to only contain masters. We may also want to look at improving the validation to consider each role, e.g here we only consider the total count (which could mean terraform fails if e.g there's a role mistake that results on one master tagged as worker, the tfvars list will end up with too few hosts): https://github.com/openshift/installer/blob/master/pkg/types/baremetal/validation/platform.go#L287
@Andrea Can we please have Doc Text to assist in developing a Release Notes entry for this bug? Thanks!
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.10.3 security 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-2022:0056