-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.14.z, 4.15.z
-
No
-
False
-
-
Release Note Not Required
-
In Progress
Description of problem:
In the current official documentation of IPI installation of Openstack [1]. [1]: https://docs.openshift.com/container-platform/4.14/installing/installing_openstack/installing-openstack-installer-custom.html The use of additional Network: The documentation just indicates the entry in install-config.yaml to enable additional networks, like this: ~~~ You can add additional networks, including provider networks, to the platform.openstack.additionalNetworkIDs list.After you deploy your cluster, you can attach pods to additional networks. For more information, see Understanding multiple networks. [+] https://docs.openshift.com/container-platform/4.14/installing/installing_openstack/installing-openstack-installer-custom.html#:~:text=You%20can%20add,multiple%20networks. ~~~ However, the default OpenStack behavior is to enable DHCP to makes it more versatile and dynamic. It is observed that openshift installation with multiple network fails if the additional network are DHCP enabled. Hence below information needs to be updated in the documentation. "Make sure to disable DHCP on the additional network as it leads to failure of the cluster installation". [+] https://docs.openshift.com/container-platform/4.14/installing/installing_openstack/installing-openstack-installer-custom.html#:~:text=You%20can%20add,multiple%20networks.
Version-Release number of selected component (if applicable):
4.14.z
How reproducible:
Steps to Reproduce:
1. 2. 3.
Actual results:
Cluster Installation fails with additional Network
Expected results:
Installation should be successful
Additional info:
- is related to
-
RFE-5175 OpenShift installer to reject the nameserver coming from the additional network - IPI OpenStack
- Backlog