- Infra - oVirt List Archives

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 22 Jan '19

22 Jan '19

Failed to run project_setup.sh for: #3245 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-mlcw7.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 22 Jan '19

22 Jan '19

Failed to run project_setup.sh for: #3243 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-9b6qc.

1 0

[ANN] oVirt 4.2.8 is now generally available
by Sandro Bonazzola 22 Jan '19

22 Jan '19

The oVirt Project is pleased to announce the general availability of oVirt 4.2.8, as of January 22nd, 2019. This update is the eighth and last in a series of stabilization updates to the 4.2 series. Please note that no further updates will be issued for the 4.2 series. We encourage users to upgrade to 4.3 series when generally available to receive new features and updates. This release is available now for: * Red Hat Enterprise Linux 7.6 or later * CentOS Linux (or similar) 7.6 or later This release supports Hypervisor Hosts running: * Red Hat Enterprise Linux 7.6 or later * CentOS Linux (or similar) 7.6 or later * oVirt Node 4.2 See the release notes [1] for installation / upgrade instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is available - oVirt Node update is available, ISO will be available soon [2] - oVirt Tools Setup ISO is available[2] oVirt Node has been updated including: - oVirt 4.2.8: http://www.ovirt.org/release/4.2.8/ - Release for CentOS Linux 7 (1810) ( https://lists.centos.org/pipermail/centos-announce/2018-December/023082.html ) - Ansible 2.7.5: https://github.com/ansible/ansible/blob/stable-2.7/changelogs/CHANGELOG-v2.… Relevant CentOS Errata included: - CEBA-2019:0037 CentOS 7 tzdata BugFix Update ( https://lists.centos.org/pipermail/centos-announce/2019-January/023142.html ) - CESA-2019:0049 Important CentOS 7 systemd Security Update ( https://lists.centos.org/pipermail/centos-announce/2019-January/023143.html ) - CESA-2018:3651 Moderate CentOS 7 kernel Security Update ( https://lists.centos.org/pipermail/centos-announce/2018-December/023132.html ) - CEBA-2018:3338 CentOS 7 sos BugFix Update ( https://lists.centos.org/pipermail/centos-announce/2018-December/023125.html ) - CEBA-2018:3664 CentOS 7 selinux-policy BugFix Update ( https://lists.centos.org/pipermail/centos-announce/2018-December/023124.html ) - CESA-2018:3738 Important CentOS 7 ruby Security Update ( https://lists.centos.org/pipermail/centos-announce/2018-December/023122.html ) - CESA-2018:3347 Critical CentOS 7 python-paramiko Security Update ( https://lists.centos.org/pipermail/centos-announce/2018-December/023119.html ) - CESA-2018:3665 Important CentOS 7 NetworkManager Security Update ( https://lists.centos.org/pipermail/centos-announce/2018-December/023116.html ) - CEBA-2018:3442 CentOS 7 lvm2 BugFix Update ( https://lists.centos.org/pipermail/centos-announce/2018-December/023112.html ) - CEBA-2018:3669 CentOS 7 libvirt BugFix Update ( https://lists.centos.org/pipermail/centos-announce/2018-December/023110.html ) - CEBA-2018:3659 CentOS 7 libguestfs BugFix Update ( https://lists.centos.org/pipermail/centos-announce/2018-December/023108.html ) Additional Resources: * Read more about the oVirt 4.2.8 release highlights: http://www.ovirt.org/release/4.2.8/ * Get more oVirt Project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] http://www.ovirt.org/release/4.2.8/ [2] http://resources.ovirt.org/pub/ovirt-4.2/iso/ -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig>

1 0

DNF is used on CentOS CI by default
by Yedidyah Bar David 22 Jan '19

22 Jan '19

Hi all, I now noticed that at least in [1], otopi found and used DNF on CentOS. Meaning, we install at least enough of dnf there to make otopi be able to use it. Was this done on purpose? Or is this an unplanned result of a recent upgrade? Something else? [1] https://jenkins.ovirt.org/job/otopi_master_check-patch-el7-x86_64/506/ -- Didi

2 2

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 22 Jan '19

22 Jan '19

Failed to run project_setup.sh for: #3239 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-nswhg.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 22 Jan '19

22 Jan '19

Failed to run project_setup.sh for: #3238 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-t45c4.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 22 Jan '19

22 Jan '19

Failed to run project_setup.sh for: #3238 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-sqvhs.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 22 Jan '19

22 Jan '19

Failed to run project_setup.sh for: #3236 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-1zk4q.

1 5

oVirt infra daily report - unstable production jobs - 712
by jenkins＠jenkins.phx.ovirt.org 22 Jan '19

22 Jan '19

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - http://jenkins.ovirt.org/job/system_jenkins-report/712//artifact/exported-a… Cheers, Jenkins

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 21 Jan '19

21 Jan '19

Failed to run project_setup.sh for: #3235 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-b8fmw.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 21 Jan '19

21 Jan '19

Failed to run project_setup.sh for: #3235 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-wktzr.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 21 Jan '19

21 Jan '19

Failed to run project_setup.sh for: #3233 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-nj6wz.

1 1

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 21 Jan '19

21 Jan '19

Failed to run project_setup.sh for: #3234 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-mvhss.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 21 Jan '19

21 Jan '19

Failed to run project_setup.sh for: #3234 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-l450q.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 21 Jan '19

21 Jan '19

Failed to run project_setup.sh for: #3234 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-qnq5s.

1 0

[JENKINS] Failed to setup proejct vdsm_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 21 Jan '19

21 Jan '19

Failed to run project_setup.sh for: #2149 vdsm [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on vm0004.workers-phx.ovirt.org.

1 0

[JENKINS] Failed to setup proejct vdsm_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 21 Jan '19

21 Jan '19

Failed to run project_setup.sh for: #2150 vdsm [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on vm0099.workers-phx.ovirt.org.

1 0

[JENKINS] Failed to setup proejct vdsm_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 21 Jan '19

21 Jan '19

Failed to run project_setup.sh for: #2147 vdsm [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on vm0001.workers-phx.ovirt.org.

1 0

[JENKINS] Failed to setup proejct vdsm_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 21 Jan '19

21 Jan '19

Failed to run project_setup.sh for: #2149 vdsm [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on vm0035.workers-phx.ovirt.org.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 21 Jan '19

21 Jan '19

Failed to run project_setup.sh for: #3232 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-06hp5.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 21 Jan '19

21 Jan '19

Failed to run project_setup.sh for: #3232 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-q37cv.

1 0

[JIRA] (OVIRT-2656) Upstream-sources trigger for ovirt-engine-metrics does not work
by Ehud Yonasi (oVirt JIRA) 21 Jan '19

21 Jan '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2656?page=com.atlassian.jira.… ] Ehud Yonasi reassigned OVIRT-2656: ---------------------------------- Assignee: Ehud Yonasi (was: infra) > Upstream-sources trigger for ovirt-engine-metrics does not work > --------------------------------------------------------------- > > Key: OVIRT-2656 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2656 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Shirly Radco > Assignee: Ehud Yonasi > > -- > SHIRLY RADCO > BI SENIOR SOFTWARE ENGINEER > Red Hat Israel <https://www.redhat.com/> > <https://red.ht/sig> > TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

Build failed in Jenkins: system-sync_mirrors-glusterfs-5-el7-x86_64 #4
by jenkins＠jenkins.phx.ovirt.org 21 Jan '19

21 Jan '19

See <http://jenkins.ovirt.org/job/system-sync_mirrors-glusterfs-5-el7-x86_64/4/d…> ------------------------------------------ Started by timer [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-glusterfs-5-el7-x86_64/ws/> > 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 http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* --prune > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision 681568f1b88d94eec0e2a80959e00a4f078ebe16 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 681568f1b88d94eec0e2a80959e00a4f078ebe16 Commit message: "Fix JJB defaults" > git rev-list --no-walk 681568f1b88d94eec0e2a80959e00a4f078ebe16 # timeout=10 [system-sync_mirrors-glusterfs-5-el7-x86_64] $ /bin/bash -xe /tmp/jenkins6828599159785438557.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror glusterfs-5-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 glusterfs-5-el7 x86_64 jenkins/data/mirrors-reposync.conf + local command=resync_yum_mirror + command_args=("${@:2}") + local command_args + cmd_resync_yum_mirror glusterfs-5-el7 x86_64 jenkins/data/mirrors-reposync.conf + local repo_name=glusterfs-5-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 glusterfs-5-el7 yum + local repo_name=glusterfs-5-el7 + local repo_type=yum + sudo install -o jenkins -d /var/www/html/repos/yum /var/www/html/repos/yum/glusterfs-5-el7 /var/www/html/repos/yum/glusterfs-5-el7/base + check_yum_sync_needed glusterfs-5-el7 x86_64 jenkins/data/mirrors-reposync.conf sync_needed + local repo_name=glusterfs-5-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/glusterfs-5-el7 ++ IFS=, ++ echo x86_64 + for arch in '$(IFS=,; echo $repo_archs)' ++ run_reposync glusterfs-5-el7 x86_64 jenkins/data/mirrors-reposync.conf --urls --quiet ++ local repo_name=glusterfs-5-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=glusterfs-5-el7 --arch=x86_64 --cachedir=/home/jenkins/mirrors_cache --download_path=/var/www/html/repos/yum/glusterfs-5-el7/base --norepopath --newest-only --urls --quiet + reposync_out='http://mirror.centos.org/centos/7/storage/x86_64/gluster-5/glusterfs-5.3-1.… http://mirror.centos.org/centos/7/storage/x86_64/gluster-5/glusterfs-api-5.… http://mirror.centos.org/centos/7/storage/x86_64/gluster-5/glusterfs-api-de… http://mirror.centos.org/centos/7/storage/x86_64/gluster-5/glusterfs-cli-5.… http://mirror.centos.org/centos/7/storage/x86_64/gluster-5/glusterfs-client… http://mirror.centos.org/centos/7/storage/x86_64/gluster-5/glusterfs-clouds… http://mirror.centos.org/centos/7/storage/x86_64/gluster-5/glusterfs-devel-… http://mirror.centos.org/centos/7/storage/x86_64/gluster-5/glusterfs-events… http://mirror.centos.org/centos/7/storage/x86_64/gluster-5/glusterfs-extra-… http://mirror.centos.org/centos/7/storage/x86_64/gluster-5/glusterfs-fuse-5… http://mirror.centos.org/centos/7/storage/x86_64/gluster-5/glusterfs-geo-re… http://mirror.centos.org/centos/7/storage/x86_64/gluster-5/glusterfs-libs-5… http://mirror.centos.org/centos/7/storage/x86_64/gluster-5/glusterfs-rdma-5… http://mirror.centos.org/centos/7/storage/x86_64/gluster-5/glusterfs-resour… http://mirror.centos.org/centos/7/storage/x86_64/gluster-5/glusterfs-server… http://mirror.centos.org/centos/7/storage/x86_64/gluster-5/python2-gluster-…' + [[ -n http://mirror.centos.org/centos/7/storage/x86_64/gluster-5/glusterfs-5.3-1.… http://mirror.centos.org/centos/7/storage/x86_64/gluster-5/glusterfs-api-5.… http://mirror.centos.org/centos/7/storage/x86_64/gluster-5/glusterfs-api-de… http://mirror.centos.org/centos/7/storage/x86_64/gluster-5/glusterfs-cli-5.… http://mirror.centos.org/centos/7/storage/x86_64/gluster-5/glusterfs-client… http://mirror.centos.org/centos/7/storage/x86_64/gluster-5/glusterfs-clouds… http://mirror.centos.org/centos/7/storage/x86_64/gluster-5/glusterfs-devel-… http://mirror.centos.org/centos/7/storage/x86_64/gluster-5/glusterfs-events… http://mirror.centos.org/centos/7/storage/x86_64/gluster-5/glusterfs-extra-… http://mirror.centos.org/centos/7/storage/x86_64/gluster-5/glusterfs-fuse-5… http://mirror.centos.org/centos/7/storage/x86_64/gluster-5/glusterfs-geo-re… http://mirror.centos.org/centos/7/storage/x86_64/gluster-5/glusterfs-libs-5… http://mirror.centos.org/centos/7/storage/x86_64/gluster-5/glusterfs-rdma-5… http://mirror.centos.org/centos/7/storage/x86_64/gluster-5/glusterfs-resour… http://mirror.centos.org/centos/7/storage/x86_64/gluster-5/glusterfs-server… http://mirror.centos.org/centos/7/storage/x86_64/gluster-5/python2-gluster-… ]] + eval sync_needed=true ++ sync_needed=true + return + [[ -n true ]] + install_repo_pubkey glusterfs-5-el7 jenkins/data/mirrors-reposync.conf + local repo_name=glusterfs-5-el7 + local reposync_conf=jenkins/data/mirrors-reposync.conf + local gpg_key_file ++ sed -nr -e '/\[glusterfs-5-el7]/{ :loop; s#^gpgkey\s*=\s*file://(.*)$#\1#p; n; /^\[.*\]$/q ; b loop }' jenkins/data/mirrors-reposync.conf + gpg_key_file=/etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-SIG-Storage + [[ -n /etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-SIG-Storage ]] + [[ -r /etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-SIG-Storage ]] + sudo /usr/bin/rpmkeys --import /etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-SIG-Storage + echo 'Resyncing repo: glusterfs-5-el7' Resyncing repo: glusterfs-5-el7 + perform_yum_sync glusterfs-5-el7 x86_64 jenkins/data/mirrors-reposync.conf + local repo_name=glusterfs-5-el7 + local repo_archs=x86_64 + local reposync_conf=jenkins/data/mirrors-reposync.conf + local repo_mp + local repo_comps + repo_mp=/var/www/html/repos/yum/glusterfs-5-el7/base ++ IFS=, ++ echo x86_64 + for arch in '$(IFS=,; echo $repo_archs)' + echo 'Syncing yum repo glusterfs-5-el7 for arch: x86_64' Syncing yum repo glusterfs-5-el7 for arch: x86_64 + run_reposync glusterfs-5-el7 x86_64 jenkins/data/mirrors-reposync.conf --downloadcomps --gpgcheck + local repo_name=glusterfs-5-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=glusterfs-5-el7 --arch=x86_64 --cachedir=/home/jenkins/mirrors_cache --download_path=/var/www/html/repos/yum/glusterfs-5-el7/base --norepopath --newest-only --downloadcomps --gpgcheck glusterfs-5.3-1.el7.x86_64.rpm FAILED (1/16): glusterfs-5.3-1.el 0% [ ] 0.0 B/s | 0 B --:-- ETA (1/16): glusterfs-api-5.3-1.el7.x86_64.rpm | 107 kB 00:00 glusterfs-api-devel-5.3-1.el7. FAILED (2/16): glusterfs-api-deve 0% [ ] 0.0 B/s | 0 B --:-- ETA glusterfs-cli-5.3-1.el7.x86_64 FAILED (2/16): glusterfs-cli-5.3- 0% [ ] 0.0 B/s | 0 B --:-- ETA glusterfs-client-xlators-5.3-1 FAILED (2/16): glusterfs-client-x 0% [ ] 0.0 B/s | 0 B --:-- ETA glusterfs-cloudsync-plugins-5. FAILED (2/16): glusterfs-cloudsyn 0% [ ] 0.0 B/s | 0 B --:-- ETA glusterfs-devel-5.3-1.el7.x86_ FAILED (2/16): glusterfs-devel-5. 0% [ ] 0.0 B/s | 0 B --:-- ETA glusterfs-events-5.3-1.el7.x86 FAILED (2/16): glusterfs-events-5 0% [ ] 0.0 B/s | 0 B --:-- ETA glusterfs-extra-xlators-5.3-1. FAILED (2/16): glusterfs-extra-xl 0% [ ] 0.0 B/s | 0 B --:-- ETA glusterfs-fuse-5.3-1.el7.x86_6 FAILED (2/16): glusterfs-fuse-5.3 0% [ ] 0.0 B/s | 0 B --:-- ETA glusterfs-geo-replication-5.3- FAILED (2/16): glusterfs-geo-repl 0% [ ] 0.0 B/s | 0 B --:-- ETA glusterfs-libs-5.3-1.el7.x86_6 FAILED (2/16): glusterfs-libs-5.3 0% [ ] 0.0 B/s | 0 B --:-- ETA glusterfs-rdma-5.3-1.el7.x86_6 FAILED (2/16): glusterfs-rdma-5.3 0% [ ] 0.0 B/s | 0 B --:-- ETA glusterfs-resource-agents-5.3- FAILED (2/16): glusterfs-resource 0% [ ] 0.0 B/s | 0 B --:-- ETA glusterfs-server-5.3-1.el7.x86 FAILED (2/16): glusterfs-server-5 0% [ ] 0.0 B/s | 0 B --:-- ETA python2-gluster-5.3-1.el7.x86_ FAILED (2/16): python2-gluster-5. 0% [ ] 0.0 B/s | 0 B --:-- ETA glusterfs-libs-5.3-1.el7.x86_64: [Errno 256] No more mirrors to try. glusterfs-client-xlators-5.3-1.el7.x86_64: [Errno 256] No more mirrors to try. glusterfs-cloudsync-plugins-5.3-1.el7.x86_64: [Errno 256] No more mirrors to try. glusterfs-events-5.3-1.el7.x86_64: [Errno 256] No more mirrors to try. glusterfs-server-5.3-1.el7.x86_64: [Errno 256] No more mirrors to try. python2-gluster-5.3-1.el7.x86_64: [Errno 256] No more mirrors to try. glusterfs-extra-xlators-5.3-1.el7.x86_64: [Errno 256] No more mirrors to try. glusterfs-rdma-5.3-1.el7.x86_64: [Errno 256] No more mirrors to try. glusterfs-api-devel-5.3-1.el7.x86_64: [Errno 256] No more mirrors to try. glusterfs-resource-agents-5.3-1.el7.noarch: [Errno 256] No more mirrors to try. glusterfs-cli-5.3-1.el7.x86_64: [Errno 256] No more mirrors to try. glusterfs-5.3-1.el7.x86_64: [Errno 256] No more mirrors to try. glusterfs-fuse-5.3-1.el7.x86_64: [Errno 256] No more mirrors to try. glusterfs-geo-replication-5.3-1.el7.x86_64: [Errno 256] No more mirrors to try. glusterfs-devel-5.3-1.el7.x86_64: [Errno 256] No more mirrors to try. Removing glusterfs-5.3-1.el7.x86_64.rpm due to failed signature check. Removing glusterfs-api-devel-5.3-1.el7.x86_64.rpm due to failed signature check. Removing glusterfs-cli-5.3-1.el7.x86_64.rpm due to failed signature check. Removing glusterfs-client-xlators-5.3-1.el7.x86_64.rpm due to failed signature check. Removing glusterfs-cloudsync-plugins-5.3-1.el7.x86_64.rpm due to failed signature check. Removing glusterfs-devel-5.3-1.el7.x86_64.rpm due to failed signature check. Removing glusterfs-events-5.3-1.el7.x86_64.rpm due to failed signature check. Removing glusterfs-extra-xlators-5.3-1.el7.x86_64.rpm due to failed signature check. Removing glusterfs-fuse-5.3-1.el7.x86_64.rpm due to failed signature check. Removing glusterfs-geo-replication-5.3-1.el7.x86_64.rpm due to failed signature check. Removing glusterfs-libs-5.3-1.el7.x86_64.rpm due to failed signature check. Removing glusterfs-rdma-5.3-1.el7.x86_64.rpm due to failed signature check. Removing glusterfs-resource-agents-5.3-1.el7.noarch.rpm due to failed signature check. Removing glusterfs-server-5.3-1.el7.x86_64.rpm due to failed signature check. Removing python2-gluster-5.3-1.el7.x86_64.rpm due to failed signature check. Build step 'Execute shell' marked build as failure

1 1

[JIRA] (OVIRT-2658) Error when fetching upstream sources
by Dafna Ron (oVirt JIRA) 21 Jan '19

21 Jan '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2658?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2658: ---------------------------------- The error in the check-patch is: {noformat} Yum-utils package has been deprecated, use dnf instead. See 'man yum2dnf' for more information. Cannot retrieve metalink for repository: updates/28/x86_64. Please verify its path and try again Took 73 seconds =================================== ock-chroot><mock-chroot> sh-4.4# res=${PIPESTATUS[0]} ock-chroot><mock-chroot> sh-4.4# mv "$logdir" "./mock_logs.xB3Fe6uq" ock-chroot><mock-chroot> sh-4.4# if [[ "$(find . -uid 0 -print -quit)" != '' ]]; the en > chown -R "1012:$runner_GID" . > fi ock-chroot><mock-chroot> sh-4.4# exit $res logout Finish: shell {noformat} I am not sure what is the nightly patch. if its a different ticket? > Error when fetching upstream sources > ------------------------------------ > > Key: OVIRT-2658 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2658 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Shirly Radco > Assignee: infra > > Hi, > Please see my check patch > https://jenkins.ovirt.org/job/ovirt-engine-metrics_standard-check-patch/123… > Can you please check what is the issue? > Also, I still did not get a nightly patch for the upstream sources updates. > Thanks, > -- > SHIRLY RADCO > BI SENIOR SOFTWARE ENGINEER > Red Hat Israel <https://www.redhat.com/> > <https://red.ht/sig> > TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2658) Error when fetching upstream sources
by Shirly Radco (oVirt JIRA) 21 Jan '19

21 Jan '19

Shirly Radco created OVIRT-2658: ----------------------------------- Summary: Error when fetching upstream sources Key: OVIRT-2658 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2658 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Shirly Radco Assignee: infra Hi, Please see my check patch https://jenkins.ovirt.org/job/ovirt-engine-metrics_standard-check-patch/123… Can you please check what is the issue? Also, I still did not get a nightly patch for the upstream sources updates. Thanks, -- SHIRLY RADCO BI SENIOR SOFTWARE ENGINEER Red Hat Israel <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[CQ]: a395b96 (ovirt-ansible-hosted-engine-setup) failed "ovirt-master" system tests
by oVirt Jenkins 21 Jan '19

21 Jan '19

Change a395b96 (ovirt-ansible-hosted-engine-setup) 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-ansible-hosted-engine-setup/commit/a395b9682… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12386/

1 0

[JIRA] (OVIRT-2656) Upstream-sources trigger for ovirt-engine-metrics does not work
by Shirly Radco (oVirt JIRA) 21 Jan '19

21 Jan '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2656?page=com.atlassian.jira.… ] Shirly Radco commented on OVIRT-2656: ------------------------------------- Hi, Is this issue fixed or still at work? Thanks, -- SHIRLY RADCO BI SENIOR SOFTWARE ENGINEER Red Hat Israel <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> On Sun, Jan 20, 2019 at 12:15 PM Daniel Belenky <dbelenky(a)redhat.com> wrote: > I'm checking > > On Sun, Jan 20, 2019 at 10:30 AM Shirly Radco <sradco(a)redhat.com> wrote: > >> >> -- >> >> SHIRLY RADCO >> >> BI SENIOR SOFTWARE ENGINEER >> >> Red Hat Israel <https://www.redhat.com/> >> <https://red.ht/sig> >> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> >> > > > -- > > DANIEL BELENKY > > Upstream-sources trigger for ovirt-engine-metrics does not work > --------------------------------------------------------------- > > Key: OVIRT-2656 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2656 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Shirly Radco > Assignee: infra > > -- > SHIRLY RADCO > BI SENIOR SOFTWARE ENGINEER > Red Hat Israel <https://www.redhat.com/> > <https://red.ht/sig> > TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2657) Please import ovirt-engine-sdk-go in oVirt organization
by Eyal Edri (oVirt JIRA) 21 Jan '19

21 Jan '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2657?page=com.atlassian.jira.… ] Eyal Edri updated OVIRT-2657: ----------------------------- Resolution: Fixed Status: Done (was: To Do) I've created the repo under oVirt org and gave <majunjiev(a)gmail.com> admin rights. Feel free to import the code from the private repo to new one under oVirt. > Please import ovirt-engine-sdk-go in oVirt organization > ------------------------------------------------------- > > Key: OVIRT-2657 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2657 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > Hi, > ovirt-engine-sdk-go project has been accepted as incubator project under > oVirt organization. > Can you please import it granting Joey Ma <majunjiev(a)gmail.com> maintainer > privileges for it? Joey has been already added as developer to oVirt team > in github with https://ovirt-jira.atlassian.net/browse/OVIRT-2460 > The project is currently in github at > https://github.com/imjoey/ovirt-engine-sdk-go > Joey, once the project is imported, please ensure to create jenkins jobs > for testing and building it and add builds to master and 4.3 change queues. > Thanks, > -- > SANDRO BONAZZOLA > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2657) Please import ovirt-engine-sdk-go in oVirt organization
by sbonazzo (oVirt JIRA) 21 Jan '19

21 Jan '19

sbonazzo created OVIRT-2657: ------------------------------- Summary: Please import ovirt-engine-sdk-go in oVirt organization Key: OVIRT-2657 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2657 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: sbonazzo Assignee: infra Hi, ovirt-engine-sdk-go project has been accepted as incubator project under oVirt organization. Can you please import it granting Joey Ma <majunjiev(a)gmail.com> maintainer privileges for it? Joey has been already added as developer to oVirt team in github with https://ovirt-jira.atlassian.net/browse/OVIRT-2460 The project is currently in github at https://github.com/imjoey/ovirt-engine-sdk-go Joey, once the project is imported, please ensure to create jenkins jobs for testing and building it and add builds to master and 4.3 change queues. Thanks, -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

oVirt infra daily report - unstable production jobs - 711
by jenkins＠jenkins.phx.ovirt.org 21 Jan '19

21 Jan '19

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - http://jenkins.ovirt.org/job/system_jenkins-report/711//artifact/exported-a… Cheers, Jenkins

1 0

[JIRA] (OVIRT-2556) kubevirt test runs and nested docker issue
by Eyal Edri (oVirt JIRA) 20 Jan '19

20 Jan '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2556?page=com.atlassian.jira.… ] Eyal Edri closed OVIRT-2556. ---------------------------- Resolution: Cannot Reproduce (was: Fixed) No replies on the ticket, please reopen if still relevant > kubevirt test runs and nested docker issue > ------------------------------------------ > > Key: OVIRT-2556 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2556 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Roman Mohr > Assignee: infra > Priority: High > > Hi, > we see a lot of tests which fail with during the setup [1] : > ``` > /usr/bin/docker-current: Error response from daemon: grpc: the > connection is unavailable. > time="2018-10-23T07:17:55Z" level=error msg="error getting events from > daemon: context canceled" > ``` > It looks like the docker daemon may not run properly. > Best Regards, > Roman > [1] https://jenkins.ovirt.org/job/kubevirt_kubevirt_standard-check-pr/2344//art… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

Build failed in Jenkins: system-sync_mirrors-fedora-updates-fc27-x86_64 #1279
by jenkins＠jenkins.phx.ovirt.org 20 Jan '19

20 Jan '19

See <http://jenkins.ovirt.org/job/system-sync_mirrors-fedora-updates-fc27-x86_64…> Changes: [Evgheni Dereveanchin] move jenkins check_patch from fc27 to fc29 [Ehud Yonasi] mirror_sync: add gluster5 to mirrors. ------------------------------------------ Started by timer [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-fedora-updates-fc27-x86_64…> > 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 http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* --prune > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision 605cf461270dd03c872bdc64c38b9f0827aeca6e (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 605cf461270dd03c872bdc64c38b9f0827aeca6e Commit message: "mirror_sync: add gluster5 to mirrors." > git rev-list --no-walk e8b9034e509402e9e9ce1073efc73c70a8c53793 # timeout=10 [system-sync_mirrors-fedora-updates-fc27-x86_64] $ /bin/bash -xe /tmp/jenkins7982671899973815369.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror fedora-updates-fc27 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 fedora-updates-fc27 x86_64 jenkins/data/mirrors-reposync.conf + local command=resync_yum_mirror + command_args=("${@:2}") + local command_args + cmd_resync_yum_mirror fedora-updates-fc27 x86_64 jenkins/data/mirrors-reposync.conf + local repo_name=fedora-updates-fc27 + 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 fedora-updates-fc27 yum + local repo_name=fedora-updates-fc27 + local repo_type=yum + sudo install -o jenkins -d /var/www/html/repos/yum /var/www/html/repos/yum/fedora-updates-fc27 /var/www/html/repos/yum/fedora-updates-fc27/base + check_yum_sync_needed fedora-updates-fc27 x86_64 jenkins/data/mirrors-reposync.conf sync_needed + local repo_name=fedora-updates-fc27 + 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/fedora-updates-fc27 ++ IFS=, ++ echo x86_64 + for arch in '$(IFS=,; echo $repo_archs)' ++ run_reposync fedora-updates-fc27 x86_64 jenkins/data/mirrors-reposync.conf --urls --quiet ++ local repo_name=fedora-updates-fc27 ++ 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=fedora-updates-fc27 --arch=x86_64 --cachedir=/home/jenkins/mirrors_cache --download_path=/var/www/html/repos/yum/fedora-updates-fc27/base --norepopath --newest-only --urls --quiet Traceback (most recent call last): File "/usr/bin/reposync", line 343, in <module> main() File "/usr/bin/reposync", line 175, in main my.doRepoSetup() File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 681, in doRepoSetup return self._getRepos(thisrepo, True) File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 721, in _getRepos self._repos.doSetup(thisrepo) File "/usr/lib/python2.7/site-packages/yum/repos.py", line 157, in doSetup self.retrieveAllMD() File "/usr/lib/python2.7/site-packages/yum/repos.py", line 88, in retrieveAllMD dl = repo._async and repo._commonLoadRepoXML(repo) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1474, in _commonLoadRepoXML if self._latestRepoXML(local): File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1452, in _latestRepoXML repomd = self.metalink_data.repomd File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 918, in <lambda> metalink_data = property(fget=lambda self: self._getMetalink(), File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 914, in _getMetalink self._metalink = metalink.MetaLinkRepoMD(self.metalink_filename) File "/usr/lib/python2.7/site-packages/yum/metalink.py", line 189, in __init__ raise MetaLinkRepoErrorParseFail, "File %s is not XML" % filename yum.metalink.MetaLinkRepoErrorParseFail: File /home/jenkins/mirrors_cache/epel-el7/metalink.xml is not XML + reposync_out='Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64 error was 16: error opening file from https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64, IOError: [Errno 2] No such file or directory: '\''/home/jenkins/mirrors_cache/epel-el7/metalink.xml.tmp'\''' Build step 'Execute shell' marked build as failure

1 1

[JIRA] (OVIRT-2631) [VDSM] Build fail with "Curl error (28): Timeout was reached for..."
by Eyal Edri (oVirt JIRA) 20 Jan '19

20 Jan '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2631?page=com.atlassian.jira.… ] Eyal Edri updated OVIRT-2631: ----------------------------- Resolution: Cannot Reproduce Status: Done (was: To Do) looks like a network outage that caused this issue, which isn't happening anymore > [VDSM] Build fail with "Curl error (28): Timeout was reached for..." > -------------------------------------------------------------------- > > Key: OVIRT-2631 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2631 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: Evgheni Dereveanchin > > Looks like creating mock env fail because of slow network. > Can we have local mirror to avoid such issues? > Error: > # /usr/bin/dnf --installroot > /var/lib/mock/fedora-28-x86_64-4a1ad1766b02e7fc37cf465ffb164e2f-15798/root/ > --releasever 28 --disableplugin=local --setopt=deltarpm=False install > @buildsys-build autoconf automake createrepo dnf dnf-utils gdb git > iproute-tc libguestfs-tools-c libselinux-python3 libvirt-python3 lshw > make mom openvswitch ovirt-imageio-common policycoreutils-python > python2-augeas python2-blivet1 python2-coverage python2-dateutil > python2-dbus python2-decorator python2-devel python2-dmidecode > python2-enum34 python2-inotify python2-ioprocess python2-ipaddress > python2-magic python2-mock python2-netaddr python2-pthreading > python2-pyudev python2-pyyaml python2-requests python2-setuptools > python2-six python2-subprocess32 python3-PyYAML python3-augeas > python3-coverage python3-dateutil python3-dbus python3-decorator > python3-devel python3-magic python3-netaddr python3-nose > python3-pyudev python3-six python3-yaml rpm-build > ... > Transaction Summary > ================================================================================ > Install 675 Packages > Total download size: 424 M > Installed size: 1.5 G > Downloading Packages: > ... > (530/675): rest-0.8.1-2.fc28.x86_64.rpm 211 kB/s | 69 kB 00:00 > (531/675): libXau-1.0.8-11.fc28.x86_64.rpm 193 kB/s | 34 kB 00:00 > (532/675): libogg-1.3.2-10.fc28.x86_64.rpm 147 kB/s | 30 kB 00:00 > [MIRROR] gtk3-3.22.30-1.fc28.x86_64.rpm: Curl error (28): Timeout was > reached for http://mirrors.phx.ovirt.org/repos/yum/fedora-base-fc28/base/Packages/g/gtk… > [Operation too slow. Less than 1000 bytes/sec transferred the last 30 > seconds] > [FAILED] gtk3-3.22.30-1.fc28.x86_64.rpm: Curl error (28): Timeout was > reached for http://mirrors.phx.ovirt.org/repos/yum/fedora-base-fc28/base/Packages/g/gtk… > [Operation too slow. Less than 1000 bytes/sec transferred the last 30 > seconds] > Error: Error downloading packages: > Curl error (28): Timeout was reached for > http://mirrors.phx.ovirt.org/repos/yum/fedora-base-fc28/base/Packages/g/gtk… > [Operation too slow. Less than 1000 bytes/sec transferred the last 30 > seconds] > Build: > https://jenkins.ovirt.org/blue/rest/organizations/jenkins/pipelines/vdsm_st… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2644) [VDSM] Error in CI check-patch linter
by Eyal Edri (oVirt JIRA) 20 Jan '19

20 Jan '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2644?page=com.atlassian.jira.… ] Eyal Edri updated OVIRT-2644: ----------------------------- Resolution: Won't Fix Status: Done (was: To Do) seems to be related to broken copr repos, not in our control. either replace the copr repos with something more stable or you can try to use oVirt mirrors if the same pkgs appear there > [VDSM] Error in CI check-patch linter > ------------------------------------- > > Key: OVIRT-2644 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2644 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Daniel Erez > Assignee: infra > > Hi, > I'm encountering a CI failure in the following test: > https://jenkins.ovirt.org/job/vdsm_standard-check-patch/1236/artifact/check… > ... > Start(bootstrap): yum install > ERROR: Command failed: > # /usr/bin/yum --installroot > /var/lib/mock/fedora-28-x86_64-4a1ad1766b02e7fc37cf465ffb164e2f-bootstrap-23494/root/ > --releasever 28 install dnf dnf-plugins-core distribution-gpg-keys > --setopt=tsflags=nocontexts > Failed to set locale, defaulting to C > https://copr-be.cloud.fedoraproject.org/results/rhawalsh/dm-vdo/fedora-28-x…: > [Errno 12] Timeout on > https://copr-be.cloud.fedoraproject.org/results/rhawalsh/dm-vdo/fedora-28-x…: > (28, 'Operation timed out after 30001 milliseconds with 0 out of 0 bytes > received') > Trying other mirror. > https://copr-be.cloud.fedoraproject.org/results/rhawalsh/dm-vdo/fedora-28-x…: > [Errno 12] Timeout on > https://copr-be.cloud.fedoraproject.org/results/rhawalsh/dm-vdo/fedora-28-x…: > (28, 'Operation timed out after 30001 milliseconds with 0 out of 0 bytes > received') > Trying other mirror. > ... -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2645) [VDSM] Tests mounting loop devices fail randomly again
by Eyal Edri (oVirt JIRA) 20 Jan '19

20 Jan '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2645?page=com.atlassian.jira.… ] Eyal Edri updated OVIRT-2645: ----------------------------- Resolution: Fixed Status: Done (was: To Do) please reopen if issue wasn't solved > [VDSM] Tests mounting loop devices fail randomly again > ------------------------------------------------------ > > Key: OVIRT-2645 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2645 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > We had this issue few years ago, and it was solved when we started > to create loop devices to the slave in check-path.sh. > Before we run the tests, we created loop devices. Looking at the log, we > had 5 > nodes and we added 3 nodes - this is typical log. > + create_loop_devices 8 > + local last=7 > + local min > ++ seq 0 7 > + for min in '`seq 0 $last`' > + local name=/dev/loop0 > + '[' '!' -e /dev/loop0 ']' > + for min in '`seq 0 $last`' > + local name=/dev/loop1 > + '[' '!' -e /dev/loop1 ']' > + for min in '`seq 0 $last`' > + local name=/dev/loop2 > + '[' '!' -e /dev/loop2 ']' > + for min in '`seq 0 $last`' > + local name=/dev/loop3 > + '[' '!' -e /dev/loop3 ']' > + for min in '`seq 0 $last`' > + local name=/dev/loop4 > + '[' '!' -e /dev/loop4 ']' > + for min in '`seq 0 $last`' > + local name=/dev/loop5 > + '[' '!' -e /dev/loop5 ']' > + mknod --mode 0666 /dev/loop5 b 7 5 > + for min in '`seq 0 $last`' > + local name=/dev/loop6 > + '[' '!' -e /dev/loop6 ']' > + mknod --mode 0666 /dev/loop6 b 7 6 > + for min in '`seq 0 $last`' > + local name=/dev/loop7 > + '[' '!' -e /dev/loop7 ']' > + mknod --mode 0666 /dev/loop7 b 7 7 > But mounting images failed later as you can see bellow. > Failed build: > https://jenkins.ovirt.org/blue/rest/organizations/jenkins/pipelines/vdsm_st… > The same tests run fine in travis inside a container: > https://travis-ci.org/nirs/vdsm/jobs/471920126 > Anyone has idea why mounting fail randomly in Jenkins slaves, and how we > can fix this issue? > ====================================================================== > ERROR: Tests mkimage.mkFloppyFs creating an image and checking its content. > ---------------------------------------------------------------------- > Traceback (most recent call last): > File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/testlib.py", > line 142, in wrapper > return f(self, *args) > File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/testValidation.py", > line 194, in wrapper > return f(*args, **kwargs) > File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/mkimage_test.py", > line 211, in test_mkFloppyFs > floppy = mkimage.mkFloppyFs("vmId_floppy", self.files, label) > File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/vdsm/mkimage.py", > line 137, in mkFloppyFs > injectFilesToFs(floppy, files, 'vfat') > File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/vdsm/mkimage.py", > line 113, in injectFilesToFs > m.mount(mntOpts='loop', vfstype=fstype) > File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/vdsm/storage/mount.py", > line 207, in mount > cgroup=cgroup) > File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/vdsm/storage/mount.py", > line 277, in _mount > _runcmd(cmd) > File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/vdsm/storage/mount.py", > line 305, in _runcmd > raise MountError(rc, b";".join((out, err))) > MountError: (32, ';mount: > /tmp/vdsm-mkimage-testsxtGqen/images/vmId_floppy.e83b907eacb704d3942b8cab79561d2a.img: > failed to setup loop device: No such file or directory\n') > -------------------- >> begin captured logging << -------------------- > 2019-01-08 23:46:19,720 DEBUG (MainThread) [root] /usr/bin/taskset > --cpu-list 0-1 /usr/sbin/mkfs.msdos -C > /tmp/vdsm-mkimage-testsxtGqen/images/vmId_floppy.e83b907eacb704d3942b8cab79561d2a.img > 1440 -n FSLABEL (cwd None) (commands:198) > 2019-01-08 23:46:19,729 DEBUG (MainThread) [root] SUCCESS: <err> = ''; > <rc> = 0 (commands:219) > 2019-01-08 23:46:19,731 INFO (MainThread) [storage.Mount] mounting > /tmp/vdsm-mkimage-testsxtGqen/images/vmId_floppy.e83b907eacb704d3942b8cab79561d2a.img > at /tmp/tmpSejvmr (mount:204) > 2019-01-08 23:46:19,731 DEBUG (MainThread) [root] /usr/bin/taskset > --cpu-list 0-1 /usr/bin/mount -t vfat -o loop > /tmp/vdsm-mkimage-testsxtGqen/images/vmId_floppy.e83b907eacb704d3942b8cab79561d2a.img > /tmp/tmpSejvmr (cwd None) (commands:198) > 2019-01-08 23:46:19,743 DEBUG (MainThread) [root] FAILED: <err> = > 'mount: /tmp/vdsm-mkimage-testsxtGqen/images/vmId_floppy.e83b907eacb704d3942b8cab79561d2a.img: > failed to setup loop device: No such file or directory\n'; <rc> = 32 > (commands:219) > --------------------- >> end captured logging << --------------------- > ====================================================================== > ERROR: Tests mkimage.mkFloppyFs creating an image and checking its content. > ---------------------------------------------------------------------- > Traceback (most recent call last): > File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/testlib.py", > line 142, in wrapper > return f(self, *args) > File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/testValidation.py", > line 194, in wrapper > return f(*args, **kwargs) > File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/mkimage_test.py", > line 211, in test_mkFloppyFs > floppy = mkimage.mkFloppyFs("vmId_floppy", self.files, label) > File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/vdsm/mkimage.py", > line 137, in mkFloppyFs > injectFilesToFs(floppy, files, 'vfat') > File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/vdsm/mkimage.py", > line 113, in injectFilesToFs > m.mount(mntOpts='loop', vfstype=fstype) > File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/vdsm/storage/mount.py", > line 207, in mount > cgroup=cgroup) > File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/vdsm/storage/mount.py", > line 277, in _mount > _runcmd(cmd) > File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/vdsm/storage/mount.py", > line 305, in _runcmd > raise MountError(rc, b";".join((out, err))) > MountError: (32, ';mount: > /tmp/vdsm-mkimage-testsnlTJrM/images/vmId_floppy.4f26a597fe7f8a916fd808350e62bdc0.img: > failed to setup loop device: No such file or directory\n') > -------------------- >> begin captured logging << -------------------- > 2019-01-08 23:46:19,750 DEBUG (MainThread) [root] /usr/bin/taskset > --cpu-list 0-1 /usr/sbin/mkfs.msdos -C > /tmp/vdsm-mkimage-testsnlTJrM/images/vmId_floppy.4f26a597fe7f8a916fd808350e62bdc0.img > 1440 (cwd None) (commands:198) > 2019-01-08 23:46:19,759 DEBUG (MainThread) [root] SUCCESS: <err> = ''; > <rc> = 0 (commands:219) > 2019-01-08 23:46:19,761 INFO (MainThread) [storage.Mount] mounting > /tmp/vdsm-mkimage-testsnlTJrM/images/vmId_floppy.4f26a597fe7f8a916fd808350e62bdc0.img > at /tmp/tmpiDcstj (mount:204) > 2019-01-08 23:46:19,762 DEBUG (MainThread) [root] /usr/bin/taskset > --cpu-list 0-1 /usr/bin/mount -t vfat -o loop > /tmp/vdsm-mkimage-testsnlTJrM/images/vmId_floppy.4f26a597fe7f8a916fd808350e62bdc0.img > /tmp/tmpiDcstj (cwd None) (commands:198) > 2019-01-08 23:46:19,773 DEBUG (MainThread) [root] FAILED: <err> = > 'mount: /tmp/vdsm-mkimage-testsnlTJrM/images/vmId_floppy.4f26a597fe7f8a916fd808350e62bdc0.img: > failed to setup loop device: No such file or directory\n'; <rc> = 32 > (commands:219) > --------------------- >> end captured logging << --------------------- > ====================================================================== > ERROR: Test that mkimage.mkFloppyFs handle situation when the floppy image > ---------------------------------------------------------------------- > Traceback (most recent call last): > File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/testlib.py", > line 142, in wrapper > return f(self, *args) > File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/testValidation.py", > line 194, in wrapper > return f(*args, **kwargs) > File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/mkimage_test.py", > line 230, in test_mkFloppyFs_overwrite > floppy = mkimage.mkFloppyFs("vmId_floppy", self.files, label) > File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/vdsm/mkimage.py", > line 137, in mkFloppyFs > injectFilesToFs(floppy, files, 'vfat') > File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/vdsm/mkimage.py", > line 113, in injectFilesToFs > m.mount(mntOpts='loop', vfstype=fstype) > File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/vdsm/storage/mount.py", > line 207, in mount > cgroup=cgroup) > File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/vdsm/storage/mount.py", > line 277, in _mount > _runcmd(cmd) > File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/vdsm/storage/mount.py", > line 305, in _runcmd > raise MountError(rc, b";".join((out, err))) > MountError: (32, ';mount: > /tmp/vdsm-mkimage-testslSTYsV/images/vmId_floppy.3af4c566a929c30f605091dd7a5b7deb.img: > failed to setup loop device: No such file or directory\n') > -------------------- >> begin captured logging << -------------------- > 2019-01-08 23:46:19,779 DEBUG (MainThread) [root] /usr/bin/taskset > --cpu-list 0-1 /usr/sbin/mkfs.msdos -C > /tmp/vdsm-mkimage-testslSTYsV/images/vmId_floppy.3af4c566a929c30f605091dd7a5b7deb.img > 1440 -n FSLABEL (cwd None) (commands:198) > 2019-01-08 23:46:19,789 DEBUG (MainThread) [root] SUCCESS: <err> = ''; > <rc> = 0 (commands:219) > 2019-01-08 23:46:19,790 INFO (MainThread) [storage.Mount] mounting > /tmp/vdsm-mkimage-testslSTYsV/images/vmId_floppy.3af4c566a929c30f605091dd7a5b7deb.img > at /tmp/tmpX4UcrB (mount:204) > 2019-01-08 23:46:19,791 DEBUG (MainThread) [root] /usr/bin/taskset > --cpu-list 0-1 /usr/bin/mount -t vfat -o loop > /tmp/vdsm-mkimage-testslSTYsV/images/vmId_floppy.3af4c566a929c30f605091dd7a5b7deb.img > /tmp/tmpX4UcrB (cwd None) (commands:198) > 2019-01-08 23:46:19,803 DEBUG (MainThread) [root] FAILED: <err> = > 'mount: /tmp/vdsm-mkimage-testslSTYsV/images/vmId_floppy.3af4c566a929c30f605091dd7a5b7deb.img: > failed to setup loop device: No such file or directory\n'; <rc> = 32 > (commands:219) > --------------------- >> end captured logging << --------------------- > ====================================================================== > ERROR: Test that mkimage.mkFloppyFs handle situation when the floppy image > ---------------------------------------------------------------------- > Traceback (most recent call last): > File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/testlib.py", > line 142, in wrapper > return f(self, *args) > File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/testValidation.py", > line 194, in wrapper > return f(*args, **kwargs) > File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/mkimage_test.py", > line 230, in test_mkFloppyFs_overwrite > floppy = mkimage.mkFloppyFs("vmId_floppy", self.files, label) > File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/vdsm/mkimage.py", > line 137, in mkFloppyFs > injectFilesToFs(floppy, files, 'vfat') > File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/vdsm/mkimage.py", > line 113, in injectFilesToFs > m.mount(mntOpts='loop', vfstype=fstype) > File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/vdsm/storage/mount.py", > line 207, in mount > cgroup=cgroup) > File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/vdsm/storage/mount.py", > line 277, in _mount > _runcmd(cmd) > File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/vdsm/storage/mount.py", > line 305, in _runcmd > raise MountError(rc, b";".join((out, err))) > MountError: (32, ';mount: > /tmp/vdsm-mkimage-testsOy036Z/images/vmId_floppy.7d36c87a8c8c6c8ad83dc972edfcb3cc.img: > failed to setup loop device: No such file or directory\n') > -------------------- >> begin captured logging << -------------------- > 2019-01-08 23:46:19,809 DEBUG (MainThread) [root] /usr/bin/taskset > --cpu-list 0-1 /usr/sbin/mkfs.msdos -C > /tmp/vdsm-mkimage-testsOy036Z/images/vmId_floppy.7d36c87a8c8c6c8ad83dc972edfcb3cc.img > 1440 (cwd None) (commands:198) > 2019-01-08 23:46:19,821 DEBUG (MainThread) [root] SUCCESS: <err> = ''; > <rc> = 0 (commands:219) > 2019-01-08 23:46:19,822 INFO (MainThread) [storage.Mount] mounting > /tmp/vdsm-mkimage-testsOy036Z/images/vmId_floppy.7d36c87a8c8c6c8ad83dc972edfcb3cc.img > at /tmp/tmpJNTkWb (mount:204) > 2019-01-08 23:46:19,823 DEBUG (MainThread) [root] /usr/bin/taskset > --cpu-list 0-1 /usr/bin/mount -t vfat -o loop > /tmp/vdsm-mkimage-testsOy036Z/images/vmId_floppy.7d36c87a8c8c6c8ad83dc972edfcb3cc.img > /tmp/tmpJNTkWb (cwd None) (commands:198) > 2019-01-08 23:46:19,836 DEBUG (MainThread) [root] FAILED: <err> = > 'mount: /tmp/vdsm-mkimage-testsOy036Z/images/vmId_floppy.7d36c87a8c8c6c8ad83dc972edfcb3cc.img: > failed to setup loop device: No such file or directory\n'; <rc> = 32 > (commands:219) > --------------------- >> end captured logging << --------------------- > ====================================================================== > ERROR: Tests mkimage.mkIsoFs creating an image and checking its content > ---------------------------------------------------------------------- > Traceback (most recent call last): > File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/testlib.py", > line 142, in wrapper > return f(self, *args) > File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/testValidation.py", > line 194, in wrapper > return f(*args, **kwargs) > File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/mkimage_test.py", > line 252, in test_mkIsoFs > m.mount(mntOpts='loop') > File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/vdsm/storage/mount.py", > line 207, in mount > cgroup=cgroup) > File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/vdsm/storage/mount.py", > line 277, in _mount > _runcmd(cmd) > File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/vdsm/storage/mount.py", > line 305, in _runcmd > raise MountError(rc, b";".join((out, err))) > MountError: (32, ';mount: > /tmp/vdsm-mkimage-testsS16Km7/images/vmId_iso.1d6daeff12530405cbf56a511812e581.img: > failed to setup loop device: No such file or directory\n') > -------------------- >> begin captured logging << > --------------------Coverage.py warning: Module > /home/jenkins/workspace/vdsm_standard-check-patch/vdsm/vdsm was never > imported. (module-not-imported) > 2019-01-08 23:46:19,851 DEBUG (MainThread) [root] /usr/bin/taskset > --cpu-list 0-1 /usr/bin/mkisofs -R -J -o > /tmp/vdsm-mkimage-testsS16Km7/images/vmId_iso.1d6daeff12530405cbf56a511812e581.img > -V fslabel /tmp/tmphPPnKt (cwd None) (commands:198) > 2019-01-08 23:46:19,882 DEBUG (MainThread) [root] SUCCESS: <err> = > 'Total translation table size: 0\nTotal rockridge attributes bytes: > 1796\nTotal directory bytes: 8192\nPath table size(bytes): 64\nMax brk > space used 22000\n199 extents written (0 MB)\n'; <rc> = 0 > (commands:219) > 2019-01-08 23:46:19,885 INFO (MainThread) [storage.Mount] mounting > /tmp/vdsm-mkimage-testsS16Km7/images/vmId_iso.1d6daeff12530405cbf56a511812e581.img > at /tmp/vdsm-mkimage-testsS16Km7/work (mount:204) > 2019-01-08 23:46:19,886 DEBUG (MainThread) [root] /usr/bin/taskset > --cpu-list 0-1 /usr/bin/mount -o loop > /tmp/vdsm-mkimage-testsS16Km7/images/vmId_iso.1d6daeff12530405cbf56a511812e581.img > /tmp/vdsm-mkimage-testsS16Km7/work (cwd None) (commands:198) > 2019-01-08 23:46:19,898 DEBUG (MainThread) [root] FAILED: <err> = > 'mount: /tmp/vdsm-mkimage-testsS16Km7/images/vmId_iso.1d6daeff12530405cbf56a511812e581.img: > failed to setup loop device: No such file or directory\n'; <rc> = 32 > (commands:219) > --------------------- >> end captured logging << --------------------- > ====================================================================== > ERROR: Tests mkimage.mkIsoFs creating an image and checking its content > ---------------------------------------------------------------------- > Traceback (most recent call last): > File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/testlib.py", > line 142, in wrapper > return f(self, *args) > File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/testValidation.py", > line 194, in wrapper > return f(*args, **kwargs) > File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/mkimage_test.py", > line 252, in test_mkIsoFs > m.mount(mntOpts='loop') > File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/vdsm/storage/mount.py", > line 207, in mount > cgroup=cgroup) > File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/vdsm/storage/mount.py", > line 277, in _mount > _runcmd(cmd) > File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/vdsm/storage/mount.py", > line 305, in _runcmd > raise MountError(rc, b";".join((out, err))) > MountError: (32, ';mount: > /tmp/vdsm-mkimage-testsxv7k7G/images/vmId_iso.afeec73d2b486c5f33df966a0306836a.img: > failed to setup loop device: No such file or directory\n') > -------------------- >> begin captured logging << -------------------- > 2019-01-08 23:46:19,907 DEBUG (MainThread) [root] /usr/bin/taskset > --cpu-list 0-1 /usr/bin/mkisofs -R -J -o > /tmp/vdsm-mkimage-testsxv7k7G/images/vmId_iso.afeec73d2b486c5f33df966a0306836a.img > /tmp/tmpfk8az9 (cwd None) (commands:198) > 2019-01-08 23:46:19,931 DEBUG (MainThread) [root] SUCCESS: <err> = > 'Total translation table size: 0\nTotal rockridge attributes bytes: > 1796\nTotal directory bytes: 8192\nPath table size(bytes): 64\nMax brk > space used 22000\n199 extents written (0 MB)\n'; <rc> = 0 > (commands:219) > 2019-01-08 23:46:19,933 INFO (MainThread) [storage.Mount] mounting > /tmp/vdsm-mkimage-testsxv7k7G/images/vmId_iso.afeec73d2b486c5f33df966a0306836a.img > at /tmp/vdsm-mkimage-testsxv7k7G/work (mount:204) > 2019-01-08 23:46:19,934 DEBUG (MainThread) [root] /usr/bin/taskset > --cpu-list 0-1 /usr/bin/mount -o loop > /tmp/vdsm-mkimage-testsxv7k7G/images/vmId_iso.afeec73d2b486c5f33df966a0306836a.img > /tmp/vdsm-mkimage-testsxv7k7G/work (cwd None) (commands:198) > 2019-01-08 23:46:19,946 DEBUG (MainThread) [root] FAILED: <err> = > 'mount: /tmp/vdsm-mkimage-testsxv7k7G/images/vmId_iso.afeec73d2b486c5f33df966a0306836a.img: > failed to setup loop device: No such file or directory\n'; <rc> = 32 > (commands:219) > --------------------- >> end captured logging << --------------------- -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2648) Failing Jenkins job
by Eyal Edri (oVirt JIRA) 20 Jan '19

20 Jan '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2648?page=com.atlassian.jira.… ] Eyal Edri updated OVIRT-2648: ----------------------------- Resolution: Fixed Status: Done (was: To Do) > Failing Jenkins job > ------------------- > > Key: OVIRT-2648 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2648 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Shirly Radco > Assignee: infra > > Hi, > My patch for releang-tools fails but not sure why.. > https://gerrit.ovirt.org/#/c/96812/ > Can you please help me to understand why? > Thanks, > -- > SHIRLY RADCO > BI SENIOR SOFTWARE ENGINEER > Red Hat Israel <https://www.redhat.com/> > <https://red.ht/sig> > TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2651) All vdsm builds fail now
by Eyal Edri (oVirt JIRA) 20 Jan '19

20 Jan '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2651?page=com.atlassian.jira.… ] Eyal Edri updated OVIRT-2651: ----------------------------- Resolution: Fixed Status: Done (was: To Do) seem like problem was solved (due to pinning to same os?) > All vdsm builds fail now > ------------------------ > > Key: OVIRT-2651 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2651 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > See https://jenkins.ovirt.org/job/vdsm_standard-check-patch/ > https://jenkins.ovirt.org/blue/rest/organizations/jenkins/pipelines/vdsm_st… > https://jenkins.ovirt.org/blue/rest/organizations/jenkins/pipelines/vdsm_st… > Both fail in network tests that used to work yesterday. > Is this https://gerrit.ovirt.org/c/96921/? > ====================================================================== > ERROR: test_multiple_vlans (network.tc_test.TestConfigureOutbound) > ---------------------------------------------------------------------- > Traceback (most recent call last): > File "/usr/lib/python2.7/site-packages/mock/mock.py", line 1305, in patched > return func(*args, **keywargs) > File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/network/tc_test.py", > line 455, in test_multiple_vlans > self.device_name, v.tag) > File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/vdsm/network/configurators/qos.py", > line 47, in configure_outbound > _fresh_qdisc_conf_out(device, vlan_tag, class_id, qosOutbound) > File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/vdsm/network/configurators/qos.py", > line 116, in _fresh_qdisc_conf_out > default='%#x' % _NON_VLANNED_ID) > File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/vdsm/network/tc/qdisc.py", > line 43, in add > _wrapper.process_request(command) > File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/vdsm/network/tc/_wrapper.py", > line 43, in process_request > raise TrafficControlException(retcode, err, command) > TrafficControlException: (34, 'RTNETLINK answers: Numerical result out > of range', ['/sbin/tc', 'qdisc', 'add', 'dev', 'dummy_ghyx4', 'root', > 'handle', '0x1389:', 'hfsc', 'default', '0x1388']) > -------------------- >> begin captured logging << -------------------- > 2019-01-15 18:27:00,089 DEBUG (MainThread) [root] /sbin/ip link add > name dummy_ghyx4 type dummy (cwd None) (cmdutils:133) > 2019-01-15 18:27:00,105 DEBUG (MainThread) [root] SUCCESS: <err> = ''; > <rc> = 0 (cmdutils:141) > 2019-01-15 18:27:00,107 DEBUG (MainThread) [root] /sbin/ip link set > dev dummy_ghyx4 up (cwd None) (cmdutils:133) > 2019-01-15 18:27:00,135 DEBUG (MainThread) [root] SUCCESS: <err> = ''; > <rc> = 0 (cmdutils:141) > 2019-01-15 18:27:00,138 DEBUG (MainThread) [root] /sbin/ip link add > link dummy_ghyx4 name dummy_ghyx4.16 type vlan id 16 (cwd None) > (cmdutils:133) > 2019-01-15 18:27:00,159 DEBUG (MainThread) [root] SUCCESS: <err> = ''; > <rc> = 0 (cmdutils:141) > 2019-01-15 18:27:00,163 DEBUG (MainThread) [root] /sbin/ip link set > dev dummy_ghyx4.16 up (cwd None) (cmdutils:133) > 2019-01-15 18:27:00,193 DEBUG (MainThread) [root] SUCCESS: <err> = ''; > <rc> = 0 (cmdutils:141) > 2019-01-15 18:27:00,196 DEBUG (MainThread) [root] /sbin/ip link add > link dummy_ghyx4 name dummy_ghyx4.17 type vlan id 17 (cwd None) > (cmdutils:133) > 2019-01-15 18:27:00,216 DEBUG (MainThread) [root] SUCCESS: <err> = ''; > <rc> = 0 (cmdutils:141) > 2019-01-15 18:27:00,218 DEBUG (MainThread) [root] /sbin/ip link set > dev dummy_ghyx4.17 up (cwd None) (cmdutils:133) > 2019-01-15 18:27:00,236 DEBUG (MainThread) [root] SUCCESS: <err> = ''; > <rc> = 0 (cmdutils:141) > 2019-01-15 18:27:00,238 DEBUG (MainThread) [root] /sbin/tc qdisc show > dev dummy_ghyx4 (cwd None) (cmdutils:133) > 2019-01-15 18:27:00,275 DEBUG (MainThread) [root] SUCCESS: <err> = ''; > <rc> = 0 (cmdutils:141) > 2019-01-15 18:27:00,282 DEBUG (MainThread) [root] /sbin/tc qdisc del > dev dummy_ghyx4 root (cwd None) (cmdutils:133) > 2019-01-15 18:27:00,305 DEBUG (MainThread) [root] FAILED: <err> = > 'RTNETLINK answers: No such file or directory\n'; <rc> = 2 > (cmdutils:141) > 2019-01-15 18:27:00,307 DEBUG (MainThread) [root] /sbin/tc qdisc del > dev dummy_ghyx4 ingress (cwd None) (cmdutils:133) > 2019-01-15 18:27:00,320 DEBUG (MainThread) [root] FAILED: <err> = > 'RTNETLINK answers: No such file or directory\n'; <rc> = 2 > (cmdutils:141) > 2019-01-15 18:27:00,323 DEBUG (MainThread) [root] /sbin/tc qdisc add > dev dummy_ghyx4 root handle 0x1389: hfsc default 0x1388 (cwd None) > (cmdutils:133) > 2019-01-15 18:27:00,350 DEBUG (MainThread) [root] FAILED: <err> = > 'RTNETLINK answers: Numerical result out of range\n'; <rc> = 2 > (cmdutils:141) > 2019-01-15 18:27:00,355 DEBUG (netlink/events) [root] START thread > <Thread(netlink/events, started daemon 140628604352256)> (func=<bound > method Monitor._scan of <vdsm.network.netlink.monitor.Monitor object > at 0x7fe6a7a1b0d0>>, args=(), kwargs={}) (concurrent:193) > 2019-01-15 18:27:00,358 DEBUG (MainThread) [root] /sbin/ip link set > dev dummy_ghyx4.17 down (cwd None) (cmdutils:133) > 2019-01-15 18:27:00,376 DEBUG (MainThread) [root] SUCCESS: <err> = ''; > <rc> = 0 (cmdutils:141) > 2019-01-15 18:27:00,378 DEBUG (netlink/events) [root] FINISH thread > <Thread(netlink/events, started daemon 140628604352256)> > (concurrent:196) > 2019-01-15 18:27:00,380 DEBUG (MainThread) [root] /sbin/ip link del > dev dummy_ghyx4.17 (cwd None) (cmdutils:133) > 2019-01-15 18:27:00,399 DEBUG (MainThread) [root] SUCCESS: <err> = ''; > <rc> = 0 (cmdutils:141) > 2019-01-15 18:27:00,404 DEBUG (netlink/events) [root] START thread > <Thread(netlink/events, started daemon 140628604352256)> (func=<bound > method Monitor._scan of <vdsm.network.netlink.monitor.Monitor object > at 0x7fe6a7a1b110>>, args=(), kwargs={}) (concurrent:193) > 2019-01-15 18:27:00,407 DEBUG (MainThread) [root] /sbin/ip link set > dev dummy_ghyx4.16 down (cwd None) (cmdutils:133) > 2019-01-15 18:27:00,423 DEBUG (MainThread) [root] SUCCESS: <err> = ''; > <rc> = 0 (cmdutils:141) > 2019-01-15 18:27:00,425 DEBUG (netlink/events) [root] FINISH thread > <Thread(netlink/events, started daemon 140628604352256)> > (concurrent:196) > 2019-01-15 18:27:00,425 DEBUG (MainThread) [root] /sbin/ip link del > dev dummy_ghyx4.16 (cwd None) (cmdutils:133) > 2019-01-15 18:27:00,447 DEBUG (MainThread) [root] SUCCESS: <err> = ''; > <rc> = 0 (cmdutils:141) > --------------------- >> end captured logging << --------------------- > ====================================================================== > ERROR: test_single_non_vlan (network.tc_test.TestConfigureOutbound) > ---------------------------------------------------------------------- > Traceback (most recent call last): > File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/network/tc_test.py", > line 416, in test_single_non_vlan > qos.configure_outbound(HOST_QOS_OUTBOUND, self.device_name, None) > File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/vdsm/network/configurators/qos.py", > line 47, in configure_outbound > _fresh_qdisc_conf_out(device, vlan_tag, class_id, qosOutbound) > File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/vdsm/network/configurators/qos.py", > line 116, in _fresh_qdisc_conf_out > default='%#x' % _NON_VLANNED_ID) > File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/vdsm/network/tc/qdisc.py", > line 43, in add > _wrapper.process_request(command) > File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/vdsm/network/tc/_wrapper.py", > line 43, in process_request > raise TrafficControlException(retcode, err, command) > TrafficControlException: (34, 'RTNETLINK answers: Numerical result out > of range', ['/sbin/tc', 'qdisc', 'add', 'dev', 'dummy_ErG82', 'root', > 'handle', '0x1389:', 'hfsc', 'default', '0x1388']) > -------------------- >> begin captured logging << -------------------- > 2019-01-15 18:27:00,477 DEBUG (MainThread) [root] /sbin/ip link add > name dummy_ErG82 type dummy (cwd None) (cmdutils:133) > 2019-01-15 18:27:00,488 DEBUG (MainThread) [root] SUCCESS: <err> = ''; > <rc> = 0 (cmdutils:141) > 2019-01-15 18:27:00,490 DEBUG (MainThread) [root] /sbin/ip link set > dev dummy_ErG82 up (cwd None) (cmdutils:133) > 2019-01-15 18:27:00,501 DEBUG (MainThread) [root] SUCCESS: <err> = ''; > <rc> = 0 (cmdutils:141) > 2019-01-15 18:27:00,502 DEBUG (MainThread) [root] /sbin/tc qdisc show > dev dummy_ErG82 (cwd None) (cmdutils:133) > 2019-01-15 18:27:00,516 DEBUG (MainThread) [root] SUCCESS: <err> = ''; > <rc> = 0 (cmdutils:141) > 2019-01-15 18:27:00,517 DEBUG (MainThread) [root] /sbin/tc qdisc del > dev dummy_ErG82 root (cwd None) (cmdutils:133) > 2019-01-15 18:27:00,529 DEBUG (MainThread) [root] FAILED: <err> = > 'RTNETLINK answers: No such file or directory\n'; <rc> = 2 > (cmdutils:141) > 2019-01-15 18:27:00,531 DEBUG (MainThread) [root] /sbin/tc qdisc del > dev dummy_ErG82 ingress (cwd None) (cmdutils:133) > 2019-01-15 18:27:00,541 DEBUG (MainThread) [root] FAILED: <err> = > 'RTNETLINK answers: No such file or directory\n'; <rc> = 2 > (cmdutils:141) > 2019-01-15 18:27:00,542 DEBUG (MainThread) [root] /sbin/tc qdisc add > dev dummy_ErG82 root handle 0x1389: hfsc default 0x1388 (cwd None) > (cmdutils:133) > 2019-01-15 18:27:00,552 DEBUG (MainThread) [root] FAILED: <err> = > 'RTNETLINK answers: Numerical result out of range\n'; <rc> = 2 > (cmdutils:141) > --------------------- >> end captured logging << --------------------- > ====================================================================== > ERROR: test_single_vlan(1) (network.tc_test.TestConfigureOutbound) > ---------------------------------------------------------------------- > Traceback (most recent call last): > File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/testlib.py", > line 142, in wrapper > return f(self, *args) > File "/usr/lib/python2.7/site-packages/mock/mock.py", line 1305, in patched > return func(*args, **keywargs) > File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/network/tc_test.py", > line 434, in test_single_vlan > vlan.tag) > File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/vdsm/network/configurators/qos.py", > line 47, in configure_outbound > _fresh_qdisc_conf_out(device, vlan_tag, class_id, qosOutbound) > File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/vdsm/network/configurators/qos.py", > line 116, in _fresh_qdisc_conf_out > default='%#x' % _NON_VLANNED_ID) > File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/vdsm/network/tc/qdisc.py", > line 43, in add > _wrapper.process_request(command) > File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/vdsm/network/tc/_wrapper.py", > line 43, in process_request > raise TrafficControlException(retcode, err, command) > TrafficControlException: (34, 'RTNETLINK answers: Numerical result out > of range', ['/sbin/tc', 'qdisc', 'add', 'dev', 'dummy_RLG36', 'root', > 'handle', '0x1389:', 'hfsc', 'default', '0x1388']) > -------------------- >> begin captured logging << -------------------- > 2019-01-15 18:27:00,578 DEBUG (MainThread) [root] /sbin/ip link add > name dummy_RLG36 type dummy (cwd None) (cmdutils:133) > 2019-01-15 18:27:00,587 DEBUG (MainThread) [root] SUCCESS: <err> = ''; > <rc> = 0 (cmdutils:141) > 2019-01-15 18:27:00,589 DEBUG (MainThread) [root] /sbin/ip link set > dev dummy_RLG36 up (cwd None) (cmdutils:133) > 2019-01-15 18:27:00,601 DEBUG (MainThread) [root] SUCCESS: <err> = ''; > <rc> = 0 (cmdutils:141) > 2019-01-15 18:27:00,603 DEBUG (MainThread) [root] /sbin/ip link add > link dummy_RLG36 name dummy_RLG36.16 type vlan id 16 (cwd None) > (cmdutils:133) > 2019-01-15 18:27:00,613 DEBUG (MainThread) [root] SUCCESS: <err> = ''; > <rc> = 0 (cmdutils:141) > 2019-01-15 18:27:00,614 DEBUG (MainThread) [root] /sbin/ip link set > dev dummy_RLG36.16 up (cwd None) (cmdutils:133) > 2019-01-15 18:27:00,641 DEBUG (MainThread) [root] SUCCESS: <err> = ''; > <rc> = 0 (cmdutils:141) > 2019-01-15 18:27:00,642 DEBUG (MainThread) [root] /sbin/tc qdisc show > dev dummy_RLG36 (cwd None) (cmdutils:133) > 2019-01-15 18:27:00,660 DEBUG (MainThread) [root] SUCCESS: <err> = ''; > <rc> = 0 (cmdutils:141) > 2019-01-15 18:27:00,661 DEBUG (MainThread) [root] /sbin/tc qdisc del > dev dummy_RLG36 root (cwd None) (cmdutils:133) > 2019-01-15 18:27:00,670 DEBUG (MainThread) [root] FAILED: <err> = > 'RTNETLINK answers: No such file or directory\n'; <rc> = 2 > (cmdutils:141) > 2019-01-15 18:27:00,672 DEBUG (MainThread) [root] /sbin/tc qdisc del > dev dummy_RLG36 ingress (cwd None) (cmdutils:133) > 2019-01-15 18:27:00,681 DEBUG (MainThread) [root] FAILED: <err> = > 'RTNETLINK answers: No such file or directory\n'; <rc> = 2 > (cmdutils:141) > 2019-01-15 18:27:00,683 DEBUG (MainThread) [root] /sbin/tc qdisc add > dev dummy_RLG36 root handle 0x1389: hfsc default 0x1388 (cwd None) > (cmdutils:133) > 2019-01-15 18:27:00,693 DEBUG (MainThread) [root] FAILED: <err> = > 'RTNETLINK answers: Numerical result out of range\n'; <rc> = 2 > (cmdutils:141) > 2019-01-15 18:27:00,695 DEBUG (netlink/events) [root] START thread > <Thread(netlink/events, started daemon 140628604352256)> (func=<bound > method Monitor._scan of <vdsm.network.netlink.monitor.Monitor object > at 0x7fe6a7b33b90>>, args=(), kwargs={}) (concurrent:193) > 2019-01-15 18:27:00,697 DEBUG (MainThread) [root] /sbin/ip link set > dev dummy_RLG36.16 down (cwd None) (cmdutils:133) > 2019-01-15 18:27:00,712 DEBUG (MainThread) [root] SUCCESS: <err> = ''; > <rc> = 0 (cmdutils:141) > 2019-01-15 18:27:00,714 DEBUG (netlink/events) [root] FINISH thread > <Thread(netlink/events, started daemon 140628604352256)> > (concurrent:196) > 2019-01-15 18:27:00,715 DEBUG (MainThread) [root] /sbin/ip link del > dev dummy_RLG36.16 (cwd None) (cmdutils:133) > 2019-01-15 18:27:00,729 DEBUG (MainThread) [root] SUCCESS: <err> = ''; > <rc> = 0 (cmdutils:141) > --------------------- >> end captured logging << --------------------- > ====================================================================== > ERROR: test_single_vlan(2) (network.tc_test.TestConfigureOutbound) > ---------------------------------------------------------------------- > Traceback (most recent call last): > File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/testlib.py", > line 142, in wrapper > return f(self, *args) > File "/usr/lib/python2.7/site-packages/mock/mock.py", line 1305, in patched > return func(*args, **keywargs) > File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/network/tc_test.py", > line 434, in test_single_vlan > vlan.tag) > File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/vdsm/network/configurators/qos.py", > line 47, in configure_outbound > _fresh_qdisc_conf_out(device, vlan_tag, class_id, qosOutbound) > File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/vdsm/network/configurators/qos.py", > line 116, in _fresh_qdisc_conf_out > default='%#x' % _NON_VLANNED_ID) > File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/vdsm/network/tc/qdisc.py", > line 43, in add > _wrapper.process_request(command) > File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/lib/vdsm/network/tc/_wrapper.py", > line 43, in process_request > raise TrafficControlException(retcode, err, command) > TrafficControlException: (34, 'RTNETLINK answers: Numerical result out > of range', ['/sbin/tc', 'qdisc', 'add', 'dev', 'dummy_0a4K1', 'root', > 'handle', '0x1389:', 'hfsc', 'default', '0x1388']) > -------------------- >> begin captured logging << -------------------- > 2019-01-15 18:27:00,752 DEBUG (MainThread) [root] /sbin/ip link add > name dummy_0a4K1 type dummy (cwd None) (cmdutils:133) > 2019-01-15 18:27:00,768 DEBUG (MainThread) [root] SUCCESS: <err> = ''; > <rc> = 0 (cmdutils:141) > 2019-01-15 18:27:00,769 DEBUG (MainThread) [root] /sbin/ip link set > dev dummy_0a4K1 up (cwd None) (cmdutils:133) > 2019-01-15 18:27:00,782 DEBUG (MainThread) [root] SUCCESS: <err> = ''; > <rc> = 0 (cmdutils:141) > 2019-01-15 18:27:00,784 DEBUG (MainThread) [root] /sbin/ip link add > link dummy_0a4K1 name dummy_0a4K1.16 type vlan id 16 (cwd None) > (cmdutils:133) > 2019-01-15 18:27:00,803 DEBUG (MainThread) [root] SUCCESS: <err> = ''; > <rc> = 0 (cmdutils:141) > 2019-01-15 18:27:00,805 DEBUG (MainThread) [root] /sbin/ip link set > dev dummy_0a4K1.16 up (cwd None) (cmdutils:133) > 2019-01-15 18:27:00,824 DEBUG (MainThread) [root] SUCCESS: <err> = ''; > <rc> = 0 (cmdutils:141) > 2019-01-15 18:27:00,826 DEBUG (MainThread) [root] /sbin/tc qdisc show > dev dummy_0a4K1 (cwd None) (cmdutils:133) > 2019-01-15 18:27:00,846 DEBUG (MainThread) [root] SUCCESS: <err> = ''; > <rc> = 0 (cmdutils:141) > 2019-01-15 18:27:00,848 DEBUG (MainThread) [root] /sbin/tc qdisc del > dev dummy_0a4K1 root (cwd None) (cmdutils:133) > 2019-01-15 18:27:00,858 DEBUG (MainThread) [root] FAILED: <err> = > 'RTNETLINK answers: No such file or directory\n'; <rc> = 2 > (cmdutils:141) > 2019-01-15 18:27:00,859 DEBUG (MainThread) [root] /sbin/tc qdisc del > dev dummy_0a4K1 ingress (cwd None) (cmdutils:133) > 2019-01-15 18:27:00,869 DEBUG (MainThread) [root] FAILED: <err> = > 'RTNETLINK answers: No such file or directory\n'; <rc> = 2 > (cmdutils:141) > 2019-01-15 18:27:00,870 DEBUG (MainThread) [root] /sbin/tc qdisc add > dev dummy_0a4K1 root handle 0x1389: hfsc default 0x1388 (cwd None) > (cmdutils:133) > 2019-01-15 18:27:00,889 DEBUG (MainThread) [root] FAILED: <err> = > 'RTNETLINK answers: Numerical result out of range\n'; <rc> = 2 > (cmdutils:141) > 2019-01-15 18:27:00,893 DEBUG (netlink/eveCoverage.py warning: Module > /home/jenkins/workspace/vdsm_standard-check-patch/vdsm/vdsm was never > imported. (module-not-imported) > nts) [root] START thread <Thread(netlink/events, started daemon > 140628604352256)> (func=<bound method Monitor._scan of > <vdsm.network.netlink.monitor.Monitor object at 0x7fe6a7b33d10>>, > args=(), kwargs={}) (concurrent:193) > 2019-01-15 18:27:00,895 DEBUG (MainThread) [root] /sbin/ip link set > dev dummy_0a4K1.16 down (cwd None) (cmdutils:133) > 2019-01-15 18:27:00,909 DEBUG (MainThread) [root] SUCCESS: <err> = ''; > <rc> = 0 (cmdutils:141) > 2019-01-15 18:27:00,912 DEBUG (netlink/events) [root] FINISH thread > <Thread(netlink/events, started daemon 140628604352256)> > (concurrent:196) > 2019-01-15 18:27:00,913 DEBUG (MainThread) [root] /sbin/ip link del > dev dummy_0a4K1.16 (cwd None) (cmdutils:133) > 2019-01-15 18:27:00,930 DEBUG (MainThread) [root] SUCCESS: <err> = ''; > <rc> = 0 (cmdutils:141) > --------------------- >> end captured logging << --------------------- -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2654) Kubvirt jobs stuck for one day
by Eyal Edri (oVirt JIRA) 20 Jan '19

20 Jan '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2654?page=com.atlassian.jira.… ] Eyal Edri updated OVIRT-2654: ----------------------------- Resolution: Done Status: Done (was: To Do) not related to the load. > Kubvirt jobs stuck for one day > ------------------------------ > > Key: OVIRT-2654 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2654 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > While checking why the CI is overloaded, I fund these stuck jobs: > openshift-kubevirt-org-kqjj4 > <https://jenkins.ovirt.org/computer/openshift-kubevirt-org-kqjj4/> > (offline) > 1 > kubevirt_containerized-data-importer_standard-check-pr > <https://jenkins.ovirt.org/job/kubevirt_containerized-data-importer_standard…> > #1096 containerized-data-importer [check-patch] > <https://jenkins.ovirt.org/job/kubevirt_containerized-data-importer_standard…> > (check-patch.openshift-3.11.0-release.el7.x86_64) > openshift-kubevirt-org-t1tbp > <https://jenkins.ovirt.org/computer/openshift-kubevirt-org-t1tbp/> > (offline) > 1 > kubevirt_containerized-data-importer_standard-check-pr > <https://jenkins.ovirt.org/job/kubevirt_containerized-data-importer_standard…> > #1096 containerized-data-importer [check-patch] > <https://jenkins.ovirt.org/job/kubevirt_containerized-data-importer_standard…> > (check-patch.k8s-1.11.0-release.el7.x86_64) > See https://jenkins.ovirt.org/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

Status of 4.3 CQ and OST 4.3
by Eyal Edri 20 Jan '19

20 Jan '19

I see we've added 4.3 CQ to Jenkins, but we didn't add 4.3 OST suites yet, so I assume we're using the master ones? Should we add 4.3 suites? or keep using the master suite since we don't expect too many changes to happen in the near future? -- Eyal edri MANAGER RHV/CNV DevOps EMEA VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)

2 2

[JIRA] (OVIRT-2656) Upstream-sources trigger for ovirt-engine-metrics does not work
by Daniel Belenky (oVirt JIRA) 20 Jan '19

20 Jan '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2656?page=com.atlassian.jira.… ] Daniel Belenky commented on OVIRT-2656: --------------------------------------- I'm checking On Sun, Jan 20, 2019 at 10:30 AM Shirly Radco <sradco(a)redhat.com> wrote: > > -- > > SHIRLY RADCO > > BI SENIOR SOFTWARE ENGINEER > > Red Hat Israel <https://www.redhat.com/> > <https://red.ht/sig> > TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> > -- DANIEL BELENKY > Upstream-sources trigger for ovirt-engine-metrics does not work > --------------------------------------------------------------- > > Key: OVIRT-2656 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2656 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Shirly Radco > Assignee: infra > > -- > SHIRLY RADCO > BI SENIOR SOFTWARE ENGINEER > Red Hat Israel <https://www.redhat.com/> > <https://red.ht/sig> > TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2656) Upstream-sources trigger for ovirt-engine-metrics does not work
by Shirly Radco (oVirt JIRA) 20 Jan '19

20 Jan '19

Shirly Radco created OVIRT-2656: ----------------------------------- Summary: Upstream-sources trigger for ovirt-engine-metrics does not work Key: OVIRT-2656 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2656 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Shirly Radco Assignee: infra -- SHIRLY RADCO BI SENIOR SOFTWARE ENGINEER Red Hat Israel <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

oVirt infra daily report - unstable production jobs - 710
by jenkins＠jenkins.phx.ovirt.org 20 Jan '19

20 Jan '19

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - http://jenkins.ovirt.org/job/system_jenkins-report/710//artifact/exported-a… Cheers, Jenkins

1 0

Build failed in Jenkins: system-sync_mirrors-fedora-base-fc29-x86_64 #218
by jenkins＠jenkins.phx.ovirt.org 19 Jan '19

19 Jan '19

See <http://jenkins.ovirt.org/job/system-sync_mirrors-fedora-base-fc29-x86_64/21…> Changes: [Sandro Bonazzola] ioprocess: drop 4.1 jobs [Sandro Bonazzola] mom: drop 4.1 jobs [Sandro Bonazzola] ovirt-hosted-engine-ha: drop 4.1 jobs [Sandro Bonazzola] ovirt-engine-sdk-ruby: drop 4.1 jobs [Sandro Bonazzola] ovirt-engine-nodejs-modules: drop 4.1 jobs [Sandro Bonazzola] ovirt-engine-extension-logger-log4j: drop 4.1 jobs [Sandro Bonazzola] ovirt-engine-extension-aaa-misc: drop 4.1 jobs [Sandro Bonazzola] ovirt-engine-extension-aaa-ldap: drop 4.1 jobs [Sandro Bonazzola] ovirt-engine-extension-aaa-jdbc: drop 4.1 jobs [Sandro Bonazzola] ovirt-engine-dashboard: drop 4.1 jobs [Sandro Bonazzola] ovirt-engine-api-model: drop 4.1 jobs [Sandro Bonazzola] ovirt-engine-api-metamodel: drop 4.1 jobs [Sandro Bonazzola] ovirt-demo-tool: drop 4.1 jobs [Sandro Bonazzola] ovirt-containers: drop 4.1 jobs [Sandro Bonazzola] ovirt-engine-dashboard: drop master jobs [Sandro Bonazzola] ovirt-containers: drop abandoned project ------------------------------------------ Started by timer [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-fedora-base-fc29-x86_64/ws/> > 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 http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* --prune > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision e8b9034e509402e9e9ce1073efc73c70a8c53793 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f e8b9034e509402e9e9ce1073efc73c70a8c53793 Commit message: "ovirt-containers: drop abandoned project" > git rev-list --no-walk b30d5e49fe6b620704ed2244a1c36653357a5be7 # timeout=10 [system-sync_mirrors-fedora-base-fc29-x86_64] $ /bin/bash -xe /tmp/jenkins7420747090607629775.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror fedora-base-fc29 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 fedora-base-fc29 x86_64 jenkins/data/mirrors-reposync.conf + local command=resync_yum_mirror + command_args=("${@:2}") + local command_args + cmd_resync_yum_mirror fedora-base-fc29 x86_64 jenkins/data/mirrors-reposync.conf + local repo_name=fedora-base-fc29 + 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 fedora-base-fc29 yum + local repo_name=fedora-base-fc29 + local repo_type=yum + sudo install -o jenkins -d /var/www/html/repos/yum /var/www/html/repos/yum/fedora-base-fc29 /var/www/html/repos/yum/fedora-base-fc29/base + check_yum_sync_needed fedora-base-fc29 x86_64 jenkins/data/mirrors-reposync.conf sync_needed + local repo_name=fedora-base-fc29 + 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/fedora-base-fc29 ++ IFS=, ++ echo x86_64 + for arch in '$(IFS=,; echo $repo_archs)' ++ run_reposync fedora-base-fc29 x86_64 jenkins/data/mirrors-reposync.conf --urls --quiet ++ local repo_name=fedora-base-fc29 ++ 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=fedora-base-fc29 --arch=x86_64 --cachedir=/home/jenkins/mirrors_cache --download_path=/var/www/html/repos/yum/fedora-base-fc29/base --norepopath --newest-only --urls --quiet Traceback (most recent call last): File "/usr/bin/reposync", line 343, in <module> main() File "/usr/bin/reposync", line 175, in main my.doRepoSetup() File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 681, in doRepoSetup return self._getRepos(thisrepo, True) File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 721, in _getRepos self._repos.doSetup(thisrepo) File "/usr/lib/python2.7/site-packages/yum/repos.py", line 157, in doSetup self.retrieveAllMD() File "/usr/lib/python2.7/site-packages/yum/repos.py", line 88, in retrieveAllMD dl = repo._async and repo._commonLoadRepoXML(repo) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1465, in _commonLoadRepoXML local = self.cachedir + '/repomd.xml' File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 774, in <lambda> cachedir = property(lambda self: self._dirGetAttr('cachedir')) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 757, in _dirGetAttr self.dirSetup() File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 735, in dirSetup self._dirSetupMkdir_p(dir) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 712, in _dirSetupMkdir_p raise Errors.RepoError, msg yum.Errors.RepoError: Error making cache directory: /home/jenkins/mirrors_cache/centos-kvm-common-el7/gen error was: [Errno 17] File exists: '/home/jenkins/mirrors_cache/centos-kvm-common-el7/gen' + reposync_out= Build step 'Execute shell' marked build as failure

1 1

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 19 Jan '19

19 Jan '19

Failed to run project_setup.sh for: #3215 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-rf329.

1 0

[CQ]: eb5d890 (ovirt-ansible-shutdown-env) failed "ovirt-4.2" system tests
by oVirt Jenkins 19 Jan '19

19 Jan '19

Change eb5d890 (ovirt-ansible-shutdown-env) 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-shutdown-env/commit/eb5d8900878e8719… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3754/

1 0

oVirt infra daily report - unstable production jobs - 709
by jenkins＠jenkins.phx.ovirt.org 19 Jan '19

19 Jan '19

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - http://jenkins.ovirt.org/job/system_jenkins-report/709//artifact/exported-a… Cheers, Jenkins

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 18 Jan '19

18 Jan '19

Failed to run project_setup.sh for: #3212 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-fbq72.

1 0

[Ovirt] [CQ weekly status] [18-01-2019]
by Dafna Ron 18 Jan '19

18 Jan '19

Hi, This mail is to provide the current status of CQ and allow people to review status before and after the weekend. Please refer to below colour map for further information on the meaning of the colours. *CQ-4.2*: RED (#1) one issue still pending: 1. ovirt-provider-ovn is failing due to change https://gerrit.ovirt.org/#/c/96926/ - ip_version is mandatory on POSTs The change is failing the ost test because ip version needs to be specifically provided as a result of introducing v6 There is a patch by Miguel which I merged. there are a few patches in test now so waiting to see if the patch fixes the issue. https://gerrit.ovirt.org/#/c/97072/ - basic-suite-42: align w/ networking API Jira: https://ovirt-jira.atlassian.net/browse/OVIRT-2655 *CQ-Master:* GREEN (#2) Last failure was on Jan 14th for project ovirt-ansible-hosted-engine-setup. The project was failing on https://docs.fedoraproject.org/en-US/packaging-guidelines/Directory_Replace… Jira was closed today as projects are passing: https://ovirt-jira.atlassian.net/browse/OVIRT-2650 Current running jobs for 4.2 [1] and master [2] can be found here: [1] http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.2_change-qu… [2] http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-master_change… Happy week! Dafna ------------------------------------------------------------------------------------------------------------------- COLOUR MAP Green = job has been passing successfully ** green for more than 3 days may suggest we need a review of our test coverage 1. 1-3 days GREEN (#1) 2. 4-7 days GREEN (#2) 3. Over 7 days GREEN (#3) Yellow = intermittent failures for different projects but no lasting or current regressions ** intermittent would be a healthy project as we expect a number of failures during the week ** I will not report any of the solved failures or regressions. 1. Solved job failures YELLOW (#1) 2. Solved regressions YELLOW (#2) Red = job has been failing ** Active Failures. The colour will change based on the amount of time the project/s has been broken. Only active regressions would be reported. 1. 1-3 days RED (#1) 2. 4-7 days RED (#2) 3. Over 7 days RED (#3)

1 0

[ OST Failure Report ] [ oVirt 4.2 (ovirt-provider-ovn) ] [ 18-01-2019 ] [ 098_ovirt_provider_ovn.use_ovn_provider ]
by Dafna Ron 18 Jan '19

18 Jan '19

Hi, We have a failure in ovn tests in branch 4.2. Marcin/Miguel, can you please take a look? Jira opened: https://ovirt-jira.atlassian.net/browse/OVIRT-2655 Link and headline of suspected patches: https://gerrit.ovirt.org/#/c/96926/ - ip_version is mandatory on POSTs Link to Job: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3742/ Link to all logs: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3742/artifact/ba… (Relevant) error snippet from the log: <error> 2019-01-18 00:14:30,591 root Starting server 2019-01-18 00:14:30,592 root Version: 1.2.19-0.20190117180529.gite1d4195 2019-01-18 00:14:30,592 root Build date: 20190117180529 2019-01-18 00:14:30,592 root Githash: e1d4195 2019-01-18 00:20:39,394 ovsdbapp.backend.ovs_idl.vlog ssl:127.0.0.1:6641: no response to inactivity probe after 5.01 seconds, disconnecting 2019-01-18 00:45:01,435 root From: ::ffff:192.168.200.1:49008 Request: POST /v2.0/subnets/ 2019-01-18 00:45:01,435 root Request body: {"subnet": {"network_id": "99c260ec-dad4-40b9-8732-df32dd54bd00", "dns_nameservers": ["8.8.8.8"], "cidr": "1.1.1.0/24", "gateway_ip": "1.1.1.1", "name": "subnet_1"}} 2019-01-18 00:45:01,435 root Missing 'ip_version' attribute Traceback (most recent call last): File "/usr/share/ovirt-provider-ovn/handlers/base_handler.py", line 134, in _handle_request method, path_parts, content File "/usr/share/ovirt-provider-ovn/handlers/selecting_handler.py", line 175, in handle_request return self.call_response_handler(handler, content, parameters) File "/usr/share/ovirt-provider-ovn/handlers/neutron.py", line 36, in call_response_handler return response_handler(ovn_north, content, parameters) File "/usr/share/ovirt-provider-ovn/handlers/neutron_responses.py", line 154, in post_subnets subnet = nb_db.add_subnet(received_subnet) File "/usr/share/ovirt-provider-ovn/neutron/neutron_api_mappers.py", line 74, in wrapper validate_rest_input(rest_data) File "/usr/share/ovirt-provider-ovn/neutron/neutron_api_mappers.py", line 596, in validate_add_rest_input raise BadRequestError('Missing \'ip_version\' attribute') BadRequestError: Missing 'ip_version' attribute </error>

3 3

[CQ]: 95979, 12 (ovirt-provider-ovn) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 18 Jan '19

18 Jan '19

A system test invoked by the "ovirt-4.2" change queue including change 95979,12 (ovirt-provider-ovn) failed. However, this change seems not to be the root cause for this failure. Change 96926,2 (ovirt-provider-ovn) 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 96926,2 (ovirt-provider-ovn) 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/95979/12 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/96926/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3750/

1 0