November 2018 - Infra - oVirt List Archives

[CQ]: c779414 (ovirt-ansible-repositories) failed "ovirt-4.2" system tests
by oVirt Jenkins 30 Nov '18

30 Nov '18

Change c779414 (ovirt-ansible-repositories) 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://github.com/oVirt/ovirt-ansible-repositories/commit/c779414fdf3887f8… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3571/

1 0

[CQ]: 95837, 1 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 30 Nov '18

30 Nov '18

A system test invoked by the "ovirt-master" change queue including change 95837,1 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 95756,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 95756,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/95837/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/95756/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/11732/

2 1

[CQ]: 43b04c2 (ovirt-ansible-image-template) failed "ovirt-4.2" system tests
by oVirt Jenkins 30 Nov '18

30 Nov '18

Change 43b04c2 (ovirt-ansible-image-template) 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://github.com/oVirt/ovirt-ansible-image-template/commit/43b04c27d001f9… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3567/

2 1

[JIRA] (OVIRT-2607) check-merge stuck for vdsm
by Dafna Ron (oVirt JIRA) 30 Nov '18

30 Nov '18

Dafna Ron created OVIRT-2607: -------------------------------- Summary: check-merge stuck for vdsm Key: OVIRT-2607 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2607 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Dafna Ron Assignee: infra we aborted the build. there was no restart for Jenkins https://jenkins.ovirt.org/job/vdsm_standard-on-merge/45/ It looks like it failed on lago log collection but lago should have a timeout {noformat} network/functional/bond_basic_test.py .............. network/functional/bridge_test.py ...s network/functional/dns_test.py ... network/functional/dynamic_ip_test.py ......... network/functional/link_mtu_test.py .............xx.... network/functional/net_basic_test.py ...............................ss network/functional/net_qos_test.py ... network/functional/net_with_bond_test.py ................ network/functional/rollback_test.py .FF network/functional/static_ip_test.py FFF++ collect_and_clean ++ collect_logs ++ mkdir /home/jenkins/workspace/vdsm_standard-on-merge/vdsm/exported-artifacts/test_logs ./automation/check-merged.sh: line 139: 25240 Terminated run_network_tests 25241 | tee -a "$EXPORTS/functional_tests_stdout.$DISTRO.log" ++ lago collect --output /home/jenkins/workspace/vdsm_standard-on-merge/vdsm/exported-artifacts/test_logs @ Collect artifacts: # [Thread-1] vdsm_functional_tests_host-el7: Took 11100 seconds {noformat} I kept the build logs until we finish looking at this. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[JIRA] (OVIRT-2606) upgrade jenkins.ovirt.org to 2.138.4 LTS
by Evgheni Dereveanchin (oVirt JIRA) 30 Nov '18

30 Nov '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2606?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-2606: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > upgrade jenkins.ovirt.org to 2.138.4 LTS > ---------------------------------------- > > Key: OVIRT-2606 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2606 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > > Jenkins 2.138.3 is out and a security fix version 2.138.4 is expected next week. > Opening ticket to prepare a patch and test plugins updates, then apply them together with the new Jenkins once it's out. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[JIRA] (OVIRT-2606) upgrade jenkins.ovirt.org to 2.138.4 LTS
by Evgheni Dereveanchin (oVirt JIRA) 30 Nov '18

30 Nov '18

Evgheni Dereveanchin created OVIRT-2606: ------------------------------------------- Summary: upgrade jenkins.ovirt.org to 2.138.4 LTS Key: OVIRT-2606 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2606 Project: oVirt - virtualization made easy Issue Type: Improvement Reporter: Evgheni Dereveanchin Assignee: infra Jenkins 2.138.3 is out and a security fix version 2.138.4 is expected next week. Opening ticket to prepare a patch and test plugins updates, then apply them together with the new Jenkins once it's out. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

S390x machine problem
by Ehud Yonasi 30 Nov '18

30 Nov '18

Seems like space issue.

2 1

[JIRA] (OVIRT-2594) Build fail with "# /usr/sbin/groupadd -g 1000 mock" - no test was run
by Evgheni Dereveanchin (oVirt JIRA) 30 Nov '18

30 Nov '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2594?page=com.atlassian.jira.… ] Evgheni Dereveanchin updated OVIRT-2594: ---------------------------------------- Issue Type: Bug (was: By-EMAIL) > Build fail with "# /usr/sbin/groupadd -g 1000 mock" - no test was run > --------------------------------------------------------------------- > > Key: OVIRT-2594 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2594 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Nir Soffer > Assignee: Evgheni Dereveanchin > > I have seen this issue in the recent days several times. > Here are some examples: > - > https://jenkins.ovirt.org/job/vdsm_master_check-patch-fc28-x86_64/2269/cons… > - > https://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86_64/26243/cons… > - https://jenkins.ovirt.org/job/vdsm_standard-check-patch/91/console > - > https://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86_64/26187/cons… > There are too issues: > - No test ran, so we need to retrigger manually > - Gerrit report build FAILURE instead of build ERROR > I reported the second issue many times in the last 5 years, no progress yet. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[JIRA] (OVIRT-2594) Build fail with "# /usr/sbin/groupadd -g 1000 mock" - no test was run
by Evgheni Dereveanchin (oVirt JIRA) 30 Nov '18

30 Nov '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2594?page=com.atlassian.jira.… ] Evgheni Dereveanchin commented on OVIRT-2594: --------------------------------------------- I've set fc27 to only run jobs requesting this label (as we still have lago_master_github_check-patch-fc27-x86_64 and jenkins_master_check-patch-fc27-x86_64 needing those) and am working on fc29 in OVIRT-2601 > Build fail with "# /usr/sbin/groupadd -g 1000 mock" - no test was run > --------------------------------------------------------------------- > > Key: OVIRT-2594 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2594 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: Evgheni Dereveanchin > > I have seen this issue in the recent days several times. > Here are some examples: > - > https://jenkins.ovirt.org/job/vdsm_master_check-patch-fc28-x86_64/2269/cons… > - > https://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86_64/26243/cons… > - https://jenkins.ovirt.org/job/vdsm_standard-check-patch/91/console > - > https://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86_64/26187/cons… > There are too issues: > - No test ran, so we need to retrigger manually > - Gerrit report build FAILURE instead of build ERROR > I reported the second issue many times in the last 5 years, no progress yet. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[oVirt Jenkins] ovirt-node-ng-image_master_build-artifacts-el7-x86_64 - Build # 128 - Failure!
by jenkins＠jenkins.phx.ovirt.org 30 Nov '18

30 Nov '18

Project: http://jenkins.ovirt.org/job/ovirt-node-ng-image_master_build-artifacts-el7… Build: http://jenkins.ovirt.org/job/ovirt-node-ng-image_master_build-artifacts-el7… Build Number: 128 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #128 [Yuval Turgeman] stdci: move build-artifacts to a v1 job [Evgheni Dereveanchin] 2018.11.27 Update FC mirror snapshots ----------------- Failed Tests: ----------------- No tests ran.

1 2