Deploying CentOS 7 using Bond interface with DHCP

Hello,

Did anyone faced issue deploying CentOS 7 instance with Bond interface configure in active/backup model using DHCP ? We are currently running “2.9.2 (9164-g.ac176b5c4-0ubuntu1~20.04.1)” and we came to a deployment issue when deploying CentOS in DHCP but it work just fine on Ubuntu 20.04. It look like the host is not getting IP or proper configuration for the network, using the same host it work fine with Ubuntu.

here is some output from maas admin machine get-curtin-config <nodeid>

Ubuntu:

network:
bonds:
 bond0:
  dhcp4: true
  interfaces:
  - ens3f0
  - ens3f1
  macaddress: ...REMOVED...
  mtu: 1500
  parameters:
    down-delay: 0
    gratuitious-arp: 1
    mii-monitor-interval: 0
    mode: active-backup
    transmit-hash-policy: layer2
    up-delay: 0
ethernets:
 ens3f0:
  match:
    macaddress: ...REMOVED...
  mtu: 1500
  set-name: ens3f0
ens3f1:
  match:
    macaddress: ...REMOVED...
  mtu: 1500
  set-name: ens3f1
version: 2

CentOS:

network:
config:
 - id: ens3f0
   mac_address: ...REMOVED...
   mtu: 1500
   name: ens3f0
   subnets:
- type: manual
  type: physical
- id: ens3f1
  mac_address: ...REMOVED...
  mtu: 1500
  name: ens3f1
  subnets:
  - type: manual
type: physical
- bond_interfaces:
   - ens3f0
   - ens3f1
  id: bond0
  mac_address: ...REMOVED...
  mtu: 1500
  name: bond0
  params:
    bond-downdelay: 0
    bond-miimon: 0
    bond-mode: active-backup
    bond-num-grat-arp: 1
    bond-updelay: 0
    bond-xmit-hash-policy: layer2
 subnets:
 - type: dhcp4
 type: bond
 version: 1

Thanks!

Hi @pdion891, this looks like it might warrant reporting a bug, would you mind creating a bug report here?

bug report created: https://bugs.launchpad.net/maas/+bug/1931610

marking this one as “waiting on user”, since bug has been marked “Incomplete”