[Bug 2032532] Re: cron autopkgtest failure on armhf

[Bryce Harrington]

I haven't identified where the command `logger` gets called in this
particular test case, however the following bug report filed against
util-linux seems relevant:

    https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1991436
    https://github.com/util-linux/util-linux/issues/2336

According to that report, the issue crops up inside LXD containers only,
which may explain why this occurs on armhf only.  As I understand it,
that architecture is implemented synthetically in the autopkgtest
infrastructure as a container, unlike how the other architectures are
set up, and probably unlike how Debian implements their armhf testing.

The upstream fix for this appears to be included in util-linux v2.39,
which is currently in mantic-proposed:

    https://github.com/util-linux/util-
linux/commit/3b59942da4bd157ed9a4a5d12e2f62317e2c61e3

    util-linux | 2.38.1-5ubuntu2   | mantic
    util-linux | 2.39.1-4ubuntu1   | mantic-proposed

Thus, I believe triggering against this latter version of util-linux
should resolve the migration issue.

** Bug watch added: github.com/util-linux/util-linux/issues #2336
   https://github.com/util-linux/util-linux/issues/2336

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

Title:
  cron autopkgtest failure on armhf

Status in cron package in Ubuntu:
  New
Status in exim4 package in Ubuntu:
  New

Bug description:
  The cron autopkgtests fail on armhf when run with exim4, blocking the
  latest exim4 merge's migration:

  https://code.launchpad.net/~bryce/ubuntu/+source/exim4/+git/exim4/+merge/448540
  https://autopkgtest.ubuntu.com/packages/c/cron/mantic/armhf
  https://autopkgtest.ubuntu.com/results/autopkgtest-mantic/mantic/armhf/c/cron/20230821_121833_8b636@/log.gz

  1824s autopkgtest [07:59:06]: test check-listings-protection: [-----------------------
  1826s +---------------------------------+
  1826s |  Here we are testing the patch  |
  1826s |  features/protect-list.patch    |
  1826s +---------------------------------+
  1826s ================= adding user 'dummy' =====================
  1826s info: Adding user `dummy' ...
  1826s logger: send message failed: Invalid argument
  1826s info: Selecting UID/GID from range 1000 to 59999 ...
  1826s logger: send message failed: Invalid argument
  1826s info: Adding new group `dummy' (1001) ...
  1826s logger: send message failed: Invalid argument
  1826s info: Adding new user `dummy' (1001) with group `dummy (1001)' ...
  1826s logger: send message failed: Invalid argument
  1826s info: Creating home directory `/home/dummy' ...
  1826s logger: send message failed: Invalid argument
  1826s info: Copying files from `/etc/skel' ...
  1826s logger: send message failed: Invalid argument
  1826s info: Adding new user `dummy' to supplemental / extra groups `users' ...
  1826s logger: send message failed: Invalid argument
  1826s info: Adding user `dummy' to group `users' ...
  1826s logger: send message failed: Invalid argument
  1826s ========= Inject an obfuscated line into dummy's crontab ==============
  1827s ========== testing the crontab of user 'dummy' =============
  1827s ========= here is a hexa dump of $(crontab -u dummy -l) ====
  1827s 00000000  2a 20 2a 20 2a 20 2a 20  2a 20 3e 2f 74 6d 70 2f  |* * * * * >/tmp/|
  1827s 00000010  78 3b 0d 6e 6f 20 63 72  6f 6e 74 61 62 20 66 6f  |x;.no crontab fo|
  1827s 00000020  72 20 64 75 6d 6d 79 08  08 62 6f 0a              |r dummy..bo.|
  1827s 0000002c
  1827s +---------------------------------------------+
  1827s |  Good! characters
   and  were protected  |
  1827s +---------------------------------------------+
  1827s autopkgtest [07:59:09]: test check-listings-protection: -----------------------]

  1831s check-listings-protection FAIL stderr: logger: send message failed: Invalid argument
  1831s autopkgtest [07:59:13]: test check-listings-protection:  - - - - - - - - - - stderr - - - - - - - - - -
  1831s logger: send message failed: Invalid argument
  1831s logger: send message failed: Invalid argument
  1831s logger: send message failed: Invalid argument
  1831s logger: send message failed: Invalid argument
  1831s logger: send message failed: Invalid argument
  1831s logger: send message failed: Invalid argument
  1831s logger: send message failed: Invalid argument

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