This is a clone of issue OCPBUGS-61840. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-61835. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-61824. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-61695. The following is the description of the original issue:
—
Description of problem:

The NMState service is failing in some OCP deployments. This seems to be a recent change caused by a new dependency on NetworkManager-wait-online, which often fails in baremetal deployments (and possibly other on-prem environments with multiple NICs).

1. systemctl status nmstate
   ○ nmstate.service - Apply nmstate on-disk state
        Loaded: loaded (/usr/lib/systemd/system/nmstate.service; enabled; preset: enabled)
        Active: inactive (dead)
          Docs: man:nmstate.service(8)
                https://www.nmstate.io

Sep 12 21:19:43 master-0 systemd[1]: Dependency failed for Apply nmstate on-disk state.
Sep 12 21:19:43 master-0 systemd[1]: nmstate.service: Job nmstate.service/start failed with result 'dependency'.

Version-Release number of selected component (if applicable):

4.20

How reproducible:

Seems to always reproduce in dev-scripts environments.

Steps to Reproduce:

    1. Configure to deploy with NMState managing br-ex
    2.
    3.
    

Actual results:

Deployment fails due to br-ex configuration not being applied.

Expected results:

Additional info: