Cloning this to 3.6 ELP. This impacts upgrades for any 3.6 customers and we are asking for smooth upgrade experience. +++ This bug was initially created as a clone of Bug #1580319 +++ Description of problem: With latest 3.6.13, can't reach the engine web APIs. server.log: 2018-05-21 12:15:17,210 INFO [org.quartz.core.JobRunShell] (DefaultQuartzScheduler_Worker-16) Job DEFAULT.org.ovirt.engine.core.bll.tasks.CommandExecutor.invokeCallbackMethods#-9223372036854775787 threw a JobExecutionException: : org.quartz.JobExecutionException: failed to execute job at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source) [:1.8.0_121] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_121] at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_121] at org.ovirt.engine.core.utils.timer.JobWrapper.invokeMethod(JobWrapper.java:81) [scheduler.jar:] at org.ovirt.engine.core.utils.timer.JobWrapper.execute(JobWrapper.java:52) [scheduler.jar:] at org.quartz.core.JobRunShell.run(JobRunShell.java:213) [quartz.jar:] at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:557) [quartz.jar:] Version-Release number of selected component (if applicable): [root@jenkins-vm-03 ~]# rpm -q rhevm rhevm-3.6.13.1-0.1.el6.noarch [root@jenkins-vm-03 ~]# cat /etc/redhat-release Red Hat Enterprise Linux Server release 6.9 (Santiago) How reproducible: 1/1 Actual results: Web APIs don't function, we get 404 http error Additional info: httpd and ovirt-engine are running: [root@jenkins-vm-03 ~]# service httpd status httpd (pid 2077) is running... [root@jenkins-vm-03 ~]# service ovirt-engine status ovirt-engine (pid 13255) is running... The setup is alive, please contact me for its details
missing qe_ack.
(In reply to Eyal Edri from comment #2) > missing qe_ack.
ok, rhevm-3.6.12.4-0.1.el6.noarch tested with rhevm-shell and it works fine
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://access.redhat.com/errata/RHEA-2018:2647
sync2jira