[Bug 1635024] Re: Manual Z LPAR installation blocked at ssh with vlan

[Dimitri John Ledkov]

** Changed in: netcfg (Ubuntu)
   Importance: Undecided => High

** Changed in: netcfg (Ubuntu)
     Assignee: (unassigned) => Dimitri John Ledkov (xnox)

** Changed in: netcfg (Ubuntu)
    Milestone: None => later

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

Title:
  Manual Z LPAR installation blocked at ssh with vlan

Status in netcfg package in Ubuntu:
  Confirmed

Bug description:
  An ssh connection to installer@<IP>, after starting a manually driven install of Yakkety to a Z LPAR, can not continue as described to the user in the interactive console window output because ssh connections are not possible. When attempting to connect an ssh client will give the error message:
  ssh: connect to host <IP> port 22: No route to host

  In this scenario the system to be installed is on a vlan. The default
  installer files are used, as downloaded from
  http://us.ports.ubuntu.com/ubuntu-ports/dists/yakkety/main/installer-
  s390x/current/images/generic/. That is, parmfile.ubuntu is empty, so
  all installer configuration values must be entered through the
  interact menu that is presented once the installation kernel and
  initrd are loaded.

  To avoid this issue parmfile.ubuntu can have one of the following entires added:
  1. netcfg/vlan_id=<ID> (e.g. netcfg/vlan_id=2642) which will set the vlan configuration in the installers network config.
  2. "priority=medium" which will tell debconf to ask additional questions, which have their priority set to medium (i.e. high is the default). In this case the user is required to answer a number of additional questions among which are two related to installing when a vlan is in use.

  Although the above work around can be used this bug is being opened
  because the user experience is not great in this scenario. The Yakkety
  release notes do not mention special steps are required for vlan
  installation. Therefore, it's time consuming to come to a solution.
  Ideally I think the priority of the 'Is this system connected to a
  VLAN trunk port' and the follow on 'VLAN ID' questions should be
  raised to high, so the user has the opportunity to answer.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netcfg/+bug/1635024/+subscriptions