fail to activate fcp device for installation

Please provide installer logs, and the installer version that was in use. E.g. /var/log/syslog from the d-i environment, or /var/log/installer directory from the installed system.

Sorry about the attachment delay. We are experiencing bridge issues, so the mirror is currently broken.

------- Comment From <email address hidden> 2016-06-28 12:31 EDT-------
(In reply to comment #21)
> Please provide installer logs, and the installer version that was in use.
> E.g. /var/log/syslog from the d-i environment, or /var/log/installer
> directory from the installed system.

I would love to, but we seem to have experienced some bridge hiccups today, so the attachments were not passed over, and I have no idea what LP bug number was assigned to the mirror. Please document the LP number, and I'll manually attach the data.

Thanks.

Hello,

After filing a bug report you can search for it on launchpad by arch tag:
E.g. https://bugs.launchpad.net/ubuntu/+bugs?field.tag=architecture-s39064

There is always internal bug number as tag, e.g. to find this bug using LTC-142843:
https://bugs.launchpad.net/ubuntu/+bugs?field.tag=bugnameltc-142843

The attachments seemed to have come through now.

Regards,

Dimitri.

From the logs:

After all the devices are added, and there is no pressed, and 0.0.19fd device is selected the s390-zfcp component bombs out:

Jun 20 08:39:17 s390-zfcp[5708]: DEBUG: DETECT: Added FCP device: 0.0.19fd: online=0 npiv=0
Jun 20 08:39:17 s390-zfcp[5708]: DEBUG: DETECT: Automatic LUN scanning is enabled
Jun 20 08:39:17 s390-zfcp[5708]: DEBUG: PRESEED: No preseed data available
Jun 20 08:39:18 s390-zfcp[5708]: DEBUG: SELECT: Using FCP device 0.0.1800
Jun 20 08:39:18 main-menu[346]: WARNING **: Configuring 's390-zfcp' failed with error code 139
Jun 20 08:39:18 main-menu[346]: WARNING **: Menu item 's390-zfcp' failed.
Jun 20 08:39:18 kernel: [ 220.868144] User process fault: interruption code 0038 ilc:3 in libc.so.6[3ffa2200000+185000]
Jun 20 08:39:18 kernel: [ 220.868153] failing address: 2c302e302e313000 TEID: 2c302e302e313800
Jun 20 08:39:18 kernel: [ 220.868155] Fault in primary space mode while using user ASCE.
Jun 20 08:39:18 kernel: [ 220.868157] AS:00000001eeebc1c7 R3:0000000000000024
Jun 20 08:39:18 kernel: [ 220.868161] CPU: 1 PID: 5708 Comm: zfcp-config Tainted: G E 4.4.0-21-generic #37-Ubuntu
Jun 20 08:39:18 kernel: [ 220.868162] task: 00000001f197d780 ti: 00000001f0d58000 task.ti: 00000001f0d58000
Jun 20 08:39:18 kernel: [ 220.868163] User PSW : 0705200180000000 000003ffa223a5d4
Jun 20 08:39:18 kernel: [ 220.868165] R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 AS:0 CC:2 PM:0 EA:3
Jun 20 08:39:18 kernel: [ 220.868165] User GPRS: 0000000000000000 000003ff0000004c 000003ffa234efc0 000003ffa2352370
Jun 20 08:39:18 kernel: [ 220.868166] 000003ffa2352352 2e302e313961392c 000003ffd2e7de48 000003ffa234efc2
Jun 20 08:39:18 kernel: [ 220.868167] 0000000000000010 0000000000000012 000003ff00004c49 2c302e302e313961
Jun 20 08:39:18 kernel: [ 220.868168] 000003ffa2389000 000003ffd2e7ed38 000003ffa2278eaa 000003ffd2e7dad0
Jun 20 08:39:18 kernel: [ 220.868177] User Code: 000003ffa223a5c6: 41d0d008 la %r13,8(%r13)
Jun 20 08:39:18 kernel: [ 220.868177] 000003ffa223a5ca: e3b0d0000002 ltg %r11,0(%r13)
Jun 20 08:39:18 kernel: [ 220.868177] #000003ffa223a5d0: a784ffe2 brc 8,3ffa223a594
Jun 20 08:39:18 kernel: [ 220.868177] >000003ffa223a5d4: e310b0000095 llh %r1,0(%r11)
Jun 20 08:39:18 kernel: [ 220.868177] 000003ffa223a5da: eca1fff66076 crj %r10,%r1,6,3ffa223a5c6
Jun 20 08:39:18 kernel: [ 220.868177] 000003ffa223a5e0: b9040048 lgr %r4,%r8
Jun 20 08:39:18 kernel: [ 220.868177] 000003ffa223a5e4: b9040037 lgr %r3,%r7
Jun 20 08:39:18 kernel: [ 220.868177] 000003ffa223a5e8: 4120b002 la %r2,2(%r11)
Jun 20 08:39:18 kernel: [ 220.868187] Last Breaking-Event-Address:
Jun 20 08:39:18 kernel: [ 220.868189] [<000003ffa223a5c2>] 0x3ffa223a5c2
Jun 20 08:39:23 main-menu[346]: INFO: Modifying debconf priority limit from 'high' to 'medium'
Jun 20 08:39:23 debconf: Setting debconf/priority to medium

Can you try to use cio_ignore during installation, and does that mitigate this bug?

Specifically, can you use cio_ignore such that maximum number of visible FCP devices is no more than 100?

Could you please notify Hendrik Brueckner about this bug report?

From zfcp-config.c:

/* Debconf related definitions */
#define TEMPLATE_PREFIX "s390-zfcp/"
#define DEBCONF_CAPS "backup"
#define PRESEED_DELIM ","
#define SCSI_ASYNC_TRIES 15
#define SCSI_ASYNC_TIMEOUT 250000 /* useconds */
#define MAX_HOST_LIST_ITEMS 100
#define MAX_HOST_LIST_SIZE (MAX_HOST_LIST_ITEMS * (9 + 20 +1))
#define MAX_LUN_LIST_SIZE 2048

Default Comment by Bridge

------- Comment From <email address hidden> 2016-06-29 10:48 EDT-------
Limiting the number of available devices to those that are required (<100) would be a work around. I work on patch to dynamically allocate memory for detected FCP devices. This would then be equivalent to those patches in s390-netdevice and s390-dasd.

Thanks and kind regards,
Hendrik

------- Comment From <email address hidden> 2016-07-04 06:08 EDT-------
Patch solution has been submitted to Debian bug tracker:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829562

This bug was fixed in the package s390-zfcp - 1.0.4ubuntu1

---------------
s390-zfcp (1.0.4ubuntu1) yakkety; urgency=low

  * Merge from Debian unstable LP: #1596968. Remaining changes:
    - Run update-dev, to trigger device addition and hence loading of the
    zfcp module. Previously this was only loaded after hw/disk-detect
    which is too late, as this package step is already done at that point.

s390-zfcp (1.0.4) unstable; urgency=medium

  [ Hendrik Brueckner ]
  * Improve displaying numereous detected FCP devices by replacing the
    hard-coded limit with a dynamically allocated solution (Closes: #829562)

s390-zfcp (1.0.3) unstable; urgency=medium

  * Drop useless debian/po directory. Closes: #817206, #821173

 -- Dimitri John Ledkov <email address hidden> Mon, 25 Jul 2016 17:13:55 +0000

------- Comment From <email address hidden> 2016-12-14 08:22 EDT-------
Changed target to 16.04.2 after discussion with Canonical

Hello bugproxy, or anyone else affected,

Accepted s390-zfcp into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/s390-zfcp/1.0.2ubuntu1.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Please perform installation using "apt-setup/proposed=true" in the param file and confirm that installation on an LPAR with 100+ zfcp devices visible is now possible.

I have performed installation on our LPARs without regressions using 1.0.2ubuntu1.1 s390-zfcp package from proposed. However, the mainframe I am performing this test on has insufficient amount of zfcp devices to trigger the originally reported bug.

The verification of the Stable Release Update for s390-zfcp has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

This bug was fixed in the package s390-zfcp - 1.0.2ubuntu1.1

---------------
s390-zfcp (1.0.2ubuntu1.1) xenial; urgency=medium

  [ Hendrik Brueckner ]
  * Improve displaying numereous detected FCP devices by replacing the
    hard-coded limit with a dynamically allocated solution LP: #1596968

 -- Dimitri John Ledkov <email address hidden> Wed, 14 Dec 2016 14:03:20 +0000