I'm running a number (few hundreds) of servers for a few (6 or so) years on
tumbleweed, with the network setup using
* wicked
* generated ifcfg files (own generator)
* vlan interfaces on top of a vlan enabled bridge on top of bond (lacp) on top
of eth

With the recent wicked update (0.6.74 -> 0.6.75) tested today, network did not
come up as it used to. No errors were seen in logs or systemd services, just
the interfaces all were not configured.

The change in behaviour apparently relates to recursive determination of what
to bring up. I'm used to (and thought at some point in the past had to) have
STARTMODE configured like this:

penn:~ # egrep -H ^STARTMODE /etc/sysconfig/network/ifcfg-*
/etc/sysconfig/network/ifcfg-eth0:STARTMODE=manual
/etc/sysconfig/network/ifcfg-eth1:STARTMODE=manual
/etc/sysconfig/network/ifcfg-lacp:STARTMODE=manual
/etc/sysconfig/network/ifcfg-lo:STARTMODE=nfsroot
/etc/sysconfig/network/ifcfg-v0001:STARTMODE=auto
/etc/sysconfig/network/ifcfg-v0178:STARTMODE=auto
/etc/sysconfig/network/ifcfg-v2080:STARTMODE=auto
/etc/sysconfig/network/ifcfg-vbr:STARTMODE=manual

That relies on v0001 and so on vlan interfaces (auto) triggering up-ping of
vbr, that referencing lacp, that referencing eth0+eth1.

With the wicked update, that no longer worked. Setting STARTMODE=auto for all
of the ifcfg files, again makes it work fine.

Not sure this is a bug, or intended behaviour change. But thought it best to
report.