Hi,
I want to upload a vApp template on vCD through vCO's vCD plugin.
There is out-of-box workflow available for the same.
For executing the workflow we need to provide the file path of the OVF and I have OVF on orchestrator server at path /home/ovf/DB_OVF09.ovf.
I get following error while executing the workflow.
java.io.FileNotFoundException: /home/ovf/DB_OVF09.ovf (Permission denied) (Dynamic Script Module name : uploadVappTemplateVdc#7)
Is there any setting that needs to be done? How to handle this error?
I have linux based vCO with version 5.1, and vCD is also with version 5.1.
Regards,
Shubhada
did you update the js-io-rights.conf file to allow vCO access to that local folder?? That file must be updated and the service restarted in order for vCO to have access to the local filesystem. VMware KB: Creating and locating the js-io-rights.conf file on the vCenter Orchestrator Appliance
Hi,
I modified the js-io-rights.conf file by adding following line:
+rwx /home/ovf/DB_OVF09.ovf
I am getting the following error now,
java.io.FileNotFoundException: /home/ovf/DB_OVF09.ovf (No such file or directory) (Dynamic Script Module name : uploadVappTemplateVdc#7)
Regards,
Shubhada
I also tried to add following line,
+rwx /home/ovf
But facing same issue. How can I overcome this problem?
Regards,
Shubhada
Could you check the owner and the group of /home/ovf/DB_OVF09.ovf. Also check the file permissions
I see it is in /home folder it is possible that vCO does not have permission to read this file.
As far as I remember vCO is running under vco user in Appliance.
Good point... I always forget to point that out
Earlier it was like
-rwxrwxrwx 1 root root 6855 Sep 19 07:41 LiferayDB_OVF9.ovf
I changed it to :
-rwxrwxrwx 1 vco vco 6855 Sep 19 07:41 LiferayDB_OVF9.ovf
Facing the same issue..
Check also the permissions of the parent folders /home/ovf
Silly question, but I have to ask - has the vCO Server service been restarted since the permissions changes (conf file and/or chown)?
The parent directory's owner is vco and group is vco.
I also restart the service after changes.
I had this same issue. This is how I fixed it:
While in the main directory do a "chmod -R 2710 'folder'". This adds the "d" at the beginning of the permission. I'm not a Linux person so I don't even know what that is. But, it fixed the permissions issue.