+++ This bug was initially created as a clone of Bug #757818 +++
Description of problem:
Remove the workaround for zfs-fuse service being started in %post once that BZ is fixed.
--- Additional comment from mburns on 2011-11-28 17:21:50 EST ---
This is caused by zfs-fuse starting it's service in %post. There are 2 possible fixes:
1. blacklist zfs-fuse from the node
2. manually kill the service in %post of the image build
zfs-fuse is required by: libguestfs-1:1.14.2-1.fc16.x86_64
--- Additional comment from mburns on 2011-11-28 17:25:27 EST ---
Apply the following, then rerun build starting with autogen.sh
diff --git a/recipe/ovirt-node-image.ks.in b/recipe/ovirt-node-image.ks.in
index a24275c..b3d69a8 100644
@@ -25,3 +25,6 @@
+/sbin/service zfs-fuse stop
--- Additional comment from mburns on 2011-11-30 07:58:27 EST ---
Given the chance of a guest using ZFS, we should probably leave zfs-fuse on the node. I'll apply the above workaround and file a separate bz to remove the workaround once zfs-fuse gets fixed.
--- Additional comment from mburns on 2011-11-30 08:01:23 EST ---
Moving to 2.3.0.
zfs-fuse is currently in a transition between maintainers, so highly unlikely the related bz will be fixed before we release 2.2.0