It failed on initialize engine test.
the dwh service will not come up.
from the dwh log I can see that for some reason its detecting an upgrade in
engine (even though its the basic suite that is failing) and prints that it
needs an upgrade as well.
maybe a package mismatch on engine and dwh?

http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5449/artifact/exported-artifacts/basic-suit-master-el7/test_logs/basic-suite-master/post-001_initialize_engine.py/lago-basic-suite-master-engine/_var_log/ovirt-engine-dwh/ovirt-engine-dwhd.log

2018-02-08 
20:26:35|y6xi2H|Vs9nC8|Vs9nC8|OVIRT_ENGINE_DWH|MinimalVersionCheck|Default|5|tDie|tDie_1|2018-02-08
20:26:35|You have upgraded your oVirt Engine and now require an
upgrade of the ovirt-engine-dwh package. Please run engine-setup to
upgrade the version. Service will now exit.|4
2018-02-08 20:26:35|You have upgraded your oVirt Engine and now
require an upgrade of the ovirt-engine-dwh package. Please run
engine-setup to upgrade the version. Service will now exit.
Exception in component tRunJob_2
java.lang.RuntimeException: Child job running failed
        at 
ovirt_engine_dwh.historyetl_4_2.HistoryETL.tRunJob_2Process(HistoryETL.java:8186)
        at 
ovirt_engine_dwh.historyetl_4_2.HistoryETL$3.run(HistoryETL.java:11674)
2018-02-08 
20:26:36|Vs9nC8|Vs9nC8|Vs9nC8|OVIRT_ENGINE_DWH|HistoryETL|Default|6|Java
Exception|tRunJob_2|java.lang.RuntimeException:Child job running
failed|1
2018-02-08 20:26:36|ETL Service Stopped


On Fri, Feb 9, 2018 at 8:40 AM, Sandro Bonazzola <sbona...@redhat.com>
wrote:

>
>
> 2018-02-07 16:30 GMT+01:00 Nir Soffer <nsof...@redhat.com>:
>
>>
>>
>> On Wed, Feb 7, 2018 at 5:02 PM Martin Perina <mper...@redhat.com> wrote:
>>
>>> On Wed, Feb 7, 2018 at 3:22 PM, Dafna Ron <d...@redhat.com> wrote:
>>>
>>>> it did not.
>>>> This patch did not run on CQ at all because its failing build-artifact
>>>> jobs
>>>> Those jobs need to be fixed and patch has to be re-triggered.
>>>>
>>>> The two jobs that failed are:
>>>> http://jenkins.ovirt.org/job/vdsm_master_check-merged-el7-x86_64/3151/
>>>> <http://jenkins.ovirt.org/job/standard-enqueue/9725/>
>>>>
>>>
>> check-merged fails a lot, I don't think anyone is maintaining this.
>>
>
>
> This failed on *22:37:44* network/functional/static_ip_test.py ....+
> res=124
>
> I see following jobs passed, so vdsm should be now passing the tests
> unless any other failure is preventing it.
>
>
>
>>
>>
>>>
>>>> http://jenkins.ovirt.org/job/vdsm_master_build-artifacts-fcraw-s390x/1/
>>>>
>>>>
>> 404
>>
>>
>>>
>>> ​Francesco/Sandro, could you please take a look at those failures on
>>> VDSM patch?
>>> ​
>>>
>>>
>>>> please note second job no longer exists
>>>>
>>>> thanks,
>>>> Dafna
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On Wed, Feb 7, 2018 at 2:09 PM, Martin Perina <mper...@redhat.com>
>>>> wrote:
>>>>
>>>>>
>>>>>
>>>>> On Wed, Feb 7, 2018 at 2:30 PM, Dafna Ron <d...@redhat.com> wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> We failed test 004_basic_sanity.vm_run in the upgrade from release
>>>>>> suite.
>>>>>> the reason we failed to run the vm is that the host was filtered from
>>>>>> selection for vm.
>>>>>>
>>>>>> Please also notice other errors in the log relating to network sync
>>>>>> failing.
>>>>>>
>>>>>>
>>>>>> *Link and headline of suspected patches:
>>>>>> https://gerrit.ovirt.org/#/c/87116/5 
>>>>>> <https://gerrit.ovirt.org/#/c/87116/5>
>>>>>> - core: Add 4.3 support   *
>>>>>>
>>>>>
>>>>> Do we know if VDSM in this patch already contains
>>>>> https://gerrit.ovirt.org/87181 ? It's required to have both side
>>>>> fixed to properly support 4.3 cluster level
>>>>> ​
>>>>>
>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> *Link to
>>>>>> Job:http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5307/
>>>>>> <http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5307/>Link
>>>>>> to all
>>>>>> logs:http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5307/artifact/
>>>>>> <http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5307/artifact/>(Relevant)
>>>>>> error snippet from the log: <error>2018-02-06 16:42:39,431-05 INFO
>>>>>> [org.ovirt.engine.core.vdsbroker.IsVmDuringInitiatingVDSCommand] (default
>>>>>> task-5) [03cdc0e6-eb94-46a4-9882-77762b2ed787] FINISH,
>>>>>> IsVmDuringInitiatingVDSCommand, return: false, log id: 4d0244492018-02-06
>>>>>> 16:42:39,472-05 INFO  [org.ovirt.engine.core.bll.RunVmOnceCommand] 
>>>>>> (default
>>>>>> task-5) [03cdc0e6-eb94-46a4-9882-77762b2ed787] Running command:
>>>>>> RunVmOnceCommand internal: false. Entities affected :  ID:
>>>>>> ccfe9852-f2d6-4e18-8213-29d958d3a8ed Type: VMAction group RUN_VM with 
>>>>>> role
>>>>>> type USER,  ID: ccfe9852-f2d6-4e18-8213-29d958d3a8ed Type: VMAction group
>>>>>> EDIT_ADMIN_VM_PROPERTIES with role type ADMIN2018-02-06 16:42:39,486-05
>>>>>> INFO  [org.ovirt.engine.core.bll.scheduling.SchedulingManager] (default
>>>>>> task-5) [03cdc0e6-eb94-46a4-9882-77762b2ed787] Candidate host
>>>>>> 'lago-upgrade-from-release-suite-master-host0'
>>>>>> ('6ec7721d-beae-4b7e-807f-7f3a794fb7c4') was filtered out by
>>>>>> 'VAR__FILTERTYPE__INTERNAL' filter 'CPU-Level' (correlation id:
>>>>>> 03cdc0e6-eb94-46a4-9882-77762b2ed787)2018-02-06 16:42:39,486-05 ERROR
>>>>>> [org.ovirt.engine.core.bll.RunVmCommand] (default task-5)
>>>>>> [03cdc0e6-eb94-46a4-9882-77762b2ed787] Can't find VDS to run the VM
>>>>>> 'ccfe9852-f2d6-4e18-8213-29d958d3a8ed' on, so this VM will not be
>>>>>> run.2018-02-06 16:42:39,493-05 ERROR
>>>>>> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
>>>>>> (default task-5) [03cdc0e6-eb94-46a4-9882-77762b2ed787] EVENT_ID:
>>>>>> USER_FAILED_RUN_VM(54), Failed to run VM vm0 (User:
>>>>>> admin@internal-authz).2018-02-06 16:42:39,500-05 INFO
>>>>>> [org.ovirt.engine.core.bll.RunVmOnceCommand] (default task-5)
>>>>>> [03cdc0e6-eb94-46a4-9882-77762b2ed787] Lock freed to object
>>>>>> 'EngineLock:{exclusiveLocks='[ccfe9852-f2d6-4e18-8213-29d958d3a8ed=VM]',
>>>>>> sharedLocks=''}'2018-02-06 16:42:39,505-05 ERROR
>>>>>> [org.ovirt.engine.api.restapi.resource.AbstractBackendResource] (default
>>>>>> task-5) [] Operation Failed: []2018-02-06 16:42:39,512-05 INFO
>>>>>> [org.ovirt.engine.core.bll.Pro
>>>>>> <http://org.ovirt.engine.core.bll.Pro>cessDownVmCommand]
>>>>>> (EE-ManagedThreadFactory-engine-Thread-17) [4fe81490] Running command:
>>>>>> ProcessDownVmCommand internal: true.(END)</error>*
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Devel mailing list
>>>>>> Devel@ovirt.org
>>>>>> http://lists.ovirt.org/mailman/listinfo/devel
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Martin Perina
>>>>> Associate Manager, Software Engineering
>>>>> Red Hat Czech s.r.o.
>>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> Martin Perina
>>> Associate Manager, Software Engineering
>>> Red Hat Czech s.r.o.
>>> _______________________________________________
>>> Devel mailing list
>>> Devel@ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/devel
>>
>>
>
>
> --
>
> SANDRO BONAZZOLA
>
> ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D
>
> Red Hat EMEA <https://www.redhat.com/>
> <https://red.ht/sig>
> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
>
>
_______________________________________________
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Reply via email to