The bug is also present in version 1.12.1

Jonas kirk Pedersen wrote:

The bug is also present in version 1.12.1 if you forget to add path like <ovirt-engine>/ovirt-engine/api/v3

Works with update and ovirt 4.0.1

Jonas kirk Pedersen wrote:

Jonas kirk Pedersen wrote:

The bug is also present in version 1.12.1 if you forget to add path like <ovirt-engine>/ovirt-engine/api/v3

Works with update and ovirt 4.0.1

Jonas,

how you fix the problem?

i have the same problems to create vm...

2016-08-01 14:41:00 [app] [W] Failed to create a compute Minc_Cloud (oVirt) instance ubuntu-ovirt-aval.minc.cloud.srv.produ: 404 Resource Not Found | | OVIRT::OvirtException: 404 Resource Not Found

my enviroments:
ovirt 4.0.2.1-1.el7.centos
the foreman 1.12.0

Clesio Santos wrote:

Jonas,

how you fix the problem?

i have the same problems to create vm...

2016-08-01 14:41:00 [app] [W] Failed to create a compute Minc_Cloud (oVirt) instance ubuntu-ovirt-aval.minc.cloud.srv.produ: 404 Resource Not Found | | OVIRT::OvirtException: 404 Resource Not Found

my enviroments:
ovirt 4.0.2.1-1.el7.centos
the foreman 1.12.0

Hello Clesio

I notice when trying to load the datacenters that the connection to the ovirt-engine worked and the certificate was updated. This was after updating foreman to 1.12.1 and ovirt to 4.0.1. Then 404 error pointing me to that URL was wrong and reading the comments to the bug #15560, I notice a new url for the API. So add ovirt-engine/api/v3 instead of the old way /api after FQDN. I have a clean install of foreman so creating a new vm that I have not tried but I can power manage and load clusters from ovirt

Not fixed here on an ypdated 1.12.2 release.

I was wrong, you really need:

ovirt-engine/api/v3

Without ovirt-engine it doesn't work and you get a good connection but 404 error.