Ubiquity in the 20191008 daily image for 19.10 doesn't present the minimal install option

[Martin Wimpress ]

Ubuntu Deskop 20191008

In the current 19.10 daily image, the minimal install option is no longer presented for flavours that support it.

[Iain Lane (laney)]

The bug is actually in casper, but maybe we should leave a ubiquity task for visibility.

[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:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1847251

[Steve Langasek (vorlon)]

Iain, could you provide some more details on how you determined this was a casper bug?

[Steve Langasek (vorlon)]

Sounds like Dimitri has seen some similar symptom and is going to retest on today's image using current casper.

[Iain Lane (laney)]

This is fixed in casper 1.424. casper 1.423 introduced a systemd mount unit which was intended to facilitate unmounting of /cdrom.

But it was wrong: you cannot use DefaultDepdencies=no to override the BindsTo= that systemd generates for the corresponding device node (dev-sr0.device in this case). So if this wasn't available to the live system - because udev hadn't finished cold plugging by the time systemd got around to starting the mount unit - the device was *unmounted* instead.

You ended up with an empty directory in /cdrom. The minimal install option relies on reading a file out of there to decide if it should be presented. The file didn't exist, and so the minimal option wasn't shown.

Fixed, as I say. Seb closed a different bug with the upload, but this one can also be done away with.

It's a revert, so that means that the reliable unmounting that this was supposed to achieve is not present either.

[Dimitri John Ledkov (xnox)]

cannot reproduce with 20191010 incomplete... / fix released... ?

also see https://lists.freedesktop.org/archives/systemd-devel/2019-October/043573.html