Bug 1252745 - oVirt engine randomly fails to start due to unsatisfied dependencies
Summary: oVirt engine randomly fails to start due to unsatisfied dependencies
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-core
Version: 3.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 3.6.0
Assignee: Moti Asayag
QA Contact: Pavel Stehlik
URL:
Whiteboard: infra
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-12 08:02 UTC by Maor
Modified: 2016-02-10 19:30 UTC (History)
11 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-08-17 13:11:30 UTC
oVirt Team: Infra
Embargoed:


Attachments (Terms of Use)
server log which has the error (17.42 MB, text/plain)
2015-08-14 09:53 UTC, Maor
no flags Details
server (388.80 KB, text/plain)
2015-08-14 10:06 UTC, Maor
no flags Details
full server log (417.76 KB, text/plain)
2015-08-17 06:45 UTC, Maor
no flags Details

Description Maor 2015-08-12 08:02:30 UTC
Description of problem:
Trying to start a compiled environment of engine fails to start due to missing/unsatisfied dependencies (see [1])
After some tries it starts as expected.

JBAS018558: Undeployed "engine.ear" (runtime-name: "engine.ear")
2015-08-12 10:53:16,941 INFO  [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report
JBAS014775:    New missing/unsatisfied dependencies:
      service jboss.deployment.subunit."engine.ear"."bll.jar".component.Backend.CREATE (missing) dependents: [service jboss.deployment.subunit."engine.ear"."bll.jar".component.Backend.START] 
      service jboss.deployment.subunit."engine.ear"."bll.jar".component.Backend.START (missing) dependents: [service jboss.deployment.subunit."engine.ear"."bll.jar".component.InitBackendServicesOnStartupBean.START] 
      service jboss.deployment.subunit."engine.ear"."bll.jar".component.Backend.VIEW."org.ovirt.engine.core.bll.interfaces.BackendCommandObjectsHandler".LOCAL (missing) dependents: [service jboss.deployment.subunit."engine.ear"."bll.jar".component.Backend.START] 


Version-Release number of selected component (if applicable):
last commit id is 2e96b9b23aeeb37ca3724a062bb69faae7fb4934

How reproducible:
sometimes

Steps to Reproduce:
1. Start your engine
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Oved Ourfali 2015-08-13 09:25:53 UTC
Can you please attach logs of time when it happens?

Comment 2 Maor 2015-08-14 09:53:43 UTC
Created attachment 1062955 [details]
server log which has the error

Comment 3 Maor 2015-08-14 10:06:20 UTC
Created attachment 1062956 [details]
server

Comment 4 Alon Bar-Lev 2015-08-16 09:24:17 UTC
wildfly - I see - please try to use eap, there is no reason to use wildfly.

partial log so I cannot see if it is devenv or not.

Comment 5 Maor 2015-08-17 06:45:44 UTC
Created attachment 1063643 [details]
full server log

Comment 6 Maor 2015-08-17 06:51:05 UTC
I've added the full server log, this is a developer environment.
Why there is no reason to use wildfly? we already suggesting to use wildfly in the devel mailing list, so other contributes might encounter this problem as well

Comment 7 Alon Bar-Lev 2015-08-17 07:02:30 UTC
please do not open bugs for devenv, you have mail and proper contacts.

do you have the wildfly overlay in PREFIX/etc/ovirt-engine/engine.conf.d? see README.developer.

any reason you use wildfly and not eap for devenv?

Comment 8 Maor 2015-08-17 08:48:46 UTC
There is no special reason I use wildfly, basically it is a community jboss AS project which I prefer to use then EAP.
I followed the steps at this mail:
 http://lists.ovirt.org/pipermail/devel/2015-June/010832.html

I've also followed the README.developer file, and saw that the ovirt-nightly.repo contains ovirt-master-snapshot-static:

[ovirt-master-snapshot-static]
name=oVirt Master Static Test Releases
baseurl=http://resources.ovirt.org/pub/ovirt-master-snapshot-static/rpm/fc@$releasever/
enabled=1
skip_if_unavailable=1
gpgcheck=0

I've been trying to re-execute engine-setup once again, and for now I see that the engine has been able to start without any error.
I will try to play with it some more just to make sure it doesn't fail no more.
If I will encounter this problem again, I will use the appropriate mailing list instead of bugzilla.

Comment 9 Maor 2015-08-17 13:11:30 UTC
I'm closing the the bug for now, if this error will be regenerated I will post the details through the devel mailing list.


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