cron autopkgtest failure on armhf

Bug #2032532 reported by Bryce Harrington
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cron (Ubuntu)
New
Undecided
Unassigned
exim4 (Ubuntu)
New
Undecided
Unassigned

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

Bryce Harrington (bryce)
tags: added: update-excuse
summary: - exim4 autopkgtest failure on armhf
+ cron autopkgtest failure on armhf
Revision history for this message
Bryce Harrington (bryce) wrote :

The command generating the failure is:

echo "================= adding user 'dummy' ====================="
getent passwd dummy || adduser --disabled-password --gecos "" dummy

Debian does not seem to hit this error running with exim4 on armhf:

https://ci.debian.net/data/autopkgtest/testing/armhf/c/cron/36827801/log.gz

361s +---------------------------------+
361s | Here we are testing the patch |
361s | features/protect-list.patch |
361s +---------------------------------+
361s ================= adding user 'dummy' =====================
362s info: Adding user `dummy' ...
362s info: Selecting UID/GID from range 1000 to 59999 ...
362s info: Adding new group `dummy' (1001) ...
362s info: Adding new user `dummy' (1001) with group `dummy (1001)' ...
362s info: Creating home directory `/home/dummy' ...
362s info: Copying files from `/etc/skel' ...
362s info: Adding new user `dummy' to supplemental / extra groups `users' ...
362s info: Adding user `dummy' to group `users' ...
362s ========= Inject an obfuscated line into dummy's crontab ==============
362s ========== testing the crontab of user 'dummy' =============
362s ========= here is a hexa dump of $(crontab -u dummy -l) ====
362s 00000000 2a 20 2a 20 2a 20 2a 20 2a 20 3e 2f 74 6d 70 2f |* * * * * >/tmp/|
362s 00000010 78 3b 0d 6e 6f 20 63 72 6f 6e 74 61 62 20 66 6f |x;.no crontab fo|
362s 00000020 72 20 64 75 6d 6d 79 08 08 62 6f 0a |r dummy..bo.|
362s 0000002c

description: updated
Revision history for this message
Bryce Harrington (bryce) wrote :

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.

Revision history for this message
Bryce Harrington (bryce) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.