I have a thread going reference the NFS permission issue. Going to move all my replies into that since it is not a direct issue with the hosted engine.
Thanks for your replies. ________________________________ From: Yedidyah Bar David <d...@redhat.com> Sent: Tuesday, December 10, 2019 1:46 AM To: Robert Webb <rw...@ropeguru.com> Cc: Nate Revo <nr...@redhat.com>; users@ovirt.org <users@ovirt.org> Subject: Re: [ovirt-users] Re: Issue deploying self hosted engine on new install On Mon, Dec 9, 2019 at 3:06 PM Robert Webb <rw...@ropeguru.com> wrote: > > Nate, > > > > Thanks for the tip, but the NAS is Debian based. > > > > > > Is it potentially an SELinux denial? I seem to recall an SELinux Boolean > that needs to be set on the nfs server. You might want to check audit log on both nfs server and your host. What error do you get in vdsm.log? > > > > On Sun, Dec 8, 2019, 4:00 PM Robert Webb <rw...@ropeguru.com> wrote: > > Didi, > > Apologies for the delayed reply. > > I tracked the issue down after giving up on the self hosted install. I > installed it to a VM running CentOS 7 running on another platform and then > added my hosts. > > After adding the hosts and dploying a VM on oVirt, everything deployed > perfectly, I could never get the VM to start. Digging further, I found that > it is apparently a NFS permission on my NAS. What is odd is that I can add > the Storage domain with no issues, I can create a VM, but the VM will never > start due to a permission issue on the disk image. > > On my NAS if I just go into the shared folder permissions and not change > anything but just tell it to apply configured permissions to all files and > folders, the newly created VM runs just fine. For some reason when oVirt > creates new files in storage, it is leaving off the execute for the vdsm > user. I also notice that for the image and lease files, it also leaves off > any permisson for "other" . NOt sure why the permissions are not being > applied correctly. But that is an issue for me to figure out on my NAS, > OpenMediaVault. > > drwxrwsrwx+ 2 vdsm kvm 4096 Dec 7 23:53 . > drwxrwsrwx+ 8 vdsm kvm 4096 Dec 7 23:13 .. > -rw-rw----+ 1 vdsm kvm 53687091200 Dec 7 23:13 > 0605d785-f4df-49b1-af27-1f035148921c > -rw-rw----+ 1 vdsm kvm 1048576 Dec 7 23:13 > 0605d785-f4df-49b1-af27-1f035148921c.lease > -rw-rw-rw-+ 1 vdsm kvm 251 Dec 7 23:53 > 0605d785-f4df-49b1-af27-1f035148921c.meta > _______________________________________________ > Users mailing list -- users@ovirt.org > To unsubscribe send an email to users-le...@ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/FQGIOYW36MWWWDS3UBSQV5QKC3BNGZDS/ > > _______________________________________________ > Users mailing list -- users@ovirt.org > To unsubscribe send an email to users-le...@ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/TBHWVVP67DDLFMAN3WMHG3BYYNLU2DOU/ -- Didi
_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/UZNQ55KY4UOFUKCM6QUSIHED2WEFXCWS/
