iSCSI volumes are not discovered during ubuntu 14.04.04 installation (Shinner)

Bug #1540995 reported by bugproxy
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
hw-detect (Ubuntu)
Fix Released
High
Mathieu Trudel-Lapierre
Trusty
Triaged
High
Mathieu Trudel-Lapierre
open-iscsi (Ubuntu)
Fix Released
High
Mathieu Trudel-Lapierre
Trusty
Triaged
High
Mathieu Trudel-Lapierre
partman-iscsi (Ubuntu)
Fix Released
High
Mathieu Trudel-Lapierre
Trusty
Triaged
High
Mathieu Trudel-Lapierre

Bug Description

---Problem Description---
iSCSI volumes are not discovered during ubuntu 14.04.04 installation

---uname output---
Linux ltcalpine-lp4 4.2.0-19-generic #23~14.04.1-Ubuntu SMP Thu Nov 12 12:32:48 UTC 2015 ppc64le GNU/Linux

---boot type---
CDROM / ISO image

---Install repository type---
CDROM

---Point of failure---
Other failure during installation (stage 1)

steps to reproduce:

1. on PowerVM, download the latest ubuntu 14.04.04 ISO from below location and setup virtual DVD.
http://cdimage.ubuntu.com/ubuntu-server/trusty/daily/current/

2. Once configured boot the virtual DVD, in the test system select the option 6 to boot from virtual cdrom

Version FW840.00 (SV840_047)
 SMS (c) Copyright IBM Corp. 2000,2015 All rights reserved.
-------------------------------------------------------------------------------
 Select Device
 Device Current Device
 Number Position Name
 1. - Interpartition Logical LAN
        ( loc=U8408.E8E.10A7AAV-V4-C2-T1 )
 2. - PCIe2 4-Port (10GbE SFP+ & 1GbE RJ45) Adapter
        ( loc=U78C7.001.RCH0040-P1-C4-T1 )
 3. - PCIe2 4-Port (10GbE SFP+ & 1GbE RJ45) Adapter
        ( loc=U78C7.001.RCH0040-P1-C4-T2 )
 4. - PCIe2 4-Port (10GbE SFP+ & 1GbE RJ45) Adapter
        ( loc=U78C7.001.RCH0040-P1-C4-T3 )
 5. - PCIe2 4-Port (10GbE SFP+ & 1GbE RJ45) Adapter
        ( loc=U78C7.001.RCH0040-P1-C4-T4 )
 6. - SCSI CD-ROM
        ( loc=U8408.E8E.10A7AAV-V4-C14-T1-L8300000000000000 )
 -------------------------------------------------------------------------------
 Navigation keys:
 M = return to Main Menu N = Next page of list
 ESC key = return to previous screen X = eXit System Management Services
 -------------------------------------------------------------------------------

3. During install configure eth3 which is configured to V7000 for iSCSI

  ??????????????????????? [!!] Configure the network ????????????????????????
  ? ?
  ? Your system has multiple network interfaces. Choose the one to use as ?
  ? the primary network interface during the installation. If possible, ?
  ? the first connected network interface found has been selected. ?
  ? ?
  ? Primary network interface: ?
  ? ?
  ? eth0: Ethernet ?
  ? eth1: Broadcom Corporation NetXtreme II BCM57800 1/10 Gigabit Eth ?
  ? eth2: Broadcom Corporation NetXtreme II BCM57800 1/10 Gigabit Eth ?
  ? eth3: Broadcom Corporation NetXtreme II BCM57800 1/10 Gigabit Eth <---- ?
  ? eth4: Broadcom Corporation NetXtreme II BCM57800 1/10 Gigabit Eth ?
  ? ?
  ? <Go Back> ?
  ? ?
  ???????????????????????????????????????????????????????????????????????????

4. configure iSCSI in the installer

           ?????????????????? [!!] Partition disks ??????????????????
           ? ?
           ? This menu allows you to configure iSCSI volumes. ?
           ? ?
           ? iSCSI configuration actions ?
           ? ?
           ? Log into iSCSI targets ?
           ? Finish ?
           ? ?
           ? <Go Back> ?
           ? ?
           ??????????????????????????????????????????????????????????

    ???????????????????????? [!!] Partition disks ?????????????????????????
    ? ?
    ? Enter an IP address to scan for iSCSI targets. To use a port other ?
    ? than the default of 3260, use "IP:port" notation, for example ?
    ? "1.2.3.4:3261". ?
    ? ?
    ? iSCSI target portal address: ?
    ? ?
    ? 10.10.10.10:3260,1 iqn.1986-03.com.ibm:2145.cluster9.114.15.142.node1 ?
    ? ?
    ? <Go Back> <Continue> ?
    ? ?
    ???????????????????????????????????????????????????????????????????????

    ????????????????????????? [!!] Partition disks ?????????????????????????
    ? ?
    ? Some iSCSI targets require the initiator (client) to authenticate ?
    ? using a username and password. If that is the case for this target, ?
    ? enter the username here. Otherwise, leave this blank. ?
    ? ?
    ? iSCSI initiator username for 10.10.10.10:3260,1 ?
    ? iqn.1986-03.com.ibm:2145.cluster9.114.15.142.node1: ?
    ? ?
    ? ____________________________________________________________________ ?
    ? ?
    ? <Go Back> <Continue> ?
    ? ?
    ????????????????????????????????????????????????????????????????????????

         ??????????????????? [!!] Partition disks ????????????????????
         ? ?
         ? Select the iSCSI targets you wish to use. ?
         ? ?
         ? iSCSI targets on 10.10.10.10:3260,1 ?
         ? iqn.1986-03.com.ibm:2145.cluster9.114.15.142.node1: ?
         ? ?
         ? [*] iqn.1986-03.com.ibm:2145.cluster9.114.15.142.node1 ?
         ? ?
         ? <Go Back> <Continue> ?
         ? ?
         ?????????????????????????????????????????????????????????????

           ?????????????????? [!!] Partition disks ??????????????????
           ? ?
           ? This menu allows you to configure iSCSI volumes. ?
           ? ?
           ? iSCSI configuration actions ?
           ? ?
           ? Log into iSCSI targets ?
           ? Finish ?
           ? ?
           ? <Go Back> ?
           ? ?
           ??????????????????????????????????????????????????????????

5. after successful iSCSI configure, the installer doesn't detect the iSCSI volumes, only the local disk is being detected.

  ?????????????????????????? [!!] Partition disks ???????????????????????????
  ? ?
  ? This is an overview of your currently configured partitions and mount ?
  ? points. Select a partition to modify its settings (file system, mount ?
  ? point, etc.), a free space to create partitions, or a device to ?
  ? initialize its partition table. ?
  ? ?
  ? ?
  ? SCSI1 (0,1,0) (sda) - 53.7 GB AIX VDASD ? ?
  ? > 1.0 MB FREE SPACE ? ?
  ? > #1 7.3 MB K ? ?
  ? > #2 51.4 GB ext4 ? ?
  ? > #3 2.2 GB F swap swap ? ?
  ? > 1.0 MB FREE SPACE ? ?
  ? ? ?
  ? Undo changes to partitions ?
  ? Finish partitioning and write changes to disk ?
  ? ?
  ? <Go Back> ?
  ? ?
  ???????????????????????????????????????????????????????????????????????????

Note:
1. With the OS installed on the local disk, we can discover the iSCSI volumes without any issues, however the ubuntu installer doesn't detect the volumes.
2. refer install_steps, for complete steps.
3. install folder contains the installation logs.

== Comment: #8 - Guilherme Guaglianoni Piccoli <email address hidden> - 2016-02-02 10:37:44 ==
This issue happens because Ubuntu installer creates a random initiatorName and does not allow user to change it - it does not even show the initiatorName to user. As a result, the Initiator (Ubuntu Installer) can't communicate with Target (the iSCSI server).

Talking to cyphermox at #Ubuntu-powerpc IRC channel, we discussed about the possibility of the Installer shows a dialog that allows user to choose the initiatorName manually before trying to connect to Target. Seems a good approach that would solve this issue.

Mirroring to LaunchPad.
Cheers,

Guilherme

Revision history for this message
bugproxy (bugproxy) wrote : iSCSI install logs

Default Comment by Bridge

tags: added: architecture-ppc64le bugnameltc-135434 severity-high targetmilestone-inin14044
Changed in ubuntu:
assignee: nobody → Taco Screen team (taco-screen-team)
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1540995/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
Steve Langasek (vorlon)
affects: ubuntu → partman-iscsi (Ubuntu)
Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

Work is in progress to land these fixes; I'll update here once the relevant packages have landed in the development release for testing, before we land things in 14.04. Sorry, things won't update automatically for this case, I forgot to add the bug tags for the devel uploads.

Changed in hw-detect (Ubuntu):
status: New → Triaged
Changed in open-iscsi (Ubuntu):
status: New → Triaged
Changed in partman-iscsi (Ubuntu):
assignee: Taco Screen team (taco-screen-team) → Mathieu Trudel-Lapierre (mathieu-tl)
status: New → Triaged
Changed in hw-detect (Ubuntu):
importance: Undecided → High
Changed in open-iscsi (Ubuntu):
importance: Undecided → High
Changed in partman-iscsi (Ubuntu):
importance: Undecided → High
Changed in open-iscsi (Ubuntu):
assignee: nobody → Mathieu Trudel-Lapierre (mathieu-tl)
Changed in hw-detect (Ubuntu):
assignee: nobody → Mathieu Trudel-Lapierre (mathieu-tl)
status: Triaged → In Progress
Changed in open-iscsi (Ubuntu):
status: Triaged → In Progress
Changed in partman-iscsi (Ubuntu):
status: Triaged → In Progress
Changed in hw-detect (Ubuntu Trusty):
status: New → Triaged
Changed in open-iscsi (Ubuntu Trusty):
status: New → Triaged
Changed in partman-iscsi (Ubuntu Trusty):
status: New → Triaged
importance: Undecided → High
Changed in open-iscsi (Ubuntu Trusty):
importance: Undecided → High
Changed in hw-detect (Ubuntu Trusty):
importance: Undecided → High
assignee: nobody → Mathieu Trudel-Lapierre (mathieu-tl)
Changed in open-iscsi (Ubuntu Trusty):
assignee: nobody → Mathieu Trudel-Lapierre (mathieu-tl)
Changed in partman-iscsi (Ubuntu Trusty):
assignee: nobody → Mathieu Trudel-Lapierre (mathieu-tl)
Changed in hw-detect (Ubuntu):
status: In Progress → Fix Released
Changed in open-iscsi (Ubuntu):
status: In Progress → Fix Released
Changed in partman-iscsi (Ubuntu):
status: In Progress → Fix Released
Revision history for this message
bugproxy (bugproxy) wrote : Comment bridged from LTC Bugzilla

------- Comment From <email address hidden> 2016-04-13 13:58 EDT-------
.

Revision history for this message
bugproxy (bugproxy) wrote :

------- Comment From <email address hidden> 2016-05-05 02:54 EDT-------
Hello Ubuntu,

is their a way to qualify the fix released?

we picked up ISO from http://cdimage.ubuntu.com/releases/14.04/release/ which is of dated feb 18th and the issue still persists.

if the issue is fixed during March/April , from where should we pick up the installer fix?

Revision history for this message
bugproxy (bugproxy) wrote : iSCSI install logs

Default Comment by Bridge

Revision history for this message
Dimitri John Ledkov (xnox) wrote :

As per bug statuses as visible at:
https://bugs.launchpad.net/ubuntu/+source/partman-iscsi/+bug/1540995

The fixes for these three packages are fixed in xenial, but the fixes are not yet in trusty as per status information on launchpad. A bridge to bugzilla, does not correctly show per-package with per-series status of the bug report.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.