[Bug 1802354] Re: iscsid does not run if there are only initramfs initiated targets

Tue Nov 20 17:16:03 UTC 2018

Hello Scott, or anyone else affected,

Accepted open-iscsi into cosmic-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/open-
iscsi/2.0.874-5ubuntu9.1 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 and change the tag from
verification-needed-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. 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.

** Changed in: open-iscsi (Ubuntu Cosmic)
       Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-cosmic

** Changed in: open-iscsi (Ubuntu Bionic)
       Status: In Progress => Fix Committed

** Tags added: verification-needed-bionic

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

Title:
  iscsid does not run if there are only initramfs initiated targets

Status in open-iscsi package in Ubuntu:
  Fix Released
Status in open-iscsi source package in Bionic:
  Fix Committed
Status in open-iscsi source package in Cosmic:
  Fix Committed

Bug description:
  === Begin SRU Template ===
  [Impact]
  A previous change to open-iscsi made under bug 1755858 caused a regression
  that is seen when a system has only a iscsi mounts that were made
  in the initramfs.  The most likely scenario would be iscsi root.

  The problem seen is that in this scenario the iscsid.service will not be
  started.  That generally works, but will have unexpected issues if
  service is done to the iscsi target (external system).  That could occur
  if the remote system needed to be serviced for any reason.  If iscsid
  is running, the client will handle this scenario properly.

  The change made here is to add a udev rule installed into
  /lib/udev/rules.d/70-iscsi-disk.rules with the content:
     SUBSYSTEM=="block", ACTION=="add", ENV{ID_PATH}=="*-iscsi-*",
         ENV{SYSTEMD_WANTS}="iscsid.service"

  The key things to see in that rule are:
  a.) only matches on add of a block device.
  We will not currently stop the iscsid.service ever via udev.

  b.) only matches a PATH with '-iscsi-' in it.
  tests show that ID_PATH will come up with something like:
     ip-<ipv4-dotted-quad>:<port>-iscsi-<target>-lun-<lun>
  example:
     ip-192.168.1.1:3270-iscsi-mydisk1-lun-2

  See other info section below for a 'udevadm info' output.

  c.) uses SYSTEMD_WANTS.
  More information can be seen on that at
   https://www.freedesktop.org/software/systemd/man/systemd.device.html
  doc states:

    "[systemd_wants] may be used to activate arbitrary units when a specific
     device becomes available."

  [Test Case]
  A check for iscsid.service to be running has been added to the dep8
  test of the open-iscsi package.  The simplist check is to have
  the dep8 test run.  The test will gate entry into -proposed so
  we can have confidence the bug is fixed.

  Since this bug was originally reported on Oracle public cloud instances
  we should also test that platform.

  To do that:
   * launch a hardware instance on oracle of 16.04.
   * verify iscsid.service is *not* running.
     If iscsid.service is already running, it may have been started by
     an image modification.  To make this a valid test, you will
     then need to disable whatever change made that occur.
   * enable proposed and upgrade
   * reboot
   * verify that iscsid.service is running.

  [Regression Potential]
  The most likely chance for regression here would be the iscsid.service
  running when it should not be running.  Saving a udev rule execution
  error, a false-positive on the 'match' above would trigger this.
  It seems relatively unlikely that a non-iscsi device would have a ID_PATH
  containing '-iscsi-', but is possible.

  [Other Info]
  Here is output of 'udevadm info' on a iscsi root device:
      http://paste.ubuntu.com/p/dj89ScVR82/

  There is autopkgtest run of proposed
    bionic: http://paste.ubuntu.com/p/FqPPtD8jV6/
    cosmic: http://paste.ubuntu.com/p/Fb3rYP7Xhs/

  === End SRU Template ===

  It was reported that after the changes made in bug 1755858, the iscsid
  service was not running when initramfs (via iscsi_* params or iBft)
  set up an iscsi mount.

  This seems to not be a problem until there is a restart of the iscsi
  *host* service or some other hiccup.  Thus, in normal testing you will
  not see this issue.

  --
  Related bugs:
   * bug 1755858: iscsid autostarts on all servers when it has nothing to do.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: open-iscsi 2.0.874-5ubuntu2.3 [modified: lib/systemd/system/open-iscsi.service]
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  Date: Thu Nov  8 17:42:46 2018
  ProcEnviron:
   TERM=screen.xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: open-iscsi
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.iscsi.iscsid.conf: 2018-10-12T16:51:00.187144

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1802354/+subscriptions