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 Bugs, which is subscribed to 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 To manage notifications about this bug go to: https://bugs.launchpad.net/initramfs-tools/+bug/1924794/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
