group.of.nepali.translators team mailing list archive

[Launchpad Bug Tracker <1589526@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package multipath-tools -
0.5.0+git1.656f8865-5ubuntu2.1

---------------
multipath-tools (0.5.0+git1.656f8865-5ubuntu2.1) xenial; urgency=medium

  * Cherrypick from debian:
   - Call clean target before rebuilding with systemd support
   - Call systemd in debian/rules. Also adapt init service
     aliasing.
   - Resolves LP: #1578638, LP: #1589526, LP: #1583563. Separate bugs, all
    due to same root cause.

 -- Dimitri John Ledkov <xnox@xxxxxxxxxx>  Thu, 16 Jun 2016 11:53:33
+0300

** Changed in: multipath-tools (Ubuntu Xenial)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1589526

Title:
  fcp multipath devices does not exist after reboot

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in multipath-tools package in Ubuntu:
  Fix Released
Status in multipath-tools source package in Xenial:
  Fix Released

Bug description:
  [Impact]

   * Both systemd units and init scripts are shipped for multipath-
  tools.

   * However units did not correctly take priority, as initscripts and
  units names did not match.

   * Further more multipath-tools was miscompiled without systemd
  support for Type=Notify unit

  [Test Case]

   * Using service command, init script, or systemctl commands starting
  "multipath-tools" should operate on systemd "multipathd.service" unit.

   * Systems must boot with multipath-tools installed correctly, and
  multipathd.service started.

  == Comment: #0 - Ofer Baruch <OFERBA@xxxxxxxxxx> - 2016-06-06 06:37:19 ==
  Hi,

  i have installed an Ubuntu Server from the installation ISO.
  i then installed multipath support (multipath-tools and multipath-tools-boot).
  i added an FCP device, format it, mount it and added to the fstab using it's /dev/mapper representation. everything worked fine...
  i then reboot the server and it failed to start due to the missing /dev/mapper device that needs to be mounted (as the fstab states).
  i get into maintenance mode.

  i am not using cio_ignore and the devices are available in maintenance mode.
  running multipath -ll will fail to show the device (as expected... that is why the boot failed).
  running multipat without any parameters (to rescan) will find the devices and it will now show on multipath -ll.

  i was able to get around this by rebuilding the initrd and running
  zipl... but that should not be the case. multipath should scan during
  reboot to find all the devices available.

  i am attaching both an sosreport and dbginfo for you to review.
  i hope this is something i am doing wrong but i don't think so...
  either way i would love to get a quick workaround that will avoid this issue without rebuilding the initrd.

  == Comment: #4 - Hendrik Brueckner <brueckner@xxxxxxxxxx> - 2016-06-06 06:44:53 ==
  Hi Ofer,

  (In reply to comment #0)
  > i have installed an Ubuntu Server from the installation ISO.
  > i then installed multipath support (multipath-tools and
  > multipath-tools-boot).
  > i added an FCP device, format it, mount it and added to the fstab using it's

  How did you add the FCP device?

  == Comment: #5 - Ofer Baruch <OFERBA@xxxxxxxxxx> - 2016-06-06 07:07:42 ==
  using:

  chzdev zfcp-host <fcp_vdev> -e -p

  that is after i vary the device online.
  as i said the device comes online just fine... i can see all the /dev/sd* devices.
  i am just missing the multipath device.

  == Comment: #6 - Ofer Baruch <OFERBA@xxxxxxxxxx> - 2016-06-06 07:11:09 ==
  the missing file is:
  /dev/mapper/3600507630bffc0470000000000002333

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1589526/+subscriptions