[Bug 1542389] Re: ubuntu-installer drops network connection when trying to configure a second network device

[Dimitri John Ledkov]

Installation guides are published at https://help.ubuntu.com/

And we have published an early pre-release draft for xenial (16.04)
there (follow 16.04 -> s390x).

https://help.ubuntu.com/16.04/installation-guide/s390x/index.html

There are some mentions of expert mode, but there are no explicit
warnings to "not use it".

In general, the guide guides one without using it. In general,
ubuntu/debian users/sysadmins do know about expert mode not being that
much more useful and asking too many pointless questions.

It is mentioned here https://help.ubuntu.com/16.04/installation-
guide/s390x/ch06s01.html: If your hardware requires you to pass options
to kernel modules as they are installed, you will need to start the
installer in “expert” mode. This can be done by either using the expert
command to start the installer or by adding the boot argument
priority=low. Expert mode gives you full control over debian-installer.

Not sure if that is sufficient.

I will close this bug report (w.r.t. installing with multiple networking
connection) as an invalid one / user support. And if more inquiries
w.r.t. expert mode arise, we may have to look into improving
documentation and/or in-installer wording.

** Changed in: debian-installer (Ubuntu)
       Status: Incomplete => Invalid

** Changed in: debian-installer (Ubuntu)
   Importance: Undecided => Low

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to debian-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1542389

Title:
  ubuntu-installer drops network connection when trying to configure a
  second network device

Status in debian-installer package in Ubuntu:
  Invalid

Bug description:
  == Comment: #0 - Thorsten Diehl <thorsten.diehl at de.ibm.com> - 2016-02-03 12:52:53 ==
  I IPLed a system (version 20101020ubuntu416), started the installer, configured a first network device with static IPv4 and connected via ssh to the installer.
  I chose "expert mode" and selected "Configure the network device" instead of continuing at "Choose language".
  I selected my second OSA device and accepted this configuration.
  Consequently I chose "Configure a network using static addressing" instead of continuing at the proposed "Choose language".
  And immediatedly this session wasn't reachable any more. A parallel ping to this session did stall at the moment, when I pressed "Configure a network using static addressing". Obviously this action dropped the default gateway - here the result when entereing a shell to debug the situation:
  ~ #>ip a s
  ip a s  
  1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue   
      link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00  
      inet 127.0.0.1/8 scope host lo  
         valid_lft forever preferred_lft forever  
      inet6 ::1/128 scope host   
         valid_lft forever preferred_lft forever  
  2: enccw0.0.f5f0: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast qlen 1000  
      link/ether 02:a2:0f:00:00:99 brd ff:ff:ff:ff:ff:ff  
      inet 9.152.162.103/22 brd 9.152.163.255 scope global enccw0.0.f5f0  
         valid_lft forever preferred_lft forever  
  3: enccw0.0.b1c6: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000  
      link/ether 02:00:00:5b:9f:69 brd ff:ff:ff:ff:ff:ff  
  ~ #>ip r l
  ip r l  
  ~ #>
  The network interfaces are both down, and thus all routes were lost!!
  When I bring up the first interface manually
  ip link set enccw0.0.f5f0 up
  and add the route and the default gw:
  ip route add 9.152.160.0/22 via 9.152.160.1
  ip route add default via 9.152.160.1
  I can continue with the IP configuration of the second network interface

  == Comment: #4 - Thorsten Diehl <thorsten.diehl at de.ibm.com> -
  2016-02-04 08:34:29 ==

  
  == Comment: #5 - Thorsten Diehl <thorsten.diehl at de.ibm.com> - 2016-02-04 08:36:21 ==
  I revived the first network interface as described above to get access to the system and to collect the data.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1542389/+subscriptions