[Bug 1444992] Re: fastpath install duplicates iSCSI initiator names, blocking iSCSI HW

[Launchpad Bug Tracker]

This bug was fixed in the package livecd-rootfs - 2.440

---------------
livecd-rootfs (2.440) zesty; urgency=medium

  [ Steve Langasek ]
  * live-build/ubuntu-cpc/functions: don't call sleep as part of
    umount_settle; udevadm settle is synchronous and there's no reason to
    sleep after it.
  * live-build/ubuntu-cpc/functions: umount_partition: don't call
    umount_settle for each submount; just unmount them one by one and
    settle at the end.
  * Support passing IMAGE_TARGETS in the environment, to limit which images
    are output as part of a build; particularly useful for ubuntu-cpc builds
    which output multiple image types.

  [ Nishanth Aravamudan ]
  * live-build/ubuntu-cpc/hooks/061-open-iscsi.chroot: generate iSCSI
    Initiator Name at first iscsid run for cloud images to ensure it is
    unique (LP: #1444992).

  [ Brian Murray ]
  * Fix the OVF's metadata to include Ubuntu specific identifiers and
    descriptions instead of the generic Linux ones. Thanks to Chris Glass.
    (LP: #1656293)
  * Add replace_grub_root_with_label function thereby consolidating multiple
    uses of the same calls to sed. Thanks to Dan Watkins.

  [ Adam Conrad ]
  * Set device_tree_address for the new kernel in the RPi bootloader config.txt

 -- Adam Conrad <adconrad at ubuntu.com>  Thu, 23 Mar 2017 11:39:22 -0600

** Changed in: livecd-rootfs (Ubuntu)
       Status: New => Fix Released

-- 
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/1444992

Title:
  fastpath install duplicates iSCSI initiator names, blocking iSCSI HW

Status in cloud-images:
  New
Status in curtin:
  Triaged
Status in MAAS:
  Triaged
Status in maas-images:
  Triaged
Status in livecd-rootfs package in Ubuntu:
  Fix Released

Bug description:
  When using fastpath install, each host is given an identical iSCSI
  initiator name. This does not happen with Debian install mode. The
  result is HW SANs that use iSCSI get confused. This is an actual
  customer/partner issue at present.

  It would appear to be fallout of the image based approach to installation.
  The /etc/iscsi/initiatorname.iscsi file contains something like:
   ## DO NOT EDIT OR REMOVE THIS FILE!
   ## If you remove this file, the iSCSI daemon will not start.
   ## If you change the InitiatorName, existing access control lists
   ## may reject this initiator.  The InitiatorName must be unique
   ## for each iSCSI initiator.  Do NOT duplicate iSCSI InitiatorNames.
   InitiatorName=iqn.1993-08.org.debian:01:dcafddf1c8b

  That is what gets used as the initiator, and is seemingly generated at
  package-install time. It needs to be re-created
  uniquely per installed host.

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