Platform:

baremetal IPI

When deploying with the provisioning network disabled, the generated bootstrap VM clouds.yaml (which is used only for debugging AFAIK) is incomplete, e.g:

$ ssh core.111.54 sudo cat /opt/metal3/auth/clouds.yaml
clouds:
  metal3-bootstrap:
    auth_type: http_basic
    username: bootstrap-user
    password: thepassword
    baremetal_endpoint_override: http://:6385/v1
    baremetal_introspection_endpoint_override: http://:5050/v1

In the case where there is no provisioning network, there is no dedicated provisioning IP, which is expected in the templating here:

https://github.com/openshift/installer/blob/master/data/data/bootstrap/baremetal/files/opt/metal3/auth/clouds.yaml.template#L6..L7

Instead I think we need to populate the IP at runtime, e.g somewhere in:

https://github.com/openshift/installer/blob/master/data/data/bootstrap/baremetal/files/usr/local/bin/startironic.sh.template

This could potentially just sed a placeholder in the templated file after discovering the active IP for PROVISIONING_NIC

How to reproduce:

In a dev-scripts environment, deploy with these in your config_$USER.sh
export PROVISIONING_NETWORK_PROFILE=Disabled
export OPENSHIFT_INSTALL_PRESERVE_BOOTSTRAP=y

Alternatively any deployment where provisioningNetwork: "Disabled" is configured in the install-config should show the same behavior