System and Network configuration • VLAN interface renamed to RENAME#

On several fresh installs (via cloud-init from the OpenStack image) of Debian 10; vlan interfaces on a bond are getting incorrectly renamed by peristant NIC naming. This behavior breaks cloud-ini installations where a bond is required with a vlan interface on the bond. How do I disable this rule without disabling all of persistent NIC naming (Which would change all the NIC names and so also break cloud-init installations)

Sample /etc/network/interfaces

Code:

auto bond0iface bond0 inet manual        bond-slaves eno1 eno2        bond-mode 4        bond-miimon 100        bond-downdelay 200        bond-updelay 200        bond-lacp-rate 1        bond-xmit-hash-policy layer2+3        up ifconfig bond0 0.0.0.0 upauto bond0.12iface bond0.12 inet static        address 10.0.0.10/24        gateway 10.0.0.1        vlan-raw-device bond0

Code:

Sample log output

Code:

Feb  2 17:30:48 HOSTNAME systemd[1]: Reached target Network (Pre).Feb  2 17:30:48 HOSTNAME systemd[1]: Started ifup for eno2.Feb  2 17:30:48 HOSTNAME systemd[1]: Starting Network Service...Feb  2 17:30:48 HOSTNAME systemd[1]: Started ifup for eno1.Feb  2 17:30:48 HOSTNAME systemd[1]: Starting Raise network interfaces...Feb  2 17:30:48 HOSTNAME systemd-networkd[1008]: Enumeration completedFeb  2 17:30:48 HOSTNAME systemd[1]: Started Network Service.Feb  2 17:30:48 HOSTNAME systemd[1]: ifup@eno2.service: Main process exited, code=exited, status=1/FAILUREFeb  2 17:30:48 HOSTNAME systemd[1]: ifup@eno2.service: Failed with result 'exit-code'.Feb  2 17:30:48 HOSTNAME systemd[1]: ifup@eno1.service: Main process exited, code=exited, status=1/FAILUREFeb  2 17:30:48 HOSTNAME systemd[1]: ifup@eno1.service: Failed with result 'exit-code'.Feb  2 17:30:48 HOSTNAME kernel: [   13.116181] IPv6: ADDRCONF(NETDEV_UP): eno1: link is not readyFeb  2 17:30:48 HOSTNAME kernel: [   13.122497] IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes readyFeb  2 17:30:48 HOSTNAME kernel: [   13.129424] Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)Feb  2 17:30:48 HOSTNAME kernel: [   13.137122] bonding: bond0 is being created...Feb  2 17:30:48 HOSTNAME systemd-udevd[905]: Using default interface naming scheme 'v240'.Feb  2 17:30:48 HOSTNAME systemd-networkd[1008]: eno1: Gained carrierFeb  2 17:30:48 HOSTNAME kernel: [   13.220187] i40e 0000:60:00.0 eno1: already using mac address 3c:ec:ef:60:f5:caFeb  2 17:30:48 HOSTNAME systemd-networkd[1008]: eno1: Lost carrierFeb  2 17:30:48 HOSTNAME kernel: [   13.234289] bond0: Enslaving eno1 as a backup interface with an up linkFeb  2 17:30:48 HOSTNAME systemd-networkd[1008]: eno1: Removing non-existent address: fe80::3eec:efff:fe60:f5ca/64 (valid forever), ignoringFeb  2 17:30:48 HOSTNAME kernel: [   13.244081] i40e 0000:60:00.1 eno2: set new mac address 3c:ec:ef:60:f5:caFeb  2 17:30:48 HOSTNAME kernel: [   13.258717] bond0: Enslaving eno2 as a backup interface with an up linkFeb  2 17:30:48 HOSTNAME kernel: [   13.272551] bond0: Warning: No 802.3ad response from the link partner for any adapters in the bondFeb  2 17:30:48 HOSTNAME kernel: [   13.272593] IPv6: ADDRCONF(NETDEV_UP): bond0: link is not readyFeb  2 17:30:48 HOSTNAME systemd-networkd[1008]: eno1: Gained carrierFeb  2 17:30:48 HOSTNAME kernel: [   13.288783] IPv6: ADDRCONF(NETDEV_CHANGE): bond0: link becomes readyFeb  2 17:30:48 HOSTNAME systemd-networkd[1008]: eno1: Could not set route: Network is unreachableFeb  2 17:30:48 HOSTNAME systemd-networkd[1008]: bond0: Gained carrierFeb  2 17:30:48 HOSTNAME systemd-networkd[1008]: eno2: Gained carrierFeb  2 17:30:48 HOSTNAME kernel: [   13.297984] bond0: link status definitely up for interface eno1, 10000 Mbps full duplexFeb  2 17:30:48 HOSTNAME kernel: [   13.306826] bond0: first active interface up!Feb  2 17:30:48 HOSTNAME kernel: [   13.312033] bond0: link status definitely up for interface eno2, 10000 Mbps full duplexFeb  2 17:30:48 HOSTNAME kernel: [   13.337692] 8021q: 802.1Q VLAN Support v1.8Feb  2 17:30:48 HOSTNAME kernel: [   13.342312] 8021q: adding VLAN 0 to HW filter on device eno1Feb  2 17:30:48 HOSTNAME kernel: [   13.348368] 8021q: adding VLAN 0 to HW filter on device eno2Feb  2 17:30:48 HOSTNAME kernel: [   13.354371] 8021q: adding VLAN 0 to HW filter on device bond0Feb  2 17:30:48 HOSTNAME systemd-udevd[905]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.Feb  2 17:30:48 HOSTNAME systemd-udevd[905]: Could not set WakeOnLan of bond0.12 to off: Operation not supportedFeb  2 17:30:48 HOSTNAME kernel: [   13.364958] rename5: renamed from bond0.12Feb  2 17:30:48 HOSTNAME systemd-networkd[1008]: bond0.12: Interface name change detected, bond0.12 has been renamed to rename5.Feb  2 17:30:48 HOSTNAME ifup[1023]: Error: 8021q: VLAN device already exists.Feb  2 17:30:48 HOSTNAME ifup[1023]: Cannot find device "bond0.12"Feb  2 17:30:48 HOSTNAME ifup[1023]: ifup: failed to bring up bond0.12Feb  2 17:30:48 HOSTNAME systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILUREFeb  2 17:30:48 HOSTNAME systemd[1]: networking.service: Failed with result 'exit-code'.Feb  2 17:30:48 HOSTNAME systemd[1]: Failed to start Raise network interfaces.Feb  2 17:30:48 HOSTNAME systemd[1]: Reached target Network.

Statistics: Posted by HuweyII — 2024-02-02 17:35 — Replies 3 — Views 71