A lower level error occurred while refreshing NFS exports: (Error running a command. cmd

Support
8

@jwoods Re:

I’ve been unable to reproduce the issue I thought may have been related thus far and have so far tested the following, setup via Web-UI, as the closest to yours from the information provided:

cat /etc/exports
/export/data 192.168.1.159/24(rw,async,insecure)
/export/ovirt 192.168.1.159/24(rw,async,insecure)
/export/isos 192.168.1.159/24(ro,async,insecure)  192.168.1.130(rw,no_root_squash)

Where the last entry was from:
admin-host-example

with the consequent relevant mounts created of:

mount | grep 'data\|ovirt\|isos'
...
/dev/sdb on /mnt2/data type btrfs (rw,relatime,space_cache,subvolid=310,subvol=/data)
/dev/sdb on /mnt2/isos type btrfs (rw,relatime,space_cache,subvolid=309,subvol=/isos)
...
/dev/sdb on /mnt2/ovirt type btrfs (rw,relatime,space_cache,subvolid=311,subvol=/ovirt)
/dev/sdb on /export/data type btrfs (rw,relatime,space_cache,subvolid=310,subvol=/data)
/dev/sdb on /export/ovirt type btrfs (rw,relatime,space_cache,subvolid=311,subvol=/ovirt)
/dev/sdb on /export/isos type btrfs (rw,relatime,space_cache,subvolid=309,subvol=/isos)

And this arrangement then persisted post reboot.

So we are still looking for a simple reproducer of your observed issue of NFS mounts not persisting reboot as the closest I can replicate here from your last exports file info looks to be working OK. I think we need more log entries if possible to see if their is a reported reason for the NFS bootstrap stuff to be failing.