Activity log for bug #1444992

Date Who What changed Old value New value Message
2015-04-16 12:57:33 Mark Brown bug added bug
2015-04-16 16:50:32 Raphaël Badin bug task added curtin
2015-04-21 12:59:54 Blake Rouse bug task added maas-images
2015-04-21 13:00:36 Blake Rouse maas: milestone 1.8.0
2015-04-21 13:00:38 Blake Rouse maas: status New Triaged
2015-04-21 13:00:52 Blake Rouse maas: importance Undecided High
2015-06-03 14:15:13 Andres Rodriguez maas: milestone 1.8.0 1.9.0
2015-10-29 20:16:18 Scott Moser curtin: status New Triaged
2015-10-29 20:16:20 Scott Moser maas-images: status New Triaged
2015-10-29 20:16:25 Scott Moser maas-images: importance Undecided Medium
2015-10-29 20:16:28 Scott Moser curtin: importance Undecided Medium
2016-02-18 15:47:42 Andres Rodriguez maas: milestone 1.9.0
2016-03-31 05:36:49 Nobuto Murata bug added subscriber Nobuto Murata
2016-10-03 16:27:30 Blake Rouse bug task added cloud-images
2016-12-06 13:26:45 Jon Grimm bug added subscriber Jon Grimm
2016-12-15 17:43:56 Nish Aravamudan curtin: assignee Nish Aravamudan (nacc)
2017-02-03 01:21:41 Nish Aravamudan bug task added livecd-rootfs (Ubuntu)
2017-02-09 02:11:43 Nish Aravamudan branch linked lp:~nacc/livecd-rootfs/iscsi-initiatorname
2017-03-23 18:27:33 Launchpad Janitor livecd-rootfs (Ubuntu): status New Fix Released
2017-07-25 21:44:47 Dan Watkins cloud-images: status New Fix Released
2017-09-14 14:22:32 Victor Tapia bug added subscriber Victor Tapia
2017-09-14 20:11:18 Kellen Renshaw bug added subscriber Kellen Renshaw
2017-09-17 02:50:57 Dominique Poulain bug added subscriber Dominique Poulain
2017-09-18 09:29:38 Edward Hope-Morley nominated for series Ubuntu Xenial
2017-09-19 09:27:29 Victor Tapia branch linked lp:~vtapia/livecd-rootfs/xenial-proposed-lp1444992
2017-09-19 19:57:39 Steve Langasek bug task added livecd-rootfs (Ubuntu Xenial)
2017-10-04 18:38:21 Balint Reczey livecd-rootfs (Ubuntu Xenial): status New Confirmed
2017-10-04 19:58:21 Nish Aravamudan 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. [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.
2017-10-19 23:02:59 Brian Murray livecd-rootfs (Ubuntu Xenial): status Confirmed Fix Committed
2017-10-19 23:03:02 Brian Murray bug added subscriber Ubuntu Stable Release Updates Team
2017-10-19 23:03:04 Brian Murray bug added subscriber SRU Verification
2017-10-19 23:03:09 Brian Murray tags verification-needed verification-needed-xenial
2017-10-21 06:36:29 Steve Langasek tags verification-needed verification-needed-xenial verification-done-xenial
2017-10-30 16:44:55 Launchpad Janitor livecd-rootfs (Ubuntu Xenial): status Fix Committed Fix Released
2017-11-03 22:14:59 Andres Rodriguez maas: status Triaged Won't Fix