Bug 1345986 - oVirt engine RESTAPI cannot be deployed on Fedora 23 due to fop 2.0
Summary: oVirt engine RESTAPI cannot be deployed on Fedora 23 due to fop 2.0
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: RestAPI
Version: 4.0.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: ovirt-4.0.0-rc
: 4.0.0
Assignee: Martin Perina
QA Contact: movciari
Depends On:
TreeView+ depends on / blocked
Reported: 2016-06-13 15:28 UTC by Martin Perina
Modified: 2016-07-05 07:56 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2016-07-05 07:56:55 UTC
oVirt Team: Infra
rule-engine: ovirt-4.0.0+
ykaul: blocker+
rule-engine: planning_ack+
mperina: devel_ack+
gklein: testing_ack+

Attachments (Terms of Use)
logs (382.53 KB, application/x-gzip)
2016-06-13 15:32 UTC, Martin Perina
no flags Details

System ID Private Priority Status Summary Last Updated
oVirt gerrit 59084 0 master MERGED packaging: Remove dependency on fop on F23+ 2016-06-14 17:46:33 UTC
oVirt gerrit 59184 0 ovirt-engine-4.0 MERGED packaging: Remove dependency on fop on F23+ 2016-06-15 05:31:18 UTC

Description Martin Perina 2016-06-13 15:28:08 UTC
Description of problem:

oVirt engine depends on fop 1.1, but on Fedora 23 there's available only fop 2.0, which has incompatible API. This causes RESTAPI unavailable after installation, because restapi.war cannot be loaded due to incompatible API between fop 1.1 and 2.0

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Install ovirt-engine on Fedora 23
2. Run engine-setup
3. Try to get list of datacenters using RESTAPI

Actual results:

HTTP 404 error is shown when accessing /ovirt-engine/api/datacenters

Expected results:

List of existing datacenters should be returned

Additional info:

Comment 1 Martin Perina 2016-06-13 15:32:01 UTC
Created attachment 1167545 [details]

Comment 2 Sandro Bonazzola 2016-07-05 07:56:55 UTC
oVirt 4.0.0 has been released, closing current release.

Note You need to log in before you can comment on or make changes to this bug.