Comment 2 for bug 2032532

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.