Installation over VLAN Interface Trunk Port not possible netcfg/vlan_id= paramter in parmfile not recognize implementation in installer not done

[bugproxy]

Hi
VLAN Trunk Port installation is not working see bugzilla 433568
The VLAN Trunk Port interface will recognize as a regular OSA interface for installation and not as Vlan Trunk Port interface
parmfile
ro locale=C cio_ignore=all,!f500-f502,!af06-af07 DEBCONF_DEBUG=5 s390-netdevice/qeth/port=0 netcfg/get_gateway=10.203.0.1 netcfg/get_nameservers=10.203.1.1 netdevice/qeth/layer2=true netcfg/confirm_static=true netcfg/vlan_id=203 netcfg/disable_dhcp=true netcfg/get_ipaddress=i10.203.60.2 netcfg/get_netmask=255.255.0.0 netcfg/get_hostname=s35lp02 netcfg/get_domain=boeblingen.de.ibm.com network-console/password=xxxx network-console/password-again=xxxx

add additionally parmfile for syslog file

ro locale=C cio_ignore=all,!b300-b302,!af06-af07 DEBCONF_DEBUG=5 s390-netdevice/qeth/port=0 netcfg/get_gateway=10.203.0.1 netcfg/get_nameservers=10.203.1.1 netdevice/qeth/layer2=true netcfg/confirm_static=true netcfg/vlan_id=203 netcfg/disable_dhcp=true netcfg/get_ipaddress=10.203.60.2 netcfg/get_netmask=255.255.0.0 netcfg/get_hostname=s35lp02 netcfg/get_domain=boeblingen.de.ibm.com network-console/password=xxxx network-console/password-again=xxxx

[bugproxy (bugproxy)]

Default Comment by Bridge

[bugproxy (bugproxy)]

Default Comment by Bridge

[Dimitri John Ledkov (xnox)]

VLAN support is brand new, which only just landed for the release. I am managing to successfully complete vlan based installs, but I'm yet to confirm if those propagate all the way to the installed system. From release notes point of view, this has never yet been supported, thus is not a regression. However we should fix it to start working, such that with 16.04.1 we can claim vlan trunk port support.

Looking at your pressed keys, I don't see:
netcfg/use_vlan=true

which should be there in addition to: netcfg/vlan_id=203

Regards,

Dimitri.

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2016-04-22 02:56 EDT-------
Hi Dimitri
add netcfg/use_vlan=true parameter to parmfile result is the same I have attached to bugzilla
new parmfile and syslog
Helmut

[bugproxy (bugproxy)]

------- Comment (attachment only) From <email address hidden> 2016-04-22 02:58 EDT-------

[Dimitri John Ledkov (xnox)]

Hi,

Could you please try the 455 installer from yakkety-proposed at http://ports.ubuntu.com/ubuntu-ports/dists/yakkety-proposed/main/installer-s390x/20101020ubuntu455/images/generic/ ?

That one has fixes and e.g. just specifying "netcfg/vlan_id=2654" in the paramfile does the right thing throughout. And installed system comes up with vlan networking too.

Also when submitting installer syslog, please submit the full one /var/log/installer/syslog (from installed system) or /var/log/syslog from the still running d-i. The syslogs attached to the bug report are incomplete, and e.g. are missing the kernel messages from early boot.

Successful vlan install, in brief:

May 13 11:03:55 kernel: [ 0.830924] Kernel command line: netcfg/vlan_id=2654
May 13 11:04:15 main-menu[217]: INFO: Menu item 'netcfg' selected
May 13 11:04:15 netcfg[256]: INFO: Starting netcfg v.1.135ubuntu6
May 13 11:04:15 netcfg[256]: DEBUG: Flushing addresses and routes on interface: encc000
May 13 11:04:15 netcfg[256]: INFO: Could not find valid BOOTIF= entry in /proc/cmdline
May 13 11:04:15 netcfg[256]: INFO: Taking down interface encc000
May 13 11:05:18 netcfg[256]: INFO: Taking down interface lo
May 13 11:05:18 netcfg[256]: INFO: Taking down interface lo
May 13 11:05:18 netcfg[256]: INFO: Activating interface encc000
May 13 11:05:18 netcfg[256]: INFO: Activating interface encc000.2654
May 13 11:05:18 netcfg[256]: INFO: executing: ip addr add 10.245.237.7/24 broadcast 10.245.237.255 dev encc000.2654
May 13 11:05:18 netcfg[256]: INFO: Waiting time set to 3
May 13 11:05:18 netcfg[256]: INFO: ethtool-lite: encc000.2654: carrier up
May 13 11:05:18 netcfg[256]: INFO: Found link on encc000.2654
May 13 11:05:18 netcfg[256]: ARPING to 10.245.237.1 from 10.245.237.7 via encc000.2654
May 13 11:05:18 netcfg[256]: Unicast reply from 10.245.237.1 [40:a8:f0:20:29:ad] 0.386ms
May 13 11:05:18 netcfg[256]: Sent 1 probe(s) (1 broadcast(s))
May 13 11:05:18 netcfg[256]: Received 1 replies (0 request(s), 0 broadcast(s))
May 13 11:05:18 netcfg[256]: INFO: Gateway reachable on encc000.2654
May 13 11:05:18 netcfg[256]: DEBUG: Getting default hostname from rDNS lookup of static-configured address 10.245.237.7
May 13 11:05:18 netcfg[256]: DEBUG: getnameinfo() returned -2 (Name or service not known)
May 13 11:05:25 netcfg[256]: DEBUG: No interface given; clearing /etc/network/interfaces
May 13 11:05:25 netcfg[256]: DEBUG: Writing informative header
May 13 11:05:25 netcfg[256]: DEBUG: Success!
May 13 11:05:25 netcfg[256]: DEBUG: Writing loopback interface
May 13 11:05:25 netcfg[256]: DEBUG: Success!
May 13 11:05:25 netcfg[256]: DEBUG: Writing static IPv4 stanza for encc000.2654
May 13 11:05:25 netcfg[256]: DEBUG: Writing VLAN: encc000.2654
May 13 11:05:25 netcfg[256]: DEBUG: Success!
May 13 11:18:17 finish-install: info: Running /usr/lib/finish-install.d/55netcfg-copy-config

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2016-05-28 13:50 EDT-------
We would like to retest the bug with 16.04.01 if this is OK. As strategy we would like to keep 16.04 bugs not to be mixed as verification on other release 16.10. Is this OK?

[Dimitri John Ledkov (xnox)]

@ Kate

All bugs must be fixed in development release first, before stable release update is release. This is to ensure that people upgrading to development release, or future stable release do not see regressions.

In Launchpad bug tracking we track bugs per package and series. And same bug # is used for both development release fix, and stable release update. This bug is "fix released" in the development series (yakkety), and "fix committed" in (xenial). See statuses at https://bugs.launchpad.net/ubuntu/xenial/+source/netcfg/+bug/1573077

There are multiple bug reports about vlan functionality. However, this bug report should be fixed as part of https://launchpad.net/bugs/1567687 and https://launchpad.net/bugs/1572607 SRU.

Which for xenial are available as part of the https://launchpad.net/ubuntu/+source/debian-installer/20101020ubuntu451.1 build, and thus from - http://ports.ubuntu.com/dists/xenial-proposed/main/installer-s390x/20101020ubuntu451.1/images/

Note the /xenial-proposed/ path. Once the update is validated, it will be released into /xenial-updates/ pocket, and the xenial daily isos.

Please test http://ports.ubuntu.com/dists/xenial-proposed/main/installer-s390x/20101020ubuntu451.1/images/ for xenial VLAN and DHCP fixes in netcfg.

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2016-07-14 11:04 EDT-------
Helmut Grauer 2016-07-14 06:52:18 EDT :
====

Hi,
sorry for the late testing.
I download the installer files from http://ports.ubuntu.com/dists/xenial-proposed/main/installer-s390x/20101020ubuntu451.1/images/
configure Parmfile with the related information
see
ro locale=C cio_ignore=all,!b300-b302,!af39 DEBCONF_DEBUG=5 s390-netdevice/choose_networktype=qeth s390-netdevice/qeth/choose=0.0.b300-0.0.b301-0.0.b302 s390-netdevice/qeth/port=0 s390-netdevice/qeth/layer2=true netcfg/use_autoconfig=false netcfg/disable_dhcp=true netcfg/get_ipaddress=10.203.60.18 netcfg/get_netmask=255.255.0.0 netcfg/get_gateway=10.203.0.1 netcfg/get_nameservers= netcfg/get_hostname=s35lp18 netcfg/get_domain=boeblingen.de.ibm.com network-console/password=xxxx network-console/password-again=xxxx netcfg/vlan_id=203
and start installation. Installation over ssh

I have two observation

after Load from removable media
I got ti selcet the network interface see
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:
1: enP1s23: Unknown interface [*], 4: ens22: Unknown interface,
2: enP1s23d1: Unknown interface, 5: ens22d1: Unknown interface,
3: encb300: Unknown interface,
Prompt: '?' for help, default=1>
3
Detecting link on encb300.203; please wait...
Generating SSH host key
Continue installation remotely using SSH

my base interface will be shown as unknown interface , when I select the base interface Vlan interface will define correctly. Do I something wrong in parmfile ?

Second Observation
The installation panel shows only the IPV6 address for ssh connection not the ipv4 I have specified in parmfile

start SSH
To continue the installation, please use an SSH client to connect to the IP
address fe80::ff:fedc:5463 10.203.60.18 fe80::ff:fedc:5463 and log in as the
"installer" user. For example:
ssh installer@fe80::ff:fedc:5463
The fingerprint of this SSH server's host key is:
SHA256:vC4Mi/ILiNKNZr6dgbamCjOMKkGspbSFxm5yZn183fE
Please check this carefully against the fingerprint reported by your SSH
client.
[Press enter to continue]
<
Select your location

I could connect via ssh over the IPV4 address but this should normally shown in installer

Greetings Helmut

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2016-08-03 10:18 EDT-------
(comment #24)
> Hi
> install over VLAN with the latest installer files 20101020ubuntu451.4,
> installation was possible and successfully.
> Helmiut