Created attachment 1167416 [details] engine + server logs Description of problem: After attempting to create a pool with same name as an existing pool in the cluster and failing (as expected), trying to restart ovirt-engine will result in failure: 2016-06-13 11:47:27,593 ERROR [org.ovirt.engine.core.bll.CommandsFactory] (ServerService Thread Pool -- 60) [] Error in invocating CTOR of command 'AddVmPoolWithVms': null 2016-06-13 11:47:27,594 ERROR [org.ovirt.engine.core.bll.InitBackendServicesOnStartupBean] (ServerService Thread Pool -- 60) [] Failed to initialize backend: org.jboss.weld.exceptions.WeldException: WELD-000049: Unable to invoke private v oid org.ovirt.engine.core.bll.tasks.CommandCallbacksPoller.init() on org.ovirt.engine.core.bll.tasks.CommandCallbacksPoller@642601aa ............ (see full engine log attached) Need to remove the relevant entries from asyn_tasks and command_entities in order to restart engine properly again. Version-Release number of selected component (if applicable): rhevm-4.0.0.2-0.1.el7ev.noarch How reproducible: always Steps to Reproduce: 1. Create a vm pool with some name e.g. 'test'. 2. Attempt to create another pool with the same name 'test' - this will fail as expected. 3. Restart engine. Actual results: engine restarts successfully. Expected results: engine starts and is active but is in failed state: ● ovirt-engine.service - oVirt Engine Loaded: loaded (/usr/lib/systemd/system/ovirt-engine.service; enabled; vendor preset: disabled) Active: active (running) since Mon 2016-06-13 13:11:45 IDT; 1min 50s ago Main PID: 9399 (ovirt-engine.py) CGroup: /system.slice/ovirt-engine.service ├─9399 /usr/bin/python /usr/share/ovirt-engine/services/ovirt-engine/ovirt-engine.py --redirect-output --systemd=notify start └─9430 ovirt-engine -server -XX:+TieredCompilation -Xms1024M -Xmx1024M -Djava.awt.headless=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djsse.enableSNIExtension=false -XX:+HeapDumpOnO... Jun 13 13:11:42 slitmano-rhevm.scl.lab.tlv.redhat.com systemd[1]: ovirt-engine.service: main process exited, code=exited, status=1/FAILURE Jun 13 13:11:42 slitmano-rhevm.scl.lab.tlv.redhat.com systemd[1]: Unit ovirt-engine.service entered failed state. Jun 13 13:11:42 slitmano-rhevm.scl.lab.tlv.redhat.com systemd[1]: ovirt-engine.service failed. Jun 13 13:11:42 slitmano-rhevm.scl.lab.tlv.redhat.com systemd[1]: Starting oVirt Engine... Jun 13 13:11:45 slitmano-rhevm.scl.lab.tlv.redhat.com systemd[1]: Started oVirt Engine. In DB command_entities table has a command type 304 stuck with status: ENDED_WITH_FAILURE. Additional info:
This bug report has Keywords: Regression or TestBlocker. Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.
included in the last released build of ovirt-4.0.0-rc3
verified with rhevm-4.0.0.6-0.1.el7ev.noarch according to steps in description.
oVirt 4.0.0 has been released, closing current release.