cloud-init fails to configure a bond on CentOS 8

This bug was originally filed in Launchpad as [LP: #1905358](https://bugs.launchpad.net/cloud-init/+bug/1905358)

Launchpad details

affected_projects = []

assignee = None

assignee_name = None

date_closed = None

date_created = 2020-11-24T06:15:30.936527+00:00

date_fix_committed = None

date_fix_released = None

id = 1905358

importance = medium

is_complete = False

lp_url = https://bugs.launchpad.net/cloud-init/+bug/1905358

milestone = None

owner = ltrager

owner_name = Lee Trager

private = False

status = triaged

submitter = ltrager

submitter_name = Lee Trager

tags = []

duplicates = []

_Launchpad user **Lee Trager(ltrager)** wrote on 2020-11-24T06:15:30.936527+00:00_

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]: [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