So I've confirmed that the python3 side of this has been resolved.
zfsutils-linux as it is in yakkety right now has now been changed over
to python3 by Colin.
Though, as discussed by e-mail when Dustin first brought this up, there
is a second issue I think we should have resolved before we start
including the zfs tools by default on all Ubuntu 64bit server
installations.
That's the fact that zfs brings with it a daemon (zfs-zed) which will
start on all systems, regardless of their use of zfs. I'm not against us
running zed as it does seem to provide some value in background
monitoring of zfs pools, but I don't think we want all Ubuntu servers to
run that daemon when they're not using zfs themselves.
In containers, zed fails to start, but systemd attempts to respawn it
for about 10s, leading to a whole bunch of log messages, a unit startup
failure and quite a waste of CPU time.
I believe the zed systemd unit should at the very least be modified not to
start inside containers and should then be further modified to only start on
systems which have at least one zpool defined.
Subscribing Colin to this bug.
** Also affects: zfs-linux (Ubuntu)
Importance: Undecided
Status: New
--
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/1624540
Title:
please have lxd recommend zfs
Status in lxd package in Ubuntu:
Incomplete
Status in zfs-linux package in Ubuntu:
New
Bug description:
Since ZFS is now in Main (Bug #1532198), LXD should recommend the ZFS
userspace package, such that 'sudo lxd init' just works.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1624540/+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
