Guess I was wrong about the ACL, in the end what made the difference was the fact that during the “forced” tests I used “/export/images” as image path in the storage configuration instead of “/images” (because of the missing “/export” lines in /etc/exports)
Here some screenshots with the working configuration I’m actually using:
OMV Shared folder configuration
OMV Shared folder ACL configuration
OMV NFS shares
FOG Storage configuration
The actual /etc/exports file on OMV:
# /etc/exports: the access control list for filesystems which may be exported
# to NFS clients. See exports(5).
# NFSv4 - pseudo filesystem root
Could be that NSFv4 pseudo fs to cause the problem? Maybe by giving to FOG the full path I somehow bypass it, just a random guess tho, I don’t know how NFS works apart from the basics.
This is so simple a problem, and actually well known about.
The issue is VirtualBox. It will only work on the initial load up of the System from a “cold” status. If you only restart the system, you will get this message because the VB resources aren’t releasing the NIC properly. It’s nothing I can fix. However, there is a way around it, but it is not a viable solution if your fog server is dealing with more than just VirtualBox hosts. The Fix, for Virtual Box at least, is to use the ipxe.pxe file rather than the undionly.kpxe file.