fun with ovirt ansible
by Fedor Gavrilov
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 following:
- ovirt_auth:
url: "{{engine_url}}"
username: "{{engine_user}}"
password: "{{engine_password}}"
state: present
insecure: true
and the inventory file is very straightforward as well, just a bunch of vars:
[local:vars]
engine_url=https://apple/ovirt-engine/api
engine_user=admin@internal
engine_password=engine
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, apparently:
2019-08-16 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
2019-08-16 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 https://10-37-137-185.rhev.lab.eng.brq.redhat.com/ovirt-engine/api everthing runs fine.
So I guess it's engine messing up the URL after all?
Fedor
5 years, 3 months
Fwd: [CentOS-devel] SIG Content to remove for the 7.7.1908 release
by Sandro Bonazzola
FYI.
---------- Forwarded message ---------
Da: Johnny Hughes <johnny(a)centos.org>
Date: ven 16 ago 2019 alle ore 03:49
Subject: [CentOS-devel] SIG Content to remove for the 7.7.1908 release
To: CentOS-Devel <centos-devel(a)centos.org>
For all the c7 SIGs, if you have content that you want removed (to make
inactive) when we create the new 7.7.1908 tree, please let me know here
what needs to be removed.
If all files in a specific directory can be removed, you can just list
the directory.
You will also obviously need to make any changes to your
centos-release-* files to remove those file locations from your repos.
After we release 7.7.1908 .. we will copy over the SIG directories prune
the SIG content. The http://mirror.centos.org/centos/7/<repo>/ paths
will then be shifted to the new 7.7.1908 tree.
I expect that some time early next week we will release the CR content
.. with the full release coming 7 to 14 days after that .. so full
release likely some time between 29 August to 6 September 2019.
If you don't tell us to remove content, we will move everything over as is.
Thanks,
Johnny Hughes
_______________________________________________
CentOS-devel mailing list
CentOS-devel(a)centos.org
https://lists.centos.org/mailman/listinfo/centos-devel
--
Sandro Bonazzola
MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
Red Hat EMEA <https://www.redhat.com/>
sbonazzo(a)redhat.com
<https://www.redhat.com/>*Red Hat respects your work life balance.
Therefore there is no need to answer this email out of your office hours.
<https://mojo.redhat.com/docs/DOC-1199578>*
5 years, 3 months