mount: /var/lib/snapd/seed/systems: mountpoint does not exist

[Olivier Gayot]

I am testing the server installer in a VM based on current development branch [1]. I am trying to perform a normal install, i.e., without TPM-backed FDE.

After passing the source screen, the installation crashes with the following error:

subprocess.CalledProcessError: Command '['systemd-run', '--wait', '--same-dir', '--property', 'SyslogIdentifier=subiquity_log.1793', '--setenv', 'PATH=/snap/subiquity/x1/bin:/snap/subiquity/x1/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/snap/subiquity/x1/bin:/snap/subiquity/x1/sbin', '--setenv', 'PYTHONPATH=:/snap/subiquity/x1/lib/python3.8/site-packages', '--setenv', 'PYTHON=/snap/subiquity/x1/usr/bin/python3.8', '--setenv', 'SNAP=/snap/subiquity/x1', '--', 'mount', '-o', 'bind', '/tmp/tmpd9fr2ql6/root.dir/var/lib/snapd/seed/systems', '/var/lib/snapd/seed/systems']' returned non-zero exit status 32.

The journal shows that the mountpoint specified does not exist.

Nov 23 08:42:15 ubuntu-server kernel: overlayfs: "xino" feature enabled using 32 upper inode bits.
Nov 23 08:42:15 ubuntu-server systemd[1]: Started /usr/bin/mount -o bind /tmp/tmpc211euj5/root.dir/var/lib/snapd/seed/systems /var/lib/snapd/seed/systems.
Nov 23 08:42:15 ubuntu-server subiquity_log.1793[2006]: mount: /var/lib/snapd/seed/systems: mount point does not exist.
Nov 23 08:42:15 ubuntu-server subiquity_log.1793[2006]: dmesg(1) may have more information after failed mount system call.
Nov 23 08:42:15 ubuntu-server systemd[1]: run-u17.service: Main process exited, code=exited, status=32/n/a
Nov 23 08:42:15 ubuntu-server systemd[1]: run-u17.service: Failed with result 'exit-code'.

By examining the filesystem, it turns out that the source directory does not exist either.

[1] fd3a856bc4d924650bd9d1bbb19b9883fa83c5bc

[Olivier Gayot (ogayot)]

PR opened on Github: https://github.com/canonical/subiquity/pull/1493

[Ubuntu QA Website (ubuntuqa)]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
https://iso.qa.ubuntu.com/qatracker/reports/bugs/1997538