cloud-init's only interaction with ureadahead is in its postinst [1] where it disables ureadahead per bug 499520.
curtin has no interaction with ureadahead. ureadahead gets invoked via dpkg triggers. I'm not exactly sure what it triggers off of. likely one of the packages installed or updated triggered that. -- [1] https://git.launchpad.net/cloud-init/tree/debian/cloud-init.postinst?h=ubuntu/devel ** No longer affects: cloud-init (Ubuntu) ** No longer affects: curtin -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ureadahead in Ubuntu. https://bugs.launchpad.net/bugs/1643838 Title: ureadahead trying to read entire filesystem Status in MAAS: Invalid Status in ureadahead package in Ubuntu: New Bug description: MAAS Version 2.1.1+bzr5544-0ubuntu1 (16.04.1), deploying Ubuntu 16.04.1 As shown in bug 1635560 and specifically in https://pastebin.canonical.com/171385/ during deployment, ureadahead (sometimes?) tries to index the whole filesystem, complaining about all of the relative paths. These are the log messages immediately before the spamminess: Nov 22 08:32:32 faraday systemd[1]: Starting Stop ureadahead data collection... Nov 22 08:32:32 faraday systemd[1]: Stopping Read required files in advance... Nov 22 08:32:32 faraday systemd[1]: Started Stop ureadahead data collection. The ureadahead lines are responsible for the vast majority of the installation log ⟫ cat faraday-installation-log | wc -l 78777 ⟫ grep ureadahead faraday-installation-log | wc -l 76799 To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1643838/+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
