I've been trying to reproduce an issue when it was possible, using ansible, to create
an image in one dc with disk in another one.
Since adding validation to ImportRepoImage command turned out to not be enough, this time
I am trying to stick as close as possible to the original reproducer.
OS is CentOS 7, ansible-playbook is 2.8.4 (latest, that is)
I have this simplistic yml that references vars from the inventory file, like the
and the inventory file is very straightforward as well, just a bunch of vars:
However, as I run this against my engine, which is latest master, ansible is able to login
successfully and then fail with
"msg": "The response content type 'text/html;charset=UTF-8'
isn't the expected XML. Is the path '/ovirt-********/api' included in the
'url' parameter correct? The typical one is '/ovirt-engine/api'"
This ovirt-******* is very intriguing. I sniffed the traffic and here is what is done,
20:56:18 ::1 ::1 > POST apple:8080 /ovirt-engine/sso/oauth/token HTTP/1.1 - -
2019-08-16 20:56:18 ::1 ::1 < - - - HTTP/1.1 200 OK
20:56:18 ::1 ::1 > GET apple:8080 /ovirt-********/api/templates?search=name%3Dfc28-cloud-test HTTP/1.1 - -
2019-08-16 20:56:18 ::1 ::1 < - - - HTTP/1.1 404 Not Found
So it actually tries to reach /ovirt-********/api/templates?search=name%3Dfc28-cloud-test
and gets 404 page.
Once would think that something is wrong with ansible, but actually when I change engine
url in inventory file to
everthing runs fine.
So I guess it's engine messing up the URL after all?