> What is the rationale behind requesting a fix for trusty? How do you expect > it to get onto > an .iso? A customized iso?
Customers use the initrd provided in our archive, not just isos, e.g.: http://archive.ubuntu.com/ubuntu/dists/trusty-updates/main/installer- amd64/current/images/netboot/ubuntu-installer/amd64/initrd.gz And updated isos can be produced by debian-installer, e.g.: http://archive.ubuntu.com/ubuntu/dists/trusty-updates/main/installer- amd64/current/images/netboot/mini.iso So are you going to SRU this or should I? ** Changed in: debian-installer-utils (Ubuntu Trusty) Status: Won't Fix => In Progress ** Changed in: debian-installer (Ubuntu Trusty) Status: Won't Fix => In Progress ** Changed in: debian-installer (Ubuntu Zesty) Status: Won't Fix => In Progress -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1714505 Title: systemd kmod builtin uses out of date kmod context Status in systemd: Fix Released Status in debian-installer package in Ubuntu: Fix Released Status in debian-installer-utils package in Ubuntu: Fix Released Status in debian-installer source package in Trusty: In Progress Status in debian-installer-utils source package in Trusty: In Progress Status in debian-installer source package in Xenial: New Status in debian-installer-utils source package in Xenial: In Progress Status in debian-installer source package in Zesty: In Progress Status in debian-installer-utils source package in Zesty: In Progress Status in debian-installer source package in Artful: Fix Released Status in debian-installer-utils source package in Artful: Fix Released Bug description: [Impact] udev's rules use a built-in 'kmod' instead of the system modprobe/insmod, and this built-in kmod only validates/refreshes its kmod 'context' every 3 seconds (or longer) during event processing. However, because other parts of the system rely on udev to load modules correctly, it is not acceptable for it to use an out of date module context. For example, during a system installation: -the system boots with kernel and initrd with a reduced set of modules, not including nvme module -udevd starts, and creates its kmod module context, which does not include nvme module -system installer adds 'block-modules' udeb, which adds nvme module to system -system installer immediately calls hw-detect->update-dev->udevadm trigger -udevd sees its kmod module context is not more than 3 seconds old, and does not update it -udevd rule 80-drivers.rules finds NVMe pci modalias and asks kmod builtin to load matching driver -udevd kmod builtin does not find NVMe pci modalias because its context is out of date this results in the system installer complaining to the user that it found no disks, even though there is a NVMe drive in the system, and the nvme module is installed in the system. The fix is to reload udevadm rules, as per upstream recommendation. [Test Case] This is reproducable when trying to install using debian-installer and a preseed file that skips all questions, although not on all systems, since other events can cause udevd to reload all its builtins, or the installer may take longer than 3 seconds to call udevadm trigger after installing the nvme module udeb. Stale context in udevd is expected, and one is supposed to reload rules via udevadm, which is the fix proposed in debian-installer- utils. Removing the previous second test case that does not reload via udevadm. [Regression Potential] Additional calls to udevadm reload will cause all udev rules to be re- read correctly. This may lead to new devices discovered/configured/symlink during d-i installer, which were previously skipped/missed. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1714505/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : [email protected] Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
