E: 15binfmt: touch: cannot touch '<snip>/usr/libexec/qemu-binfmt/s390x-binfmt-P': No such file or directory

[Juerg Haefliger]

[SRU Justification]

[Impact]

Failed to setup schroot of a foreign arch.

[Fix]

This has been fixed in debian salsa git commit f6da297a ("schroot-setup: create parent directory for binfmt interpreter"), version 1.6.10-12.

[Test Case]

$ mk-sbuild --arch s390x jammy

[Where problems could occur]

This fixes only a static setup script. Unlikely to have any other issue.

[Other Info]

Only X/T/B/F are proposed for fixing because it should have been fixed in Impish or later.

========== original bug description ==========

Creating an sbuild chroot for a foreign arch fails on hirsute:

$ mk-sbuild --arch s390x impish
/usr/sbin/qemu-debootstrap
W: qemu-debootstrap is deprecated. Please use regular debootstrap directly
I: Running command: debootstrap --arch=s390x --variant=buildd --components=main,restricted,universe,multiverse impish /var/lib/schroot/chroots/impish-s390x http://ports.ubuntu.com/ubuntu-ports
I: Target architecture can be executed
I: Retrieving InRelease
I: Checking Release signature
<snip>
I: Configuring build-essential...
I: Configuring libc-bin...
I: Base system installed successfully.
E: 15binfmt: touch: cannot touch '/var/run/schroot/mount/impish-s390x-a4aa318e-7cda-4f86-bc28-1517d689fdfc/usr/libexec/qemu-binfmt/s390x-binfmt-P': No such file or directory
E: 15binfmt: touch: cannot touch '/var/run/schroot/mount/impish-s390x-a4aa318e-7cda-4f86-bc28-1517d689fdfc/usr/libexec/qemu-binfmt/s390x-binfmt-P': No such file or directory
E: impish-s390x-a4aa318e-7cda-4f86-bc28-1517d689fdfc: Chroot setup failed: stage=setup-start

It seems we need a bump to 1.6.10-12:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983087

[You-Sheng Yang (vicamo)]

This has been fixed in debian salsa git commit f6da297a ("schroot-setup: create parent directory for binfmt interpreter"), version 1.6.10-12. Ubuntu Impish/Jammy/Kinetic have it already.

[You-Sheng Yang (vicamo)]

Test builds are available in
https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1939974.

Need sponsor for uploading.

[Steve Langasek (vorlon)]

trusty, xenial, and bionic have all reached the end of standard support and accept security updates only via the ESM archive. This is not a security fix so does not fit the update policy for those series. Marking wontfix accordingly.

[Steve Langasek (vorlon)]

Thank you for the patch. I've rebased this on 1.6.10-9ubuntu0.1 in focal-security and uploaded it to the unapproved queue. The only substantive change necessary was to use 1.6.10-9ubuntu0.2 instead of 1.6.10-9ubuntu1 as the version in the changelog.

[Chris Halse Rogers (raof)]

Hello Juerg, or anyone else affected,

Accepted schroot into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/schroot/1.6.10-9ubuntu0.2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-focal. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Steve Langasek (vorlon)]

In a focal chroot on a lunar system:

$ sudo apt install ubuntu-dev-tools
$ mk-sbuild --arch s390x jammy
$ schroot -c jammy-s390x
E: 10mount: mount: /run/schroot/mount/jammy-s390x-b4220f6e-610c-49e6-ab0c-60eb067368c2: unknown filesystem type 'aufs'.
E: jammy-s390x-b4220f6e-610c-49e6-ab0c-60eb067368c2: Chroot setup failed: stage=setup-start
$

Um ok then.

$ sudo sed -i -e'/aufs/d' /etc/schroot/chroot.d/sbuild-jammy-s390x
$ schroot -c jammy-s390x
(jammy-s390x)vorlon@homer:/tmp$ ls
(jammy-s390x)vorlon@homer:/tmp$
logout
(focal)vorlon@homer:/tmp$

So I don't appear to be able to reproduce the original bug?

[Steve Langasek (vorlon)]

Alright, let's try this in a focal VM.

$ sudo apt install ubuntu-dev-tools
$ sg sbuild -c 'mk-sbuild --arch s390x jammy'
$ sg sbuild -c 'schroot -c jammy-s390x'
$

So I can't reproduce it in a focal VM, either.

[Steve Langasek (vorlon)]

Marking verification-failed. Juerg, You-Sheng, please clarify how to reproduce the original problem.

[Juerg Haefliger (juergh)]

Steve, there is no problem in Focal. The issue was introduced in qemu-user-static *after* Focal when /usr/libexec/qemu-binfmt/<arch>-binfmt-P symlinks were added which breaks old schroot packages (specifically the 15binfmt script). Jammy and later has the above mentioned schroot fix so we're all good.

[Steve Langasek (vorlon)]

Ok, the patch had been raised for the focal series. I guess we'll drop this SRU then.

[Chris Halse Rogers (raof)]

The version of schroot in the proposed pocket of Focal that was purported to fix this bug report has been removed because one or more bugs that were to be fixed by the upload have failed verification and been in this state for more than 10 days.

[Chris Halse Rogers (raof)]

The sru-remove tooling doesn't support custom rejection messages, but this has been removed and the Focal bug marked as Invalid as per the discussion above.