Hi all,
I think I might have discovered a bug in the network GUI.
Description:
When I need to make changes to the network configuration through the GUI the node will always come up without connection to the cluster but it can be easily fixed by manually rearrange the configuration file made by the pve-manager.
The reason for the failed cluster membership is because pve-manager insists on placing the vlan configuration before the bond configuration in the config file which causes the activation of the vlan's to fail because at the time of activating the vlan's the bond is unknown. Activating the bond before the vlan's always fixes this.
Example:
Created by pve-manager. Will fail
# network interface settings
auto vlan10
iface vlan10 inet manual
vlan-raw-device bond0
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet manual
auto eth1
iface eth1 inet manual
auto bond0
iface bond0 inet manual
slaves eth0 eth1
bond_miimon 100
bond_mode 802.3ad
bond_xmit_hash_policy layer2+3
bond_lacp_rate fast
auto vmbr10
iface vmbr10 inet static
address 172.16.1.9
netmask 255.255.255.0
bridge_ports vlan10
bridge_stp off
bridge_fd 0
Working example hand edited by me
# network interface settings
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet manual
auto eth1
iface eth1 inet manual
auto bond0
iface bond0 inet manual
slaves eth0 eth1
bond_miimon 100
bond_mode 802.3ad
bond_xmit_hash_policy layer2+3
bond_lacp_rate fast
auto vlan10
iface vlan10 inet manual
vlan-raw-device bond0
iface vmbr10 inet static
address 172.16.1.9
netmask 255.255.255.0
bridge_ports vlan10
bridge_stp off
bridge_fd 0
I think I might have discovered a bug in the network GUI.
Description:
When I need to make changes to the network configuration through the GUI the node will always come up without connection to the cluster but it can be easily fixed by manually rearrange the configuration file made by the pve-manager.
The reason for the failed cluster membership is because pve-manager insists on placing the vlan configuration before the bond configuration in the config file which causes the activation of the vlan's to fail because at the time of activating the vlan's the bond is unknown. Activating the bond before the vlan's always fixes this.
Example:
Created by pve-manager. Will fail
# network interface settings
auto vlan10
iface vlan10 inet manual
vlan-raw-device bond0
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet manual
auto eth1
iface eth1 inet manual
auto bond0
iface bond0 inet manual
slaves eth0 eth1
bond_miimon 100
bond_mode 802.3ad
bond_xmit_hash_policy layer2+3
bond_lacp_rate fast
auto vmbr10
iface vmbr10 inet static
address 172.16.1.9
netmask 255.255.255.0
bridge_ports vlan10
bridge_stp off
bridge_fd 0
Working example hand edited by me
# network interface settings
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet manual
auto eth1
iface eth1 inet manual
auto bond0
iface bond0 inet manual
slaves eth0 eth1
bond_miimon 100
bond_mode 802.3ad
bond_xmit_hash_policy layer2+3
bond_lacp_rate fast
auto vlan10
iface vlan10 inet manual
vlan-raw-device bond0
iface vmbr10 inet static
address 172.16.1.9
netmask 255.255.255.0
bridge_ports vlan10
bridge_stp off
bridge_fd 0