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

[Frank Heimes]

Yes, this behavior is quite consistent - and it happens on different systems that require vlan configurations (tested on two systems - each several times - happened every time).
I may try on another or more systems - maybe under less load conditions ...

Well, I'm not sure if looking back to groovy is enough, I have to admit
that I mainly used autoinstall on focal, and tried it here and there on
other releases too, but then w/o vlan for just doing a quick test (I
should have taken more time for tests with vlan though).

One of the two systems that I used for the test is the same I used
before with autoinstall (and vlan), and the environment didn't really
changed - so I'm sure that it's not due to changes in the hw, setup or
environment itself. (On the 2nd system autoinstall was used for the 1st
time).

The z system got moved a few month ago to a different data center, but
that didn't changed anything internally with the OSA network adapters,
their ports or configuration - there might have been changes in the
external network (different switches etc.), but that shouldn't have such
an impact. And btw. doing a manual/interactive installation (incl. vlan)
works fine - and that is what I do very often - on all releases.

And yes, the test with just dropping the vlan config is interesting.
That make me think that it must have to do with the vlan config and
setup itself. Well, maybe a race - but that race got for some reason
introduced at some point in time ...

-- 
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 initramfs-tools:
  New
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/initramfs-tools/+bug/1924794/+subscriptions