* zfs services fail on firstboot if zfs-utils is integrated into the deployment image.
* Output from systemd -
sudo systemctl --failed
UNIT LOAD ACTIVE SUB DESCRIPTION
● zfs-import-scan.service loaded failed failed Import ZFS pools by device scanning
● zfs-mount.service loaded failed failed Mount ZFS filesystems
* This is particularly frustrating for users who use automated monitoring as it means virtual machines must always be restarted before showing as clean.
* This failure is due to zfs services starting up before /etc/mtab has a chance to be symlinked to /proc/mounts.
[Test Case]
1. Grab a stock xenial image, and unpack it and add zfs-utils to it. Repack it.
2. Boot machine
3. Check systemctl --failed.
[Regression Potential]
*
[Other Info]
* This can likely be resolved in the systemd init scripts, by modifying zfs-linux to depend on /proc/mounts instead, or inclusion of /lib/init/mount-functions.sh in initscripts (sysvinit).
[Impact]
* zfs services fail on firstboot if zfs-utils is integrated into the deployment image.
* Output from systemd - scan.service loaded failed failed Import ZFS pools by device scanning
sudo systemctl --failed
UNIT LOAD ACTIVE SUB DESCRIPTION
● zfs-import-
● zfs-mount.service loaded failed failed Mount ZFS filesystems
* This is particularly frustrating for users who use automated monitoring as it means virtual machines must always be restarted before showing as clean.
* This failure is due to zfs services starting up before /etc/mtab has a chance to be symlinked to /proc/mounts.
[Test Case]
1. Grab a stock xenial image, and unpack it and add zfs-utils to it. Repack it.
2. Boot machine
3. Check systemctl --failed.
[Regression Potential]
*
[Other Info]
* This can likely be resolved in the systemd init scripts, by modifying zfs-linux to depend on /proc/mounts instead, or inclusion of /lib/init/ mount-functions .sh in initscripts (sysvinit).