Adding a priority "high" task against zfs-linux since this is a post-FF regression in expected behavior from a tool in main.
Consider this as coming from me as a release team member and TB member rather than LXD upstream. My preference here is that rather than just breaking every single script and tools that create zfs pools today on clean systems, the "zpool" utility should be patched to automatically load the "zfs" kernel module if not already loaded. With my upstream LXD hat on, we will modify LXD itself to attempt to load the zfs module on first use, if only to cope with other distros that may use this non-optimal behavior. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1672749 Title: Please don't assume zfs module is always loaded Status in lxd package in Ubuntu: Triaged Status in zfs-linux package in Ubuntu: Triaged Bug description: Since zfsutils-linux/0.6.5.9-4, zfs module is not automatically loaded on systems that no zpool exists, this avoids tainting everyone's kernel who has the package installed but is not using zfs. ADT test of lxd (at least at 2.11-0ubuntu4[1]) shows the storage tests are failing because "Could not determine ZFS module version." which is printed by zfsModuleVersionGet() in lxd/storage_zfs.go. This indicates there are pieces of code assuming zfs kernel module is always loaded which turns out to be not true anymore. [1] https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-zesty/zesty/amd64/l/lxd/20170314_120059_2ce5b@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1672749/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
