yahoo-eng-team team mailing list archive

[James Falcon <1905358@xxxxxxxxxxxxxxxxxx>]

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

** Bug watch added: github.com/canonical/cloud-init/issues #3810
   https://github.com/canonical/cloud-init/issues/3810

** Changed in: cloud-init
       Status: Triaged => Expired

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1905358

Title:
  cloud-init fails to configure a bond on CentOS 8

Status in cloud-init:
  Expired

Bug description:
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1905358/+subscriptions