Bug 1400619
| Summary: | [EAP] engine UI not accessible when using EAP 7.0.4 | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Dusan Fodor <dfodor> |
| Component: | ovirt-engine | Assignee: | Oved Ourfali <oourfali> |
| Status: | CLOSED ERRATA | QA Contact: | Lucie Leistnerova <lleistne> |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | unspecified | CC: | dfodor, eedri, fnasser, gklein, juan.hernandez, lsurette, mgoldboi, michal.skrivanek, mperina, nsednev, oourfali, pnovotny, rbalakri, Rhev-m-bugs, srevivo, vtunka, ykaul |
| Target Milestone: | ovirt-4.0.7 | Keywords: | Regression, ZStream |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-03-16 15:29:56 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | UX | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Comment 1
Juan Hernández
2016-12-01 16:29:19 UTC
(In reply to Juan Hernández from comment #1) > Dusan, what version of EAP are you using exactly? boot.log says: JBoss EAP 7.0.4.GA (WildFly Core 2.1.10.Final-redhat-1 This is a regression in EAP 7.0.4, everything works fine in EAP 7.0.3 So QE can continue testing release with EAP 7.0.3 from following repository: http://download.eng.brq.redhat.com/pub/rhel/devel/candidates/JBEAP/composing/JBEAP-7.0.3-RHEL-7-20161108.0/compose/Server/x86_64/os/ *** Bug 1401919 has been marked as a duplicate of this bug. *** tested EAP 7.4 eap7-wildfly-7.0.4-4.GA_redhat_2.1.ep7.el7.noarch verified in ovirt-engine-4.0.6.3-0.1.el7ev.noarch verified in ovirt-engine-4.0.7-0.1.el7ev.noarch - upgrade/clean install Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2017-0542.html |