group.of.nepali.translators team mailing list archive

[Andres Rodriguez <andreserl@xxxxxxxxxxxxx>]

We believe this is no longer an issue in the latest releases of MAAS.
Please upgrade to the latest version of MAAS, and If you believe this
issue is still present, please re-open this bug report or file a new
one.

** Changed in: maas
       Status: Triaged => Won't Fix

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

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

Status in cloud-images:
  Fix Released
Status in curtin:
  Triaged
Status in MAAS:
  Won't Fix
Status in maas-images:
  Triaged
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in livecd-rootfs source package in Xenial:
  Fix Released

Bug description:
  [Impact]

  * All Xenial cloud images currently share a fixed iSCSI Initiator Name
  by default when booted.

  * The Initiator Name is intended to be a globally unique identifier of
  a given initiator.

  [Test Case]

  * Start two instances (LXD, VMs) using cloud images built using the current livecd-rootfs.
    - Both instances will have the same InitiatorName in /etc/iscsi/initiatorname.iscsi.

  * Start two instances (LXD, VMs) using cloud images built using an updated livecd-rootfs.
    - The two instances should have distinct InitiatorName values in /etc/iscsi/initiatorname.iscsi.

  * Alternatively, the resulting cloud image from using the old and new
  livecd-rootfs can be compared. In the older case,
  /etc/iscsi/initiatorname.iscsi will contain a iqn value. In the fixed
  case, the file will container "Generate=yes".

  [Regression Potential]

  * It is currently an error that all cloud images of a given version
  share the same initiator name. (Even mentioned in the file in
  question!)

  * The likelihood of this regressing any real world iSCSI deployments
  is very low.

  * I imagine the primary source of regressions would be end-
  users/sysadmins already working around the broken iSCSI behavior in
  16.04 by manually rewriting this file. If they rely on detecting the
  fixed Debian initiatornname to do so, that detection will be broken.
  However, since in those cases, the initiator name is being generated
  at boot, that should be sufficient.

  * Note that this does not solve the known issue for iSCSI that if a
  snapshot of a booted image is used to launch more instances, they will
  share iSCSI initiator names.

  ---

  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