Answering my own question; and maybe a very obvious cause for the
failing provider: the missing provider plugin in forman!
So one needs to do:
yum install ruby193-rubygem-ovirt_provision_plugin
on the foreman host.
After that, the connection test in the engine comes up positive. Sadly,
this is not documented anywhere; only on the GitHub repo readme [1].
This is also a little bit outdated, as the rbovirt dependency is
resolved now automatically.
Also, but I am not sure, the porvider lugin needs the foreman_discovery
plugin to work:
yum install ruby193-rubygem-foreman_discovery
[1]
https://github.com/theforeman/ovirt_provision_plugin/blob/master/README.md
On 29.10.2014 00:36, Daniel Helgenberger wrote:
Hello,
did anyone actually get this working in oVirt 3.5 / EL6 - Engine? I am
trying this for two days now.
Setup:
Engine; EL6.5
Foreman; EL6.5
Foreman seems to do it's as I can use it to deploy hosts and also smart
proxies are running fine.
I have opened a BZ [1]; because this really can not work out of the box
with EL6 plain vanilla packages. I wonder if this was ever tested... ?
Java 7 used i n EL6 [4] does only support DH keys up to 1024byte. This
is known issue in Foreman [2] as longer DH keys are now used by default
in Foreman / PuppetCA.
A dirty fix confirmed working is adding default DH parameters to the
foreman cert; effectively disabling it [3].
So I got SSL working and I get beyond the authentication (entering wrong
data gets me auth errors)- however, I am still not able to add the
external provider. Pressing 'test' results in
(Failed with error PROVIDER_FAILURE and code 5050)
Sample engine.log
2014-10-28 23:49:40,860 ERROR
[org.ovirt.engine.core.bll.provider.TestProviderConnectivityCommand]
(ajp--127.0.0.1-8702-1) [6a3da4e7] Command
org.ovirt.engine.core.bll.provider.TestProviderConnectivityCommand throw
Vdc Bll exception. With error message VdcBLLException: PROVIDER_FAILURE
(Failed with error PROVIDER_FAILURE and code 5050)
I can't find any more hints in oVirt; access logs in Foreman are telling
me API queries by the engine. Did I miss a crucial step in the foreman
setup? How can I debug this issue?
I am willing to upgrade openjdk; provided this does not break my engine...
Thanks!
[1]
https://bugzilla.redhat.com/show_bug.cgi?id=1157749
[2]
https://tickets.puppetlabs.com/browse/SERVER-17
[3]
http://httpd.apache.org/docs/current/ssl/ssl_faq.html#javadh
[4] java-1.7.0-openjdk-1.7.0.65-2.5.1.2.el6_5.x86_64
--
Daniel Helgenberger
m box bewegtbild GmbH
P: +49/30/2408781-22
F: +49/30/2408781-10
ACKERSTR. 19
D-10115 BERLIN
www.m-box.de www.monkeymen.tv
Geschäftsführer: Martin Retschitzegger / Michaela Göllner
Handeslregister: Amtsgericht Charlottenburg / HRB 112767