What were you trying to do that didn't work?

Deployment of OpenShift cluster using mode balance-slb. Here is an example of the configuration used (see also attached):

interfaces:
 - name: eno1
description: Ethernet eno1
type: ethernet
state: up
ipv4:
enabled: false
 - name: eno2
description: Ethernet eno1
type: ethernet
state: up
ipv4:
enabled: false
 - name: bond0
type: bond
state: up
ipv4:
address:
 - ip: 10.0.1.11
prefix-length: 24
enabled: true
link-aggregation:
mode: balance-xor
options:
xmit_hash_policy: vlan+srcmac
balance-slb: 1
port:
 - eno1
 - eno2
dns-resolver:
config:
search:
 - gfontana.me
 - lab.gfontana.me
server:
 - 10.0.1.2
routes:
config:
 - destination: 0.0.0.0/0
next-hop-address: 10.0.1.1
next-hop-interface: bond0

Note: Issue only happens if "balance-slb: 1" is set.

What is the impact of this issue to you?

Cluster deployment using bond mode balance-slb. Tested with OCP 4.16.16 and 4.17 with Assisted Installer AND Agent Based installer.

How reproducible is this bug?: Happens 100% of the time

Steps to reproduce

1. Using either Assisted installer or Agent Based installer deploy a cluster with a bond with two network interfaces. Bond mode needs to be as follows:

  link-aggregation:
    mode: balance-xor
    options:
      xmit_hash_policy: vlan+srcmac
      balance-slb: 1
    port:
    - eno1
    - eno2

Expected results

Cluster deployed successfully

Actual results

Node deployment gets stuck after first reboot, during ignition. Attached are some evidences. I noticed the following error message in the console: 

`nft configuration for balance-slb failed`