Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Deploying with multiple NICs will end up placing all NICs on the same default NM connection. If one of these interfaces fails to DHCP or does not DHCP in time during boot, NM-wait-online will fail (even though 1 NIC may have DHCP'ed correctly). Therefore the ovs-configuration service should not require NM-wait-online, but we should wait until it is completed and we do want it. However, if it fails we still try to to check the system if a default gateway is present. Additionally, since multiple NICs may share the same NM connection, we cannot always just bring it down. Instead, change the behavior to just disconnect the NIC and then bring up the higher priority connection later to preserve the default NM connection. Signed-off-by: Tim Rozet <trozet@redhat.com>
- Loading branch information