Description of problem: When I generate nmconnection files with "nmstatectl gc" and apply them to a node, the bridge is not correctly created. When I apply the same configuration using the kubernetes-nmstate operator, the bridge is created as expected. I find very few differences between the generated nmconnection files. The main difference seems to be that the files applied directly via nmstatectl define their master devices by UUID, whereas the ones generated by gc define masters by name.

It looks like there may be a conflict between the applied configuration and the default connection that just DHCPs all interfaces, but I haven't found a way to keep the default connection from overriding the one I apply.


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


How reproducible: Always


Steps to Reproduce:
1. Create configuration files for ovs-bridge (see below) using nmstatectl gc
2. Apply those files to OCP node

Actual results:
Bridge br-ey
        Port br-ey
            Interface br-ey
                type: internal

Expected results: 
Bridge br-ey
        Port br-ey
            Interface br-ey
                type: internal
        Port enp3s0
            Interface enp3s0
                type: system

Additional info:
nmstate-config for bridge
interfaces:
- name: enp3s0
  type: ethernet
  state: up
  ipv4:
    enabled: false
  ipv6:
    enabled: false
- name: br-ey
  type: ovs-bridge
  state: up
  bridge:
    port:
    - name: enp3s0
    - name: br-ey
- name: br-ey
  type: ovs-interface
  state: up
  ipv4:
    enabled: true
    dhcp: true
    auto-dns: true
    auto-gateway: true
    auto-routes: true
  ipv6:
    enabled: false
    dhcp: false