cloud-init fails to configure a bond on CentOS 8

[Lee Trager]

On a test system I configured a machine with a bond. Curtin successfully installed CentOS 8 but the deployment failed in MAAS. When I dug in it is because the bond never comes up so the machine has no way to communicate with MAAS. I can deploy the same machine with a bond on CentOS 7 or Ubuntu. I can also deploy with CentOS 8 using DHCP, static IP, or a bridge, just not a bond.

MAAS: 2.9.0-rc1
CentOS 8 image from images.maas.io
cloud-init-19.4-1.el8.7.noarch

From /var/log/messages

messages:Nov 24 05:33:43 localhost NetworkManager[1025]: <warn> [1606196023.8922] ifcfg-rh: load[/etc/sysconfig/network-scripts/ifcfg-bond0]: failure to read file: bond.options: 'updelay' option requires 'miimon' option to be set

[Dan Watkins (oddbloke)]

Could we get a `cloud-init collect-logs` from an affected instance, please? (Set this back to New once added. :)

[Lee Trager (ltrager)]

Attached are the cloud-init logs. Note due to the bond not coming up I could only access the system by booting into rescue mode(Ubuntu) and chrooting in to the CentOS install to gather logs.

[James Falcon (falcojr)]

Tracked in Github Issues as https://github.com/canonical/cloud-init/issues/3810