Description of problem:
Docs bug highlight - we see instructions for creating custom br-ex bridge in section: https://github.com/openshift/openshift-docs/blob/enterprise-4.16/modules/creating-manifest-file-customized-br-ex-bridge.adoc https://docs.openshift.com/container-platform/4.16/installing/installing_bare_metal_ipi/ipi-install-installation-workflow.html#creating-manifest-file-customized-br-ex-bridge_ipi-install-installation-workflow procedure section dictates creation an nmstate network manifest file that defines all interfaces, and placing it at `/etc/nmstate/openshift/cluster.yml` to create a definition file for networking that will prevent `configure-ovs.sh` from overwriting the network parameters on the host and allow customizability. However, Our code (currently) is specifying that network overrides only require the presence of the following file which is empty https://github.com/openshift/machine-config-operator/blob/4532a85a67a3e1347ed0a89a6d08ef87d6da2a62/templates/common/_base/files/configure-ovs-network.yaml#L8-L11 ~~~ if [ -e /etc/nmstate/openshift/applied ]; then echo "Skipping configure-ovs due to manual network configuration" exit 0 fi ~~~ Therefore, the manifest instructions should advise the creation of a manifest for `/etc/NetworkManager/system-connections/br-ex.nmconnection` file (or nmstate network configuration) and place those configs at `/etc/NetworkManager/system-connections`, AND, create a manifest to touch a file at `/etc/nmstate/openshift/applied` to override `configure-ovs.sh`. Currently as written, these instructions will not override configure-ovs.sh, and customer deployments will not allow custom br-ex network config. Please contact me with any questions/concerns, and we might should also loop in engineering at https://issues.redhat.com/browse/OCPSTRAT-439 working on TE feature set to confirm that they want to maintain this `/etc/nmstate/openshift/applied` option (instead of /etc/nmstate/openshift/cluster) or otherwise - which will require a PR/code change. Thanks!
Version-Release number of selected component (if applicable):
4.16.0-z