November 2019 - Infra - Ovirt List Archives

[CQ]: 103401, 5 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause

by oVirt Jenkins

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

5 years

1
0
0 / 0

Build failed in Jenkins: system-sync_mirrors-centos-updates-7.6-el7-x86_64 #88

by jenkins＠jenkins.phx.ovirt.org

See <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-updates-7.6-el7-x...> Changes: ------------------------------------------ Started by timer Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-updates-7.6-el7-x...> No credentials specified > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -fdx # timeout=10 Pruning obsolete local branches Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git > git --version # timeout=10 > git fetch --tags --progress --prune http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision 5a9e02bc132175985f5c1820df4b65a215c107c5 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 5a9e02bc132175985f5c1820df4b65a215c107c5 Commit message: "global-setup: Ensure selinux-policy is up to date" > git rev-list --no-walk 5a9e02bc132175985f5c1820df4b65a215c107c5 # timeout=10 [system-sync_mirrors-centos-updates-7.6-el7-x86_64] $ /bin/bash -xe /tmp/jenkins1613629674272405626.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror centos-updates-7.6-el7 x86_64 jenkins/data/mirrors-reposync.conf + MIRRORS_MP_BASE=/var/www/html/repos + MIRRORS_HTTP_BASE=http://mirrors.phx.ovirt.org/repos + MIRRORS_CACHE=/home/jenkins/mirrors_cache + MAX_LOCK_ATTEMPTS=120 + LOCK_WAIT_INTERVAL=5 + LOCK_BASE=/home/jenkins + OLD_MD_TO_KEEP=100 + HTTP_SELINUX_TYPE=httpd_sys_content_t + HTTP_FILE_MODE=644 + main resync_yum_mirror centos-updates-7.6-el7 x86_64 jenkins/data/mirrors-reposync.conf + local command=resync_yum_mirror + command_args=("${@:2}") + local command_args + cmd_resync_yum_mirror centos-updates-7.6-el7 x86_64 jenkins/data/mirrors-reposync.conf + local repo_name=centos-updates-7.6-el7 + local repo_archs=x86_64 + local reposync_conf=jenkins/data/mirrors-reposync.conf + local sync_needed + mkdir -p /home/jenkins/mirrors_cache + verify_repo_fs centos-updates-7.6-el7 yum + local repo_name=centos-updates-7.6-el7 + local repo_type=yum + sudo install -o jenkins -d /var/www/html/repos/yum /var/www/html/repos/yum/centos-updates-7.6-el7 /var/www/html/repos/yum/centos-updates-7.6-el7/base + check_yum_sync_needed centos-updates-7.6-el7 x86_64 jenkins/data/mirrors-reposync.conf sync_needed + local repo_name=centos-updates-7.6-el7 + local repo_archs=x86_64 + local reposync_conf=jenkins/data/mirrors-reposync.conf + local p_sync_needed=sync_needed + local reposync_out + echo 'Checking if mirror needs a resync' Checking if mirror needs a resync + rm -rf /home/jenkins/mirrors_cache/centos-updates-7.6-el7 ++ IFS=, ++ echo x86_64 + for arch in '$(IFS=,; echo $repo_archs)' ++ run_reposync centos-updates-7.6-el7 x86_64 jenkins/data/mirrors-reposync.conf --urls --quiet ++ local repo_name=centos-updates-7.6-el7 ++ local repo_arch=x86_64 ++ local reposync_conf=jenkins/data/mirrors-reposync.conf ++ extra_args=("${@:4}") ++ local extra_args ++ reposync --config=jenkins/data/mirrors-reposync.conf --repoid=centos-updates-7.6-el7 --arch=x86_64 --cachedir=/home/jenkins/mirrors_cache --download_path=/var/www/html/repos/yum/centos-updates-7.6-el7/base --norepopath --newest-only --urls --quiet Error setting up repositories: Error making cache directory: /home/jenkins/mirrors_cache/centos-sclo-rh-release-7.6-el7/packages error was: [Errno 17] File exists: '/home/jenkins/mirrors_cache/centos-sclo-rh-release-7.6-el7/packages' + reposync_out= Build step 'Execute shell' marked build as failure

5 years

1
1
0 / 0

[CQ]: 104702, 5 (ovirt-system-tests) failed "ovirt-4.3" system tests, but isn't the failure root cause

by oVirt Jenkins

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

5 years

1
0
0 / 0

[oVirt Jenkins] deploy-to-gated-ovirt-4.3 - Build #38 - FAILURE!

by jenkins＠jenkins.phx.ovirt.org

Build: http://jenkins.ovirt.org/job/deploy-to-gated-ovirt-4.3/38/ Build Name: #38 Build Status: FAILURE Gerrit change: null - title: null - project: null - branch: null - author: null <null>

5 years

1
1
0 / 0

[CQ]: c7fa92b (ovirt-ansible) failed "ovirt-4.3" system tests

by oVirt Jenkins

Change c7fa92b (ovirt-ansible) is probably the reason behind recent system test failures in the "ovirt-4.3" 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/commit/c7fa92b45ecb88d26ffa959b103... For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/2534/

5 years

1
0
0 / 0

[CQ]: 104790, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause

by oVirt Jenkins

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

5 years

1
0
0 / 0

[CQ]: 840e846 (ovirt-web-ui) failed "ovirt-4.3" system tests

by oVirt Jenkins

Change 840e846 (ovirt-web-ui) is probably the reason behind recent system test failures in the "ovirt-4.3" 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-web-ui/commit/840e846f852971d411b6687f7f1f... For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/2532/

5 years

1
0
0 / 0

[CQ]: 840e846 (ovirt-web-ui) failed "ovirt-master" system tests

by oVirt Jenkins

Change 840e846 (ovirt-web-ui) is probably the reason behind recent system test failures in the "ovirt-master" 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-web-ui/commit/840e846f852971d411b6687f7f1f... For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/17217/

5 years

1
0
0 / 0

[JIRA] (OVIRT-2841) ovirt-srv20: failed to run CNI IPAM ADD

by Evgheni Dereveanchin (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2841?page=com.atlassian.jir... ] Evgheni Dereveanchin reassigned OVIRT-2841: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > ovirt-srv20: failed to run CNI IPAM ADD > --------------------------------------- > > Key: OVIRT-2841 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2841 > Project: oVirt - virtualization made easy > Issue Type: Outage > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > > One of the bare metals used by Kubevirt is failing to spawn pods due to issues with the CNI plugin: > NetworkPlugin cni failed to set up pod \"c1d6a5c2-0c47-11ea-8dea-0a580a8209d6_kubevirt-prow-jobs\" network: Multus: Err in tearing down failed plugins: Multus: error in invoke Delegate add - \"openshift-sdn\": CNI request failed with status 400: 'failed to run IPAM for 3c0733334a7cf85a19b753794755697025d68028f121b0737c38ab04aaea9b09: failed to run CNI IPAM ADD: failed to allocate for range 0: no IP addresses available in range set: 10.128.6.1-10.128.7.254\n'" > Rebooting the node did not fix the issue, logging ticket to investigate further. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100114)

5 years

1
0
0 / 0

[JIRA] (OVIRT-2841) ovirt-srv20: failed to run CNI IPAM ADD

by Evgheni Dereveanchin (oVirt JIRA)

Evgheni Dereveanchin created OVIRT-2841: ------------------------------------------- Summary: ovirt-srv20: failed to run CNI IPAM ADD Key: OVIRT-2841 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2841 Project: oVirt - virtualization made easy Issue Type: Outage Reporter: Evgheni Dereveanchin Assignee: infra One of the bare metals used by Kubevirt is failing to spawn pods due to issues with the CNI plugin: NetworkPlugin cni failed to set up pod \"c1d6a5c2-0c47-11ea-8dea-0a580a8209d6_kubevirt-prow-jobs\" network: Multus: Err in tearing down failed plugins: Multus: error in invoke Delegate add - \"openshift-sdn\": CNI request failed with status 400: 'failed to run IPAM for 3c0733334a7cf85a19b753794755697025d68028f121b0737c38ab04aaea9b09: failed to run CNI IPAM ADD: failed to allocate for range 0: no IP addresses available in range set: 10.128.6.1-10.128.7.254\n'" Rebooting the node did not fix the issue, logging ticket to investigate further. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100114)

5 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Infra November 2019