Bug 1179276

Created attachment 976819 [details]
anaconda.log

Created attachment 976820 [details]
anaconda-yum.conf

Created attachment 976821 [details]
ifcfg.log

Created attachment 976822 [details]
packaging.log

Created attachment 976823 [details]
program.log

Created attachment 976824 [details]
storage.log

Created attachment 976825 [details]
storage.state

Created attachment 976826 [details]
syslog

Created attachment 976827 [details]
team.json

Created attachment 976828 [details]
X.log

The json config file from Description seems invalid, using it teamd dies:

11:05:38,551 INFO NetworkManager: <info>  Auto-activating connection 'Team connection 1'.
11:05:38,554 INFO NetworkManager: <info>  (team0): Activation: starting connection 'Team connection 1'
11:05:38,554 INFO NetworkManager: <info>  (team0): Activation: Stage 1 of 5 (Device Prepare) scheduled...
11:05:38,558 INFO NetworkManager: <info>  (team0): Activation: Stage 1 of 5 (Device Prepare) started...
11:05:38,558 INFO NetworkManager: <info>  (team0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
11:05:38,644 INFO NetworkManager: <info>  (team0): Activation: (team) started teamd...
11:05:38,644 INFO NetworkManager: <info>  (team0): Activation: Stage 1 of 5 (Device Prepare) complete.
11:05:38,681 INFO NetworkManager: <info>  (team0): teamd died with status 256
11:05:38,681 INFO NetworkManager: <info>  (team0): device state change: prepare -> failed (reason 'teamd-control-failed') [40 120 56]
11:05:38,681 WARNING NetworkManager: <warn>  (team0): Activation: failed for connection 'Team connection 1'
11:05:38,683 INFO NetworkManager: <info>  (team0): device state change: failed -> disconnected (reason 'none') [120 30 0]
11:05:38,683 INFO NetworkManager: <info>  (team0): deactivating device (reason 'none') [0]
11:05:38,684 INFO kernel:[  415.344147] IPv6: ADDRCONF(NETDEV_UP): team0: link is not ready
11:05:38,694 INFO NetworkManager: <info>  (team0): device state change: disconnected -> unmanaged (reason 'removed') [30 10 36]

I've succeeded to add team device with this json config:

{
   "device": "team0",
   "runner": {
      "name": "activebackup"
   },
   "link_watch": {
      "name": "ethtool",
      "delay_up": 1000,
      "delay_down": 500
   },
   "ports": {
      "ens7": {
         "prio": -10,
         "sticky": true
      },
      "ens8": {
         "prio": 100
      }
   }
}



The problem is that if the team device is not activated successfully (and therefore removed by NM)  we don't keep the team connection in the list (Anaconda silently ignores the configuration). We should probably try to keep the config so that it could be fixed in UI by Configure button.

But given that teamd dies (this should be probably filed as a bug for NM?) just fixing anaconda to keep the configuration in the list might be worthless.

With the fix, if invalid team configuration is set in GUI, the device is not created but the connection is added to device list. The configuration can be then fixed with [Configure] button in nm-c-e and by turning the device/connection [ON] in GUI the device should be created and connected (this last step requires fix for bug 1172751 though).

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-2284.html