Comment # 21 on bug 956755 from Knut Alejandro Anderssen Gonz�lez

(In reply to Patrick Mullin from comment #20)
> I am running into a similar error on SLES 12 SP1 server.  I have attached
> y2log debug and network files.

The exception is the same but the origin of the problem is not.

Basically the exception is raised when there is an inconsistency in the
interface type, in this case the interface (bond0) should be a bond interface
but it is detected as a eth interface.

$["bus":"PCI", "bus_hwcfg":"pci", "bus_id":1, "class_id":2, "dev_name":"bond0",
"dev_names":["bond0"], "device":"82599 10 Gigabit Dual Port Backplane
Connection", "device_id":69880, "driver":"ixgbe", "driver_module":"ixgbe",
"drivers":[$["active":true, "modprobe":true, "modules":[["ixgbe", ""]]]],
"func_id":1,
"modalias":"pci:v00008086d000010F8sv0000103Csd000018D0bc02sc00i00",
"model":"Hewlett-Packard Company Ethernet 10Gb 2-port 560FLB Adapter",
"old_unique_key":"fmF7.fgiiCosKJzC", "parent_unique_key":"_Znp.3B9ooyvRRt3",
"resource":$["hwaddr":[$["addr":"14:02:ec:83:a0:75"]]

Is the bond active?, It seems that not, and that that bond0 
It seems that the bond0 is not active, and it is detected as what should be the
eth1

And when "/sys/class/net/bond0/bonding" is checked it seems to not exist, is
really the bond0 active?

BTW, please create a separate bug, if not this one will start to be like a box
to put all of them that looks similar.