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

[Dimitri John Ledkov]

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

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

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

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

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

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

** Also affects: livecd-rootfs (Ubuntu Xenial)
   Importance: Undecided
       Status: New

** Description changed:

+ #! NB Foundations coding day task !#
+ 
+ [Impact]
+ 
+  * An explanation of the effects of the bug on users and
+ 
+  * justification for backporting the fix to the stable release.
+ 
+  * In addition, it is helpful, but not required, to include an
+    explanation of how the upload fixes this bug.
+ 
+ [Test Case]
+ 
+  * detailed instructions how to reproduce the bug
+ 
+  * these should allow someone who is not familiar with the affected
+    package to reproduce the bug and verify that the updated package fixes
+    the problem.
+ 
+ [Regression Potential]
+ 
+  * discussion of how regressions are most likely to manifest as a result
+ of this change.
+ 
+  * It is assumed that any SRU candidate patch is well-tested before
+    upload and has a low overall risk of regression, but it's important
+    to make the effort to think about what ''could'' happen in the
+    event of a regression.
+ 
+  * This both shows the SRU team that the risks have been considered,
+    and provides guidance to testers in regression-testing the SRU.
+ 
+ [Other Info]
+  
+  * Anything else you think is useful to include
+  * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board
+  * and address these questions in advance
+ 
+ ===
+ 
  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.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to livecd-rootfs in Ubuntu.
https://bugs.launchpad.net/bugs/1792905

Title:
  [2.5] iSCSI systemd services fails and blocks for 1 min 30 secconds

Status in cloud-images:
  Triaged
Status in MAAS:
  Triaged
Status in livecd-rootfs package in Ubuntu:
  New
Status in open-iscsi package in Ubuntu:
  Confirmed
Status in livecd-rootfs source package in Xenial:
  New
Status in open-iscsi source package in Xenial:
  New
Status in livecd-rootfs source package in Bionic:
  New
Status in open-iscsi source package in Bionic:
  New
Status in livecd-rootfs source package in Cosmic:
  New
Status in open-iscsi source package in Cosmic:
  Confirmed

Bug description:
  #! NB Foundations coding day task !#

  [Impact]

   * An explanation of the effects of the bug on users and

   * justification for backporting the fix to the stable release.

   * In addition, it is helpful, but not required, to include an
     explanation of how the upload fixes this bug.

  [Test Case]

   * detailed instructions how to reproduce the bug

   * these should allow someone who is not familiar with the affected
     package to reproduce the bug and verify that the updated package fixes
     the problem.

  [Regression Potential]

   * discussion of how regressions are most likely to manifest as a
  result of this change.

   * It is assumed that any SRU candidate patch is well-tested before
     upload and has a low overall risk of regression, but it's important
     to make the effort to think about what ''could'' happen in the
     event of a regression.

   * This both shows the SRU team that the risks have been considered,
     and provides guidance to testers in regression-testing the SRU.

  [Other Info]
   
   * Anything else you think is useful to include
   * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board
   * and address these questions in advance

  ===

  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1792905/+subscriptions