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:
please note second job no longer exists
thanks,
Dafna
On Wed, Feb 7, 2018 at 2:09 PM, Martin Perina <mperina(a)redhat.com> wrote:
On Wed, Feb 7, 2018 at 2:30 PM, Dafna Ron <dron(a)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/a...
>
<
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5307/artifa...
> 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(a)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(a)ovirt.org
>
http://lists.ovirt.org/mailman/listinfo/devel
>
--
Martin Perina
Associate Manager, Software Engineering
Red Hat Czech s.r.o.