Network does not come up after installing bionic daily (2018-03-21) on s390x

[Frank Heimes]

After installing bionic daily from 2018-03-21 (in either LPAR or on z/VM - KVM not tried yet) the network does not come up after the post install reboot.

$ ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group defaul
t qlen 1000
    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

$ cat /etc/netplan/01-netcfg.yaml
# This file describes the network interfaces available on your system
# For more information, see netplan(5).
network:
  version: 2
  renderer: networkd
  ethernets:
    encc000:
      dhcp4: no
      dhcp6: no
  vlans:
    encc000.2653:
      link: encc000
      id: 2653
      addresses: [ 10.245.236.11/24 ]
      gateway4: 10.245.236.1
      nameservers:
          search: [ canonical.com ]
          addresses:
              - 10.245.236.1

See attachment for dmesg output ...

[Frank Heimes (fheimes)]

In addition such messages are shows during bootup:

...   ¬K¬   ¬0;31m* ¬0;1;31m* ¬0m ¬0;31m*  ¬0m| A start job is running for Wait for     to be Configured (40s / no limit)  ¬K¬    ¬0;31m* ¬0;1;31m* ¬0m ¬0;31m* ¬0m|  A start job is running for Wait for    to be Configured (41s / no limit)  ¬K¬      ¬0;31m* ¬0;1;31m* ¬0m| A start job is running for Wait for    to be Configured  (41s / no limit)  ¬K¬      ¬0;31m* ¬0m| A start job is running for Wait for     to be Configured (42s / no limit)  ¬K¬     ¬0;31m* ¬0;1;31m* ¬0m| A start job is  running for Wait for    to be Configured (42s / no limit)  ¬K¬    ¬0;31m* ¬0;1; 31m* ¬0m ¬0;31m* ¬0m| A start job is running for Wait for    to be Configured (4 3s / no limit)  ¬K¬   ¬0;31m* ¬0;1;31m* ¬0m ¬0;31m*  ¬0m| A start job is running  for Wait for    to be Configured (43s / no limit)  ¬K¬  ¬0;31m* ¬0;1;31m* ¬0m ¬ 0;31m*   ¬0m| A start job is running for Wait for    to be Configured (44s / no  limit)  ¬K¬ ¬0;31m* ¬0;1;31m* ¬0m ¬0;31m*    ¬0m| A start job is running for Wai t for    to be Configured (44s / no limit)  ¬K¬ ¬0;1;31m* ¬0m ¬0;31m*     ¬0m| A  start job is running for Wait for    to be Configured (45s / no limit)  ¬K¬ ¬0m  ¬0;31m*      ¬0m| A start job is running for Wait for    to be Configured (45s  ...

[Frank Heimes (fheimes)]

Probably worth to mention that the udev rule file for the qeth device is missing on the installed system... (on both)

[Steve Langasek (vorlon)]

Not sure what's going on here yet but it must be in either netplan.io or systemd, so assigning to netplan.io initially.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Frank Heimes (fheimes)]

I marked LP 1757995 "[Ubuntu 18.04] No active network interface after installation" as a duplicate of this (1757369).

[Dimitri John Ledkov (xnox)]

It's a bug in s390-tools / s390-sysconfig-writer

[Dimitri John Ledkov (xnox)]

Looks like s390-tools, chzdev generates =n/a attributes, which later are not accepted by chzdev...

Adjusting s390-sysconfig-writer to adjust for that.

[Launchpad Janitor (janitor)]

This bug was fixed in the package s390-sysconfig-writer - 0.6ubuntu2

---------------
s390-sysconfig-writer (0.6ubuntu2) bionic; urgency=medium

  * Strip =n/a values from chzdev active configuration, before storing
    persistent one, as chzdev does not accept it. LP: #1757369

 -- Dimitri John Ledkov <email address hidden> Mon, 26 Mar 2018 17:44:49 +0100

[Frank Heimes (fheimes)]

Successfully verified with bionic daily image March 27th - thx xnox!