Verification performed in cosmic using the generic kernel (4.18.0-15.16) and the previous behaviour was preserved as expected.
We currently don't have a kernel in cosmic that enables that feature by default, but I built a custom kernel in order to test it and it worked as expected. In theory it was also possible to manually add the config variable, but the test kernel is as closest as we can get to the real use case. ** Tags removed: verification-needed verification-needed-cosmic ** Tags added: verification-done verification-done-cosmic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1814818 Title: Skip enslaved devices during boot Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Cosmic: Fix Committed Bug description: [Impact] In some scenarios, we need to skip enslaved network devices from being brought up in initrd. In order to avoid regressions for other users, the new behaviour is being conditioned to the configuration variable NETWORK_SKIP_ENSLAVED. This mechanism enable us to use it only for the required kernels. The target kernel should be responsible to include the configuration via an initramfs-tools hook. [Test Case] Enslaved network devices shouldn't be brought up when the configuration is set by certain kernels. For any other scenario, such as the generic Ubuntu kernel, the behaviour should not be changed. [Regression Potential] The potential for regressions was vastly reduced by conditioning the new behaviour. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1814818/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp