-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
False
-
None
-
False
-
-
OSPdO, when using the default ProvisioningServer, assumes that whatever node the provisioning server pod lands on will have an IP on the OpenShift provisioning network.
In environments such as Assisted Installer with static IPs or with virtual media provisioning without a provisioning network, it is possible for only the node running metal3 to have a provisioning IP.
The OSPdO docs should be updated to note this assumption and the following solutions:
- Enable DHCP on the provisioning interface of all OpenShift nodes so that nodes not running metal3 will get an address from DHCP
- Create a custom ProvisioningServer on a different interface (i.e. br-ex) that is reachable by the bare metal hosts using either DHCP or static pre-provisioning network configuration.