Description of problem: After updating the ovirt-engine and running engine-setup, the web Manager cannot be accessed. ovirt-engine service is up and running, however, there are errors in the engine.log and service.log: service.log: ``` 2021-01-19 19:08:02,132+01 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "engine.ear")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.subunit.\"engine.ear\".\"bll.jar\".component.Backend.START" => "java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance Caused by: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance Caused by: javax.ejb.EJBException: org.jboss.weld.exceptions.UnsatisfiedResolutionException: WELD-001334: Unsatisfied dependencies for type VmMigrationProgressMonitoring with qualifiers @Any WELD-001474: Class org.ovirt.engine.core.vdsbroker.monitoring.VmMigrationProgressMonitoring is on the classpath, but was ignored because a class it references was not found: org.reactivestreams.Subscription from [Module \"deployment.engine.ear\" from Service Module Loader]. Caused by: org.jboss.weld.exceptions.UnsatisfiedResolutionException: WELD-001334: Unsatisfied dependencies for type VmMigrationProgressMonitoring with qualifiers @Any WELD-001474: Class org.ovirt.engine.core.vdsbroker.monitoring.VmMigrationProgressMonitoring is on the classpath, but was ignored because a class it references was not found: org.reactivestreams.Subscription from [Module \"deployment.engine.ear\" from Service Module Loader]. "}} ... 2021-01-19 19:08:02,283+01 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 19.1.0.Final (WildFly Core 11.1.1.Final) started (with errors) in 24633ms - Started 1648 of 1890 services (5 services failed or missing dependencies, 393 services are lazy, passive or on-demand) ``` engine.log: ``` 2021-01-19 19:08:02,028+01 ERROR [org.ovirt.engine.core.bll.Backend] (ServerService Thread Pool -- 50) [] Error during initialization: org.jboss.weld.exceptions.UnsatisfiedResolutionException: WELD-001334: Unsatisfied dependencies for type VmMigrationProgressMonitoring with qualifiers @Any WELD-001474: Class org.ovirt.engine.core.vdsbroker.monitoring.VmMigrationProgressMonitoring is on the classpath, but was ignored because a class it references was not found: org.reactivestreams.Subscription from [Module "deployment.engine.ear" from Service Module Loader]. ``` Version-Release number of selected component (if applicable): ovirt-engine-4.4.4-0.0.master.20201109161351.git5dac13e7e22.el8.noarch ovirt-engine-wildfly-19.1.0-2.el8.x86_64 firefox-82.0.2-1.fc31.x86_64 google-chrome-stable-87.0.4280.141-1.x86_64 How reproducible: Always Steps to Reproduce: 1. Update engine and run engine-setup successfully 2. Go to engine-fqdn 3. Actual results: Cannot load the Manager. Expected results: Manager is loaded successfully, welcome page is shown, user can login into WebAdmin, VMPortal,... Additional info:
Artur, can't it be related to https://gerrit.ovirt.org/c/ovirt-engine/+/112347 ?
Please check version of vdsm-jsonrpc-java being installed on the test environment. Based on the engine's git hash vdsm-jsonrpc-java must be in version < 1.6.0 because starting from 1.6.0 reactive stream support is dropped.
The version is: vdsm-jsonrpc-java-1.6.0-1.20201127100238.git15877ca.el8.noarch
That explains the issue. Please use vdsm-jsonrpc-java 1.5.x (1.5.7 is the latest) for any builds before the engine's patch [1] being merged. [1] https://gerrit.ovirt.org/c/ovirt-engine/+/112347
Yes, getting the older vdsm-jsonrpc-java package from the 4.4 repo instead of the master-snapshot repo fixed the issue for me. Thank you very much!
Then you should have added Conflicts: to vdsm-jsonrpc-java-1.6.0 blocking ovirt-engine versions older then the change requiring 1.6
(In reply to Michal Skrivanek from comment #8) > Then you should have added Conflicts: to vdsm-jsonrpc-java-1.6.0 blocking > ovirt-engine versions older then the change requiring 1.6 We can't do that, that would introduce circular dependency. Anyway users can get into the situation only when they don't follow upgrade guide (running only 'yum update' instead of full engine upgrade)
As agreed offline for future vdsm-jsonrpc-java version will be restricted to 1.6.x not allowing automatic update to 1.7.x which could contain breaking change. This approach should handle situation like the one described in this BZ.
Verified on ovirt-engine-4.4.5.6-0.0.master.20210211101802.giteb733a55fff.el8.noarch
This bugzilla is included in oVirt 4.4.5 release, published on March 18th 2021. Since the problem described in this bug report should be resolved in oVirt 4.4.5 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.