[Bug 1924794] Re: Getting error "ipconfig: no devices to configure" while trying to autoinstall in a VLAN env on s390x

Frank Heimes 1924794 at bugs.launchpad.net
Mon Apr 19 05:53:50 UTC 2021


I just did an autoinstall attempt with having removed all config
snippets from the parm-file that are required for the VLAN:

--------%<----------------%<----------------%<----------------%<----------------%<--------
A manual update of the initial RAM-disk is required.
QETH device 0.0.c000:0.0.c001:0.0.c002 configured
Note: The initial RAM-disk must be updated for these changes to take effect:
- QETH device 0.0.c000:0.0.c001:0.0.c002
IP-Config: encc000 hardware address 12:34:45:67:89:0a mtu 1500
IP-Config: encc000 guessed broadcast address 10.123.124.255
IP-Config: encc000 complete:
address: 10.123.124.14    broadcast: 10.123.124.255   netmask: 255.255.255.0
 
gateway: 10.123.124.1     dns0     : 10.123.124.1     dns1   : 0.0.0.0
 
host   : hostname
rootserver: 0.0.0.0 rootpath:
filename  :
Connecting to install-server:80 (installer-server:80)

BusyBox v1.30.1 (Ubuntu 1:1.30.1-6ubuntu2) built-in shell (ash)
Enter 'help' for a list of built-in commands.
 
(initramfs) [6nwget: can't connect to remote host (install-server): Connection timed
out
Unable to find a live file system on the network
--------%<----------------%<----------------%<----------------%<----------------%<--------

and now the device c000 and the interface encc000 get activated:

encc000: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq qlen 1000
link/ether 26:e4:7c:23:c1:c9 brd ff:ff:ff:ff:ff:ff
inet 10.245.236.14/24 brd 10.245.236.255 scope global encc000
valid_lft forever preferred_lft forever
inet6 fe80::24e4:7cff:fe23:c1c9/64 scope link
valid_lft forever preferred_lft forever

The installation can of course not be completed in this case (since the
VLAN config is now missing), but it shows that this is only a problem
with handling potential VLAN config in the early boot stage (casper?).

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

Title:
  Getting error "ipconfig: no devices to configure" while trying to
  autoinstall in a VLAN env on s390x

Status in subiquity:
  New
Status in Ubuntu on IBM z Systems:
  New
Status in casper package in Ubuntu:
  New

Bug description:
  Trying to autoinstall on a LPAR (that is connected to a VLAN
  environment) and using the 21.04 image from today (time stamp April
  16th) fails and to boot ends up with the following error message:

  
  BusyBox v1.30.1 (Ubuntu 1:1.30.1-6ubuntu2) built-in shell (ash)
  Enter 'help' for a list of built-in commands.
   
  (initramfs) [6n
  ip: SIOCGIFFLAGS: No such device
  ip: can't find device 'encc000'
  ipconfig: encc000.2653: SIOCGIFINDEX: No such device
  ipconfig: no devices to configure
  ipconfig: encc000.2653: SIOCGIFINDEX: No such device
  ipconfig: no devices to configure
  ipconfig: encc000.2653: SIOCGIFINDEX: No such device
  ipconfig: no devices to configure
  ipconfig: encc000.2653: SIOCGIFINDEX: No such device
  ipconfig: no devices to configure
  ipconfig: encc000.2653: SIOCGIFINDEX: No such device
  ipconfig: no devices to configure
  ipconfig: encc000.2653: SIOCGIFINDEX: No such device
  ipconfig: no devices to configure
  ipconfig: encc000.2653: SIOCGIFINDEX: No such device
  ipconfig: no devices to configure
  ipconfig: encc000.2653: SIOCGIFINDEX: No such device
  ipconfig: no devices to configure
  ipconfig: encc000.2653: SIOCGIFINDEX: No such device
  ipconfig: no devices to configure
  ipconfig: encc000.2653: SIOCGIFINDEX: No such device
  ipconfig: no devices to configure
  no search or nameservers found in /run/net-encc000.2653.conf /run/net-*.conf /ru
  n/net6-*.conf
  Connecting to installserver:80 (installserver:80)
  wget: can't connect to remote host (installserver): Network is unreachable
  Unable to find a live file system on the network

  So the network device encc000 and it related encc000.2653 is not
  automatically activated/enabled like it was in the past.

  It worked in the past with the same config I used today 
  ip=10.245.236.14::10.245.236.1:255.255.255.0:hostname:encc000.2653:none:10.245.236.1 vlan=encc000.2653:encc000 url=http://installserver:80/ubuntu-live-server-21.04/hirsute-live-server-s390x.iso autoinstall ds=nocloud-net;s=http://installserver:80/autoinstall/hostname/ --- quiet

  With "worked in the past" I mean it's already a while ago when I tried
  it last time - right now it does not seem to work with 21.04 and
  20.04.2 - BUT only on this particular environment where I have to
  specify the VLAN as kernel arg ("parm-file").

  It works in a different non VLAN environments (for example in a z/VM
  guest environment where I do NOT have to specify the VLAN at the
  autoistall config, since the VLAN is handled there by the z/VM
  vSwitch).

  Doing an interactive installation on this particular LPAR (incl.
  specifying the VLAN id) works fine!

To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/1924794/+subscriptions



More information about the foundations-bugs mailing list