System generated network bond fails after kernel update.

Server info (20.04)
After i updated my docker server yesterday i had to reboot because of a kernel update (new version 5.4.0-58-generic x86_64). My main network interface that i use all of a sudden failed to apply its configuration and was not able to connect. I believe this issue is linked to this bug (Bug #1860926) but not exactly the same issue.
When setting up my server on first install i used the startup walk-through to auto configure my eno1&eno2 network bond. I unfortunately didn't save the previous netplan yaml to post here,but it had said it was written by subiquity. Every time i tried to apply the netplan it replied that eno2 was not defined. I had to change the yaml to this configuration to get my link back up.

network:
  bonds:
    bond0:
      interfaces:
      - eno1
      - eno2
      parameters:
        mode: balance-rr
  ethernets:
    eno1: {}
    eno2: {}
  version: 2
  bridges:
    br0:
      addresses:
        - 172.16.10.2/24
      dhcp4: false
      gateway4: 172.16.10.254
      nameservers:
        addresses:
          - 172.16.10.251
          - 172.16.10.254
        search: []
      interfaces:
        - bond0

I found this in my syslog right after the reboot from update,

/usr/lib/systemd/system-generators/netplan failed with exit status 1.
PRIORITY 3
SYSLOG_FACILITY 3
SYSLOG_IDENTIFIER systemd
SYSLOG_PID 675
_BOOT_ID de464fb514a34d149ca9ace3c7ee5a83
_HOSTNAME bagul.dev
_MACHINE_ID e610a37f963a4ad499cd78b0e181e679
_SOURCE_MONOTONIC_TIMESTAMP 46968227
_TRANSPORT kernel
__CURSOR s=0b1205c7c02b486389e1f63666ec005f;i=15575e;b=de464fb514a34d149ca9ace3c7ee5a83;m=2e45a41;t=5b77d16e3b0b9;x=e5d61684f5e8d985
__MONOTONIC_TIMESTAMP 48519745
__REALTIME_TIMESTAMP 1609122766368953