Booting a system installed on an iSCSI LUN with an additional network interface is not possible

Bug #1689309 reported by bugproxy
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu on IBM z Systems
Fix Released
Medium
Unassigned
debian-installer (Ubuntu)
Won't Fix
Undecided
Unassigned
netcfg (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

Installer version: 20101020ubuntu451.10

Description/Reproduction:

System is installed with the following partitioning:
/boot on DASD
/ on an iSCSI LUN

Network:
1 OSA with VLAN as the regular network device for the system
2 OSAs with VLAN used for iSCSI. Those two OSAs were configured manually in a command shell during installation

After installation, the system is not bootable and the console is displaying the following error every second:
"iscsistart: cannot make a connection to 10.209.9.1:3260 (-1,101)"

bugproxy (bugproxy)
tags: added: architecture-s39064 bugnameltc-154051 severity-medium targetmilestone-inin---
Changed in ubuntu:
assignee: nobody → Skipper Bug Screeners (skipper-screen-team)
affects: ubuntu → debian-installer (Ubuntu)
bugproxy (bugproxy)
tags: added: targetmilestone-inin16042
removed: targetmilestone-inin---
Revision history for this message
Dimitri John Ledkov (xnox) wrote :

When you brought up the networking manually, did you write out the updated /etc/network/interfaces and updated the target initramfs? By e.g. dropping back into shell at finish install step.

Because the installed system's /etc/network/interfaces will only have the netcfg configured network (the first one), but not any other networks brought up with ifup command.

Could you please extract and attache
1) the initramfs from the /boot DASD
2) /etc/network/interfaces from the / iSCSI LUN
3) /var/log/installer from the / iSCSI LUN

Changed in debian-installer (Ubuntu):
status: New → Incomplete
Revision history for this message
bugproxy (bugproxy) wrote : Comment bridged from LTC Bugzilla

------- Comment From <email address hidden> 2017-05-11 06:18 EDT-------
> When you brought up the networking manually, did you write out the updated
> /etc/network/interfaces and updated the target initramfs? By e.g. dropping
> back into shell at finish install step.

> Because the installed system's /etc/network/interfaces will only have the
> netcfg configured network (the first one), but not any other networks
> brought up with ifup command.

I edited the file /etc/network/interfaces but I wasn't able to update the initramfs because I don't know which tool to use for that. I was looking for update-initramfs but it doesn't seem to be installed.
I would appreciate if you could point me to the tool to use.

> Could you please extract and attache
> 1) the initramfs from the /boot DASD

Are you talking about the file "initrd.img-4.4.0-77-generic"?

> 2) /etc/network/interfaces from the / iSCSI LUN
> 3) /var/log/installer from the / iSCSI LUN

I will attach those files.

Revision history for this message
bugproxy (bugproxy) wrote :

------- Comment From <email address hidden> 2017-05-11 06:24 EDT-------
Sorry the file is larger than 10 MB and in case mirroring doesn't work, here's a link to the same file:
https://testcase.software.ibm.com/fromibm/linux/installer_logs_interfaces.tar

You can login as "anonymous" to download the file

Revision history for this message
bugproxy (bugproxy) wrote : Installer log folder and interfaces file

------- Comment (attachment only) From <email address hidden> 2017-05-11 06:19 EDT-------

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

from the interactive shell of d-i, one should be able to do:

$ in-target update-initramfs -k all

To update initramfs, that essentially does: `chroot /target update-initramfs -k all`, but with extra logging and clean-up such that those commands end up in logs.

Downloaded the logs. Will inspect them.

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

And when I mean editing the /etc/network/interfaces, I mean /target/etc/network/interfaces at the end of the installation once netcfg purged and recreated it. Such that the installed system has correct interfaces.

Looking at the interfaces from the logs, it only has one vlan defined. Thus ence530.209 is missing from /target/etc/network/interfaces which needs to be adjusted when installer offers to "finish & reboot", by going back to the main menu and dropping into the shell, editing that file, and updating initramfs in-target.

Revision history for this message
bugproxy (bugproxy) wrote : Comment bridged from LTC Bugzilla

------- Comment From <email address hidden> 2017-05-11 07:46 EDT-------
(In reply to comment #10)
> And when I mean editing the /etc/network/interfaces, I mean
> /target/etc/network/interfaces at the end of the installation once netcfg
> purged and recreated it. Such that the installed system has correct
> interfaces.
>
> Looking at the interfaces from the logs, it only has one vlan defined. Thus
> ence530.209 is missing from /target/etc/network/interfaces which needs to be
> adjusted when installer offers to "finish & reboot", by going back to the
> main menu and dropping into the shell, editing that file, and updating
> initramfs in-target.

Thank you for your hints. When "Finish and reboot" was displayed, I edited the /target/etc/network/interfaces file and afterwards executed "in-target update-initramfs -k all".

The system still doesn't boot although the interfaces are now listed in the "interfaces" file. I have uploaded the logs again.

https://testcase.software.ibm.com/fromibm/linux/logfiles_2nd_try.tar

Frank Heimes (fheimes)
Changed in ubuntu-z-systems:
importance: Undecided → Medium
status: New → Triaged
Changed in debian-installer (Ubuntu):
assignee: Skipper Bug Screeners (skipper-screen-team) → nobody
Revision history for this message
bugproxy (bugproxy) wrote :

------- Comment From <email address hidden> 2018-04-17 03:57 EDT-------
Canonical, any update on this LP ?

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

d-i only supports configuring only one network connection. This is unlikely to change, even for the 20.04 timeframe. The workarounds are 1) getting install media exported on the same network as the network attached hard drives 2) configuring additional network interfaces by-hand using d-i interactive shell.

bugproxy (bugproxy)
tags: added: targetmilestone-inin---
removed: targetmilestone-inin16042
Frank Heimes (fheimes)
tags: added: installer
Revision history for this message
Frank Heimes (fheimes) wrote :

Setting to 'In Progress' with the work on subiquity.

Changed in ubuntu-z-systems:
status: Triaged → In Progress
Revision history for this message
Dimitri John Ledkov (xnox) wrote :

The new installer is now out, and supports configuring many networks at the same time.

Changed in netcfg (Ubuntu):
status: New → Won't Fix
Changed in debian-installer (Ubuntu):
status: Incomplete → Won't Fix
Changed in ubuntu-z-systems:
status: In Progress → Fix Released
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.