[Bug 1927005] Re: /etc/default/mdadm refers to non-existent /etc/cron.* files

[Balint Reczey]

I've fixed the reference to /etc/cron.daily/mdadm in 4.1-11ubuntu1
because it is already honored by mdmonitor-oneshot.service , but
AUTOCHECK should be honored by the other servicing replacing the cron
job. This will be a follow-up change for LP: #1815201.

** Changed in: mdadm (Ubuntu)
       Status: New => Confirmed

** Changed in: mdadm (Ubuntu)
   Importance: Undecided => Low

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

Title:
  /etc/default/mdadm refers to non-existent /etc/cron.* files

Status in mdadm package in Ubuntu:
  Confirmed

Bug description:
  To quote:

  # AUTOCHECK:
  #   should mdadm run periodic redundancy checks over your arrays? See
  #   /etc/cron.d/mdadm.
  AUTOCHECK=true

  # AUTOSCAN:
  #   should mdadm check once a day for degraded arrays? See
  #   /etc/cron.daily/mdadm.
  AUTOSCAN=true

  Neither /etc/cron.d/mdadm nor /etc/cron.daily/mdadm exist (having been
  converted to systemd timers at some point, I believe).

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: mdadm 4.1-10ubuntu3
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted
  Date: Mon May  3 20:18:03 2021
  MachineType: Gigabyte Technology Co., Ltd. B450M DS3H
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-16-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash resume=UUID=73909634-a75d-42c9-8f66-a69138690756 pcie_aspm=off
  ProcMDstat:
   Personalities : 
   unused devices: <none>
  SourcePackage: mdadm
  UpgradeStatus: No upgrade log present (probably fresh install)
  acpidump:
   
  dmi.bios.date: 01/25/2019
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: Default string
  dmi.board.name: B450M DS3H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd01/25/2019:br5.13:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: B450M DS3H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  etc.blkid.tab: Error: [Errno 2] No such file or directory: '/etc/blkid.tab'
  initrd.files: Error: [Errno 2] No such file or directory: '/boot/initrd.img-5.11.0-16-generic'

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