Re: [ovirt-users] oVirt 4 + Foreman

2016-09-13 Thread Arsène Gschwind
Hi, Thanks, that was the problem, it works now. Regards, Arsène On 09/08/2016 06:16 PM, Karli Sjöberg wrote: Den 8 sep 2016 15:32 skrev Arsène Gschwind : > > Hi, > > Sorry for this late reply, i've been busy with some other projects in the last weeks. > > I did

Re: [ovirt-users] oVirt 4 + Foreman

2016-09-08 Thread Arsène Gschwind
Hi, Sorry for this late reply, i've been busy with some other projects in the last weeks. I did some log analysing and could find the following in the foreman log when trying to add foreman as an external provider for oVirt: 2016-09-08 15:20:03 [app] [I] Started GET "/api/v2" for

Re: [ovirt-users] oVirt 4 + Foreman

2016-08-22 Thread Oved Ourfali
Can you please attach the complete logs of ovirt and foreman? On Wed, Aug 17, 2016 at 10:25 AM, Martin Perina wrote: > Adding Yaniv ... > > On Wed, Aug 17, 2016 at 9:16 AM, Arsène Gschwind < > arsene.gschw...@unibas.ch> wrote: > >> Hi, >> >> Thanks a lot this did work on

Re: [ovirt-users] oVirt 4 + Foreman

2016-08-17 Thread Martin Perina
Adding Yaniv ... On Wed, Aug 17, 2016 at 9:16 AM, Arsène Gschwind wrote: > Hi, > > Thanks a lot this did work on the Foreman side using https:// > /ovirt-engine/api/v3 . > > But on the oVirt Side, to define Foreman as an external provider, it still > doesn't work, is

Re: [ovirt-users] oVirt 4 + Foreman

2016-08-17 Thread Arsène Gschwind
Hi, Thanks a lot this did work on the Foreman side using https:///ovirt-engine/api/v3 . But on the oVirt Side, to define Foreman as an external provider, it still doesn't work, is there also a special URL to enter? I didn't find anything in the docs. Thanks for any hint. Regards, Arsène

Re: [ovirt-users] oVirt 4 + Foreman

2016-08-16 Thread Juan Hernández
On 08/16/2016 11:58 AM, Arsène Gschwind wrote: > Hi, > > has anybody been able to configure Foreman with oVirt 4 ? When trying to > add Foreman as an external provider and test the login it always return > : Failed to communicate with the external provider, see log for > additional details. > >