----- 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?
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.
For now, unless you care about this, just remove and install 1.7.
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.
Adding Oved: are we going to use 1.7 or 1.8 on EL6/EL7 ?
On Fedora we only have 1.8 so there we can't enforce 1.7.
Maybe we can use a config file enforcing the java home on EL6/7 as we do with JBoss.
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at