-
Notifications
You must be signed in to change notification settings - Fork 91
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ovirt_vm OVA import failing with "ovirtsdk4.NotFoundError: HTTP response code is 404." #590
Comments
Hi, what did not come to my mind is: |
I have an update for you. When checking the httpd logs on the manager I can see this when executing my playbook: When I access the same API URL through e.g. the RESTClient extension for Firefox I get this in the logs using the "OPTIONS" method:
or this when I use the "POST" method:
FYI: In both cases I am not send sending data with the request. And the ovirt-engine/server.log shows this exception:
So I am still not sure where this 404 comes from. Can you elaborate on how to use the module to import OVAs? Thanks, |
Hi,
|
I found the problem. |
SUMMARY
I have a playbook, that should import multiple OVAs through ovirt_vm.
but on import using url as per docs "ova:///path/to/image.ova" I run into the aforementioned error.
This feature seems rarely used as I cannot find examples on it, just other people having similar issues, without solutions...
I used this expample from the docs and adopted it to my needs:
COMPONENT NAME
ovirt.ovirt.ovirt_vm module
STEPS TO REPRODUCE
Place the OVA on the hypervisor in a locally mounted NFS share, do the authentication against the api and run the below snippet.
I did set a couple of parameters (cluster_name, vm_name, rhv_host (my hypervisor to import on), etc).
The variable "ova_to_use" has the full path to the OVA file on the hypervisor and the "SDName" holds the human readable name of the SD.
EXPECTED RESULTS
Starting OVA import
ACTUAL RESULTS
The text was updated successfully, but these errors were encountered: