I update udev package from udev-104-r13 to udev-114. After this update VLAN is not properly up at boot. On my server setting up 3 network interfaces (eth0, eth1, eth2). On each interface I have from 5 to 20 VLANs. In boot time server print diferent messages about not properly up VLAN interfaces and attempts initialise different network interfaces which i not have physicaly. On one boot system not up with errors something like: Adding VLAN 31 to eth0 - OK Can't find device eth0.31 .... Config for eth22 not find. Try dhclinet.... Adding VLAN 178 to eth1 - OK Can't add VLAN 178 to eth1..... Config for eth57 not find. Try dhclient...... Where from system find ETH57 or ETH22 ? In next reboot, this VLANs normal up, but other VLANs failed with same errors.
Created attachment 129576 [details] 70-persistent-net.rules and emerge --info
Ugly errors this persistent-net causes if it contains some typos. Like this one upstream had (already fixed). We detected this first via Bug 189042. The solution is this change to 75-persistent-net-generator.rules file change the two occurences of DRIVERS!="?*" to DRIVERS=="?*". Either do this change by hand, or update to at least udev-114-r2 (better use udev-115). Also delete all redundant entries from 70-persisten-net.rules (The ones with empty "()" in comment).
As noted above, already fixed in >=udev-114-r2 *** This bug has been marked as a duplicate of bug 189042 ***
