[ovirt-devel] can't create a VM on engine master

[Roy Golan]

https://gerrit.ovirt.org/#/c/81636/ should solve it. I made
MacPoolPerCluster @DependOn("Backend") which should make the config
available at init time

On Mon, 11 Sep 2017 at 21:08 Roy Golan <rgolan at redhat.com> wrote:

> Maybe the MacPoolPerCluster EJB bean is started before the Backed bean,
> probably a backfire of Wildfly 11 move
>
> I'll try to make a dependency and see if it helps
>
> On Mon, 11 Sep 2017 at 18:40 Benny Zlotnik <bzlotnik at redhat.com> wrote:
>
>> This error can be observed in server.log:
>> 2017-09-11 18:37:03,268+03 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.MacPoolPerCluster.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.WeldException: WELD-000049: Unable to invoke
>> public void
>> org.ovirt.engine.core.bll.CpuFlagsManagerHandler.initDictionaries() on
>> org.ovirt.engine.core.bll.CpuFlagsManagerHandler at 7f971888
>>     Caused by: org.jboss.weld.exceptions.WeldException: WELD-000049:
>> Unable to invoke public void
>> org.ovirt.engine.core.bll.CpuFlagsManagerHandler.initDictionaries() on
>> org.ovirt.engine.core.bll.CpuFlagsManagerHandler at 7f971888
>>     Caused by: java.lang.reflect.InvocationTargetException
>>     Caused by: java.lang.NullPointerException"}}
>>
>>
>> On Mon, Sep 11, 2017 at 6:11 PM, Benny Zlotnik <bzlotnik at redhat.com>
>> wrote:
>>
>>> Yes, reverting this patch[1] helped (there's a discussion about OST
>>> failing)
>>>
>>> [1] - https://gerrit.ovirt.org/#/c/80450/
>>>
>>> On Mon, Sep 11, 2017 at 6:05 PM, Greg Sheremeta <gshereme at redhat.com>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> With a fresh engine (new path and new db) and a fresh f24 4.1 host, I'm
>>>> unable to add a VM either via the UI or REST API. Both hang, and I see no
>>>> helpful logs. Engine log just says it's running the command, and then
>>>> nothing. I don't see anything in vdsm.log that suggests the command came
>>>> through, so I think it's a problem in engine. Logs attached.
>>>>
>>>> Anyone else seeing this?
>>>>
>>>> Greg
>>>>
>>>> --
>>>>
>>>> GREG SHEREMETA
>>>>
>>>> SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX
>>>>
>>>> Red Hat
>>>>
>>>> <https://www.redhat.com/>
>>>>
>>>> gshereme at redhat.com    IRC: gshereme
>>>> <https://red.ht/sig>
>>>>
>>>> _______________________________________________
>>>> Devel mailing list
>>>> Devel at ovirt.org
>>>> http://lists.ovirt.org/mailman/listinfo/devel
>>>>
>>>
>>>
>> _______________________________________________
>> Devel mailing list
>> Devel at ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/devel/attachments/20170911/77807d9d/attachment.html>