Lot of our customer face issue when they do leapp upgrade of RHEL systems with bond interface because the leap file created for a bond NICs carry same MAC address and interface names get changed after reboot leading to inconsistent bonding. Eg:

Before upgrade:
+++
$ cat proc/net/bonding/bond1 |grep -e 'Slave Interface' -e 'Permanent HW addr'
Slave Interface: enp55s1f0
Permanent HW addr: aa:bb:cc:20:00:4a
Slave Interface: enp55s1f1
Permanent HW addr: aa:bb:cc:20:00:4b
+++

But the leap file created is:

$ cat etc/systemd/network/10-leapp-enp55s1f

.link

1. Generated by LEAPP
   [Match]
   MACAddress=aa:bb:cc:20:00:4a
   [Link]
   Name=enp55s1f0

1. Generated by LEAPP
   [Match]
   MACAddress=aa:bb:cc:20:00:4a <--------- same mac. So the renaming failed
   [Link]
   Name=enp55s1f1
   +++

The bond slaves will always carry same MAC address for its slave. Actual MAC address can be read from '/proc/net/bonding/<bond-name>' file.

The issue is described in your knowledge base article https://access.redhat.com/solutions/7071412 where its suggested to set ' LEAPP_NO_NETWORK_RENAMING=1' as its known issue and suggested for manual configuration of bond devices. I guess the leapp man page also indicate same.

But since many of our customer affected, can we fix this issue ? I see the issue is getting noticed only after upgrade and customer opens the case with us