On 05/05/2015 09:15 AM, Yedidyah Bar David wrote:
----- Original Message -----
> From: "knarra" <knarra(a)redhat.com>
> To: devel(a)ovirt.org
> Cc: "Stanislav Graf" <sgraf(a)redhat.com>
> Sent: Tuesday, May 5, 2015 8:50:38 AM
> Subject: [ovirt-devel] ovirt-engine replies with 503 Service Temporarily Unavailable
on fresh install
>
>
> Hi,
>
> >From last Tuesday (Apr-28), I'm experiencing
> "ovirt-engine replies with 503 Service Temporarily Unavailable on fresh
> install"
https://bugzilla.redhat.com/show_bug.cgi?id=1217023 I tried to
> completely reinstall before filing BZ and the issue was reproducible. I also
> updated today my install with latest, still the same.
>
> Am I alone who is hit by this BZ? Anything I could try? Should I reinstall
> again tomorrow?
I saw something similar at my dev env and only after I drop-create my db
it was solved. if
I'll see it again I'll report on the bz.
The mentioned bug does not seem very relevant.
After checking with Kasturi, it seems that he is trying to run it with
java-1.8.0-openjdk on RHEL6.6.
EAP 6.4 supports jdk8, jboss-as-7.1.1 doesn't(will fail to load)
For now, unless you care about this, just remove and install 1.7.
fair, but I don't think is related to the DB problem he is seeing.
Until the situation with 1.8 stabilizes, we might want to do
something, not
sure exactly what - perhaps change the script java-home to not accept 1.8
for now (and people that want to test that will have to override by having there
a trivial java-home.local pointing at their 1.8 home), or make engine-setup
notice and prompt, whatever.
for overriding jdk use :
OVIRT_ENGINE_JAVA_HOME=/path/to/jdk/home
OVIRT_ENGINE_JAVA_HOME_FORCE=1