Having a bit of an issue with a cluster/ storage network not coming up properly after rebooting a node here;

[   76.204319] A link change request failed with some changes committed already. Interface vm-br may have been left with an inconsistent configuration, please check.

controller:
time="2023-03-10T20:03:15Z" level=error msg="error syncing 'har-04': handler harvester-network-vlanconfig-controller: set up VLAN failed, vlanconfig: har-04, node: har-04, error: ensure bridge vm-br failed, error: set vlan filtering failed, error: invalid argument, iface: &{0xc0006de140}, requeuing"
I0310 20:03:15.252249       1 controller.go:75] vlan config har-04 has been changed, spec: {Description: ClusterNetwork:vm NodeSelector:map[<http://kubernetes.io/hostname:har-04|kubernetes.io/hostname:har-04>] Uplink:{NICs:[eno1 eno2] LinkAttrs:0xc001c85e30 BondOptions:0xc00052ad50}}

The associated bond is brought up just fine, any ideas what could be causing such a scenario?

Hi @orange-policeman-97710, could you help to check this?

Will do - thank you!