ncm-network: interfaces brought up in wrong order

[apdibbo]

When using the network component to configure OpenVSwitch the it seems that the bridge interface is attempted to be brought up before its physical ports leaving the host without networking. The network component runs ifup br0 eth0. Using the config generated by the network component and running ifup eth0 br0 brings the interfaces up and everything works fine.

This is on SL7. The following is the interfaces section of the profile:

+-/system/network
  $ default_gateway : '130.246.216.254'
  $ domainname : 'nubes.rl.ac.uk'
  $ hostname : 'hv25'
  +-interfaces
    +-br0
      $ bootproto : 'static'
      $ broadcast : '130.246.223.255'
      $ fqdn : 'hv25.nubes.rl.ac.uk'
      $ gateway : '130.246.216.254'
      $ ip : '130.246.223.152'
      $ mtu : 9000
      $ netmask : '255.255.248.0'
      $ network_environment : 'internal'
      $ network_type : 'wan'
      +-route
        +-0
          $ address : '130.246.216.254'
          $ netmask : '255.255.248.0'
      $ set_hwaddr : true
      $ type : 'OVSBridge'
    +-eth0
      $ bootproto : 'none'
      $ ovs_bridge : 'br0'
      $ set_hwaddr : true
      $ type : 'OVSPort'
  +-ipv6
    $ enabled : false
  +-nameserver
    $ 0 : '130.246.180.55'
    $ 1 : '130.246.181.239'
    $ 2 : '130.246.181.240'
  $ primary_ip : '130.246.223.152'
  +-routers
    +-br0
      $ 0 : '130.246.216.254'

Is there something else I need to add to get this to work?

[stdweird]

@apdibbo can you PM me the --debug 5 output? also, can you send met the ccm /system/network of the config before this change? or is this the inital config (ie after installation)

[apdibbo]

@stdweird, I have emailed you the debug 5 output. This is initial configuration, but I have seen the same issue when moving from unmanaged network to using the component (I dont have an example of this at the moment)