[Bug 1937953] Re: systemd forcibly disables use of dummy/bond interfaces

[Simon Arlott]

A workaround is to create an empty file /etc/modprobe.d/systemd.conf but
this is too imprecise. The files that systemd uses should ideally be
named specifically for their purpose so that they can be overridden
without affecting any future changes in systemd, e.g.
/etc/modprobe.d/systemd-dummy.conf and /etc/modprobe.d/systemd-
bonding.conf

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1937953

Title:
  systemd forcibly disables use of dummy/bond interfaces

Status in systemd package in Ubuntu:
  New

Bug description:
  /etc/modprobe.d/local-dummy.conf contains:
  options dummy numdummies=10

  /etc/modules-load.d/local-dummy.conf contains:
  dummy

  /lib/modprobe.d/systemd.conf contains:
  options bonding max_bonds=0
  options dummy numdummies=0

  On boot, the "dummy" module is loaded with the options "numdummies=10
  numdummies=0" because configuration in /lib/modprobe.d/ overrides
  configuration in /etc/modprobe.d/.

  This makes it impossible to automatically load the dummy module with
  10 interfaces and then use them in /etc/network/interfaces.d/ because
  the configuration file provided with systemd overrides my module
  configuration by setting the number of interfaces back to 0.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10.50
  Uname: Linux 5.4.132+ x86_64
  ApportVersion: 2.20.9-0ubuntu7.24
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 25 19:18:14 2021
  InstallationDate: Installed on 2014-05-10 (2633 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.132+ root=UUID=3d2fba1f-59b9-424f-a0df-2e7f1e2d8637 ro rootflags=subvol=@ sysrq_always_enabled panic=600 reboot=p sd_mod.stop_before_reboot=0 page_owner=on page_poison=1 debug_objects=1
  SourcePackage: systemd
  UpgradeStatus: Upgraded to bionic on 2018-11-24 (973 days ago)
  dmi.bios.date: 11/22/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P7.20
  dmi.board.name: Z170 Extreme4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP7.20:bd11/22/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ170Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  modified.conffile..etc.systemd.journald.conf: [modified]
  modified.conffile..etc.systemd.logind.conf: [modified]
  mtime.conffile..etc.systemd.journald.conf: 2018-11-24T15:04:07.599704
  mtime.conffile..etc.systemd.logind.conf: 2015-07-04T15:46:37.746749

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1937953/+subscriptions