April 2018 - Infra - Ovirt List Archives

[JIRA] (OVIRT-1962) [gerrit hooks] check related-to logic and consider updating logic

by eyal edri (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1962?page=com.atlassian.jir... ] eyal edri updated OVIRT-1962: ----------------------------- Epic Link: OVIRT-411 > [gerrit hooks] check related-to logic and consider updating logic > ----------------------------------------------------------------- > > Key: OVIRT-1962 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1962 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: eyal edri > Assignee: infra > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100082)

6 years, 1 month

1
0
0 / 0

[JIRA] (OVIRT-1962) [gerrit hooks] check related-to logic and consider updating logic

by eyal edri (oVirt JIRA)

eyal edri created OVIRT-1962: -------------------------------- Summary: [gerrit hooks] check related-to logic and consider updating logic Key: OVIRT-1962 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1962 Project: oVirt - virtualization made easy Issue Type: Improvement Reporter: eyal edri Assignee: infra Following https://bugzilla.redhat.com/show_bug.cgi?id=1547479#c13 and other requests around 'Related-To' logic in the Gerrit hooks, we should check current logic and see if we need to update/fix it. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100082)

6 years, 1 month

1
0
0 / 0

[CQ]: 89897,2 (vdsm) failed "ovirt-4.2" system tests

by oVirt Jenkins

Change 89897,2 (vdsm) is probably the reason behind recent system test failures in the "ovirt-4.2" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/89897/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/1589/

6 years, 1 month

2
1
0 / 0

[CQ]: 89879,2 (vdsm) failed "ovirt-4.2" system tests

by oVirt Jenkins

Change 89879,2 (vdsm) is probably the reason behind recent system test failures in the "ovirt-4.2" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/89879/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/1576/

6 years, 1 month

2
1
0 / 0

[CQ]: 89533, 3 (vdsm) failed "ovirt-4.2" system tests, but isn't the failure root cause

by oVirt Jenkins

A system test invoked by the "ovirt-4.2" change queue including change 89533,3 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 89531,3 (vdsm) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 89531,3 (vdsm) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/89533/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/89531/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/1574/

6 years, 1 month

2
1
0 / 0

[CQ]: 89531,3 (vdsm) failed "ovirt-4.2" system tests

by oVirt Jenkins

Change 89531,3 (vdsm) is probably the reason behind recent system test failures in the "ovirt-4.2" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/89531/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/1570/

6 years, 1 month

2
1
0 / 0

[JIRA] (OVIRT-1849) enable all gerrit hooks for cockpit-ovirt project

by eyal edri (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1849?page=com.atlassian.jir... ] eyal edri commented on OVIRT-1849: ---------------------------------- [~amarchuk] any update? > enable all gerrit hooks for cockpit-ovirt project > ------------------------------------------------- > > Key: OVIRT-1849 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1849 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eyal edri > Assignee: infra > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100082)

6 years, 1 month

1
0
0 / 0

[CQ]: 89508, 4 (vdsm) failed "ovirt-4.2" system tests, but isn't the failure root cause

by oVirt Jenkins

A system test invoked by the "ovirt-4.2" change queue including change 89508,4 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 89506,4 (vdsm) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 89506,4 (vdsm) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/89508/4 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/89506/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/1565/

6 years, 1 month

2
1
0 / 0

[ OST Failure Report ] [ oVirt 4.2 (vdsm) ] [ 05-04-2018 ] [ 004_basic_sanity.hotplug_cpu ]

by Dafna Ron

Hi, We had a failure on 004_basic_sanity.hotplug_cpu. looking at the logs, I do not see an issue on the cpu hotplug but it seems that the host had an issue with network config. can you please have a look? *Link and headline of suspected patches: Failed patch: * *virt: storage: minimal changes to the drive XML - https://gerrit.ovirt.org/#/c/89508/ <https://gerrit.ovirt.org/#/c/89508/> * *Reported as failure cause: * *virt: extract local adjustments to XML - https://gerrit.ovirt.org/#/c/89506/ <https://gerrit.ovirt.org/#/c/89506/> * *Link to Job:http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/1565/ <http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/1565/>Link to all logs:http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/1565/arti... <http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/1565/artifact/...>(Relevant) error snippet from the log: <error>MainProcess|jsonrpc/2::DEBUG::2018-04-05 18:58:17,451::cmdutils::150::root::(exec_cmd) /sbin/ifdown eth2 (cwd None)MainProcess|jsonrpc/2::DEBUG::2018-04-05 18:58:17,719::cmdutils::158::root::(exec_cmd) SUCCESS: <err> = ''; <rc> = 0MainProcess|jsonrpc/2::DEBUG::2018-04-05 18:58:17,720::cmdutils::150::root::(exec_cmd) /sbin/ifdown eth3 (cwd None)MainProcess|jsonrpc/2::DEBUG::2018-04-05 18:58:17,982::cmdutils::158::root::(exec_cmd) SUCCESS: <err> = ''; <rc> = 0ifup/onc5bbb5eed6a84::DEBUG::2018-04-05 18:58:18,165::cmdutils::158::root::(exec_cmd) FAILED: <err> = 'Running scope as unit b32c8477-857f-476c-96c8-580daf0d4217.scope.\n/etc/sysconfig/network-scripts/ifup-eth: line 304: 12145 Terminated /sbin/dhclient ${DHCLIENTARGS} ${DEVICE}\nDevice "onc5bbb5eed6a84" does not exist.\nCannot find device "onc5bbb5eed6a84"\nDevice "onc5bbb5eed6a84" does not exist.\nDevice "onc5bbb5eed6a84" does not exist.\nDevice "onc5bbb5eed6a84" does not exist.\nDevice "onc5bbb5eed6a84" does not exist.\nDevice "onc5bbb5eed6a84" does not exist.\nDevice "onc5bbb5eed6a84" does not exist.\nDevice "onc5bbb5eed6a84" does not exist.\nDevice "onc5bbb5eed6a84" does not exist.\nDevice "onc5bbb5eed6a84" does not exist.\nDevice "onc5bbb5eed6a84" does not exist.\nDevice "onc5bbb5eed6a84" does not exist.\nDevice "onc5bbb5eed6a84" does not exist.\nDevice "onc5bbb5eed6a84" does not exist.\nDevice "onc5bbb5eed6a84" does not exist.\nDevice "onc5bbb5eed6a84" does not exist.\nDevice "onc5bbb5eed6a84" does not exist.\nDevice "onc5bbb5eed6a84" does not exist.\nDevice "onc5bbb5eed6a84" does not exist.\nDevice "onc5bbb5eed6a84" does not exist.\nDevice "onc5bbb5eed6a84" does not exist.\nDevice "onc5bbb5eed6a84" does not exist.\nDevice "onc5bbb5eed6a84" does not exist.\nDevice "onc5bbb5eed6a84" does not exist.\nDevice "onc5bbb5eed6a84" does not exist.\nDevice "onc5bbb5eed6a84" does not exist.\nDevice "onc5bbb5eed6a84" does not exist.\nDevice "onc5bbb5eed6a84" does not exist.\nDevice "onc5bbb5eed6a84" does not exist.\nDevice "onc5bbb5eed6a84" does not exist.\nDevice "onc5bbb5eed6a84" does not exist.\nDevice "onc5bbb5eed6a84" does not exist.\nDevice "onc5bbb5eed6a84" does not exist.\nDevice "onc5bbb5eed6a84" does not exist.\nDevice "onc5bbb5eed6a84" does not exist.\nDevice "onc5bbb5eed6a84" does not exist.\nDevice "onc5bbb5eed6a84" does not exist.\nDevice "onc5bbb5eed6a84" does not exist.\nDevice "onc5bbb5eed6a84" does not exist.\nDevice "onc5bbb5eed6a84" does not exist.\nDevice "onc5bbb5eed6a84" does not exist.\nDevice "onc5bbb5eed6a84" does not exist.\nDevice "onc5bbb5eed6a84" does not exist.\nDevice "onc5bbb5eed6a84" does not exist.\nDevice "onc5bbb5eed6a84" does not exist.\nDevice "onc5bbb5eed6a84" does not exist.\nDevice "onc5bbb5eed6a84" does not exist.\nDevice "onc5bbb5eed6a84" does not exist.\nDevice "onc5bbb5eed6a84" does not exist.\nDevice "onc5bbb5eed6a84" does not exist.\nDevice "onc5bbb5eed6a84" does not exist.\nDevice "onc5bbb5eed6a84" does not exist.\n'; <rc> = 1ifup/onc5bbb5eed6a84::ERROR::2018-04-05 18:58:18,165::concurrent::201::root::(run) FINISH thread <Thread(ifup/onc5bbb5eed6a84, stopped daemon 139876090296064)> failedTraceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/common/concurrent.py", line 194, in run ret = func(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/network/configurators/ifcfg.py", line 942, in _exec_ifup _exec_ifup_by_name(iface.name <http://iface.name>, cgroup) File "/usr/lib/python2.7/site-packages/vdsm/network/configurators/ifcfg.py", line 928, in _exec_ifup_by_name raise ConfigNetworkError(ERR_FAILED_IFUP, out[-1] if out else '')ConfigNetworkError: (29, '\n')MainProcess|jsonrpc/2::DEBUG::2018-04-05 18:58:20,075::cmdutils::150::root::(exec_cmd) /sbin/ip addr flush dev eth2 scope global (cwd None)MainProcess|jsonrpc/2::DEBUG::2018-04-05 18:58:20,081::cmdutils::158::root::(exec_cmd) SUCCESS: <err> = ''; <rc> = 0MainProcess|jsonrpc/2::DEBUG::2018-04-05 18:58:20,082::ifcfg::479::root::(_atomicBackup) Backed up /etc/sysconfig/network-scripts/ifcfg-eth2MainProcess|jsonrpc/2::DEBUG::2018-04-05 18:58:20,084::ifcfg::512::root::(_persistentBackup) backing up ifcfg-eth2: HWADDR="54:52:c0:a8:c9:02" BOOTPROTO="dhcp" ONBOOT="yes" TYPE="Ethernet" NAME="eth2" </error>*

6 years, 1 month

2
1
0 / 0

[CQ]: 89506,4 (vdsm) failed "ovirt-4.2" system tests

by oVirt Jenkins

Change 89506,4 (vdsm) is probably the reason behind recent system test failures in the "ovirt-4.2" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/89506/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/1558/

6 years, 1 month

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Infra April 2018