On Mon, Oct 12, 2020 at 9:33 PM Amit Bawer <abawer(a)redhat.com> wrote:
On Mon, Oct 12, 2020 at 9:12 PM Lee Hanel <lee.hanel(a)gmail.com> wrote:
> my /etc/exports looks like:
>
>
(rw,async,no_wdelay,crossmnt,insecure,no_root_squash,insecure_locks,sec=sys,anonuid=1025,anongid=100)
>
The anongid,anonuid options could be failing the qemu user access check,
Is there a special need to have them for the nfs shares for ovirt?
I'd suggest to specify the exports for ovirt on their own
/export/path1 *(rw,sync,no_root_suqash)
/export/path2 *(rw,sync,no_root_suqash)
mind the typo "squash":
/export/path2 *(rw,sync,no_root_squash)
...
> also to note, as vdsm I can create files/directories on the share.
>
>
> On Mon, Oct 12, 2020 at 12:34 PM Amit Bawer <abawer(a)redhat.com> wrote:
> >
> >
> >
> > On Mon, Oct 12, 2020 at 7:47 PM <lee.hanel(a)gmail.com> wrote:
> >>
> >> ok, I think that the selinux context might be wrong? but I saw
> nothing in the audit logs about it.
> >>
> >> drwxr-xr-x. 1 vdsm kvm system_u:object_r:nfs_t:s0 40 Oct 8 17:19 /data
> >>
> >> I don't see in the ovirt docs what the selinux context needs to be.
> Is what you shared as an example the correct setting?
> >
> > It's taken from a working nfs setup,
> > what is the /etc/exports (or equiv.) options settings on the server?
> >
> >> _______________________________________________
> >> Users mailing list -- users(a)ovirt.org
> >> To unsubscribe send an email to users-leave(a)ovirt.org
> >> Privacy Statement:
https://www.ovirt.org/privacy-policy.html
> >> oVirt Code of Conduct:
>
https://www.ovirt.org/community/about/community-guidelines/
> >> List Archives:
>
https://lists.ovirt.org/archives/list/users@ovirt.org/message/5OSGBFRHYC3...
>
>