[Bug 1792905] [NEW] [2.5] iSCSI systemd services fails and blocks for 1 min 30 secconds

[Launchpad Bug Tracker]

You have been subscribed to a public bug by Ubuntu Foundations Team Bug Bot (crichton):

[Impact]

 * Affects environments where the base image is read-only but kernel
modules are copied to a tempfs or other overlay mounted on /lib/modules.

 * This affects users of our stable release images available from http
://cloud-images.ubuntu.com.

 * The attached fixes ensure /lib/modules always exists by creating it
explicitly instead of relying on it to come from a package.

[Test Case]

 * Download http://cloud-images.ubuntu.com/bionic/current/bionic-server-
cloudimg-amd64.squashfs

 * Unpack it via `sudo unsquashfs bionic-server-cloudimg-amd64.squashfs`

 * Inspect the unpacked root filesystem and find that '/lib/modules' is
missing.

 * Install local build scripts as described at
https://github.com/chrisglass/ubuntu-old-fashioned (note: you will need
ubuntu-old-fashioned master for cosmic)

* Re-build the images using the updated livecd-rootfs package.

* Unpack the resulting livecd.ubuntu-cpc.squashfs artifact using
unsquashfs again.

* Inspect the unpacked root filesystem and find that '/lib/modules'
exists.

* It is pure luck that package purges which are done analogously in
Cosmic image builds do not remove '/lib/modules', hence this fix is
introduced there, as well.

* Xenial is not affected.

* Test builds were carried out for Cosmic and Bionic with the expected
results.

[Regression Potential]

 * This is a fix to a regression. The existence of the directory had
previously been ensured, but the mkdir call got lost in recent re-
factoring. See also:

https://bazaar.launchpad.net/~ubuntu-core-dev/livecd-rootfs/bionic-
proposed/revision/1678

https://bazaar.launchpad.net/~ubuntu-core-dev/livecd-
rootfs/trunk/revision/1681

 * Packaging tools should not take offense at the existence of a
directory, even if it was not part of a package. So potential for
unforseeable regressions is very low.

===ORIGINAL BUG DESCRIPTION===

Let me first start with saying MAAS is *not* using iSCSI anymore and is
*NOT* in this case either.

For some reason now using enlistment, commissioning, and deploying the
ephemeral environment will block for 1 min 30 seconds waiting for the
iSCSI daemon to succeed, which it never does.

This increases the boot time drastically.

** Affects: cloud-images
     Importance: Critical
         Status: Triaged

** Affects: maas
     Importance: High
         Status: Triaged

** Affects: livecd-rootfs (Ubuntu)
     Importance: Undecided
         Status: New

** Affects: open-iscsi (Ubuntu)
     Importance: Low
         Status: Confirmed

** Affects: livecd-rootfs (Ubuntu Xenial)
     Importance: Undecided
         Status: Invalid

** Affects: open-iscsi (Ubuntu Xenial)
     Importance: Undecided
         Status: New

** Affects: livecd-rootfs (Ubuntu Bionic)
     Importance: Undecided
         Status: New

** Affects: open-iscsi (Ubuntu Bionic)
     Importance: Undecided
         Status: New

** Affects: livecd-rootfs (Ubuntu Cosmic)
     Importance: Undecided
         Status: New

** Affects: open-iscsi (Ubuntu Cosmic)
     Importance: Low
         Status: Confirmed


** Tags: patch
-- 
[2.5] iSCSI systemd services fails and blocks for 1 min 30 secconds
https://bugs.launchpad.net/bugs/1792905
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.