----- Original Message ----- > From: "John Joseph" <jjk_s...@yahoo.com> > To: users@ovirt.org > Sent: Tuesday, May 5, 2015 2:12:46 PM > Subject: Re: [ovirt-users] [ ERROR ] Execution of setup failed , message > shown at the end of installation > > > > > > > On Tuesday, 5 May 2015 3:30 PM, Simone Tiraboschi <stira...@redhat.com> > wrote: > > > > > I have attached the log files and conf file setup, for reference. > > Your error is: > RequestError: > status: 400 > reason: Bad Request > detail: Permission settings on the specified path do not allow access to the > storage. > Verify permission settings on the specified storage path. > > Please check permission and ownership on /home/itsupport/images > It should be owned and writable by vdsm:kvm > Than try again. > ---- > > Hi Simone, > > > Thansk for the advice > Again I did a system clean up > > by doing > > > # engine-cleanup > # yum remove ovirt-engine > # yum install ovirt-engine > # yum install ovirt-engine-setup-plugin-allinone > > checked for the permission in for images and exports dir > [root@server itsupport]# pwd > /home/itsupport > [root@server itsupport]# ls -l > total 8 > drwxr-xr-x. 3 vdsm kvm 4096 May 5 07:54 exports > drwxr-xr-x. 2 vdsm kvm 4096 May 5 07:55 images > > did "engine-setup" > Selected all the parametes, but this time also I got the same error > [ ERROR ] Execution of setup failed > > I have attached the log files and conf file setup, for reference. > > Now prior to the engine setup, we did cross check the owenership permissions > of exports and images dir. > Guidance and advice requested > Thanks
I saw that you got the same error: RequestError: status: 400 reason: Bad Request detail: Permission settings on the specified path do not allow access to the storage. Verify permission settings on the specified storage path. 2015-05-05 07:56:52 ERROR otopi.context context._executeMethod:161 Failed to execute stage 'Closing up': status: 400 reason: Bad Request detail: Permission settings on the specified path do not allow access to the storage. Verify permission settings on the specified storage path. The problem probably lies in not having eXecute permission for vdsm on /home/itsupport. In order for any user to traverse, not necessarily look into a directory, that user must have execute permission either via a group or via a direct permission. Please ensure that vdsm user could effectively write there before trying again. You can check it with: # sudo -u vdsm touch /home/itsupport/images/wtest > Joseph John> Now this time also when I create a Virtual Machine image, the > fields are > > greyed out and in the bottom it says " Not available when no Data Center is > > up" > > > > Guidance and advice requested > > thanks > > > > Joseph John > > _______________________________________________ > > Users mailing list > > Users@ovirt.org > > http://lists.ovirt.org/mailman/listinfo/users > > > > > _______________________________________________ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
