June 2021 - Infra - oVirt List Archives

Build failed in Jenkins: system-sync_mirrors-centos-updates-el7-x86_64 #4601
by jenkins＠jenkins.phx.ovirt.org 06 Aug '21

06 Aug '21

See <https://jenkins.ovirt.org/job/system-sync_mirrors-centos-updates-el7-x86_64…> Changes: ------------------------------------------ [...truncated 237.19 KB...] /var/www/html/repos/yum/centos-updates-el7/2021-01-27-08-43 /var/www/html/repos/yum/centos-updates-el7/2021-01-28-08-43 /var/www/html/repos/yum/centos-updates-el7/2021-01-29-16-43 /var/www/html/repos/yum/centos-updates-el7/2021-01-30-08-42 /var/www/html/repos/yum/centos-updates-el7/2021-01-31-00-43 /var/www/html/repos/yum/centos-updates-el7/2021-01-31-16-43 /var/www/html/repos/yum/centos-updates-el7/2021-02-01-08-43 /var/www/html/repos/yum/centos-updates-el7/2021-02-02-00-43 /var/www/html/repos/yum/centos-updates-el7/2021-02-02-16-42 /var/www/html/repos/yum/centos-updates-el7/2021-02-03-08-43 /var/www/html/repos/yum/centos-updates-el7/2021-02-04-00-43 /var/www/html/repos/yum/centos-updates-el7/2021-02-05-00-43 /var/www/html/repos/yum/centos-updates-el7/2020-10-08-08-42 == *\/\v\a\r\/\w\w\w\/\h\t\m\l\/\r\e\p\o\s\/\y\u\m\/\c\e\n\t\o\s\-\u\p\d\a\t\e\s\-\e\l\7\/\2\0\2\1\-\0\2\-\0\2\-\1\6\-\4\2* ]] + for snapshot in '"${all_snapshots[@]}"' + [[ ! /var/www/html/repos/yum/centos-updates-el7/2021-01-28-16-43 /var/www/html/repos/yum/centos-updates-el7/2021-01-30-00-43 /var/www/html/repos/yum/centos-updates-el7/2021-01-30-16-42 /var/www/html/repos/yum/centos-updates-el7/2021-01-31-08-42 /var/www/html/repos/yum/centos-updates-el7/2021-02-01-00-43 /var/www/html/repos/yum/centos-updates-el7/2021-02-01-16-44 /var/www/html/repos/yum/centos-updates-el7/2021-02-02-08-43 /var/www/html/repos/yum/centos-updates-el7/2021-02-03-00-43 /var/www/html/repos/yum/centos-updates-el7/2021-02-03-16-43 /var/www/html/repos/yum/centos-updates-el7/2021-02-04-08-43 /var/www/html/repos/yum/centos-updates-el7/2021-02-07-16-43 /var/www/html/repos/yum/centos-updates-el7/2021-02-05-08-43 /var/www/html/repos/yum/centos-updates-el7/2021-02-05-16-43 /var/www/html/repos/yum/centos-updates-el7/2021-02-06-00-43 /var/www/html/repos/yum/centos-updates-el7/2021-02-06-08-43 /var/www/html/repos/yum/centos-updates-el7/2021-02-06-16-43 /var/www/html/repos/yum/centos-updates-el7/2021-02-07-08-43 /var/www/html/repos/yum/centos-updates-el7/2021-02-08-00-43 /var/www/html/repos/yum/centos-updates-el7/2021-02-08-16-43 /var/www/html/repos/yum/centos-updates-el7/2021-01-26-08-43 /var/www/html/repos/yum/centos-updates-el7/2021-01-27-16-43 /var/www/html/repos/yum/centos-updates-el7/2021-01-29-00-43 /var/www/html/repos/yum/centos-updates-el7/2021-02-04-16-43 /var/www/html/repos/yum/centos-updates-el7/2021-02-07-00-43 /var/www/html/repos/yum/centos-updates-el7/2021-02-08-08-43 /var/www/html/repos/yum/centos-updates-el7/2021-01-26-00-42 /var/www/html/repos/yum/centos-updates-el7/2021-01-26-16-42 /var/www/html/repos/yum/centos-updates-el7/2021-01-27-00-43 /var/www/html/repos/yum/centos-updates-el7/2021-01-28-00-43 /var/www/html/repos/yum/centos-updates-el7/2021-01-29-08-43 /var/www/html/repos/yum/centos-updates-el7/2021-01-27-08-43 /var/www/html/repos/yum/centos-updates-el7/2021-01-28-08-43 /var/www/html/repos/yum/centos-updates-el7/2021-01-29-16-43 /var/www/html/repos/yum/centos-updates-el7/2021-01-30-08-42 /var/www/html/repos/yum/centos-updates-el7/2021-01-31-00-43 /var/www/html/repos/yum/centos-updates-el7/2021-01-31-16-43 /var/www/html/repos/yum/centos-updates-el7/2021-02-01-08-43 /var/www/html/repos/yum/centos-updates-el7/2021-02-02-00-43 /var/www/html/repos/yum/centos-updates-el7/2021-02-02-16-42 /var/www/html/repos/yum/centos-updates-el7/2021-02-03-08-43 /var/www/html/repos/yum/centos-updates-el7/2021-02-04-00-43 /var/www/html/repos/yum/centos-updates-el7/2021-02-05-00-43 /var/www/html/repos/yum/centos-updates-el7/2020-10-08-08-42 == *\/\v\a\r\/\w\w\w\/\h\t\m\l\/\r\e\p\o\s\/\y\u\m\/\c\e\n\t\o\s\-\u\p\d\a\t\e\s\-\e\l\7\/\2\0\2\1\-\0\2\-\0\3\-\0\8\-\4\3* ]] + for snapshot in '"${all_snapshots[@]}"' + [[ ! /var/www/html/repos/yum/centos-updates-el7/2021-01-28-16-43 /var/www/html/repos/yum/centos-updates-el7/2021-01-30-00-43 /var/www/html/repos/yum/centos-updates-el7/2021-01-30-16-42 /var/www/html/repos/yum/centos-updates-el7/2021-01-31-08-42 /var/www/html/repos/yum/centos-updates-el7/2021-02-01-00-43 /var/www/html/repos/yum/centos-updates-el7/2021-02-01-16-44 /var/www/html/repos/yum/centos-updates-el7/2021-02-02-08-43 /var/www/html/repos/yum/centos-updates-el7/2021-02-03-00-43 /var/www/html/repos/yum/centos-updates-el7/2021-02-03-16-43 /var/www/html/repos/yum/centos-updates-el7/2021-02-04-08-43 /var/www/html/repos/yum/centos-updates-el7/2021-02-07-16-43 /var/www/html/repos/yum/centos-updates-el7/2021-02-05-08-43 /var/www/html/repos/yum/centos-updates-el7/2021-02-05-16-43 /var/www/html/repos/yum/centos-updates-el7/2021-02-06-00-43 /var/www/html/repos/yum/centos-updates-el7/2021-02-06-08-43 /var/www/html/repos/yum/centos-updates-el7/2021-02-06-16-43 /var/www/html/repos/yum/centos-updates-el7/2021-02-07-08-43 /var/www/html/repos/yum/centos-updates-el7/2021-02-08-00-43 /var/www/html/repos/yum/centos-updates-el7/2021-02-08-16-43 /var/www/html/repos/yum/centos-updates-el7/2021-01-26-08-43 /var/www/html/repos/yum/centos-updates-el7/2021-01-27-16-43 /var/www/html/repos/yum/centos-updates-el7/2021-01-29-00-43 /var/www/html/repos/yum/centos-updates-el7/2021-02-04-16-43 /var/www/html/repos/yum/centos-updates-el7/2021-02-07-00-43 /var/www/html/repos/yum/centos-updates-el7/2021-02-08-08-43 /var/www/html/repos/yum/centos-updates-el7/2021-01-26-00-42 /var/www/html/repos/yum/centos-updates-el7/2021-01-26-16-42 /var/www/html/repos/yum/centos-updates-el7/2021-01-27-00-43 /var/www/html/repos/yum/centos-updates-el7/2021-01-28-00-43 /var/www/html/repos/yum/centos-updates-el7/2021-01-29-08-43 /var/www/html/repos/yum/centos-updates-el7/2021-01-27-08-43 /var/www/html/repos/yum/centos-updates-el7/2021-01-28-08-43 /var/www/html/repos/yum/centos-updates-el7/2021-01-29-16-43 /var/www/html/repos/yum/centos-updates-el7/2021-01-30-08-42 /var/www/html/repos/yum/centos-updates-el7/2021-01-31-00-43 /var/www/html/repos/yum/centos-updates-el7/2021-01-31-16-43 /var/www/html/repos/yum/centos-updates-el7/2021-02-01-08-43 /var/www/html/repos/yum/centos-updates-el7/2021-02-02-00-43 /var/www/html/repos/yum/centos-updates-el7/2021-02-02-16-42 /var/www/html/repos/yum/centos-updates-el7/2021-02-03-08-43 /var/www/html/repos/yum/centos-updates-el7/2021-02-04-00-43 /var/www/html/repos/yum/centos-updates-el7/2021-02-05-00-43 /var/www/html/repos/yum/centos-updates-el7/2020-10-08-08-42 == *\/\v\a\r\/\w\w\w\/\h\t\m\l\/\r\e\p\o\s\/\y\u\m\/\c\e\n\t\o\s\-\u\p\d\a\t\e\s\-\e\l\7\/\2\0\2\1\-\0\2\-\0\4\-\0\0\-\4\3* ]] + for snapshot in '"${all_snapshots[@]}"' + [[ ! /var/www/html/repos/yum/centos-updates-el7/2021-01-28-16-43 /var/www/html/repos/yum/centos-updates-el7/2021-01-30-00-43 /var/www/html/repos/yum/centos-updates-el7/2021-01-30-16-42 /var/www/html/repos/yum/centos-updates-el7/2021-01-31-08-42 /var/www/html/repos/yum/centos-updates-el7/2021-02-01-00-43 /var/www/html/repos/yum/centos-updates-el7/2021-02-01-16-44 /var/www/html/repos/yum/centos-updates-el7/2021-02-02-08-43 /var/www/html/repos/yum/centos-updates-el7/2021-02-03-00-43 /var/www/html/repos/yum/centos-updates-el7/2021-02-03-16-43 /var/www/html/repos/yum/centos-updates-el7/2021-02-04-08-43 /var/www/html/repos/yum/centos-updates-el7/2021-02-07-16-43 /var/www/html/repos/yum/centos-updates-el7/2021-02-05-08-43 /var/www/html/repos/yum/centos-updates-el7/2021-02-05-16-43 /var/www/html/repos/yum/centos-updates-el7/2021-02-06-00-43 /var/www/html/repos/yum/centos-updates-el7/2021-02-06-08-43 /var/www/html/repos/yum/centos-updates-el7/2021-02-06-16-43 /var/www/html/repos/yum/centos-updates-el7/2021-02-07-08-43 /var/www/html/repos/yum/centos-updates-el7/2021-02-08-00-43 /var/www/html/repos/yum/centos-updates-el7/2021-02-08-16-43 /var/www/html/repos/yum/centos-updates-el7/2021-01-26-08-43 /var/www/html/repos/yum/centos-updates-el7/2021-01-27-16-43 /var/www/html/repos/yum/centos-updates-el7/2021-01-29-00-43 /var/www/html/repos/yum/centos-updates-el7/2021-02-04-16-43 /var/www/html/repos/yum/centos-updates-el7/2021-02-07-00-43 /var/www/html/repos/yum/centos-updates-el7/2021-02-08-08-43 /var/www/html/repos/yum/centos-updates-el7/2021-01-26-00-42 /var/www/html/repos/yum/centos-updates-el7/2021-01-26-16-42 /var/www/html/repos/yum/centos-updates-el7/2021-01-27-00-43 /var/www/html/repos/yum/centos-updates-el7/2021-01-28-00-43 /var/www/html/repos/yum/centos-updates-el7/2021-01-29-08-43 /var/www/html/repos/yum/centos-updates-el7/2021-01-27-08-43 /var/www/html/repos/yum/centos-updates-el7/2021-01-28-08-43 /var/www/html/repos/yum/centos-updates-el7/2021-01-29-16-43 /var/www/html/repos/yum/centos-updates-el7/2021-01-30-08-42 /var/www/html/repos/yum/centos-updates-el7/2021-01-31-00-43 /var/www/html/repos/yum/centos-updates-el7/2021-01-31-16-43 /var/www/html/repos/yum/centos-updates-el7/2021-02-01-08-43 /var/www/html/repos/yum/centos-updates-el7/2021-02-02-00-43 /var/www/html/repos/yum/centos-updates-el7/2021-02-02-16-42 /var/www/html/repos/yum/centos-updates-el7/2021-02-03-08-43 /var/www/html/repos/yum/centos-updates-el7/2021-02-04-00-43 /var/www/html/repos/yum/centos-updates-el7/2021-02-05-00-43 /var/www/html/repos/yum/centos-updates-el7/2020-10-08-08-42 == *\/\v\a\r\/\w\w\w\/\h\t\m\l\/\r\e\p\o\s\/\y\u\m\/\c\e\n\t\o\s\-\u\p\d\a\t\e\s\-\e\l\7\/\2\0\2\1\-\0\2\-\0\5\-\0\0\-\4\3* ]] + rm referenced_pkgs.txt + install_repo_pubkey centos-updates-el7 jenkins/data/mirrors-reposync.conf + local repo_name=centos-updates-el7 + local reposync_conf=jenkins/data/mirrors-reposync.conf + local gpg_key_file ++ sed -nr -e '/\[centos-updates-el7]/{ :loop; s#^gpgkey\s*=\s*file://(.*)$#\1#p; n; /^\[.*\]$/q ; b loop }' jenkins/data/mirrors-reposync.conf + gpg_key_file=/usr/share/distribution-gpg-keys/centos/RPM-GPG-KEY-CentOS-7 + [[ -n /usr/share/distribution-gpg-keys/centos/RPM-GPG-KEY-CentOS-7 ]] + [[ -r /usr/share/distribution-gpg-keys/centos/RPM-GPG-KEY-CentOS-7 ]] + sudo /usr/bin/rpmkeys --import /usr/share/distribution-gpg-keys/centos/RPM-GPG-KEY-CentOS-7 + echo 'Resyncing repo: centos-updates-el7' Resyncing repo: centos-updates-el7 + perform_yum_sync centos-updates-el7 x86_64 jenkins/data/mirrors-reposync.conf + local repo_name=centos-updates-el7 + local repo_archs=x86_64 + local reposync_conf=jenkins/data/mirrors-reposync.conf + local repo_mp + local repo_comps + local sync_newest_only + repo_mp=/var/www/html/repos/yum/centos-updates-el7/base ++ get_modulesmd_path centos-updates-el7 ++ local repo_name=centos-updates-el7 +++ sed -e 's/xmlns=".*"//g' /home/jenkins/mirrors_cache/centos-updates-el7/repomd.xml +++ xmllint --xpath 'string(/repomd/data[@type="modules"]/location/@href)' - +++ grep -o '[[:alnum:]_.-]*$' ++ filename= ++ [[ -z '' ]] ++ false + '[' -z '' ']' + sync_newest_only=--newest-only ++ IFS=, ++ echo x86_64 + for arch in '$(IFS=,; echo $repo_archs)' + echo 'Syncing yum repo centos-updates-el7 for arch: x86_64' Syncing yum repo centos-updates-el7 for arch: x86_64 + run_reposync centos-updates-el7 x86_64 jenkins/data/mirrors-reposync.conf --downloadcomps --gpgcheck --download-metadata --newest-only + local repo_name=centos-updates-el7 + local repo_arch=x86_64 + local reposync_conf=jenkins/data/mirrors-reposync.conf + extra_args=("${@:4}") + local extra_args + reposync --config=jenkins/data/mirrors-reposync.conf --repoid=centos-updates-el7 --arch=x86_64 --cachedir=/home/jenkins/mirrors_cache --download_path=/var/www/html/repos/yum/centos-updates-el7/base --norepopath --downloadcomps --gpgcheck --download-metadata --newest-only flatpak-builder-1.0.0-10.el7_9 FAILED (1/14): flatpak-1.0.9-10.e 0% [ ] 0.0 B/s | 0 B --:-- ETA flatpak-1.0.9-10.el7_9.x86_64. FAILED (1/14): flatpak-1.0.9-10.e 0% [ ] 0.0 B/s | 0 B --:-- ETA (2/14): flatpak-libs-1.0.9 0% [ ] 0.0 B/s | 0 B --:-- ETA flatpak-devel-1.0.9-10.el7_9.x FAILED (2/14): flatpak-libs-1.0.9 0% [ ] 0.0 B/s | 0 B --:-- ETA (2/14): glibc-2.17-323.el7 5% [- ] 0.0 B/s | 1.4 MB --:-- ETA flatpak-builder-1.0.0-10.el7_9 FAILED (2/14): glibc-2.17-323.el7 5% [- ] 0.0 B/s | 1.4 MB --:-- ETA flatpak-devel-1.0.9-10.el7_9.x FAILED (2/14): glibc-2.17-323.el7 5% [- ] 0.0 B/s | 1.4 MB --:-- ETA (1/14): glibc-static-2.17-323.el7_9.i686.rpm | 1.3 MB 00:00 (2/14): glibc-2.17-323.el7_9.x86_64.rpm | 3.6 MB 00:01 (3/14): glibc-devel-2.17-323.el7_9.i686.rpm | 1.1 MB 00:01 flatpak-1.0.9-10.el7_9.x86_64. FAILED (5/14): glibc-2.17-323.el7 5% [- ] 0.0 B/s | 1.4 MB --:-- ETA (4/14): glibc-static-2.17-323.el7_9.x86_64.rpm | 1.6 MB 00:00 (5/14): glibc-headers-2.17-323.el7_9.x86_64.rpm | 691 kB 00:01 (7/14): glibc-2.17-323.el7 43% [======- ] 15 MB/s | 12 MB 00:00 ETA (6/14): glibc-utils-2.17-323.el7_9.x86_64.rpm | 229 kB 00:00 flatpak-1.0.9-10.el7_9.x86_64. FAILED (8/14): glibc-2.17-323.el7 43% [======- ] 15 MB/s | 12 MB 00:00 ETA flatpak-builder-1.0.0-10.el7_9 FAILED (8/14): glibc-2.17-323.el7 43% [======- ] 15 MB/s | 12 MB 00:00 ETA flatpak-devel-1.0.9-10.el7_9.x FAILED (8/14): glibc-2.17-323.el7 43% [======- ] 15 MB/s | 12 MB 00:00 ETA flatpak-1.0.9-10.el7_9.x86_64. FAILED (8/14): glibc-2.17-323.el7 43% [======- ] 15 MB/s | 12 MB 00:00 ETA flatpak-builder-1.0.0-10.el7_9 FAILED (8/14): glibc-2.17-323.el7 43% [======- ] 15 MB/s | 12 MB 00:00 ETA flatpak-devel-1.0.9-10.el7_9.x FAILED (8/14): glibc-2.17-323.el7 43% [======- ] 15 MB/s | 12 MB 00:00 ETA (8/14): glibc-2.17-323.el7 54% [========- ] 15 MB/s | 15 MB 00:00 ETA (7/14): glibc-devel-2.17-323.el7_9.x86_64.rpm | 1.1 MB 00:01 (10/14): glibc-common-2.17 67% [==========- ] 15 MB/s | 18 MB 00:00 ETA (10/14): glibc-common-2.17 77% [============ ] 14 MB/s | 21 MB 00:00 ETA (8/14): glibc-common-2.17-323.el7_9.x86_64.rpm | 12 MB 00:02 (11/14): nscd-2.17-323.el7 83% [============= ] 14 MB/s | 23 MB 00:00 ETA (9/14): flatpak-libs-1.0.9 84% [=============- ] 13 MB/s | 23 MB 00:00 ETA (9/14): flatpak-libs-1.0.9 85% [=============- ] 12 MB/s | 23 MB 00:00 ETA (9/14): flatpak-libs-1.0.9 86% [=============- ] 11 MB/s | 24 MB 00:00 ETA (9/14): flatpak-libs-1.0.9 88% [============== ] 11 MB/s | 24 MB 00:00 ETA (10/14): glibc-2.17-323.el 89% [============== ] 10 MB/s | 24 MB 00:00 ETA (10/14): glibc-2.17-323.el 91% [==============- ] 9.5 MB/s | 25 MB 00:00 ETA (10/14): glibc-2.17-323.el 91% [==============- ] 8.9 MB/s | 25 MB 00:00 ETA (10/14): glibc-2.17-323.el 91% [==============- ] 8.4 MB/s | 25 MB 00:00 ETA (11/14): nscd-2.17-323.el7 92% [==============- ] 7.9 MB/s | 25 MB 00:00 ETA (9/14): glibc-2.17-323.el7_9.i686.rpm | 4.3 MB 00:05 flatpak-libs-1.0.9-10.el7_9.x8 FAILED (10/14): flatpak-libs-1.0. 92% [==============- ] 7.9 MB/s | 25 MB 00:00 ETA flatpak-libs-1.0.9-10.el7_9.x8 FAILED (10/14): nscd-2.17-323.el7 92% [==============- ] 7.9 MB/s | 25 MB 00:00 ETA flatpak-builder-1.0.0-10.el7_9 FAILED (10/14): nscd-2.17-323.el7 92% [==============- ] 7.9 MB/s | 25 MB 00:00 ETA flatpak-devel-1.0.9-10.el7_9.x FAILED (10/14): nscd-2.17-323.el7 92% [==============- ] 7.9 MB/s | 25 MB 00:00 ETA flatpak-builder-1.0.0-10.el7_9 FAILED (10/14): nscd-2.17-323.el7 92% [==============- ] 7.9 MB/s | 25 MB 00:00 ETA flatpak-devel-1.0.9-10.el7_9.x FAILED (10/14): nscd-2.17-323.el7 92% [==============- ] 7.9 MB/s | 25 MB 00:00 ETA flatpak-libs-1.0.9-10.el7_9.x8 FAILED (10/14): nscd-2.17-323.el7 92% [==============- ] 7.9 MB/s | 25 MB 00:00 ETA flatpak-builder-1.0.0-10.el7_9 FAILED (10/14): nscd-2.17-323.el7 92% [==============- ] 7.9 MB/s | 25 MB 00:00 ETA flatpak-devel-1.0.9-10.el7_9.x FAILED (10/14): nscd-2.17-323.el7 92% [==============- ] 7.9 MB/s | 25 MB 00:00 ETA nscd-2.17-323.el7_9.x86_64.rpm FAILED (10/14): nscd-2.17-323.el7 92% [==============- ] 7.9 MB/s | 25 MB 00:00 ETA flatpak-devel-1.0.9-10.el7_9.x FAILED (10/14): flatpak-1.0.9-10. 92% [==============- ] 7.9 MB/s | 25 MB 00:00 ETA flatpak-builder-1.0.0-10.el7_9 FAILED (10/14): flatpak-1.0.9-10. 92% [==============- ] 7.9 MB/s | 25 MB 00:00 ETA flatpak-libs-1.0.9-10.el7_9.x8 FAILED (10/14): flatpak-1.0.9-10. 92% [==============- ] 7.9 MB/s | 25 MB 00:00 ETA flatpak-devel-1.0.9-10.el7_9.x FAILED (10/14): flatpak-1.0.9-10. 92% [==============- ] 7.9 MB/s | 25 MB 00:00 ETA flatpak-libs-1.0.9-10.el7_9.x8 FAILED (10/14): flatpak-1.0.9-10. 92% [==============- ] 7.9 MB/s | 25 MB 00:00 ETA flatpak-builder-1.0.0-10.el7_9 FAILED (10/14): flatpak-1.0.9-10. 92% [==============- ] 7.9 MB/s | 25 MB 00:00 ETA (10/14): nscd-2.17-323.el7_9.x86_64.rpm | 288 kB 00:00 flatpak-1.0.9-10.el7_9.x86_64. FAILED (11/14): flatpak-1.0.9-10. 92% [==============- ] 7.9 MB/s | 25 MB 00:00 ETA flatpak-libs-1.0.9-10.el7_9.x8 FAILED (11/14): flatpak-devel-1.0 92% [==============- ] 7.9 MB/s | 25 MB 00:00 ETA flatpak-devel-1.0.9-10.el7_9.x FAILED (11/14): flatpak-devel-1.0 92% [==============- ] 7.9 MB/s | 25 MB 00:00 ETA flatpak-1.0.9-10.el7_9.x86_64. FAILED (11/14): flatpak-builder-1 92% [==============- ] 7.9 MB/s | 25 MB 00:00 ETA flatpak-libs-1.0.9-10.el7_9.x8 FAILED (11/14): flatpak-builder-1 92% [==============- ] 7.9 MB/s | 25 MB 00:00 ETA flatpak-1.0.9-10.el7_9.x86_64. FAILED (11/14): flatpak-builder-1 92% [==============- ] 7.9 MB/s | 25 MB 00:00 ETA flatpak-libs-1.0.9-10.el7_9.x8 FAILED (11/14): flatpak-builder-1 92% [==============- ] 7.9 MB/s | 25 MB 00:00 ETA flatpak-1.0.9-10.el7_9.x86_64. FAILED (11/14): flatpak-builder-1 92% [==============- ] 7.9 MB/s | 25 MB 00:00 ETA flatpak-libs-1.0.9-10.el7_9.x8 FAILED (11/14): flatpak-builder-1 92% [==============- ] 7.9 MB/s | 25 MB 00:00 ETA flatpak-1.0.9-10.el7_9.x86_64. FAILED (11/14): flatpak-builder-1 92% [==============- ] 7.9 MB/s | 25 MB 00:00 ETA flatpak-1.0.9-10.el7_9.x86_64. FAILED (11/14): flatpak-builder-1 92% [==============- ] 7.9 MB/s | 25 MB 00:00 ETA flatpak-libs-1.0.9-10.el7_9.x8 FAILED (11/14): flatpak-builder-1 92% [==============- ] 7.9 MB/s | 25 MB 00:00 ETA flatpak-builder-1.0.0-10.el7_9 FAILED (11/14): flatpak-builder-1 92% [==============- ] 7.9 MB/s | 25 MB 00:00 ETA flatpak-libs-1.0.9-10.el7_9.x86_64: [Errno 256] No more mirrors to try. flatpak-builder-1.0.0-10.el7_9.x86_64: [Errno 256] No more mirrors to try. flatpak-1.0.9-10.el7_9.x86_64: [Errno 256] No more mirrors to try. flatpak-devel-1.0.9-10.el7_9.x86_64: [Errno 256] No more mirrors to try. Build step 'Execute shell' marked build as failure

1 534

Re: [oVirt Jenkins] ovirt-system-tests_he-basic-suite-master - Build # 2046 - Failure!
by Yedidyah Bar David 22 Jul '21

22 Jul '21

On Tue, Jun 8, 2021 at 6:08 AM <jenkins(a)jenkins.phx.ovirt.org> wrote: > > Project: https://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-master/ > Build: https://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-master/2046/ > Build Number: 2046 > Build Status: Failure > Triggered By: Started by timer > > ------------------------------------- > Changes Since Last Success: > ------------------------------------- > Changes for Build #2046 > [Eitan Raviv] network: force select spm - wait for dc status > > > > > ----------------- > Failed Tests: > ----------------- > 1 tests failed. > FAILED: he-basic-suite-master.test-scenarios.test_004_basic_sanity.test_template_export > > Error Message: > ovirtsdk4.Error: Failed to read response: [(<pycurl.Curl object at 0x5624fe64d108>, 7, 'Failed to connect to 192.168.200.99 port 443: Connection refused')] - The engine VM went down: https://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-master/2046… MainThread::INFO::2021-06-08 05:07:34,414::hosted_engine::517::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_monitoring_loop) Current state EngineUp (score: 3400) MainThread::INFO::2021-06-08 05:07:44,575::states::135::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(score) Penalizing score by 960 due to network status - Because HA monitoring failed to get a reply from the dns server: https://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-master/2046… Thread-1::WARNING::2021-06-08 05:07:25,486::network::120::network.Network::(_dns) DNS query failed: ; <<>> DiG 9.11.26-RedHat-9.11.26-4.el8_4 <<>> +tries=1 +time=5 ;; global options: +cmd ;; connection timed out; no servers could be reached Thread-3::INFO::2021-06-08 05:07:28,543::mem_free::51::mem_free.MemFree::(action) memFree: 1801 Thread-5::INFO::2021-06-08 05:07:28,972::engine_health::246::engine_health.EngineHealth::(_result_from_stats) VM is up on this host with healthy engine Thread-2::INFO::2021-06-08 05:07:31,532::mgmt_bridge::65::mgmt_bridge.MgmtBridge::(action) Found bridge ovirtmgmt in up state Thread-1::WARNING::2021-06-08 05:07:33,011::network::120::network.Network::(_dns) DNS query failed: ; <<>> DiG 9.11.26-RedHat-9.11.26-4.el8_4 <<>> +tries=1 +time=5 ;; global options: +cmd ;; connection timed out; no servers could be reached Thread-4::INFO::2021-06-08 05:07:37,433::cpu_load_no_engine::126::cpu_load_no_engine.CpuLoadNoEngine::(calculate_load) System load total=0.3196, engine=0.1724, non-engine=0.1472 Thread-3::INFO::2021-06-08 05:07:37,839::mem_free::51::mem_free.MemFree::(action) memFree: 1735 Thread-5::INFO::2021-06-08 05:07:39,146::engine_health::246::engine_health.EngineHealth::(_result_from_stats) VM is up on this host with healthy engine Thread-1::WARNING::2021-06-08 05:07:40,535::network::120::network.Network::(_dns) DNS query failed: ; <<>> DiG 9.11.26-RedHat-9.11.26-4.el8_4 <<>> +tries=1 +time=5 ;; global options: +cmd ;; connection timed out; no servers could be reached Thread-1::WARNING::2021-06-08 05:07:40,535::network::92::network.Network::(action) Failed to verify network status, (2 out of 5) - Not sure why. DNS servers: https://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-master/2046… # Generated by NetworkManager search lago.local nameserver 192.168.200.1 nameserver fe80::5054:ff:fe0c:9ad0%ovirtmgmt nameserver fd8f:1391:3a82:200::1 - The command we run is 'dig +tries=1 +time=5', which defaults to querying for '.' (the dns root). This is normally cached locally, but has a TTL of 86400, meaning it can be cached for up to one day. So if we ran this query right after it expired, _and_ then the local dns server had some issues forwarding our request (due to external issues, perhaps), then it would fail like this. I am going to ignore this failure for now, assuming it was temporary, but it might be worth opening an RFE on ovirt-hosted-engine-ha asking for some more flexibility - setting the query string or something similar. I think that this bug is probably quite hard to reproduce, because normally, all hosts will use the same dns server, and problems with it will affect all of them similarly. - Anyway, it seems like there were temporary connectivity issues on the network there. A minute later: https://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-master/2046… Thread-1::INFO::2021-06-08 05:08:08,143::network::88::network.Network::(action) Successfully verified network status But that was too late and the engine VM was already on its way down. A remaining open question is whether we should retry before giving up, and where - in the SDK, in OST code, etc. - or whether this should be considered normal. Best regards, -- Didi

4 8

[oVirt Jenkins] ovirt-system-tests_basic-suite-4.3_el7-nightly - Build # 610 - Failure!
by jenkins＠jenkins.phx.ovirt.org 01 Jul '21

01 Jul '21

Project: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-4.3_el7-nightl… Build: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-4.3_el7-nightl… Build Number: 610 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #610 [parthdhanjal] Updating max click version ----------------- Failed Tests: ----------------- No tests ran.

1 2

oVirt infra daily report - unstable production jobs - 1603
by jenkins＠jenkins.phx.ovirt.org 01 Jul '21

01 Jul '21

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

1 0

Build failed in Jenkins: system-sync_mirrors-centos-base-el8stream-x86_64 #1
by jenkins＠jenkins.phx.ovirt.org 30 Jun '21

30 Jun '21

See <https://jenkins.ovirt.org/job/system-sync_mirrors-centos-base-el8stream-x86…> Changes: ------------------------------------------ Started by user Ehud Yonasi Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <https://jenkins.ovirt.org/job/system-sync_mirrors-centos-base-el8stream-x86…> The recommended git tool is: NONE No credentials specified Cloning the remote Git repository Cloning repository http://gerrit.ovirt.org/jenkins.git > git init <https://jenkins.ovirt.org/job/system-sync_mirrors-centos-base-el8stream-x86…> # timeout=10 Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git > git --version # timeout=10 > git --version # 'git version 1.8.3.1' > git fetch --tags --progress http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* # timeout=10 > git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10 > git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 No valid HEAD. Skipping the resetting > git clean -fdx # timeout=10 Pruning obsolete local branches Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git > git fetch --tags --progress --prune http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* # timeout=10 > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision 092d8431fd81a706fb10ce2a8474ffb1e193f0ac (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 092d8431fd81a706fb10ce2a8474ffb1e193f0ac # timeout=10 Commit message: "mirrors: add el8stream repos." First time build. Skipping changelog. [system-sync_mirrors-centos-base-el8stream-x86_64] $ /bin/bash -xe /tmp/jenkins8775310128401720512.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror centos-base-el8stream 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 + YUM_PATH=/yum/ + MIRRORS_BASE_PREFIX=/var/www/html/repos/yum/ + REPOQUERY_HTTP_BASE=http://mirrors.phx.ovirt.org/repos/yum/ + MAX_LOCK_ATTEMPTS=120 + LOCK_WAIT_INTERVAL=5 + LOCK_BASE=/home/jenkins + OLD_MD_TO_KEEP=100 + MAX_AGE=14 + HTTP_SELINUX_TYPE=httpd_sys_content_t + HTTP_FILE_MODE=644 + main resync_yum_mirror centos-base-el8stream x86_64 jenkins/data/mirrors-reposync.conf + local command=resync_yum_mirror + command_args=("${@:2}") + local command_args + cmd_resync_yum_mirror centos-base-el8stream x86_64 jenkins/data/mirrors-reposync.conf + local repo_name=centos-base-el8stream + local repo_archs=x86_64 + local reposync_conf=jenkins/data/mirrors-reposync.conf + local sync_needed + mkdir -p /home/jenkins/mirrors_cache + verify_repo_fs centos-base-el8stream yum + local repo_name=centos-base-el8stream + local repo_type=yum + sudo install -o jenkins -d /var/www/html/repos/yum /var/www/html/repos/yum/centos-base-el8stream /var/www/html/repos/yum/centos-base-el8stream/base + modify_reposync_conf centos-base-el8stream jenkins/data/mirrors-reposync.conf + local repo_name=centos-base-el8stream + local reposync_conf=jenkins/data/mirrors-reposync.conf + local tmp_file=reposync.tmp + awk -v RS= -v 'ORS=\n\n' /main/ jenkins/data/mirrors-reposync.conf + awk -v RS= -v 'ORS=\n\n' /centos-base-el8stream/ jenkins/data/mirrors-reposync.conf + mv reposync.tmp jenkins/data/mirrors-reposync.conf + check_yum_sync_needed centos-base-el8stream x86_64 jenkins/data/mirrors-reposync.conf sync_needed + local repo_name=centos-base-el8stream + local repo_archs=x86_64 + local reposync_conf=jenkins/data/mirrors-reposync.conf + local p_sync_needed=sync_needed + local reposync_out + echo 'Checking if mirror needs a resync' Checking if mirror needs a resync + rm -rf /home/jenkins/mirrors_cache/centos-base-el8stream ++ IFS=, ++ echo x86_64 + for arch in '$(IFS=,; echo $repo_archs)' ++ run_reposync centos-base-el8stream x86_64 jenkins/data/mirrors-reposync.conf --urls --quiet ++ local repo_name=centos-base-el8stream ++ local repo_arch=x86_64 ++ local reposync_conf=jenkins/data/mirrors-reposync.conf ++ extra_args=("${@:4}") ++ local extra_args ++ reposync --config=jenkins/data/mirrors-reposync.conf --repoid=centos-base-el8stream --arch=x86_64 --cachedir=/home/jenkins/mirrors_cache --download_path=/var/www/html/repos/yum/centos-base-el8stream/base --norepopath --urls --quiet Error setting up repositories: failure: repodata/195f0092e01a525af77b3d8cc0c51d56d34582efafce301ccb7e8c6fe2ee2402-primary.sqlite.xz from centos-base-el8stream: [Errno 256] No more mirrors to try. http://mirror.centos.org/centos/8-stream/BaseOS/x86_64/os/repodata/195f0092…: [Errno 14] HTTP Error 404 - Not Found + reposync_out= Build step 'Execute shell' marked build as failure

1 1

[JIRA] (OVIRT-3099) Re: oVirt CI mirror for centos stream advancedvirt-common repo
by Ehud Yonasi (oVirt JIRA) 30 Jun '21

30 Jun '21

[ https://ovirt-jira.atlassian.net/browse/OVIRT-3099?page=com.atlassian.jira.… ] Ehud Yonasi commented on OVIRT-3099: ------------------------------------ Hi Nir, You are right, we are not mirroring right now the centos8 stream repos. I've sent a patch to add them. https://gerrit.ovirt.org/c/jenkins/+/115492 On Tue, Jun 22, 2021 at 8:37 PM Nir Soffer <nsoffer(a)redhat.com> wrote: > On Fri, Jun 11, 2021 at 12:41 PM Sandro Bonazzola <sbonazzo(a)redhat.com> > wrote: > >> >> >> Il giorno ven 4 giu 2021 alle ore 19:44 Nir Soffer <nsoffer(a)redhat.com> >> ha scritto: >> >>> I updated vdsm libvirt requirement to 7.0.0-14. The package exists in >>> centos >>> stream and rhel so the change is correct, but the install check fails in >>> the CI. >>> >>> I found that adding the repo to check-patch.repos works: >>> https://gerrit.ovirt.org/c/vdsm/+/115039/4/automation/check-patch.repos >>> >>> But depending on mirror.centos.org does not feel like the right way. I >>> think >>> keeping a local mirror is the right way. >>> >> >> Please note that despite we are pointing to centos mirrors, CI is running >> under proxy, so we are caching on our datacenter the rpms we consume anyway. >> That said, we can mirror advanced virtualization repos as well and the >> local mirror will be automatically picked up. >> >> I see we are already mirroring the test repo for CentOS Linux: >> ./data/mirrors-reposync.conf: >> 70 : [ovirt-master-centos-advanced-virtualization-el8] >> 72 : baseurl= >> https://buildlogs.centos.org/centos/8/virt/x86_64/advanced-virtualization/ >> >> For CentOS Stream we'll need an addition there. Please open a ticket on >> infra-support(a)ovirt.org about it. >> > > Trying > > >> >> >> >>> It looks like the stdci docs[1] are not maintained for a while, >>> listing mirrors for >>> fedora 30 and centos 7. >>> >> >> I would suggest to open a ticket for this as well >> >> >> >>> >>> Looking in the mirrors jobs[2] we have advanced-virtualization for >>> centos[3] but >>> it holds old versions (6.x). >>> >>> Can we add a local mirror for this repo? >>> >>> [1] >>> https://ovirt-infra-docs.readthedocs.io/en/latest/CI/List_of_mirrors/index.… >>> [2] https://jenkins.ovirt.org/search/?q=system-sync_mirrors >>> [3] >>> https://buildlogs.centos.org/centos/8/virt/x86_64/advanced-virtualization/P… >>> >>> Nir >>> >>> >> >> -- >> >> Sandro Bonazzola >> >> MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV >> >> Red Hat EMEA <https://www.redhat.com/> >> >> sbonazzo(a)redhat.com >> <https://www.redhat.com/> >> >> *Red Hat respects your work life balance. Therefore there is no need to >> answer this email out of your office hours. >> <https://mojo.redhat.com/docs/DOC-1199578>* >> >> >> > Re: oVirt CI mirror for centos stream advancedvirt-common repo > -------------------------------------------------------------- > > Key: OVIRT-3099 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3099 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > On Fri, Jun 11, 2021 at 12:41 PM Sandro Bonazzola <sbonazzo(a)redhat.com> > wrote: > > > > > > Il giorno ven 4 giu 2021 alle ore 19:44 Nir Soffer <nsoffer(a)redhat.com> > > ha scritto: > > > >> I updated vdsm libvirt requirement to 7.0.0-14. The package exists in > >> centos > >> stream and rhel so the change is correct, but the install check fails in > >> the CI. > >> > >> I found that adding the repo to check-patch.repos works: > >> https://gerrit.ovirt.org/c/vdsm/+/115039/4/automation/check-patch.repos > >> > >> But depending on mirror.centos.org does not feel like the right way. I > >> think > >> keeping a local mirror is the right way. > >> > > > > Please note that despite we are pointing to centos mirrors, CI is running > > under proxy, so we are caching on our datacenter the rpms we consume anyway. > > That said, we can mirror advanced virtualization repos as well and the > > local mirror will be automatically picked up. > > > > I see we are already mirroring the test repo for CentOS Linux: > > ./data/mirrors-reposync.conf: > > 70 : [ovirt-master-centos-advanced-virtualization-el8] > > 72 : baseurl= > > https://buildlogs.centos.org/centos/8/virt/x86_64/advanced-virtualization/ > > > > For CentOS Stream we'll need an addition there. Please open a ticket on > > infra-support(a)ovirt.org about it. > > > Trying > > > > > > > >> It looks like the stdci docs[1] are not maintained for a while, > >> listing mirrors for > >> fedora 30 and centos 7. > >> > > > > I would suggest to open a ticket for this as well > > > > > > > >> > >> Looking in the mirrors jobs[2] we have advanced-virtualization for > >> centos[3] but > >> it holds old versions (6.x). > >> > >> Can we add a local mirror for this repo? > >> > >> [1] > >> https://ovirt-infra-docs.readthedocs.io/en/latest/CI/List_of_mirrors/index.… > >> [2] https://jenkins.ovirt.org/search/?q=system-sync_mirrors > >> [3] > >> https://buildlogs.centos.org/centos/8/virt/x86_64/advanced-virtualization/P… > >> > >> Nir > >> > >> > > > > -- > > > > Sandro Bonazzola > > > > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > > > > Red Hat EMEA <https://www.redhat.com/> > > > > sbonazzo(a)redhat.com > > <https://www.redhat.com/> > > > > *Red Hat respects your work life balance. Therefore there is no need to > > answer this email out of your office hours. > > <https://mojo.redhat.com/docs/DOC-1199578>* > > > > > > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100166)

1 0

nothing provides rpm = 4.14.3-14.el8_4 needed by rpm-build-4.14.3-14.el8_4.x86_64
by Yedidyah Bar David 30 Jun '21

30 Jun '21

On Wed, Jun 30, 2021 at 3:20 PM Code Review <gerrit(a)ovirt.org> wrote: > > From Jenkins CI <jenkins(a)ovirt.org>: > > Jenkins CI has posted comments on this change. ( https://gerrit.ovirt.org/c/ovirt-system-tests/+/115276 ) > > Change subject: Get rid of default_backend > ...................................................................... > > > Patch Set 21: Continuous-Integration-1 > > Build Failed > > https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/17555/ : FAILURE Failed with: nothing provides rpm = 4.14.3-14.el8_4 needed by rpm-build-4.14.3-14.el8_4.x86_64 Any clue? Thanks, -- Didi

3 2

[CQ]: 115488,1 (jenkins) failed "dummy-master" system tests
by oVirt Jenkins 30 Jun '21

30 Jun '21

Change 115488,1 (jenkins) is probably the reason behind recent system test failures in the "dummy-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://gerrit.ovirt.org/c/jenkins/+/#/c/115488/1 For failed test results see: https://jenkins.ovirt.org/job/dummy-master_change-queue-tester/631/

1 0

[oVirt Jenkins] deploy-to-gated-dummy-master - Build #559 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 30 Jun '21

30 Jun '21

Build: https://jenkins.ovirt.org/job/deploy-to-gated-dummy-master/559/ Build Name: #559 Build Status: FAILURE Gerrit change: null - title: null - project: null - branch: null - author: null <null>

1 0

[CQ]: 115417,3 (ovirt-imageio) failed "ovirt-master" system tests
by oVirt Jenkins 30 Jun '21

30 Jun '21

Change 115417,3 (ovirt-imageio) 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://gerrit.ovirt.org/c/ovirt-imageio/+/#/c/115417/3 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/30539/

1 0

[oVirt Jenkins] ovirt-system-tests_basic-suite-4.3_nightly - Build # 614 - Failure!
by jenkins＠jenkins.phx.ovirt.org 30 Jun '21

30 Jun '21

Project: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-4.3_nightly/ Build: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-4.3_nightly/61… Build Number: 614 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #614 [parthdhanjal] Updating max click version ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 004_basic_sanity.run_vms Error Message: Fault reason is "Operation Failed". Fault detail is "[Network error during communication with the Host.]". HTTP response code is 400. Stack Trace: Traceback (most recent call last): File "/usr/lib64/python2.7/unittest/case.py", line 369, in run testMethod() File "/usr/lib/python2.7/site-packages/nose/case.py", line 197, in runTest self.test(*self.arg) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 142, in wrapped_test test() File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 60, in wrapper return func(get_test_prefix(), *args, **kwargs) File "/home/jenkins/agent/workspace/ovirt-system-tests_basic-suite-4.3_nightly/ovirt-system-tests/basic-suite-4.3/test-scenarios/004_basic_sanity.py", line 694, in run_vms vm0_service.start(use_cloud_init=True, vm=vm_params) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 32520, in start return self._internal_action(action, 'start', None, headers, query, wait) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 299, in _internal_action return future.wait() if wait else future File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 55, in wait return self._code(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 296, in callback self._check_fault(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 134, in _check_fault self._raise_error(response, body.fault) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 118, in _raise_error raise error Error: Fault reason is "Operation Failed". Fault detail is "[Network error during communication with the Host.]". HTTP response code is 400.

1 2

[oVirt Jenkins] ovirt-system-tests_basic-suite-4.3_el7-nightly - Build # 607 - Failure!
by jenkins＠jenkins.phx.ovirt.org 30 Jun '21

30 Jun '21

Project: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-4.3_el7-nightl… Build: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-4.3_el7-nightl… Build Number: 607 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #607 [parthdhanjal] Updating max click version ----------------- Failed Tests: ----------------- No tests ran.

1 2

[oVirt Jenkins] ovirt-system-tests_basic-suite-master_nightly - Build # 1276 - Failure!
by jenkins＠jenkins.phx.ovirt.org 30 Jun '21

30 Jun '21

Project: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-master_nightly/ Build: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-master_nightly… Build Number: 1276 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #1276 [Lucia Jelinkova] UI: Change the navigation in the left menu ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: basic-suite-master.test-scenarios.test_100_basic_ui_sanity.test_userportal[firefox] Error Message: selenium.common.exceptions.TimeoutException: Message: Wait until VM Portal is displayed failed Stack Trace: ovirt_driver = <ost_utils.selenium.navigation.driver.Driver object at 0x7f745aad60f0> nonadmin_username = 'non_admin_user', nonadmin_password = '123456' user_login = <function user_login.<locals>.login at 0x7f745aafebf8> engine_webadmin_url = 'https://engine/ovirt-engine' def test_userportal(ovirt_driver, nonadmin_username, nonadmin_password, user_login, engine_webadmin_url): welcome_screen = WelcomeScreen(ovirt_driver) welcome_screen.wait_for_displayed() welcome_screen.open_user_portal() user_login(nonadmin_username, nonadmin_password) vm_portal = VmPortal(ovirt_driver) > vm_portal.wait_for_displayed() basic-suite-master/test-scenarios/test_100_basic_ui_sanity.py:524: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ ost_utils/ost_utils/selenium/page_objects/Displayable.py:14: in wait_for_displayed self.ovirt_driver.wait_until('Wait until ' + self.get_displayable_name() + ' is displayed failed', self.is_displayed) ost_utils/ost_utils/selenium/navigation/driver.py:276: in wait_until self._wait_until(message, assertions.SHORT_TIMEOUT, condition_method, *args) ost_utils/ost_utils/selenium/navigation/driver.py:282: in _wait_until WebDriverWait(self.driver, timeout).until(ConditionClass(condition_method, *args), message) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = <selenium.webdriver.support.wait.WebDriverWait (session="16ad857f-4407-4e03-8c00-1f6cc4f224af")> method = <ost_utils.selenium.navigation.driver.ConditionClass object at 0x7f745aa2f080> message = 'Wait until VM Portal is displayed failed' def until(self, method, message=''): """Calls the method provided with the driver as an argument until the \ return value is not False.""" screen = None stacktrace = None end_time = time.time() + self._timeout while True: try: value = method(self._driver) if value: return value except self._ignored_exceptions as exc: screen = getattr(exc, 'screen', None) stacktrace = getattr(exc, 'stacktrace', None) time.sleep(self._poll) if time.time() > end_time: break > raise TimeoutException(message, screen, stacktrace) E selenium.common.exceptions.TimeoutException: Message: Wait until VM Portal is displayed failed .tox/deps/lib/python3.6/site-packages/selenium/webdriver/support/wait.py:80: TimeoutException

1 1

oVirt infra daily report - unstable production jobs - 1602
by jenkins＠jenkins.phx.ovirt.org 30 Jun '21

30 Jun '21

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

1 0

[CQ]: 115273, 16 (ovirt-system-tests) failed "ovirt-master" system tests
by oVirt Jenkins 29 Jun '21

29 Jun '21

Change 115273,16 (ovirt-system-tests) 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://gerrit.ovirt.org/c/ovirt-system-tests/+/#/c/115273/16 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/30509/

1 0

[oVirt Jenkins] ovirt-system-tests_basic-suite-master_nightly - Build # 1273 - Failure!
by jenkins＠jenkins.phx.ovirt.org 29 Jun '21

29 Jun '21

Project: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-master_nightly/ Build: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-master_nightly… Build Number: 1273 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #1273 [Galit Rosenthal] Update ost-repo, repo was changed ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: basic-suite-master.test-scenarios.test_100_basic_ui_sanity.test_clusters[firefox] Error Message: selenium.common.exceptions.TimeoutException: Message: Clusters menu is not displayed Stack Trace: ovirt_driver = <ost_utils.selenium.navigation.driver.Driver object at 0x7fa4d2410a20> def test_clusters(ovirt_driver): webadmin_menu = WebAdminLeftMenu(ovirt_driver) > cluster_list_view = webadmin_menu.open_cluster_list_view() basic-suite-master/test-scenarios/test_100_basic_ui_sanity.py:301: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ ost_utils/ost_utils/selenium/page_objects/WebAdminLeftMenu.py:69: in open_cluster_list_view self._open_compute_menu('Clusters', 'MenuView_clustersAnchor') ost_utils/ost_utils/selenium/page_objects/WebAdminLeftMenu.py:95: in _open_compute_menu self._open_menu('compute', menu_name, menu_id) ost_utils/ost_utils/selenium/page_objects/WebAdminLeftMenu.py:105: in _open_menu self.ovirt_driver.id_wait_and_click(menu_name + ' menu', menu_id) ost_utils/ost_utils/selenium/navigation/driver.py:231: in id_wait_and_click self.xpath_wait_and_click(message, '//*[@id="' + element_id + '"]', wait_long) ost_utils/ost_utils/selenium/navigation/driver.py:301: in xpath_wait_and_click wait_until(message + ' is not displayed', self.is_xpath_displayed, xpath) ost_utils/ost_utils/selenium/navigation/driver.py:306: in wait_until self._wait_until(message, assertions.SHORT_TIMEOUT, condition_method, *args) ost_utils/ost_utils/selenium/navigation/driver.py:312: in _wait_until WebDriverWait(self.driver, timeout).until(ConditionClass(condition_method, *args), message) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = <selenium.webdriver.support.wait.WebDriverWait (session="0a6d2c5b-25ac-4c5f-8d8d-3bde1f2c5820")> method = <ost_utils.selenium.navigation.driver.ConditionClass object at 0x7fa4d2473b00> message = 'Clusters menu is not displayed' def until(self, method, message=''): """Calls the method provided with the driver as an argument until the \ return value is not False.""" screen = None stacktrace = None end_time = time.time() + self._timeout while True: try: value = method(self._driver) if value: return value except self._ignored_exceptions as exc: screen = getattr(exc, 'screen', None) stacktrace = getattr(exc, 'stacktrace', None) time.sleep(self._poll) if time.time() > end_time: break > raise TimeoutException(message, screen, stacktrace) E selenium.common.exceptions.TimeoutException: Message: Clusters menu is not displayed .tox/deps/lib/python3.6/site-packages/selenium/webdriver/support/wait.py:80: TimeoutException

1 2

[oVirt Jenkins] ovirt-system-tests_basic-suite-4.3_el7-nightly - Build # 604 - Failure!
by jenkins＠jenkins.phx.ovirt.org 29 Jun '21

29 Jun '21

Project: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-4.3_el7-nightl… Build: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-4.3_el7-nightl… Build Number: 604 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #604 [parthdhanjal] Updating max click version ----------------- Failed Tests: ----------------- No tests ran.

1 2

[oVirt Jenkins] cleanup-gated-dummy-master - Build #556 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 29 Jun '21

29 Jun '21

Build: https://jenkins.ovirt.org/job/cleanup-gated-dummy-master/556/ Build Name: #556 Build Status: FAILURE Gerrit change: null - title: null - project: null - branch: null - author: null <null>

1 0

oVirt infra daily report - unstable production jobs - 1601
by jenkins＠jenkins.phx.ovirt.org 29 Jun '21

29 Jun '21

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

1 0

[CQ]: 115458, 1 (ovirt-node-ng-image) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 29 Jun '21

29 Jun '21

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

1 0

[JIRA] (OVIRT-3106) [FIRING:1] InstanceUnreachable ibm-srv09.ovirt.org kubernetes-nodes-exporter (amd64 linux ibm-srv09.ovirt.org true external bare-metal-external ci)
by Alertmanager_Bot (oVirt JIRA) 28 Jun '21

28 Jun '21

Alertmanager_Bot created OVIRT-3106: --------------------------------------- Summary: [FIRING:1] InstanceUnreachable ibm-srv09.ovirt.org kubernetes-nodes-exporter (amd64 linux ibm-srv09.ovirt.org true external bare-metal-external ci) Key: OVIRT-3106 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3106 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Alertmanager_Bot Assignee: infra Labels: - alertname = InstanceUnreachable - beta_kubernetes_io_arch = amd64 - beta_kubernetes_io_os = linux - instance = ibm-srv09.ovirt.org - job = kubernetes-nodes-exporter - kubernetes_io_hostname = ibm-srv09.ovirt.org - node_role_kubernetes_io_compute = true - region = external - type = bare-metal-external - zone = ci Annotations: - description = ibm-srv09.ovirt.org of job kubernetes-nodes-exporter has been possibly down for more than 10 minutes. Source: http://prometheus-0:9090/graph?g0.expr=up%7Bjob%3D%22kubernetes-nodes-expor… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100166)

1 0

[JIRA] (OVIRT-3105) [FIRING:1] InstanceUnreachable ibm-srv07.ovirt.org kubernetes-nodes-exporter (amd64 linux ibm-srv07.ovirt.org true external bare-metal-external ci)
by Alertmanager_Bot (oVirt JIRA) 28 Jun '21

28 Jun '21

Alertmanager_Bot created OVIRT-3105: --------------------------------------- Summary: [FIRING:1] InstanceUnreachable ibm-srv07.ovirt.org kubernetes-nodes-exporter (amd64 linux ibm-srv07.ovirt.org true external bare-metal-external ci) Key: OVIRT-3105 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3105 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Alertmanager_Bot Assignee: infra Labels: - alertname = InstanceUnreachable - beta_kubernetes_io_arch = amd64 - beta_kubernetes_io_os = linux - instance = ibm-srv07.ovirt.org - job = kubernetes-nodes-exporter - kubernetes_io_hostname = ibm-srv07.ovirt.org - node_role_kubernetes_io_compute = true - region = external - type = bare-metal-external - zone = ci Annotations: - description = ibm-srv07.ovirt.org of job kubernetes-nodes-exporter has been possibly down for more than 10 minutes. Source: http://prometheus-0:9090/graph?g0.expr=up%7Bjob%3D%22kubernetes-nodes-expor… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100166)

1 0

[JIRA] (OVIRT-3104) [FIRING:1] InstanceUnreachable ibm-srv08.ovirt.org kubernetes-nodes-exporter (amd64 linux ibm-srv08.ovirt.org true external bare-metal-external ci)
by Alertmanager_Bot (oVirt JIRA) 28 Jun '21

28 Jun '21

Alertmanager_Bot created OVIRT-3104: --------------------------------------- Summary: [FIRING:1] InstanceUnreachable ibm-srv08.ovirt.org kubernetes-nodes-exporter (amd64 linux ibm-srv08.ovirt.org true external bare-metal-external ci) Key: OVIRT-3104 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3104 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Alertmanager_Bot Assignee: infra Labels: - alertname = InstanceUnreachable - beta_kubernetes_io_arch = amd64 - beta_kubernetes_io_os = linux - instance = ibm-srv08.ovirt.org - job = kubernetes-nodes-exporter - kubernetes_io_hostname = ibm-srv08.ovirt.org - node_role_kubernetes_io_compute = true - region = external - type = bare-metal-external - zone = ci Annotations: - description = ibm-srv08.ovirt.org of job kubernetes-nodes-exporter has been possibly down for more than 10 minutes. Source: http://prometheus-0:9090/graph?g0.expr=up%7Bjob%3D%22kubernetes-nodes-expor… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100166)

1 0

[JIRA] (OVIRT-3103) Re: [ovirt-devel] Re: 2FA requirement for oVirt GitHub org?
by Arik Hadas (oVirt JIRA) 28 Jun '21

28 Jun '21

[ https://ovirt-jira.atlassian.net/browse/OVIRT-3103?page=com.atlassian.jira.… ] Arik Hadas updated OVIRT-3103: ------------------------------ Attachment: image.png On Mon, Jun 28, 2021 at 3:26 PM Sandro Bonazzola <sbonazzo(a)redhat.com> wrote: > HI, just an heads up that turning on the 2FA will have some side effects: > > Require two-factor authentication for everyone in the oVirt organization. > Members, billing managers, and outside collaborators who do not have > two-factor authentication enabled for their personal account will be > removed from the organization and will receive an email notifying them > about the change. > > So before turning it on, we need to ensure we are not going to disrupt the > org. > +1 I don't know if it's that way by default when enabling the 2FA but when other organizations enabled it, users were allowed to keeping signing in using password for several weeks and only then those that didn't set it up were dropped from the organization > > Il giorno lun 28 giu 2021 alle ore 14:20 Martin Perina <mperina(a)redhat.com> > ha scritto: > >> >> >> On Mon, Jun 28, 2021 at 11:58 AM Sandro Bonazzola <sbonazzo(a)redhat.com> >> wrote: >> >>> +1 for enabling 2FA on my side >>> >> >> +1 >> >>> >>> Il giorno lun 28 giu 2021 alle ore 11:50 Janos Pasztor <janos(a)redhat.com> >>> ha scritto: >>> >>>> Hey folks, >>>> >>>> I just noticed that we don't have 2FA enforcement on the oVirt GitHub >>>> org. >>>> >>>> [image: image.png] >>>> Is this just an oversight or is it intentional? May I propose to turn >>>> 2FA enforcement on? >>>> >>>> Janos >>>> _______________________________________________ >>>> Devel mailing list -- devel(a)ovirt.org >>>> To unsubscribe send an email to devel-leave(a)ovirt.org >>>> Privacy Statement: https://www.ovirt.org/privacy-policy.html >>>> oVirt Code of Conduct: >>>> https://www.ovirt.org/community/about/community-guidelines/ >>>> List Archives: >>>> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/SASNDGLK3FBKB… >>>> >>> >>> >>> -- >>> >>> Sandro Bonazzola >>> >>> MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV >>> >>> Red Hat EMEA <https://www.redhat.com/> >>> >>> sbonazzo(a)redhat.com >>> <https://www.redhat.com/> >>> >>> *Red Hat respects your work life balance. Therefore there is no need to >>> answer this email out of your office hours.* >>> >>> >>> _______________________________________________ >>> Devel mailing list -- devel(a)ovirt.org >>> To unsubscribe send an email to devel-leave(a)ovirt.org >>> Privacy Statement: https://www.ovirt.org/privacy-policy.html >>> oVirt Code of Conduct: >>> https://www.ovirt.org/community/about/community-guidelines/ >>> List Archives: >>> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/CDSTENA6B4YNU… >>> >> >> >> -- >> Martin Perina >> Manager, Software Engineering >> Red Hat Czech s.r.o. >> > > > -- > > Sandro Bonazzola > > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > > Red Hat EMEA <https://www.redhat.com/> > > sbonazzo(a)redhat.com > <https://www.redhat.com/> > > *Red Hat respects your work life balance. Therefore there is no need to > answer this email out of your office hours.* > > > _______________________________________________ > Devel mailing list -- devel(a)ovirt.org > To unsubscribe send an email to devel-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/devel@ovirt.org/message/AI56Q2PSY3PN2… > > Re: [ovirt-devel] Re: 2FA requirement for oVirt GitHub org? > ----------------------------------------------------------- > > Key: OVIRT-3103 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3103 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Martin Perina > Assignee: infra > Attachments: image.png, image.png, image.png, image.png > > > On Mon, Jun 28, 2021 at 11:58 AM Sandro Bonazzola <sbonazzo(a)redhat.com> > wrote: > > +1 for enabling 2FA on my side > > > +1 > > > > Il giorno lun 28 giu 2021 alle ore 11:50 Janos Pasztor <janos(a)redhat.com> > > ha scritto: > > > >> Hey folks, > >> > >> I just noticed that we don't have 2FA enforcement on the oVirt GitHub > >> org. > >> > >> [image: image.png] > >> Is this just an oversight or is it intentional? May I propose to turn 2FA > >> enforcement on? > >> > >> Janos > >> _______________________________________________ > >> Devel mailing list -- devel(a)ovirt.org > >> To unsubscribe send an email to devel-leave(a)ovirt.org > >> Privacy Statement: https://www.ovirt.org/privacy-policy.html > >> oVirt Code of Conduct: > >> https://www.ovirt.org/community/about/community-guidelines/ > >> List Archives: > >> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/SASNDGLK3FBKB… > >> > > > > > > -- > > > > Sandro Bonazzola > > > > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > > > > Red Hat EMEA <https://www.redhat.com/> > > > > sbonazzo(a)redhat.com > > <https://www.redhat.com/> > > > > *Red Hat respects your work life balance. Therefore there is no need to > > answer this email out of your office hours.* > > > > > > _______________________________________________ > > Devel mailing list -- devel(a)ovirt.org > > To unsubscribe send an email to devel-leave(a)ovirt.org > > Privacy Statement: https://www.ovirt.org/privacy-policy.html > > oVirt Code of Conduct: > > https://www.ovirt.org/community/about/community-guidelines/ > > List Archives: > > https://lists.ovirt.org/archives/list/devel@ovirt.org/message/CDSTENA6B4YNU… > > > -- > Martin Perina > Manager, Software Engineering > Red Hat Czech s.r.o. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100166)

1 0

[JIRA] (OVIRT-3103) Re: [ovirt-devel] Re: 2FA requirement for oVirt GitHub org?
by Ehud Yonasi (oVirt JIRA) 28 Jun '21

28 Jun '21

[ https://ovirt-jira.atlassian.net/browse/OVIRT-3103?page=com.atlassian.jira.… ] Ehud Yonasi updated OVIRT-3103: ------------------------------- Attachment: image.png Hey, I personally would like to switch for 2FA. Me and my team needs to check the side effects of the ovirt ci infra user that runs the CI in github. On Mon, Jun 28, 2021 at 3:26 PM Sandro Bonazzola <sbonazzo(a)redhat.com> wrote: > HI, just an heads up that turning on the 2FA will have some side effects: > > Require two-factor authentication for everyone in the oVirt organization. > Members, billing managers, and outside collaborators who do not have > two-factor authentication enabled for their personal account will be > removed from the organization and will receive an email notifying them > about the change. > > So before turning it on, we need to ensure we are not going to disrupt the > org. > > Il giorno lun 28 giu 2021 alle ore 14:20 Martin Perina <mperina(a)redhat.com> > ha scritto: > >> >> >> On Mon, Jun 28, 2021 at 11:58 AM Sandro Bonazzola <sbonazzo(a)redhat.com> >> wrote: >> >>> +1 for enabling 2FA on my side >>> >> >> +1 >> >>> >>> Il giorno lun 28 giu 2021 alle ore 11:50 Janos Pasztor <janos(a)redhat.com> >>> ha scritto: >>> >>>> Hey folks, >>>> >>>> I just noticed that we don't have 2FA enforcement on the oVirt GitHub >>>> org. >>>> >>>> [image: image.png] >>>> Is this just an oversight or is it intentional? May I propose to turn >>>> 2FA enforcement on? >>>> >>>> Janos >>>> _______________________________________________ >>>> Devel mailing list -- devel(a)ovirt.org >>>> To unsubscribe send an email to devel-leave(a)ovirt.org >>>> Privacy Statement: https://www.ovirt.org/privacy-policy.html >>>> oVirt Code of Conduct: >>>> https://www.ovirt.org/community/about/community-guidelines/ >>>> List Archives: >>>> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/SASNDGLK3FBKB… >>>> >>> >>> >>> -- >>> >>> Sandro Bonazzola >>> >>> MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV >>> >>> Red Hat EMEA <https://www.redhat.com/> >>> >>> sbonazzo(a)redhat.com >>> <https://www.redhat.com/> >>> >>> *Red Hat respects your work life balance. Therefore there is no need to >>> answer this email out of your office hours.* >>> >>> >>> _______________________________________________ >>> Devel mailing list -- devel(a)ovirt.org >>> To unsubscribe send an email to devel-leave(a)ovirt.org >>> Privacy Statement: https://www.ovirt.org/privacy-policy.html >>> oVirt Code of Conduct: >>> https://www.ovirt.org/community/about/community-guidelines/ >>> List Archives: >>> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/CDSTENA6B4YNU… >>> >> >> >> -- >> Martin Perina >> Manager, Software Engineering >> Red Hat Czech s.r.o. >> > > > -- > > Sandro Bonazzola > > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > > Red Hat EMEA <https://www.redhat.com/> > > sbonazzo(a)redhat.com > <https://www.redhat.com/> > > *Red Hat respects your work life balance. Therefore there is no need to > answer this email out of your office hours.* > > > _______________________________________________ > Devel mailing list -- devel(a)ovirt.org > To unsubscribe send an email to devel-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/devel@ovirt.org/message/AI56Q2PSY3PN2… > > Re: [ovirt-devel] Re: 2FA requirement for oVirt GitHub org? > ----------------------------------------------------------- > > Key: OVIRT-3103 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3103 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Martin Perina > Assignee: infra > Attachments: image.png, image.png, image.png > > > On Mon, Jun 28, 2021 at 11:58 AM Sandro Bonazzola <sbonazzo(a)redhat.com> > wrote: > > +1 for enabling 2FA on my side > > > +1 > > > > Il giorno lun 28 giu 2021 alle ore 11:50 Janos Pasztor <janos(a)redhat.com> > > ha scritto: > > > >> Hey folks, > >> > >> I just noticed that we don't have 2FA enforcement on the oVirt GitHub > >> org. > >> > >> [image: image.png] > >> Is this just an oversight or is it intentional? May I propose to turn 2FA > >> enforcement on? > >> > >> Janos > >> _______________________________________________ > >> Devel mailing list -- devel(a)ovirt.org > >> To unsubscribe send an email to devel-leave(a)ovirt.org > >> Privacy Statement: https://www.ovirt.org/privacy-policy.html > >> oVirt Code of Conduct: > >> https://www.ovirt.org/community/about/community-guidelines/ > >> List Archives: > >> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/SASNDGLK3FBKB… > >> > > > > > > -- > > > > Sandro Bonazzola > > > > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > > > > Red Hat EMEA <https://www.redhat.com/> > > > > sbonazzo(a)redhat.com > > <https://www.redhat.com/> > > > > *Red Hat respects your work life balance. Therefore there is no need to > > answer this email out of your office hours.* > > > > > > _______________________________________________ > > Devel mailing list -- devel(a)ovirt.org > > To unsubscribe send an email to devel-leave(a)ovirt.org > > Privacy Statement: https://www.ovirt.org/privacy-policy.html > > oVirt Code of Conduct: > > https://www.ovirt.org/community/about/community-guidelines/ > > List Archives: > > https://lists.ovirt.org/archives/list/devel@ovirt.org/message/CDSTENA6B4YNU… > > > -- > Martin Perina > Manager, Software Engineering > Red Hat Czech s.r.o. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100166)

1 0

[JIRA] (OVIRT-3103) Re: [ovirt-devel] Re: 2FA requirement for oVirt GitHub org?
by Sandro Bonazzola (oVirt JIRA) 28 Jun '21

28 Jun '21

[ https://ovirt-jira.atlassian.net/browse/OVIRT-3103?page=com.atlassian.jira.… ] Sandro Bonazzola updated OVIRT-3103: ------------------------------------ Attachment: image.png HI, just an heads up that turning on the 2FA will have some side effects: Require two-factor authentication for everyone in the oVirt organization. Members, billing managers, and outside collaborators who do not have two-factor authentication enabled for their personal account will be removed from the organization and will receive an email notifying them about the change. So before turning it on, we need to ensure we are not going to disrupt the org. Il giorno lun 28 giu 2021 alle ore 14:20 Martin Perina <mperina(a)redhat.com> ha scritto: > > > On Mon, Jun 28, 2021 at 11:58 AM Sandro Bonazzola <sbonazzo(a)redhat.com> > wrote: > >> +1 for enabling 2FA on my side >> > > +1 > >> >> Il giorno lun 28 giu 2021 alle ore 11:50 Janos Pasztor <janos(a)redhat.com> >> ha scritto: >> >>> Hey folks, >>> >>> I just noticed that we don't have 2FA enforcement on the oVirt GitHub >>> org. >>> >>> [image: image.png] >>> Is this just an oversight or is it intentional? May I propose to turn >>> 2FA enforcement on? >>> >>> Janos >>> _______________________________________________ >>> Devel mailing list -- devel(a)ovirt.org >>> To unsubscribe send an email to devel-leave(a)ovirt.org >>> Privacy Statement: https://www.ovirt.org/privacy-policy.html >>> oVirt Code of Conduct: >>> https://www.ovirt.org/community/about/community-guidelines/ >>> List Archives: >>> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/SASNDGLK3FBKB… >>> >> >> >> -- >> >> Sandro Bonazzola >> >> MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV >> >> Red Hat EMEA <https://www.redhat.com/> >> >> sbonazzo(a)redhat.com >> <https://www.redhat.com/> >> >> *Red Hat respects your work life balance. Therefore there is no need to >> answer this email out of your office hours.* >> >> >> _______________________________________________ >> Devel mailing list -- devel(a)ovirt.org >> To unsubscribe send an email to devel-leave(a)ovirt.org >> Privacy Statement: https://www.ovirt.org/privacy-policy.html >> oVirt Code of Conduct: >> https://www.ovirt.org/community/about/community-guidelines/ >> List Archives: >> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/CDSTENA6B4YNU… >> > > > -- > Martin Perina > Manager, Software Engineering > Red Hat Czech s.r.o. > -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/> *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.* > Re: [ovirt-devel] Re: 2FA requirement for oVirt GitHub org? > ----------------------------------------------------------- > > Key: OVIRT-3103 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3103 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Martin Perina > Assignee: infra > Attachments: image.png, image.png > > > On Mon, Jun 28, 2021 at 11:58 AM Sandro Bonazzola <sbonazzo(a)redhat.com> > wrote: > > +1 for enabling 2FA on my side > > > +1 > > > > Il giorno lun 28 giu 2021 alle ore 11:50 Janos Pasztor <janos(a)redhat.com> > > ha scritto: > > > >> Hey folks, > >> > >> I just noticed that we don't have 2FA enforcement on the oVirt GitHub > >> org. > >> > >> [image: image.png] > >> Is this just an oversight or is it intentional? May I propose to turn 2FA > >> enforcement on? > >> > >> Janos > >> _______________________________________________ > >> Devel mailing list -- devel(a)ovirt.org > >> To unsubscribe send an email to devel-leave(a)ovirt.org > >> Privacy Statement: https://www.ovirt.org/privacy-policy.html > >> oVirt Code of Conduct: > >> https://www.ovirt.org/community/about/community-guidelines/ > >> List Archives: > >> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/SASNDGLK3FBKB… > >> > > > > > > -- > > > > Sandro Bonazzola > > > > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > > > > Red Hat EMEA <https://www.redhat.com/> > > > > sbonazzo(a)redhat.com > > <https://www.redhat.com/> > > > > *Red Hat respects your work life balance. Therefore there is no need to > > answer this email out of your office hours.* > > > > > > _______________________________________________ > > Devel mailing list -- devel(a)ovirt.org > > To unsubscribe send an email to devel-leave(a)ovirt.org > > Privacy Statement: https://www.ovirt.org/privacy-policy.html > > oVirt Code of Conduct: > > https://www.ovirt.org/community/about/community-guidelines/ > > List Archives: > > https://lists.ovirt.org/archives/list/devel@ovirt.org/message/CDSTENA6B4YNU… > > > -- > Martin Perina > Manager, Software Engineering > Red Hat Czech s.r.o. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100166)

1 0

[JIRA] (OVIRT-3103) Re: [ovirt-devel] Re: 2FA requirement for oVirt GitHub org?
by Martin Perina (oVirt JIRA) 28 Jun '21

28 Jun '21

Martin Perina created OVIRT-3103: ------------------------------------ Summary: Re: [ovirt-devel] Re: 2FA requirement for oVirt GitHub org? Key: OVIRT-3103 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3103 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Martin Perina Assignee: infra On Mon, Jun 28, 2021 at 11:58 AM Sandro Bonazzola <sbonazzo(a)redhat.com> wrote: > +1 for enabling 2FA on my side > +1 > > Il giorno lun 28 giu 2021 alle ore 11:50 Janos Pasztor <janos(a)redhat.com> > ha scritto: > >> Hey folks, >> >> I just noticed that we don't have 2FA enforcement on the oVirt GitHub >> org. >> >> [image: image.png] >> Is this just an oversight or is it intentional? May I propose to turn 2FA >> enforcement on? >> >> Janos >> _______________________________________________ >> Devel mailing list -- devel(a)ovirt.org >> To unsubscribe send an email to devel-leave(a)ovirt.org >> Privacy Statement: https://www.ovirt.org/privacy-policy.html >> oVirt Code of Conduct: >> https://www.ovirt.org/community/about/community-guidelines/ >> List Archives: >> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/SASNDGLK3FBKB… >> > > > -- > > Sandro Bonazzola > > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > > Red Hat EMEA <https://www.redhat.com/> > > sbonazzo(a)redhat.com > <https://www.redhat.com/> > > *Red Hat respects your work life balance. Therefore there is no need to > answer this email out of your office hours.* > > > _______________________________________________ > Devel mailing list -- devel(a)ovirt.org > To unsubscribe send an email to devel-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/devel@ovirt.org/message/CDSTENA6B4YNU… > -- Martin Perina Manager, Software Engineering Red Hat Czech s.r.o. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100166)

1 0

[oVirt Jenkins] ovirt-system-tests_basic-suite-4.3_el7-nightly - Build # 601 - Failure!
by jenkins＠jenkins.phx.ovirt.org 28 Jun '21

28 Jun '21

Project: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-4.3_el7-nightl… Build: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-4.3_el7-nightl… Build Number: 601 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #601 [parthdhanjal] Updating max click version ----------------- Failed Tests: ----------------- No tests ran.

1 2

[oVirt Jenkins] ovirt-system-tests_basic-suite-4.3_nightly - Build # 606 - Failure!
by jenkins＠jenkins.phx.ovirt.org 28 Jun '21

28 Jun '21

Project: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-4.3_nightly/ Build: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-4.3_nightly/60… Build Number: 606 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #606 [parthdhanjal] Updating max click version ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 004_basic_sanity.run_vms Error Message: Fault reason is "Operation Failed". Fault detail is "[Network error during communication with the Host.]". HTTP response code is 400. Stack Trace: Traceback (most recent call last): File "/usr/lib64/python2.7/unittest/case.py", line 369, in run testMethod() File "/usr/lib/python2.7/site-packages/nose/case.py", line 197, in runTest self.test(*self.arg) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 142, in wrapped_test test() File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 60, in wrapper return func(get_test_prefix(), *args, **kwargs) File "/home/jenkins/agent/workspace/ovirt-system-tests_basic-suite-4.3_nightly/ovirt-system-tests/basic-suite-4.3/test-scenarios/004_basic_sanity.py", line 694, in run_vms vm0_service.start(use_cloud_init=True, vm=vm_params) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 32520, in start return self._internal_action(action, 'start', None, headers, query, wait) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 299, in _internal_action return future.wait() if wait else future File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 55, in wait return self._code(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 296, in callback self._check_fault(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 134, in _check_fault self._raise_error(response, body.fault) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 118, in _raise_error raise error Error: Fault reason is "Operation Failed". Fault detail is "[Network error during communication with the Host.]". HTTP response code is 400.

1 2

oVirt infra daily report - unstable production jobs - 1600
by jenkins＠jenkins.phx.ovirt.org 28 Jun '21

28 Jun '21

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

1 0

[oVirt Jenkins] ovirt-system-tests_basic-suite-4.3_el7-nightly - Build # 598 - Failure!
by jenkins＠jenkins.phx.ovirt.org 27 Jun '21

27 Jun '21

Project: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-4.3_el7-nightl… Build: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-4.3_el7-nightl… Build Number: 598 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #598 [parthdhanjal] Updating max click version ----------------- Failed Tests: ----------------- No tests ran.

1 2

[oVirt Jenkins] ovirt-system-tests_basic-suite-master_nightly - Build # 1267 - Failure!
by jenkins＠jenkins.phx.ovirt.org 27 Jun '21

27 Jun '21

Project: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-master_nightly/ Build: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-master_nightly… Build Number: 1267 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #1267 [Galit Rosenthal] Update ost-repo, repo was changed ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: basic-suite-master.test-scenarios.test_100_basic_ui_sanity.test_clusters[firefox] Error Message: selenium.common.exceptions.ElementNotInteractableException: Message: Element <a id="MenuView_clustersAnchor" href="#clusters"> could not be scrolled into view Stack Trace: ovirt_driver = <ost_utils.selenium.navigation.driver.Driver object at 0x7f4d9efef0b8> def test_clusters(ovirt_driver): webadmin_menu = WebAdminLeftMenu(ovirt_driver) > cluster_list_view = webadmin_menu.open_cluster_list_view() basic-suite-master/test-scenarios/test_100_basic_ui_sanity.py:301: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ ost_utils/ost_utils/selenium/page_objects/WebAdminLeftMenu.py:69: in open_cluster_list_view self._open_compute_menu('Clusters', 'MenuView_clustersAnchor') ost_utils/ost_utils/selenium/page_objects/WebAdminLeftMenu.py:95: in _open_compute_menu self._open_menu('compute', menu_name, menu_id) ost_utils/ost_utils/selenium/page_objects/WebAdminLeftMenu.py:105: in _open_menu self.ovirt_driver.id_wait_and_click(menu_name + ' menu', menu_id) ost_utils/ost_utils/selenium/navigation/driver.py:231: in id_wait_and_click self.xpath_wait_and_click(message, '//*[@id="' + element_id + '"]', wait_long) ost_utils/ost_utils/selenium/navigation/driver.py:303: in xpath_wait_and_click self.xpath_click(xpath) ost_utils/ost_utils/selenium/navigation/driver.py:290: in xpath_click xpath ost_utils/ost_utils/selenium/navigation/driver.py:167: in retry_if_stale return_value = method_to_retry(*args) ost_utils/ost_utils/selenium/navigation/driver.py:294: in _xpath_click self.driver.find_element_by_xpath(xpath).click() .tox/deps/lib/python3.6/site-packages/selenium/webdriver/remote/webelement.py:80: in click self._execute(Command.CLICK_ELEMENT) .tox/deps/lib/python3.6/site-packages/selenium/webdriver/remote/webelement.py:633: in _execute return self._parent.execute(command, params) .tox/deps/lib/python3.6/site-packages/selenium/webdriver/remote/webdriver.py:321: in execute self.error_handler.check_response(response) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = <selenium.webdriver.remote.errorhandler.ErrorHandler object at 0x7f4d9efef9b0> response = {'status': 400, 'value': '{"value":{"error":"element not interactable","message":"Element <a id=\\"MenuView_clustersAn...eCommandsChild.jsm:181:24\\nreceiveMessage@chrome://marionette/content/actors/MarionetteCommandsChild.jsm:85:31\\n"}}'} def check_response(self, response): """ Checks that a JSON response from the WebDriver does not have an error. :Args: - response - The JSON response from the WebDriver server as a dictionary object. :Raises: If the response contains an error message. """ status = response.get('status', None) if status is None or status == ErrorCode.SUCCESS: return value = None message = response.get("message", "") screen = response.get("screen", "") stacktrace = None if isinstance(status, int): value_json = response.get('value', None) if value_json and isinstance(value_json, basestring): import json try: value = json.loads(value_json) if len(value.keys()) == 1: value = value['value'] status = value.get('error', None) if status is None: status = value["status"] message = value["value"] if not isinstance(message, basestring): value = message message = message.get('message') else: message = value.get('message', None) except ValueError: pass exception_class = ErrorInResponseException if status in ErrorCode.NO_SUCH_ELEMENT: exception_class = NoSuchElementException elif status in ErrorCode.NO_SUCH_FRAME: exception_class = NoSuchFrameException elif status in ErrorCode.NO_SUCH_WINDOW: exception_class = NoSuchWindowException elif status in ErrorCode.STALE_ELEMENT_REFERENCE: exception_class = StaleElementReferenceException elif status in ErrorCode.ELEMENT_NOT_VISIBLE: exception_class = ElementNotVisibleException elif status in ErrorCode.INVALID_ELEMENT_STATE: exception_class = InvalidElementStateException elif status in ErrorCode.INVALID_SELECTOR \ or status in ErrorCode.INVALID_XPATH_SELECTOR \ or status in ErrorCode.INVALID_XPATH_SELECTOR_RETURN_TYPER: exception_class = InvalidSelectorException elif status in ErrorCode.ELEMENT_IS_NOT_SELECTABLE: exception_class = ElementNotSelectableException elif status in ErrorCode.ELEMENT_NOT_INTERACTABLE: exception_class = ElementNotInteractableException elif status in ErrorCode.INVALID_COOKIE_DOMAIN: exception_class = InvalidCookieDomainException elif status in ErrorCode.UNABLE_TO_SET_COOKIE: exception_class = UnableToSetCookieException elif status in ErrorCode.TIMEOUT: exception_class = TimeoutException elif status in ErrorCode.SCRIPT_TIMEOUT: exception_class = TimeoutException elif status in ErrorCode.UNKNOWN_ERROR: exception_class = WebDriverException elif status in ErrorCode.UNEXPECTED_ALERT_OPEN: exception_class = UnexpectedAlertPresentException elif status in ErrorCode.NO_ALERT_OPEN: exception_class = NoAlertPresentException elif status in ErrorCode.IME_NOT_AVAILABLE: exception_class = ImeNotAvailableException elif status in ErrorCode.IME_ENGINE_ACTIVATION_FAILED: exception_class = ImeActivationFailedException elif status in ErrorCode.MOVE_TARGET_OUT_OF_BOUNDS: exception_class = MoveTargetOutOfBoundsException elif status in ErrorCode.JAVASCRIPT_ERROR: exception_class = JavascriptException elif status in ErrorCode.SESSION_NOT_CREATED: exception_class = SessionNotCreatedException elif status in ErrorCode.INVALID_ARGUMENT: exception_class = InvalidArgumentException elif status in ErrorCode.NO_SUCH_COOKIE: exception_class = NoSuchCookieException elif status in ErrorCode.UNABLE_TO_CAPTURE_SCREEN: exception_class = ScreenshotException elif status in ErrorCode.ELEMENT_CLICK_INTERCEPTED: exception_class = ElementClickInterceptedException elif status in ErrorCode.INSECURE_CERTIFICATE: exception_class = InsecureCertificateException elif status in ErrorCode.INVALID_COORDINATES: exception_class = InvalidCoordinatesException elif status in ErrorCode.INVALID_SESSION_ID: exception_class = InvalidSessionIdException elif status in ErrorCode.UNKNOWN_METHOD: exception_class = UnknownMethodException else: exception_class = WebDriverException if value == '' or value is None: value = response['value'] if isinstance(value, basestring): if exception_class == ErrorInResponseException: raise exception_class(response, value) raise exception_class(value) if message == "" and 'message' in value: message = value['message'] screen = None if 'screen' in value: screen = value['screen'] stacktrace = None if 'stackTrace' in value and value['stackTrace']: stacktrace = [] try: for frame in value['stackTrace']: line = self._value_or_default(frame, 'lineNumber', '') file = self._value_or_default(frame, 'fileName', '<anonymous>') if line: file = "%s:%s" % (file, line) meth = self._value_or_default(frame, 'methodName', '<anonymous>') if 'className' in frame: meth = "%s.%s" % (frame['className'], meth) msg = " at %s (%s)" msg = msg % (meth, file) stacktrace.append(msg) except TypeError: pass if exception_class == ErrorInResponseException: raise exception_class(response, message) elif exception_class == UnexpectedAlertPresentException: alert_text = None if 'data' in value: alert_text = value['data'].get('text') elif 'alert' in value: alert_text = value['alert'].get('text') raise exception_class(message, screen, stacktrace, alert_text) > raise exception_class(message, screen, stacktrace) E selenium.common.exceptions.ElementNotInteractableException: Message: Element <a id="MenuView_clustersAnchor" href="#clusters"> could not be scrolled into view .tox/deps/lib/python3.6/site-packages/selenium/webdriver/remote/errorhandler.py:242: ElementNotInteractableException

1 1

oVirt infra daily report - unstable production jobs - 1599
by jenkins＠jenkins.phx.ovirt.org 27 Jun '21

27 Jun '21

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

1 0

[oVirt Jenkins] ovirt-system-tests_basic-suite-4.3_el7-nightly - Build # 595 - Failure!
by jenkins＠jenkins.phx.ovirt.org 26 Jun '21

26 Jun '21

Project: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-4.3_el7-nightl… Build: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-4.3_el7-nightl… Build Number: 595 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #595 [parthdhanjal] Updating max click version ----------------- Failed Tests: ----------------- No tests ran.

1 2

oVirt infra daily report - unstable production jobs - 1598
by jenkins＠jenkins.phx.ovirt.org 26 Jun '21

26 Jun '21

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

1 0

[JIRA] (OVIRT-3102) Broken commit-msg hook in gerrit
by Nir Soffer (oVirt JIRA) 25 Jun '21

25 Jun '21

[ https://ovirt-jira.atlassian.net/browse/OVIRT-3102?page=com.atlassian.jira.… ] Nir Soffer updated OVIRT-3102: ------------------------------ Attachment: commit-msg On Fri, Jun 25, 2021 at 10:38 PM Nir Soffer <nsoffer(a)redhat.com> wrote: > > In ovirt-imageio developer docs, we ask to install the commit-msg hook > from gerrit: > > wget -P .git/hooks https://gerrit.ovirt.org/tools/hooks/commit-msg > > This downloads now a broken script that does not add a ChangeId header. I found the issue, our instructions were missing: chmod +x .git/hooks/commit-msg After adding it, the new script works fine. > In the past I think it returned something like the attached file, > without the code for > adding signed-off-by. > > I suggest to replace the current file at: > https://gerrit.ovirt.org/tools/hooks/commit-msg > > Or if we want to keep the default file for some reason, add: > https://gerrit.ovirt.org/tools/ovirt/hooks/commit-msg > > This file contains the code for adding the signed-off-by header, so so > developers > do not need to add this manually: > > # Add Signed-off-by trailer. > sob=$(git var GIT_AUTHOR_IDENT | sed -n 's/^$.*>$.*$/Signed-off-by: \1/p') > git interpret-trailers --in-place --trailer "$sob" "$1" But developers still need to add the code above. Attaching a version with this code to replace the current file. > Broken commit-msg hook in gerrit > -------------------------------- > > Key: OVIRT-3102 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3102 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > Attachments: commit-msg, commit-msg > > > In ovirt-imageio developer docs, we ask to install the commit-msg hook > from gerrit: > wget -P .git/hooks https://gerrit.ovirt.org/tools/hooks/commit-msg > This downloads now a broken script that does not add a ChangeId header. > In the past I think it returned something like the attached file, > without the code for > adding signed-off-by. > I suggest to replace the current file at: > https://gerrit.ovirt.org/tools/hooks/commit-msg > Or if we want to keep the default file for some reason, add: > https://gerrit.ovirt.org/tools/ovirt/hooks/commit-msg > This file contains the code for adding the signed-off-by header, so so > developers > do not need to add this manually: > # Add Signed-off-by trailer. > sob=$(git var GIT_AUTHOR_IDENT | sed -n 's/^$.*>$.*$/Signed-off-by: \1/p') > git interpret-trailers --in-place --trailer "$sob" "$1" > Later we need to replace this ugly shell script with proper code. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100166)

1 0

[JIRA] (OVIRT-3102) Broken commit-msg hook in gerrit
by Nir Soffer (oVirt JIRA) 25 Jun '21

25 Jun '21

Nir Soffer created OVIRT-3102: --------------------------------- Summary: Broken commit-msg hook in gerrit Key: OVIRT-3102 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3102 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Nir Soffer Assignee: infra In ovirt-imageio developer docs, we ask to install the commit-msg hook from gerrit: wget -P .git/hooks https://gerrit.ovirt.org/tools/hooks/commit-msg This downloads now a broken script that does not add a ChangeId header. In the past I think it returned something like the attached file, without the code for adding signed-off-by. I suggest to replace the current file at: https://gerrit.ovirt.org/tools/hooks/commit-msg Or if we want to keep the default file for some reason, add: https://gerrit.ovirt.org/tools/ovirt/hooks/commit-msg This file contains the code for adding the signed-off-by header, so so developers do not need to add this manually: # Add Signed-off-by trailer. sob=$(git var GIT_AUTHOR_IDENT | sed -n 's/^$.*>$.*$/Signed-off-by: \1/p') git interpret-trailers --in-place --trailer "$sob" "$1" Later we need to replace this ugly shell script with proper code. Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100166)

1 0

[oVirt Jenkins] ovirt-system-tests_basic-suite-master_nightly - Build # 1263 - Failure!
by jenkins＠jenkins.phx.ovirt.org 25 Jun '21

25 Jun '21

Project: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-master_nightly/ Build: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-master_nightly… Build Number: 1263 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #1263 [Yedidyah Bar David] automation: build-artifacts: Use el8 ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: basic-suite-master.test-scenarios.test_100_basic_ui_sanity.test_secure_connection_should_fail_without_root_ca[firefox] Error Message: failed on setup with "ost_utils.shell.ShellError: Command failed with rc=125. Stdout: Stderr: Trying to pull docker.io/selenium/hub:3.141.59-20210422... unable to retrieve auth token: invalid username/password: unauthorized: incorrect username or password Error: 1 error occurred: * Error initializing source docker://selenium/hub:3.141.59-20210422: unable to retrieve auth token: invalid username/password: unauthorized: incorrect username or password" Stack Trace: engine_fqdn = 'engine', engine_ip = '192.168.200.2' @pytest.fixture(scope="session") def hub_url(engine_fqdn, engine_ip): env_url = _env_hub_url() if env_url is not None: yield env_url else: backend = _grid_backend() if backend == "podman" or backend == "podman-remote": with podman.grid(engine_fqdn, engine_ip, > podman_cmd=backend) as hub_url: ost_utils/ost_utils/pytest/fixtures/selenium/__init__.py:74: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ /usr/lib64/python3.6/contextlib.py:81: in __enter__ return next(self.gen) ost_utils/ost_utils/selenium/grid/podman.py:145: in grid hub_port, podman_cmd) as url: /usr/lib64/python3.6/contextlib.py:81: in __enter__ return next(self.gen) ost_utils/ost_utils/selenium/grid/podman.py:122: in _grid with _hub(hub_image, hub_port, pod_name, podman_cmd) as hub_name: /usr/lib64/python3.6/contextlib.py:81: in __enter__ return next(self.gen) ost_utils/ost_utils/selenium/grid/podman.py:73: in _hub image _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ args = ['podman-remote', 'run', '-d', '-e', 'SE_OPTS=-port 4444', '-v', ...] bytes_output = False, kwargs = {} process = <subprocess.Popen object at 0x7f8994041ef0>, out = '' err = 'Trying to pull docker.io/selenium/hub:3.141.59-20210422...\n unable to retrieve auth token: invalid username/passwor...210422: unable to retrieve auth token: invalid username/password: unauthorized: incorrect username or password\n\n\n\n' def shell(args, bytes_output=False, **kwargs): process = subprocess.Popen(args, stdout=subprocess.PIPE, stderr=subprocess.PIPE, **kwargs) out, err = process.communicate() if not bytes_output: out = out.decode("utf-8") err = err.decode("utf-8") if process.returncode: > raise ShellError(process.returncode, out, err) E ost_utils.shell.ShellError: Command failed with rc=125. Stdout: E E Stderr: E Trying to pull docker.io/selenium/hub:3.141.59-20210422... E unable to retrieve auth token: invalid username/password: unauthorized: incorrect username or password E Error: 1 error occurred: E * Error initializing source docker://selenium/hub:3.141.59-20210422: unable to retrieve auth token: invalid username/password: unauthorized: incorrect username or password ost_utils/ost_utils/shell.py:49: ShellError

1 1

[oVirt Jenkins] ovirt-system-tests_basic-suite-4.3_nightly - Build # 599 - Failure!
by jenkins＠jenkins.phx.ovirt.org 25 Jun '21

25 Jun '21

Project: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-4.3_nightly/ Build: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-4.3_nightly/59… Build Number: 599 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #599 [parthdhanjal] Updating max click version [Ehud Yonasi] standard_stage: keep running on el7 worker. ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 004_basic_sanity.run_vms Error Message: Fault reason is "Operation Failed". Fault detail is "[Network error during communication with the Host.]". HTTP response code is 400. Stack Trace: Traceback (most recent call last): File "/usr/lib64/python2.7/unittest/case.py", line 369, in run testMethod() File "/usr/lib/python2.7/site-packages/nose/case.py", line 197, in runTest self.test(*self.arg) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 142, in wrapped_test test() File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 60, in wrapper return func(get_test_prefix(), *args, **kwargs) File "/home/jenkins/agent/workspace/ovirt-system-tests_basic-suite-4.3_nightly/ovirt-system-tests/basic-suite-4.3/test-scenarios/004_basic_sanity.py", line 694, in run_vms vm0_service.start(use_cloud_init=True, vm=vm_params) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 32520, in start return self._internal_action(action, 'start', None, headers, query, wait) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 299, in _internal_action return future.wait() if wait else future File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 55, in wait return self._code(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 296, in callback self._check_fault(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 134, in _check_fault self._raise_error(response, body.fault) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 118, in _raise_error raise error Error: Fault reason is "Operation Failed". Fault detail is "[Network error during communication with the Host.]". HTTP response code is 400.

1 1

[oVirt Jenkins] ovirt-system-tests_basic-suite-4.3_el7-nightly - Build # 589 - Failure!
by jenkins＠jenkins.phx.ovirt.org 25 Jun '21

25 Jun '21

Project: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-4.3_el7-nightl… Build: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-4.3_el7-nightl… Build Number: 589 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #589 [parthdhanjal] Updating max click version ----------------- Failed Tests: ----------------- No tests ran.

1 5

[oVirt Jenkins] ovirt-release_4.3_build-artifacts-el7-x86_64 - Build # 1019 - Failure!
by jenkins＠jenkins.phx.ovirt.org 25 Jun '21

25 Jun '21

Project: https://jenkins.ovirt.org/job/ovirt-release_4.3_build-artifacts-el7-x86_64/ Build: https://jenkins.ovirt.org/job/ovirt-release_4.3_build-artifacts-el7-x86_64/… Build Number: 1019 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #1019 [Sandro Bonazzola] Revert "automation: install centos-release if missing" ----------------- Failed Tests: ----------------- No tests ran.

1 1

[oVirt Jenkins] ovirt-system-tests_basic-suite-master_nightly - Build # 1261 - Failure!
by jenkins＠jenkins.phx.ovirt.org 25 Jun '21

25 Jun '21

Project: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-master_nightly/ Build: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-master_nightly… Build Number: 1261 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #1261 [Yedidyah Bar David] ansible: fix engine fqdn detection ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: basic-suite-master.test-scenarios.test_100_basic_ui_sanity.test_clusters[firefox] Error Message: selenium.common.exceptions.TimeoutException: Message: Clusters menu is not displayed Stack Trace: ovirt_driver = <ost_utils.selenium.navigation.driver.Driver object at 0x7f04b05565c0> def test_clusters(ovirt_driver): webadmin_menu = WebAdminLeftMenu(ovirt_driver) > cluster_list_view = webadmin_menu.open_cluster_list_view() basic-suite-master/test-scenarios/test_100_basic_ui_sanity.py:301: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ ost_utils/ost_utils/selenium/page_objects/WebAdminLeftMenu.py:69: in open_cluster_list_view self._open_compute_menu('Clusters', 'MenuView_clustersAnchor') ost_utils/ost_utils/selenium/page_objects/WebAdminLeftMenu.py:95: in _open_compute_menu self._open_menu('compute', menu_name, menu_id) ost_utils/ost_utils/selenium/page_objects/WebAdminLeftMenu.py:105: in _open_menu self.ovirt_driver.id_wait_and_click(menu_name + ' menu', menu_id) ost_utils/ost_utils/selenium/navigation/driver.py:231: in id_wait_and_click self.xpath_wait_and_click(message, '//*[@id="' + element_id + '"]', wait_long) ost_utils/ost_utils/selenium/navigation/driver.py:301: in xpath_wait_and_click wait_until(message + ' is not displayed', self.is_xpath_displayed, xpath) ost_utils/ost_utils/selenium/navigation/driver.py:306: in wait_until self._wait_until(message, assertions.SHORT_TIMEOUT, condition_method, *args) ost_utils/ost_utils/selenium/navigation/driver.py:312: in _wait_until WebDriverWait(self.driver, timeout).until(ConditionClass(condition_method, *args), message) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = <selenium.webdriver.support.wait.WebDriverWait (session="13b19ca4-f917-435c-858a-2bcf94b812e9")> method = <ost_utils.selenium.navigation.driver.ConditionClass object at 0x7f04b0684550> message = 'Clusters menu is not displayed' def until(self, method, message=''): """Calls the method provided with the driver as an argument until the \ return value is not False.""" screen = None stacktrace = None end_time = time.time() + self._timeout while True: try: value = method(self._driver) if value: return value except self._ignored_exceptions as exc: screen = getattr(exc, 'screen', None) stacktrace = getattr(exc, 'stacktrace', None) time.sleep(self._poll) if time.time() > end_time: break > raise TimeoutException(message, screen, stacktrace) E selenium.common.exceptions.TimeoutException: Message: Clusters menu is not displayed .tox/deps/lib/python3.6/site-packages/selenium/webdriver/support/wait.py:80: TimeoutException

1 1

[oVirt Jenkins] ovirt-release_4.2_build-artifacts-el7-x86_64 - Build # 1450 - Failure!
by jenkins＠jenkins.phx.ovirt.org 25 Jun '21

25 Jun '21

Project: https://jenkins.ovirt.org/job/ovirt-release_4.2_build-artifacts-el7-x86_64/ Build: https://jenkins.ovirt.org/job/ovirt-release_4.2_build-artifacts-el7-x86_64/… Build Number: 1450 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #1450 [Sandro Bonazzola] automation: add v2 configuration ----------------- Failed Tests: ----------------- No tests ran.

1 1

oVirt infra daily report - unstable production jobs - 1597
by jenkins＠jenkins.phx.ovirt.org 25 Jun '21

25 Jun '21

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

1 0

[CQ]: 115412, 1 (ovirt-node-ng-image) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 24 Jun '21

24 Jun '21

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

1 0

[CQ]: 115400,2 (jenkins) failed "dummy-master" system tests
by oVirt Jenkins 24 Jun '21

24 Jun '21

Change 115400,2 (jenkins) is probably the reason behind recent system test failures in the "dummy-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://gerrit.ovirt.org/c/jenkins/+/#/c/115400/2 For failed test results see: https://jenkins.ovirt.org/job/dummy-master_change-queue-tester/627/

1 0

[oVirt Jenkins] deploy-to-gated-dummy-master - Build #556 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 24 Jun '21

24 Jun '21

Build: https://jenkins.ovirt.org/job/deploy-to-gated-dummy-master/556/ Build Name: #556 Build Status: FAILURE Gerrit change: null - title: null - project: null - branch: null - author: null <null>

1 0

[JIRA] (OVIRT-3101) Add "ci system-test" command
by Shani Leviim (oVirt JIRA) 24 Jun '21

24 Jun '21

[ https://ovirt-jira.atlassian.net/browse/OVIRT-3101?page=com.atlassian.jira.… ] Shani Leviim commented on OVIRT-3101: ------------------------------------- +1 for adding the suite name. BTW, you can run manually OST with your own parameters (engine artifacts and OST patch set). *Regards,* *Shani Leviim* On Thu, Jun 24, 2021 at 3:08 PM Nir Soffer <nsoffer(a)redhat.com> wrote: > On Thu, Jun 24, 2021 at 2:11 PM Yedidyah Bar David <didi(a)redhat.com> > wrote: > > > > On Thu, Jun 24, 2021 at 1:51 PM Marcin Sobczyk <msobczyk(a)redhat.com> > wrote: > > > > > > > > > > > > On 6/23/21 5:44 PM, Nir Soffer wrote: > > > > Similar to "ci build", "ci test", "ci merge" add a new command that > > > > triggers OST run. > > > > > > > > Running OST is tied now in vdsm (and engine?) to Code-Review: +2. > > > > This causes trouble and does not allow non-maintainers to use the > convenient OST > > > > infrastructure. > > > > > > > > Expected flow: > > > > > > > > 1. User add a comment with "ci system-test" > > > "ci system-test" is sooo long, I vote for "ci ost". > > > > +1. > > > > Perhaps we can add an optional suite name? E.g. 'ci ost > ansible-suite-master' > > +1 > _______________________________________________ > Devel mailing list -- devel(a)ovirt.org > To unsubscribe send an email to devel-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/devel@ovirt.org/message/SKS3XFCIC6SUP… > > Add "ci system-test" command > ---------------------------- > > Key: OVIRT-3101 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3101 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > Similar to "ci build", "ci test", "ci merge" add a new command that > triggers OST run. > Running OST is tied now in vdsm (and engine?) to Code-Review: +2. > This causes trouble and does not allow non-maintainers to use the convenient OST > infrastructure. > Expected flow: > 1. User add a comment with "ci system-test" > 2. OST flow building and running OST triggered -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100166)

1 0

[JIRA] (OVIRT-3101) Add "ci system-test" command
by Nir Soffer (oVirt JIRA) 24 Jun '21

24 Jun '21

[ https://ovirt-jira.atlassian.net/browse/OVIRT-3101?page=com.atlassian.jira.… ] Nir Soffer commented on OVIRT-3101: ----------------------------------- On Thu, Jun 24, 2021 at 1:49 PM Marcin Sobczyk <msobczyk(a)redhat.com> wrote: > > > > On 6/23/21 5:44 PM, Nir Soffer wrote: > > Similar to "ci build", "ci test", "ci merge" add a new command that > > triggers OST run. > > > > Running OST is tied now in vdsm (and engine?) to Code-Review: +2. > > This causes trouble and does not allow non-maintainers to use the convenient OST > > infrastructure. > > > > Expected flow: > > > > 1. User add a comment with "ci system-test" > "ci system-test" is sooo long, I vote for "ci ost". Works for me, but "system-test" is more consistent with other ci commands: https://ovirt-infra-docs.readthedocs.io/en/latest/CI/Using_STDCI_with_Gerri… > Add "ci system-test" command > ---------------------------- > > Key: OVIRT-3101 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3101 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > Similar to "ci build", "ci test", "ci merge" add a new command that > triggers OST run. > Running OST is tied now in vdsm (and engine?) to Code-Review: +2. > This causes trouble and does not allow non-maintainers to use the convenient OST > infrastructure. > Expected flow: > 1. User add a comment with "ci system-test" > 2. OST flow building and running OST triggered -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100166)

1 0

[JIRA] (OVIRT-3101) Add "ci system-test" command
by Nir Soffer (oVirt JIRA) 24 Jun '21

24 Jun '21

[ https://ovirt-jira.atlassian.net/browse/OVIRT-3101?page=com.atlassian.jira.… ] Nir Soffer commented on OVIRT-3101: ----------------------------------- On Thu, Jun 24, 2021 at 2:11 PM Yedidyah Bar David <didi(a)redhat.com> wrote: > > On Thu, Jun 24, 2021 at 1:51 PM Marcin Sobczyk <msobczyk(a)redhat.com> wrote: > > > > > > > > On 6/23/21 5:44 PM, Nir Soffer wrote: > > > Similar to "ci build", "ci test", "ci merge" add a new command that > > > triggers OST run. > > > > > > Running OST is tied now in vdsm (and engine?) to Code-Review: +2. > > > This causes trouble and does not allow non-maintainers to use the convenient OST > > > infrastructure. > > > > > > Expected flow: > > > > > > 1. User add a comment with "ci system-test" > > "ci system-test" is sooo long, I vote for "ci ost". > > +1. > > Perhaps we can add an optional suite name? E.g. 'ci ost ansible-suite-master' +1 > Add "ci system-test" command > ---------------------------- > > Key: OVIRT-3101 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3101 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > Similar to "ci build", "ci test", "ci merge" add a new command that > triggers OST run. > Running OST is tied now in vdsm (and engine?) to Code-Review: +2. > This causes trouble and does not allow non-maintainers to use the convenient OST > infrastructure. > Expected flow: > 1. User add a comment with "ci system-test" > 2. OST flow building and running OST triggered -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100166)

1 0

[JIRA] (OVIRT-3101) Add "ci system-test" command
by Yedidyah Bar David (oVirt JIRA) 24 Jun '21

24 Jun '21

[ https://ovirt-jira.atlassian.net/browse/OVIRT-3101?page=com.atlassian.jira.… ] Yedidyah Bar David commented on OVIRT-3101: ------------------------------------------- On Thu, Jun 24, 2021 at 1:51 PM Marcin Sobczyk <msobczyk(a)redhat.com> wrote: > > > > On 6/23/21 5:44 PM, Nir Soffer wrote: > > Similar to "ci build", "ci test", "ci merge" add a new command that > > triggers OST run. > > > > Running OST is tied now in vdsm (and engine?) to Code-Review: +2. > > This causes trouble and does not allow non-maintainers to use the convenient OST > > infrastructure. > > > > Expected flow: > > > > 1. User add a comment with "ci system-test" > "ci system-test" is sooo long, I vote for "ci ost". +1. Perhaps we can add an optional suite name? E.g. 'ci ost ansible-suite-master' Best regards, -- Didi > Add "ci system-test" command > ---------------------------- > > Key: OVIRT-3101 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3101 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > Similar to "ci build", "ci test", "ci merge" add a new command that > triggers OST run. > Running OST is tied now in vdsm (and engine?) to Code-Review: +2. > This causes trouble and does not allow non-maintainers to use the convenient OST > infrastructure. > Expected flow: > 1. User add a comment with "ci system-test" > 2. OST flow building and running OST triggered -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100166)

1 0

[JIRA] (OVIRT-3101) Add "ci system-test" command
by Marcin Sobczyk (oVirt JIRA) 24 Jun '21

24 Jun '21

[ https://ovirt-jira.atlassian.net/browse/OVIRT-3101?page=com.atlassian.jira.… ] Marcin Sobczyk commented on OVIRT-3101: --------------------------------------- On 6/23/21 5:44 PM, Nir Soffer wrote: > Similar to "ci build", "ci test", "ci merge" add a new command that > triggers OST run. > > Running OST is tied now in vdsm (and engine?) to Code-Review: +2. > This causes trouble and does not allow non-maintainers to use the convenient OST > infrastructure. > > Expected flow: > > 1. User add a comment with "ci system-test" "ci system-test" is sooo long, I vote for "ci ost". Regards, Marcin > 2. OST flow building and running OST triggered > _______________________________________________ > Devel mailing list -- devel(a)ovirt.org > To unsubscribe send an email to devel-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/message/2FCJZLFJJ2SB3… > Add "ci system-test" command > ---------------------------- > > Key: OVIRT-3101 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3101 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > Similar to "ci build", "ci test", "ci merge" add a new command that > triggers OST run. > Running OST is tied now in vdsm (and engine?) to Code-Review: +2. > This causes trouble and does not allow non-maintainers to use the convenient OST > infrastructure. > Expected flow: > 1. User add a comment with "ci system-test" > 2. OST flow building and running OST triggered -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100166)

1 0

[CQ]: 115356, 3 (ovirt-system-tests) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 24 Jun '21

24 Jun '21

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

1 0

[oVirt Jenkins] cleanup-gated-dummy-master - Build #551 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 24 Jun '21

24 Jun '21

Build: https://jenkins.ovirt.org/job/cleanup-gated-dummy-master/551/ Build Name: #551 Build Status: FAILURE Gerrit change: null - title: null - project: null - branch: null - author: null <null>

1 0

oVirt infra daily report - unstable production jobs - 1596
by jenkins＠jenkins.phx.ovirt.org 24 Jun '21

24 Jun '21

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

1 0

[JIRA] (OVIRT-3101) Add "ci system-test" command
by Nir Soffer (oVirt JIRA) 23 Jun '21

23 Jun '21

Nir Soffer created OVIRT-3101: --------------------------------- Summary: Add "ci system-test" command Key: OVIRT-3101 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3101 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Nir Soffer Assignee: infra Similar to "ci build", "ci test", "ci merge" add a new command that triggers OST run. Running OST is tied now in vdsm (and engine?) to Code-Review: +2. This causes trouble and does not allow non-maintainers to use the convenient OST infrastructure. Expected flow: 1. User add a comment with "ci system-test" 2. OST flow building and running OST triggered -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100166)

1 0

[JIRA] (OVIRT-3100) Add OST flag to all oVirt projects
by Nir Soffer (oVirt JIRA) 23 Jun '21

23 Jun '21

Nir Soffer created OVIRT-3100: --------------------------------- Summary: Add OST flag to all oVirt projects Key: OVIRT-3100 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3100 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Nir Soffer Assignee: infra Similar to Continuous-Integration flag, OST needs its own flag. OST will set this flag when OST build started from gerrit was started. We want to make this field mandatory for merging patches, like Continuous-Integration. Like Continuous-Integration maintainers should be able to override the value after OST completed, or set the value before OST started. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100166)

1 0

[CQ]: 115368, 1 (ovirt-system-tests) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 23 Jun '21

23 Jun '21

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

1 0

[CQ]: 115337, 3 (ovirt-system-tests) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 23 Jun '21

23 Jun '21

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

1 0

[oVirt Jenkins] ovirt-system-tests_basic-suite-4.3_nightly - Build # 593 - Failure!
by jenkins＠jenkins.phx.ovirt.org 23 Jun '21

23 Jun '21

Project: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-4.3_nightly/ Build: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-4.3_nightly/59… Build Number: 593 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #593 [parthdhanjal] Updating max click version ----------------- Failed Tests: ----------------- No tests ran.

1 2

[CQ]: 115333, 3 (ovirt-system-tests) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 23 Jun '21

23 Jun '21

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

1 0

[oVirt Jenkins] ovirt-system-tests_basic-suite-4.3_el7-nightly - Build # 587 - Failure!
by jenkins＠jenkins.phx.ovirt.org 23 Jun '21

23 Jun '21

Project: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-4.3_el7-nightl… Build: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-4.3_el7-nightl… Build Number: 587 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #587 [parthdhanjal] Updating max click version ----------------- Failed Tests: ----------------- No tests ran.

1 1

planned Jenkins restart
by Evgheni Dereveanchin 23 Jun '21

23 Jun '21

Hi everyone, I'll be performing a planned Jenkins restart within the next hour. No new CI jobs will be scheduled during this maintenance period. I will inform you once it is back online. -- Regards, Evgheni Dereveanchin

1 1

oVirt infra daily report - unstable production jobs - 1595
by jenkins＠jenkins.phx.ovirt.org 23 Jun '21

23 Jun '21

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

1 0

[JIRA] (OVIRT-3099) Re: oVirt CI mirror for centos stream advancedvirt-common repo
by Nir Soffer (oVirt JIRA) 22 Jun '21

22 Jun '21

Nir Soffer created OVIRT-3099: --------------------------------- Summary: Re: oVirt CI mirror for centos stream advancedvirt-common repo Key: OVIRT-3099 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3099 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Nir Soffer Assignee: infra On Fri, Jun 11, 2021 at 12:41 PM Sandro Bonazzola <sbonazzo(a)redhat.com> wrote: > > > Il giorno ven 4 giu 2021 alle ore 19:44 Nir Soffer <nsoffer(a)redhat.com> > ha scritto: > >> I updated vdsm libvirt requirement to 7.0.0-14. The package exists in >> centos >> stream and rhel so the change is correct, but the install check fails in >> the CI. >> >> I found that adding the repo to check-patch.repos works: >> https://gerrit.ovirt.org/c/vdsm/+/115039/4/automation/check-patch.repos >> >> But depending on mirror.centos.org does not feel like the right way. I >> think >> keeping a local mirror is the right way. >> > > Please note that despite we are pointing to centos mirrors, CI is running > under proxy, so we are caching on our datacenter the rpms we consume anyway. > That said, we can mirror advanced virtualization repos as well and the > local mirror will be automatically picked up. > > I see we are already mirroring the test repo for CentOS Linux: > ./data/mirrors-reposync.conf: > 70 : [ovirt-master-centos-advanced-virtualization-el8] > 72 : baseurl= > https://buildlogs.centos.org/centos/8/virt/x86_64/advanced-virtualization/ > > For CentOS Stream we'll need an addition there. Please open a ticket on > infra-support(a)ovirt.org about it. > Trying > > > >> It looks like the stdci docs[1] are not maintained for a while, >> listing mirrors for >> fedora 30 and centos 7. >> > > I would suggest to open a ticket for this as well > > > >> >> Looking in the mirrors jobs[2] we have advanced-virtualization for >> centos[3] but >> it holds old versions (6.x). >> >> Can we add a local mirror for this repo? >> >> [1] >> https://ovirt-infra-docs.readthedocs.io/en/latest/CI/List_of_mirrors/index.… >> [2] https://jenkins.ovirt.org/search/?q=system-sync_mirrors >> [3] >> https://buildlogs.centos.org/centos/8/virt/x86_64/advanced-virtualization/P… >> >> Nir >> >> > > -- > > Sandro Bonazzola > > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > > Red Hat EMEA <https://www.redhat.com/> > > sbonazzo(a)redhat.com > <https://www.redhat.com/> > > *Red Hat respects your work life balance. Therefore there is no need to > answer this email out of your office hours. > <https://mojo.redhat.com/docs/DOC-1199578>* > > > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100166)

1 0

[CQ]: 115326,1 (ovirt-imageio) failed "ovirt-master" system tests
by oVirt Jenkins 22 Jun '21

22 Jun '21

Change 115326,1 (ovirt-imageio) 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://gerrit.ovirt.org/c/ovirt-imageio/+/#/c/115326/1 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/30364/

1 0

[JIRA] (OVIRT-3098) Gerrit hook adds unrelated patches to bugs
by Yedidyah Bar David (oVirt JIRA) 22 Jun '21

22 Jun '21

[ https://ovirt-jira.atlassian.net/browse/OVIRT-3098?page=com.atlassian.jira.… ] Yedidyah Bar David commented on OVIRT-3098: ------------------------------------------- On Mon, Jun 21, 2021 at 9:58 PM Eyal Shenitzky <eshenitz(a)redhat.com> wrote: > > > +Dusan Fodor > > On Mon, 21 Jun 2021 at 13:32, Nir Soffer <nsoffer(a)redhat.com> wrote: >> >> Gerrit hook is wrongly looking for https://bugzilla.redhat.com/ URLs >> in the commit message, and adding the patch to the bug. >> >> Example patch: >> https://gerrit.ovirt.org/c/vdsm/+/115339 >> >> I had to clean up the bug after the broken hook (see screenshot). >> >> The hook should really look only in the single URL in (one or more) >> Bug-Url headers: >> >> Bug-Url: https://bugzilla.redhat.com/ >> >> I reported this years ago (I think for Related-To:), and I remember we had >> a patch fixing this issue, but for some reason it was lost. >> >> Nir See also: https://ovirt-jira.atlassian.net/browse/OVIRT-3075 Best regards, -- Didi > Gerrit hook adds unrelated patches to bugs > ------------------------------------------ > > Key: OVIRT-3098 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3098 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > Attachments: Screenshot from 2021-06-21 13-16-19.png > > > Gerrit hook is wrongly looking for https://bugzilla.redhat.com/ URLs > in the commit message, and adding the patch to the bug. > Example patch: > https://gerrit.ovirt.org/c/vdsm/+/115339 > I had to clean up the bug after the broken hook (see screenshot). > The hook should really look only in the single URL in (one or more) > Bug-Url headers: > Bug-Url: https://bugzilla.redhat.com/ > I reported this years ago (I think for Related-To:), and I remember we had > a patch fixing this issue, but for some reason it was lost. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100166)

1 0

[CQ]: 115354, 5 (ovirt-system-tests) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 22 Jun '21

22 Jun '21

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

1 0

[oVirt Jenkins] ovirt-system-tests_basic-suite-master_nightly - Build # 1246 - Failure!
by jenkins＠jenkins.phx.ovirt.org 22 Jun '21

22 Jun '21

Project: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-master_nightly/ Build: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-master_nightly… Build Number: 1246 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #1246 [Shani Leviim] engine_utils: verify job status by correlation id ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: basic-suite-master.test-scenarios.test_007_sd_reattach.test_deactivate_storage_domain Error Message: AssertionError: set() != {<JobStatus.FINISHED: 'finished'>} after 180 seconds Stack Trace: engine_api = <ovirtsdk4.Connection object at 0x7f522564b5c0> @order_by(_TEST_LIST) def test_deactivate_storage_domain(engine_api): # TODO: uncomment once VnicSetup checks are fixed. # TODO: this also seems to leave running tasks behind which break the deactivation. # TODO: it should be tested in multiple runs or properly waited for. # VnicSetup.vnic_setup().init(engine_api.system_service(), # VM2_NAME, DC_NAME, CLUSTER_NAME) engine = engine_api.system_service() dc = test_utils.data_center_service(engine_api.system_service(), DC_NAME) correlation_id = 'deactivate_storage_domain' def _deactivate_with_running_ovf_update_task(): try: test_utils.get_attached_storage_domain( dc, SD_SECOND_NFS_NAME, service=True).deactivate( query={'correlation_id': correlation_id}) return True except ovirtsdk4.Error as err: # The storage domain's deactivation may fail if it has running tasks. # In case of updating ovf_store disks task (UploadStream), # ignore. Otherwise, raise the exception. if not (('UploadStream' in err.args[0]) or ('OVF' in err.args[0])): raise return False assertions.assert_true_within_short( _deactivate_with_running_ovf_update_task) # Wait for the storage deactivation to be finished. assertions.assert_equals_within_short( lambda: > engine_utils.get_jobs_statuses(engine, correlation_id), {ovirtsdk4.types.JobStatus.FINISHED} ) basic-suite-master/test-scenarios/test_007_sd_reattach.py:85: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ ost_utils/ost_utils/assertions.py:74: in assert_equals_within_short error_message=error_message _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ func = <function test_deactivate_storage_domain.<locals>.<lambda> at 0x7f522576e0d0> value = {<JobStatus.FINISHED: 'finished'>}, timeout = 180 allowed_exceptions = [], initial_wait = 0 error_message = "set() != {<JobStatus.FINISHED: 'finished'>} after 180 seconds" def assert_equals_within( func, value, timeout, allowed_exceptions=None, initial_wait=10, error_message=None ): allowed_exceptions = allowed_exceptions or [] res = '<no-result-obtained>' with _EggTimer(timeout) as timer: while not timer.elapsed(): try: res = func() if res == value: return except Exception as exc: if _instance_of_any(exc, allowed_exceptions): time.sleep(3) continue LOGGER.exception("Unhandled exception in %s", func) raise if initial_wait == 0: time.sleep(3) else: time.sleep(initial_wait) initial_wait = 0 try: if error_message is None: error_message = '%s != %s after %s seconds' % (res, value, timeout) > raise AssertionError(error_message) E AssertionError: set() != {<JobStatus.FINISHED: 'finished'>} after 180 seconds ost_utils/ost_utils/assertions.py:59: AssertionError

1 9

[CQ]: 115064, 3 (ovirt-system-tests) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 22 Jun '21

22 Jun '21

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

1 0

[oVirt Jenkins] ovirt-system-tests_basic-suite-4.3_nightly - Build # 588 - Failure!
by jenkins＠jenkins.phx.ovirt.org 22 Jun '21

22 Jun '21

Project: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-4.3_nightly/ Build: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-4.3_nightly/58… Build Number: 588 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #588 [parthdhanjal] Updating max click version ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 004_basic_sanity.run_vms Error Message: Fault reason is "Operation Failed". Fault detail is "[Network error during communication with the Host.]". HTTP response code is 400. Stack Trace: Traceback (most recent call last): File "/usr/lib64/python2.7/unittest/case.py", line 369, in run testMethod() File "/usr/lib/python2.7/site-packages/nose/case.py", line 197, in runTest self.test(*self.arg) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 142, in wrapped_test test() File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 60, in wrapper return func(get_test_prefix(), *args, **kwargs) File "/home/jenkins/agent/workspace/ovirt-system-tests_basic-suite-4.3_nightly/ovirt-system-tests/basic-suite-4.3/test-scenarios/004_basic_sanity.py", line 694, in run_vms vm0_service.start(use_cloud_init=True, vm=vm_params) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 32520, in start return self._internal_action(action, 'start', None, headers, query, wait) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 299, in _internal_action return future.wait() if wait else future File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 55, in wait return self._code(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 296, in callback self._check_fault(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 134, in _check_fault self._raise_error(response, body.fault) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 118, in _raise_error raise error Error: Fault reason is "Operation Failed". Fault detail is "[Network error during communication with the Host.]". HTTP response code is 400.

1 2

oVirt infra daily report - unstable production jobs - 1594
by jenkins＠jenkins.phx.ovirt.org 22 Jun '21

22 Jun '21

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

1 0

[CQ]: 114741, 5 (ovirt-system-tests) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 21 Jun '21

21 Jun '21

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

1 0

[CQ]: 115341, 2 (ovirt-system-tests) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 21 Jun '21

21 Jun '21

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

1 0

[CQ]: 115336, 4 (ovirt-system-tests) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 21 Jun '21

21 Jun '21

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

1 0

[CQ]: 115343, 1 (ovirt-system-tests) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 21 Jun '21

21 Jun '21

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

1 0

[JIRA] (OVIRT-3098) Gerrit hook adds unrelated patches to bugs
by Eyal Shenitzky (oVirt JIRA) 21 Jun '21

21 Jun '21

[ https://ovirt-jira.atlassian.net/browse/OVIRT-3098?page=com.atlassian.jira.… ] Eyal Shenitzky commented on OVIRT-3098: --------------------------------------- +Dusan Fodor <dfodor(a)redhat.com> On Mon, 21 Jun 2021 at 13:32, Nir Soffer <nsoffer(a)redhat.com> wrote: > Gerrit hook is wrongly looking for https://bugzilla.redhat.com/ URLs > in the commit message, and adding the patch to the bug. > > Example patch: > https://gerrit.ovirt.org/c/vdsm/+/115339 > > I had to clean up the bug after the broken hook (see screenshot). > > The hook should really look only in the single URL in (one or more) > Bug-Url headers: > > Bug-Url: https://bugzilla.redhat.com/ > > I reported this years ago (I think for Related-To:), and I remember we had > a patch fixing this issue, but for some reason it was lost. > > Nir > -- Regards, Eyal Shenitzky > Gerrit hook adds unrelated patches to bugs > ------------------------------------------ > > Key: OVIRT-3098 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3098 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > Attachments: Screenshot from 2021-06-21 13-16-19.png > > > Gerrit hook is wrongly looking for https://bugzilla.redhat.com/ URLs > in the commit message, and adding the patch to the bug. > Example patch: > https://gerrit.ovirt.org/c/vdsm/+/115339 > I had to clean up the bug after the broken hook (see screenshot). > The hook should really look only in the single URL in (one or more) > Bug-Url headers: > Bug-Url: https://bugzilla.redhat.com/ > I reported this years ago (I think for Related-To:), and I remember we had > a patch fixing this issue, but for some reason it was lost. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100166)

1 0

[JIRA] (OVIRT-3098) Gerrit hook adds unrelated patches to bugs
by Nir Soffer (oVirt JIRA) 21 Jun '21

21 Jun '21

Nir Soffer created OVIRT-3098: --------------------------------- Summary: Gerrit hook adds unrelated patches to bugs Key: OVIRT-3098 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3098 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Nir Soffer Assignee: infra Gerrit hook is wrongly looking for https://bugzilla.redhat.com/ URLs in the commit message, and adding the patch to the bug. Example patch: https://gerrit.ovirt.org/c/vdsm/+/115339 I had to clean up the bug after the broken hook (see screenshot). The hook should really look only in the single URL in (one or more) Bug-Url headers: Bug-Url: https://bugzilla.redhat.com/ I reported this years ago (I think for Related-To:), and I remember we had a patch fixing this issue, but for some reason it was lost. Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100166)

1 0

[JIRA] (OVIRT-3073) Re: Change in ovirt-engine[master]: packaging: setup: Move engine-specific pg conf to common
by Evgheni Dereveanchin (oVirt JIRA) 21 Jun '21

21 Jun '21

[ https://ovirt-jira.atlassian.net/browse/OVIRT-3073?page=com.atlassian.jira.… ] Evgheni Dereveanchin closed OVIRT-3073. --------------------------------------- Resolution: Fixed AFAIR this was fixed by setting `alternatives --set python /usr/bin/python3` to our instance build scripts > Re: Change in ovirt-engine[master]: packaging: setup: Move engine-specific pg conf to common > -------------------------------------------------------------------------------------------- > > Key: OVIRT-3073 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3073 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Yedidyah Bar David > Assignee: Evgheni Dereveanchin > > On Mon, Dec 14, 2020 at 12:21 PM Code Review <gerrit(a)ovirt.org> wrote: > > > > From Jenkins CI <jenkins(a)ovirt.org>: > > > > Jenkins CI has posted comments on this change. ( https://gerrit.ovirt.org/c/ovirt-engine/+/112414 ) > > > > Change subject: packaging: setup: Move engine-specific pg conf to common > > ...................................................................... > > > > > > Patch Set 4: Continuous-Integration-1 > > > > Build Failed > > > > https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/9236/ : FAILURE > 12:21:32 + usrc=/home/jenkins/workspace/ovirt-engine_standard-check-patch/jenkins/stdci_tools/usrc.py > 12:21:32 + [[ -x > /home/jenkins/workspace/ovirt-engine_standard-check-patch/jenkins/stdci_tools/usrc.py > ]] > 12:21:32 + /home/jenkins/workspace/ovirt-engine_standard-check-patch/jenkins/stdci_tools/usrc.py > --log -d get > 12:21:32 /usr/bin/env: ‘python’: No such file or directory > Any idea? > This is a result of manual 'ci test'. Automatic check-patch on the > same patch did succeed. > Thanks, > > > > > > -- > > To view, visit https://gerrit.ovirt.org/c/ovirt-engine/+/112414 > > To unsubscribe, or for help writing mail filters, visit https://gerrit.ovirt.org/settings > > > > Gerrit-Project: ovirt-engine > > Gerrit-Branch: master > > Gerrit-Change-Id: I8af2e259389fef59251a69c6443e3e440b93a843 > > Gerrit-Change-Number: 112414 > > Gerrit-PatchSet: 4 > > Gerrit-Owner: Yedidyah Bar David <didi(a)redhat.com> > > Gerrit-Reviewer: Asaf Rachmani <arachman(a)redhat.com> > > Gerrit-Reviewer: Evgeny Slutsky <eslutsky(a)redhat.com> > > Gerrit-Reviewer: Gal Zaidman <gzaidman(a)redhat.com> > > Gerrit-Reviewer: Jenkins CI <jenkins(a)ovirt.org> > > Gerrit-Reviewer: Lev Veyde <lveyde(a)redhat.com> > > Gerrit-Reviewer: Sandro Bonazzola <sbonazzo(a)redhat.com> > > Gerrit-Reviewer: Yedidyah Bar David <didi(a)redhat.com> > > Gerrit-Reviewer: gerrit-hooks <automation(a)ovirt.org> > > Gerrit-Comment-Date: Mon, 14 Dec 2020 10:21:34 +0000 > > Gerrit-HasComments: No > > Gerrit-Has-Labels: Yes > > Gerrit-MessageType: comment > > > -- > Didi -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100166)

1 0

[JIRA] (OVIRT-3073) Re: Change in ovirt-engine[master]: packaging: setup: Move engine-specific pg conf to common
by Evgheni Dereveanchin (oVirt JIRA) 21 Jun '21

21 Jun '21

[ https://ovirt-jira.atlassian.net/browse/OVIRT-3073?page=com.atlassian.jira.… ] Evgheni Dereveanchin updated OVIRT-3073: ---------------------------------------- Issue Type: Bug (was: By-EMAIL) > Re: Change in ovirt-engine[master]: packaging: setup: Move engine-specific pg conf to common > -------------------------------------------------------------------------------------------- > > Key: OVIRT-3073 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3073 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Yedidyah Bar David > Assignee: Evgheni Dereveanchin > > On Mon, Dec 14, 2020 at 12:21 PM Code Review <gerrit(a)ovirt.org> wrote: > > > > From Jenkins CI <jenkins(a)ovirt.org>: > > > > Jenkins CI has posted comments on this change. ( https://gerrit.ovirt.org/c/ovirt-engine/+/112414 ) > > > > Change subject: packaging: setup: Move engine-specific pg conf to common > > ...................................................................... > > > > > > Patch Set 4: Continuous-Integration-1 > > > > Build Failed > > > > https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/9236/ : FAILURE > 12:21:32 + usrc=/home/jenkins/workspace/ovirt-engine_standard-check-patch/jenkins/stdci_tools/usrc.py > 12:21:32 + [[ -x > /home/jenkins/workspace/ovirt-engine_standard-check-patch/jenkins/stdci_tools/usrc.py > ]] > 12:21:32 + /home/jenkins/workspace/ovirt-engine_standard-check-patch/jenkins/stdci_tools/usrc.py > --log -d get > 12:21:32 /usr/bin/env: ‘python’: No such file or directory > Any idea? > This is a result of manual 'ci test'. Automatic check-patch on the > same patch did succeed. > Thanks, > > > > > > -- > > To view, visit https://gerrit.ovirt.org/c/ovirt-engine/+/112414 > > To unsubscribe, or for help writing mail filters, visit https://gerrit.ovirt.org/settings > > > > Gerrit-Project: ovirt-engine > > Gerrit-Branch: master > > Gerrit-Change-Id: I8af2e259389fef59251a69c6443e3e440b93a843 > > Gerrit-Change-Number: 112414 > > Gerrit-PatchSet: 4 > > Gerrit-Owner: Yedidyah Bar David <didi(a)redhat.com> > > Gerrit-Reviewer: Asaf Rachmani <arachman(a)redhat.com> > > Gerrit-Reviewer: Evgeny Slutsky <eslutsky(a)redhat.com> > > Gerrit-Reviewer: Gal Zaidman <gzaidman(a)redhat.com> > > Gerrit-Reviewer: Jenkins CI <jenkins(a)ovirt.org> > > Gerrit-Reviewer: Lev Veyde <lveyde(a)redhat.com> > > Gerrit-Reviewer: Sandro Bonazzola <sbonazzo(a)redhat.com> > > Gerrit-Reviewer: Yedidyah Bar David <didi(a)redhat.com> > > Gerrit-Reviewer: gerrit-hooks <automation(a)ovirt.org> > > Gerrit-Comment-Date: Mon, 14 Dec 2020 10:21:34 +0000 > > Gerrit-HasComments: No > > Gerrit-Has-Labels: Yes > > Gerrit-MessageType: comment > > > -- > Didi -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100166)

1 0

[JIRA] (OVIRT-3073) Re: Change in ovirt-engine[master]: packaging: setup: Move engine-specific pg conf to common
by Evgheni Dereveanchin (oVirt JIRA) 21 Jun '21

21 Jun '21

[ https://ovirt-jira.atlassian.net/browse/OVIRT-3073?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-3073: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: Unassigned) > Re: Change in ovirt-engine[master]: packaging: setup: Move engine-specific pg conf to common > -------------------------------------------------------------------------------------------- > > Key: OVIRT-3073 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3073 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Yedidyah Bar David > Assignee: Evgheni Dereveanchin > > On Mon, Dec 14, 2020 at 12:21 PM Code Review <gerrit(a)ovirt.org> wrote: > > > > From Jenkins CI <jenkins(a)ovirt.org>: > > > > Jenkins CI has posted comments on this change. ( https://gerrit.ovirt.org/c/ovirt-engine/+/112414 ) > > > > Change subject: packaging: setup: Move engine-specific pg conf to common > > ...................................................................... > > > > > > Patch Set 4: Continuous-Integration-1 > > > > Build Failed > > > > https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/9236/ : FAILURE > 12:21:32 + usrc=/home/jenkins/workspace/ovirt-engine_standard-check-patch/jenkins/stdci_tools/usrc.py > 12:21:32 + [[ -x > /home/jenkins/workspace/ovirt-engine_standard-check-patch/jenkins/stdci_tools/usrc.py > ]] > 12:21:32 + /home/jenkins/workspace/ovirt-engine_standard-check-patch/jenkins/stdci_tools/usrc.py > --log -d get > 12:21:32 /usr/bin/env: ‘python’: No such file or directory > Any idea? > This is a result of manual 'ci test'. Automatic check-patch on the > same patch did succeed. > Thanks, > > > > > > -- > > To view, visit https://gerrit.ovirt.org/c/ovirt-engine/+/112414 > > To unsubscribe, or for help writing mail filters, visit https://gerrit.ovirt.org/settings > > > > Gerrit-Project: ovirt-engine > > Gerrit-Branch: master > > Gerrit-Change-Id: I8af2e259389fef59251a69c6443e3e440b93a843 > > Gerrit-Change-Number: 112414 > > Gerrit-PatchSet: 4 > > Gerrit-Owner: Yedidyah Bar David <didi(a)redhat.com> > > Gerrit-Reviewer: Asaf Rachmani <arachman(a)redhat.com> > > Gerrit-Reviewer: Evgeny Slutsky <eslutsky(a)redhat.com> > > Gerrit-Reviewer: Gal Zaidman <gzaidman(a)redhat.com> > > Gerrit-Reviewer: Jenkins CI <jenkins(a)ovirt.org> > > Gerrit-Reviewer: Lev Veyde <lveyde(a)redhat.com> > > Gerrit-Reviewer: Sandro Bonazzola <sbonazzo(a)redhat.com> > > Gerrit-Reviewer: Yedidyah Bar David <didi(a)redhat.com> > > Gerrit-Reviewer: gerrit-hooks <automation(a)ovirt.org> > > Gerrit-Comment-Date: Mon, 14 Dec 2020 10:21:34 +0000 > > Gerrit-HasComments: No > > Gerrit-Has-Labels: Yes > > Gerrit-MessageType: comment > > > -- > Didi -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100166)

1 0

Terraform and DNS
by Marc Dequènes (Duck) 21 Jun '21

21 Jun '21

Quack, Since you were thinking about using Terraform I was currous if NS updates were supported and they are: https://registry.terraform.io/providers/hashicorp/dns/latest/docs This means you can create a subzone of ovirt.org and delegate the full subzone or specific RRs. Then if you wish certain entries accessible from ovirt.org directly we can simply add CNAMEs. This is an alternative to using freipa's DNS management. The doc does not do into fulld etails but it's "basic DNS management" which probably means not all RR types are supported. I guess one question is how do you wish the main zone to be managed. I like to be able to manage the zone file by myself with comments and use subzones for automation but freeipa or DNS providers can do it all for you and provide an API too (with the same RR types limitation though, so it depends what kind of data you wish to put into it). I guess that's why RH decided to use IPA.REDHAT.COM instead of REDHAT.COM, freeipa can manage its own DNS entries (SRV…) for the provided services but you can still manage your main zone the way you want (for specific or historical reasons). I guess the domain to use for freeipa is also something to consider. \_o<

1 0

[oVirt Jenkins] ovirt-system-tests_basic-suite-4.3_el7-nightly - Build # 581 - Failure!
by jenkins＠jenkins.phx.ovirt.org 21 Jun '21

21 Jun '21

Project: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-4.3_el7-nightl… Build: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-4.3_el7-nightl… Build Number: 581 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #581 [parthdhanjal] Updating max click version ----------------- Failed Tests: ----------------- No tests ran.

1 1

[oVirt Jenkins] ovirt-release_4.3_build-artifacts-el7-x86_64 - Build # 1015 - Failure!
by jenkins＠jenkins.phx.ovirt.org 21 Jun '21

21 Jun '21

Project: https://jenkins.ovirt.org/job/ovirt-release_4.3_build-artifacts-el7-x86_64/ Build: https://jenkins.ovirt.org/job/ovirt-release_4.3_build-artifacts-el7-x86_64/… Build Number: 1015 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #1015 [Sandro Bonazzola] Revert "automation: install centos-release if missing" ----------------- Failed Tests: ----------------- No tests ran.

1 1

oVirt infra daily report - unstable production jobs - 1593
by jenkins＠jenkins.phx.ovirt.org 21 Jun '21

21 Jun '21

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

1 0

[oVirt Jenkins] ovirt-system-tests_basic-suite-4.3_el7-nightly - Build # 578 - Failure!
by jenkins＠jenkins.phx.ovirt.org 20 Jun '21

20 Jun '21

Project: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-4.3_el7-nightl… Build: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-4.3_el7-nightl… Build Number: 578 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #578 [parthdhanjal] Updating max click version ----------------- Failed Tests: ----------------- No tests ran.

1 1

[oVirt Jenkins] ovirt-system-tests_basic-suite-4.3_nightly - Build # 583 - Failure!
by jenkins＠jenkins.phx.ovirt.org 20 Jun '21

20 Jun '21

Project: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-4.3_nightly/ Build: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-4.3_nightly/58… Build Number: 583 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #583 [parthdhanjal] Updating max click version ----------------- Failed Tests: ----------------- No tests ran.

1 1

[oVirt Jenkins] cleanup-gated-ovirt-4.3 - Build #548 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 20 Jun '21

20 Jun '21

Build: https://jenkins.ovirt.org/job/cleanup-gated-ovirt-4.3/548/ Build Name: #548 Build Status: FAILURE Gerrit change: null - title: null - project: null - branch: null - author: null <null>

1 0

oVirt infra daily report - unstable production jobs - 1592
by jenkins＠jenkins.phx.ovirt.org 20 Jun '21

20 Jun '21

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

1 0

[oVirt Jenkins] ovirt-system-tests_basic-suite-4.3_el7-nightly - Build # 575 - Failure!
by jenkins＠jenkins.phx.ovirt.org 19 Jun '21

19 Jun '21

Project: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-4.3_el7-nightl… Build: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-4.3_el7-nightl… Build Number: 575 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #575 [parthdhanjal] Updating max click version ----------------- Failed Tests: ----------------- No tests ran.

1 1

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

19 Jun '21

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

1 0

[CQ]: 114588, 19 (ovirt-system-tests) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 18 Jun '21

18 Jun '21

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

1 0

[oVirt Jenkins] ovirt-system-tests_basic-suite-4.3_nightly - Build # 576 - Failure!
by jenkins＠jenkins.phx.ovirt.org 18 Jun '21

18 Jun '21

Project: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-4.3_nightly/ Build: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-4.3_nightly/57… Build Number: 576 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #576 [parthdhanjal] Updating max click version ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 004_basic_sanity.run_vms Error Message: Fault reason is "Operation Failed". Fault detail is "[Network error during communication with the Host.]". HTTP response code is 400. Stack Trace: Traceback (most recent call last): File "/usr/lib64/python2.7/unittest/case.py", line 369, in run testMethod() File "/usr/lib/python2.7/site-packages/nose/case.py", line 197, in runTest self.test(*self.arg) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 142, in wrapped_test test() File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 60, in wrapper return func(get_test_prefix(), *args, **kwargs) File "/home/jenkins/agent/workspace/ovirt-system-tests_basic-suite-4.3_nightly/ovirt-system-tests/basic-suite-4.3/test-scenarios/004_basic_sanity.py", line 694, in run_vms vm0_service.start(use_cloud_init=True, vm=vm_params) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 32520, in start return self._internal_action(action, 'start', None, headers, query, wait) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 299, in _internal_action return future.wait() if wait else future File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 55, in wait return self._code(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 296, in callback self._check_fault(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 134, in _check_fault self._raise_error(response, body.fault) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 118, in _raise_error raise error Error: Fault reason is "Operation Failed". Fault detail is "[Network error during communication with the Host.]". HTTP response code is 400.

1 3

[oVirt Jenkins] ovirt-system-tests_basic-suite-4.3_el7-nightly - Build # 571 - Failure!
by jenkins＠jenkins.phx.ovirt.org 18 Jun '21

18 Jun '21

Project: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-4.3_el7-nightl… Build: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-4.3_el7-nightl… Build Number: 571 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #571 [parthdhanjal] Updating max click version ----------------- Failed Tests: ----------------- No tests ran.

1 2

oVirt infra daily report - unstable production jobs - 1590
by jenkins＠jenkins.phx.ovirt.org 18 Jun '21

18 Jun '21

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

1 0

[CQ]: 115311, 1 (ovirt-system-tests) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 18 Jun '21

18 Jun '21

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

1 0

[CQ]: 115304, 2 (ovirt-system-tests) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 17 Jun '21

17 Jun '21

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

1 0

[CQ]: 114926, 9 (ovirt-system-tests) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 17 Jun '21

17 Jun '21

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

1 0

[CQ]: 115222, 6 (ovirt-system-tests) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 17 Jun '21

17 Jun '21

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

1 0

[CQ]: 115115, 2 (ovirt-system-tests) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 17 Jun '21

17 Jun '21

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

1 0