if I'm not wrong, this is not strictly java 8 issue. There are also java 7 versions behaving like this (jboss did not start on fresh install, peaking cpu usage) m. ----- Original Message -----
----- Original Message -----
From: "knarra" <knarra@redhat.com> To: devel@ovirt.org Cc: "Stanislav Graf" <sgraf@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. -- Didi _______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel