- Infra - oVirt List Archives

[CQ]: 104250, 15 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 15 Nov '19

15 Nov '19

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

1 0

[CQ]: 104232, 16 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 15 Nov '19

15 Nov '19

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

1 0

[CQ]: 104305, 6 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 15 Nov '19

15 Nov '19

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

1 0

[CQ]: 104095, 19 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 15 Nov '19

15 Nov '19

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

1 0

[CQ]: 104254, 10 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 14 Nov '19

14 Nov '19

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

1 0

[CQ]: 104203, 15 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 14 Nov '19

14 Nov '19

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

1 0

oVirt infra daily report - unstable production jobs - 1009
by jenkins＠jenkins.phx.ovirt.org 14 Nov '19

14 Nov '19

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

1 0

[JIRA] (OVIRT-2836) nlevy@redhat.com is listed twice in gerrit and can't be selected as reviewer
by Sandro Bonazzola (oVirt JIRA) 14 Nov '19

14 Nov '19

Sandro Bonazzola created OVIRT-2836: --------------------------------------- Summary: nlevy(a)redhat.com is listed twice in gerrit and can't be selected as reviewer Key: OVIRT-2836 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2836 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Sandro Bonazzola Assignee: infra nlevy(a)redhat.com is listed twice in gerrit and can't be selected as reviewer infra team, can you please fix? Thanks, -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100114)

1 0

[CQ]: 104253, 10 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 14 Nov '19

14 Nov '19

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

1 0

Build failed in Jenkins: system-sync_mirrors-centos-qemu-ev-release-el7-x86_64 #2606
by jenkins＠jenkins.phx.ovirt.org 14 Nov '19

14 Nov '19

See <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-qemu-ev-release-el7…> Changes: ------------------------------------------ Started by timer Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-qemu-ev-release-el7…> No credentials specified > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -fdx # timeout=10 Pruning obsolete local branches Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git > git --version # timeout=10 > git fetch --tags --progress --prune http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision e8e66519e6db4e1ad290c1c4bcf4c1f8a4c607dc (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f e8e66519e6db4e1ad290c1c4bcf4c1f8a4c607dc Commit message: "pipeline-loader: Ensure POD labels in right length" > git rev-list --no-walk e8e66519e6db4e1ad290c1c4bcf4c1f8a4c607dc # timeout=10 [system-sync_mirrors-centos-qemu-ev-release-el7-x86_64] $ /bin/bash -xe /tmp/jenkins5896954811327566755.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror centos-qemu-ev-release-el7 x86_64 jenkins/data/mirrors-reposync.conf + MIRRORS_MP_BASE=/var/www/html/repos + MIRRORS_HTTP_BASE=http://mirrors.phx.ovirt.org/repos + MIRRORS_CACHE=/home/jenkins/mirrors_cache + MAX_LOCK_ATTEMPTS=120 + LOCK_WAIT_INTERVAL=5 + LOCK_BASE=/home/jenkins + OLD_MD_TO_KEEP=100 + HTTP_SELINUX_TYPE=httpd_sys_content_t + HTTP_FILE_MODE=644 + main resync_yum_mirror centos-qemu-ev-release-el7 x86_64 jenkins/data/mirrors-reposync.conf + local command=resync_yum_mirror + command_args=("${@:2}") + local command_args + cmd_resync_yum_mirror centos-qemu-ev-release-el7 x86_64 jenkins/data/mirrors-reposync.conf + local repo_name=centos-qemu-ev-release-el7 + local repo_archs=x86_64 + local reposync_conf=jenkins/data/mirrors-reposync.conf + local sync_needed + mkdir -p /home/jenkins/mirrors_cache + verify_repo_fs centos-qemu-ev-release-el7 yum + local repo_name=centos-qemu-ev-release-el7 + local repo_type=yum + sudo install -o jenkins -d /var/www/html/repos/yum /var/www/html/repos/yum/centos-qemu-ev-release-el7 /var/www/html/repos/yum/centos-qemu-ev-release-el7/base + check_yum_sync_needed centos-qemu-ev-release-el7 x86_64 jenkins/data/mirrors-reposync.conf sync_needed + local repo_name=centos-qemu-ev-release-el7 + local repo_archs=x86_64 + local reposync_conf=jenkins/data/mirrors-reposync.conf + local p_sync_needed=sync_needed + local reposync_out + echo 'Checking if mirror needs a resync' Checking if mirror needs a resync + rm -rf /home/jenkins/mirrors_cache/centos-qemu-ev-release-el7 ++ IFS=, ++ echo x86_64 + for arch in '$(IFS=,; echo $repo_archs)' ++ run_reposync centos-qemu-ev-release-el7 x86_64 jenkins/data/mirrors-reposync.conf --urls --quiet ++ local repo_name=centos-qemu-ev-release-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-qemu-ev-release-el7 --arch=x86_64 --cachedir=/home/jenkins/mirrors_cache --download_path=/var/www/html/repos/yum/centos-qemu-ev-release-el7/base --norepopath --newest-only --urls --quiet + reposync_out='http://mirror.centos.org/centos/7/virt/x86_64/kvm-common/qemu-img-ev-2.12.0… http://mirror.centos.org/centos/7/virt/x86_64/kvm-common/qemu-kvm-common-ev… http://mirror.centos.org/centos/7/virt/x86_64/kvm-common/qemu-kvm-ev-2.12.0… http://mirror.centos.org/centos/7/virt/x86_64/kvm-common/qemu-kvm-tools-ev-…' + [[ -n http://mirror.centos.org/centos/7/virt/x86_64/kvm-common/qemu-img-ev-2.12.0… http://mirror.centos.org/centos/7/virt/x86_64/kvm-common/qemu-kvm-common-ev… http://mirror.centos.org/centos/7/virt/x86_64/kvm-common/qemu-kvm-ev-2.12.0… http://mirror.centos.org/centos/7/virt/x86_64/kvm-common/qemu-kvm-tools-ev-… ]] + eval sync_needed=true ++ sync_needed=true + return + [[ -n true ]] + install_repo_pubkey centos-qemu-ev-release-el7 jenkins/data/mirrors-reposync.conf + local repo_name=centos-qemu-ev-release-el7 + local reposync_conf=jenkins/data/mirrors-reposync.conf + local gpg_key_file ++ sed -nr -e '/\[centos-qemu-ev-release-el7]/{ :loop; s#^gpgkey\s*=\s*file://(.*)$#\1#p; n; /^\[.*\]$/q ; b loop }' jenkins/data/mirrors-reposync.conf + gpg_key_file=/etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-SIG-Virtualization + [[ -n /etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-SIG-Virtualization ]] + [[ -r /etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-SIG-Virtualization ]] + sudo /usr/bin/rpmkeys --import /etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-SIG-Virtualization + echo 'Resyncing repo: centos-qemu-ev-release-el7' Resyncing repo: centos-qemu-ev-release-el7 + perform_yum_sync centos-qemu-ev-release-el7 x86_64 jenkins/data/mirrors-reposync.conf + local repo_name=centos-qemu-ev-release-el7 + local repo_archs=x86_64 + local reposync_conf=jenkins/data/mirrors-reposync.conf + local repo_mp + local repo_comps + repo_mp=/var/www/html/repos/yum/centos-qemu-ev-release-el7/base ++ IFS=, ++ echo x86_64 + for arch in '$(IFS=,; echo $repo_archs)' + echo 'Syncing yum repo centos-qemu-ev-release-el7 for arch: x86_64' Syncing yum repo centos-qemu-ev-release-el7 for arch: x86_64 + run_reposync centos-qemu-ev-release-el7 x86_64 jenkins/data/mirrors-reposync.conf --downloadcomps --gpgcheck + local repo_name=centos-qemu-ev-release-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-qemu-ev-release-el7 --arch=x86_64 --cachedir=/home/jenkins/mirrors_cache --download_path=/var/www/html/repos/yum/centos-qemu-ev-release-el7/base --norepopath --newest-only --downloadcomps --gpgcheck qemu-kvm-common-ev-2.12.0-33.1 FAILED (1/4): qemu-img-ev-2.12.0- 0% [ ] 0.0 B/s | 0 B --:-- ETA qemu-kvm-ev-2.12.0-33.1.el7_7. FAILED (1/4): qemu-img-ev-2.12.0- 0% [ ] 0.0 B/s | 0 B --:-- ETA (1/4): qemu-img-ev-2.12.0-33.1.el7_7.4.x86_64.rpm | 1.3 MB 00:00 (2/4): qemu-kvm-tools-ev-2.12.0-33.1.el7_7.4.x86_64.rpm | 554 kB 00:00 10:qemu-kvm-ev-2.12.0-33.1.el7_7.4.x86_64: [Errno 256] No more mirrors to try. 10:qemu-kvm-common-ev-2.12.0-33.1.el7_7.4.x86_64: [Errno 256] No more mirrors to try. Removing qemu-kvm-common-ev-2.12.0-33.1.el7_7.4.x86_64.rpm due to failed signature check. Removing qemu-kvm-ev-2.12.0-33.1.el7_7.4.x86_64.rpm due to failed signature check. Build step 'Execute shell' marked build as failure

1 1

[JIRA] (OVIRT-2835) containers dying for no obvious reason
by Evgheni Dereveanchin (oVirt JIRA) 14 Nov '19

14 Nov '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2835?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-2835: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > containers dying for no obvious reason > -------------------------------------- > > Key: OVIRT-2835 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2835 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dusan Fodor > Assignee: Evgheni Dereveanchin > > We often see pipelines that just hang after they lost connection with their containers. It is not yet clear if containers were moved, if pod was moved, if it's on node level. But pipeline just keeps waiting forever. > Job example: > https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/6077/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100114)

1 0

[JIRA] (OVIRT-2835) containers dying for no obvious reason
by Dusan Fodor (oVirt JIRA) 14 Nov '19

14 Nov '19

Dusan Fodor created OVIRT-2835: ---------------------------------- Summary: containers dying for no obvious reason Key: OVIRT-2835 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2835 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Dusan Fodor Assignee: infra We often see pipelines that just hang after they lost connection with their containers. It is not yet clear if containers were moved, if pod was moved, if it's on node level. But pipeline just keeps waiting forever. Job example: https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/6077/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100114)

1 0

[JIRA] (OVIRT-2834) please install zanata in our ovirt infra
by Evgheni Dereveanchin (oVirt JIRA) 14 Nov '19

14 Nov '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2834?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-2834: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > please install zanata in our ovirt infra > ---------------------------------------- > > Key: OVIRT-2834 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2834 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Michal Skrivanek > Assignee: Evgheni Dereveanchin > > for now decided to use our own instance, we'll move current translations to it once it's ready -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100114)

1 0

[JIRA] (OVIRT-2833) Please add msobczyk to vdsm maintainers
by Galit Rosenthal (oVirt JIRA) 14 Nov '19

14 Nov '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2833?page=com.atlassian.jira.… ] Galit Rosenthal reassigned OVIRT-2833: -------------------------------------- Assignee: Galit Rosenthal (was: infra) > Please add msobczyk to vdsm maintainers > --------------------------------------- > > Key: OVIRT-2833 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2833 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Michal Skrivanek > Assignee: Galit Rosenthal > > per devel(a)ovirt.org -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100114)

1 0

[CQ]: 103997, 24 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 14 Nov '19

14 Nov '19

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

1 0

[JIRA] (OVIRT-2834) please install zanata in our ovirt infra
by Michal Skrivanek (oVirt JIRA) 14 Nov '19

14 Nov '19

Michal Skrivanek created OVIRT-2834: --------------------------------------- Summary: please install zanata in our ovirt infra Key: OVIRT-2834 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2834 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Michal Skrivanek Assignee: infra for now decided to use our own instance, we'll move current translations to it once it's ready -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100114)

1 0

[JIRA] (OVIRT-2833) Please add msobczyk to vdsm maintainers
by Michal Skrivanek (oVirt JIRA) 14 Nov '19

14 Nov '19

Michal Skrivanek created OVIRT-2833: --------------------------------------- Summary: Please add msobczyk to vdsm maintainers Key: OVIRT-2833 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2833 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Michal Skrivanek Assignee: infra per devel(a)ovirt.org -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100114)

1 0

[JIRA] (OVIRT-2832) Add Fedora 31 support in the CI
by Nir Soffer (oVirt JIRA) 14 Nov '19

14 Nov '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2832?page=com.atlassian.jira.… ] Nir Soffer commented on OVIRT-2832: ----------------------------------- On Thu, Nov 14, 2019 at 9:24 AM Barak Korren (oVirt JIRA) <jira(a)ovirt-jira.atlassian.net> wrote: > > > [ https://ovirt-jira.atlassian.net/browse/OVIRT-2832?page=com.atlassian.jira.… ] > > Barak Korren commented on OVIRT-2832: > ------------------------------------- > > While we could make mock work, it'd be nicer if we could get help to move the new container-based backend forward so the upstream container image could be used directly instead. Will be even better, thanks! > > Add Fedora 31 support in the CI > > ------------------------------- > > > > Key: OVIRT-2832 > > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2832 > > Project: oVirt - virtualization made easy > > Issue Type: By-EMAIL > > Reporter: Nir Soffer > > Assignee: infra > > > > Vdsm want to support only Fedora 31 at this point. > > Having Fedora 31 available, we can simplify the code since we have > > same versions of lvm and other packages in Fedora 31 and RHEL 8. > > We need: > > - mirrors for fedora 31 repos > > - mock config for fedora 31 > > Thanks, > > Nir > > > > -- > This message was sent by Atlassian Jira > (v1001.0.0-SNAPSHOT#100114) > > Add Fedora 31 support in the CI > ------------------------------- > > Key: OVIRT-2832 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2832 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > Vdsm want to support only Fedora 31 at this point. > Having Fedora 31 available, we can simplify the code since we have > same versions of lvm and other packages in Fedora 31 and RHEL 8. > We need: > - mirrors for fedora 31 repos > - mock config for fedora 31 > Thanks, > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100114)

1 0

[JIRA] (OVIRT-2832) Add Fedora 31 support in the CI
by Barak Korren (oVirt JIRA) 14 Nov '19

14 Nov '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2832?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2832: ------------------------------------- While we could make mock work, it'd be nicer if we could get help to move the new container-based backend forward so the upstream container image could be used directly instead. > Add Fedora 31 support in the CI > ------------------------------- > > Key: OVIRT-2832 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2832 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > Vdsm want to support only Fedora 31 at this point. > Having Fedora 31 available, we can simplify the code since we have > same versions of lvm and other packages in Fedora 31 and RHEL 8. > We need: > - mirrors for fedora 31 repos > - mock config for fedora 31 > Thanks, > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100114)

2 1

[CQ]: 104169, 15 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 14 Nov '19

14 Nov '19

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

1 0

[CQ]: 104655,2 (ovirt-system-tests) failed "ovirt-4.3" system tests
by oVirt Jenkins 14 Nov '19

14 Nov '19

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

1 0

Build failed in Jenkins: system-sync_mirrors-epel-el7-s390x-x86_64 #11
by jenkins＠jenkins.phx.ovirt.org 14 Nov '19

14 Nov '19

See <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el7-s390x-x86_64/11/d…> Changes: ------------------------------------------ [...truncated 74.91 KB...] (9/173): python2-rosdistro 0% [ ] 22 kB/s | 729 kB 114:09 ETA python2-rosdistro-0.7.5-1.el7. FAILED (9/173): python2-rosdistro 0% [ ] 22 kB/s | 729 kB 114:09 ETA python2-scapy-2.4.3-2.el7.noar FAILED (9/173): python2-scapy-2.4 0% [ ] 22 kB/s | 729 kB 114:09 ETA python2-scapy-2.4.3-2.el7.noar FAILED (9/173): python2-scapy-2.4 0% [ ] 22 kB/s | 729 kB 114:09 ETA python2-vcstools-0.1.42-1.el7. FAILED (9/173): python2-vcstools- 0% [ ] 22 kB/s | 729 kB 114:09 ETA python2-vcstools-0.1.42-1.el7. FAILED (9/173): python2-vcstools- 0% [ ] 22 kB/s | 729 kB 114:09 ETA python2-wstool-0.1.18-1.el7.no FAILED (9/173): python2-wstool-0. 0% [ ] 22 kB/s | 729 kB 114:09 ETA python2-wstool-0.1.18-1.el7.no FAILED (9/173): python2-wstool-0. 0% [ ] 22 kB/s | 729 kB 114:09 ETA python3-other-rpm-macros-3-26. FAILED (9/173): python3-other-rpm 0% [ ] 22 kB/s | 729 kB 114:09 ETA python3-other-rpm-macros-3-26. FAILED (9/173): python3-other-rpm 0% [ ] 22 kB/s | 729 kB 114:09 ETA python36-argh-0.26.1-6.el7.noa FAILED (9/173): python36-argh-0.2 0% [ ] 22 kB/s | 729 kB 114:09 ETA python36-argh-0.26.1-6.el7.noa FAILED (9/173): python36-argh-0.2 0% [ ] 22 kB/s | 729 kB 114:09 ETA (9/173): python36-astroid- 0% [ ] 106 kB/s | 1.2 MB 23:08 ETA (9/173): python36-astroid-1.4.9-4.el7.noarch.rpm | 200 kB 00:00 python36-colcon-bash-0.4.1-1.e FAILED (10/173): python36-colcon- 0% [ ] 106 kB/s | 1.2 MB 23:08 ETA python36-colcon-bash-0.4.1-1.e FAILED (10/173): python36-colcon- 0% [ ] 106 kB/s | 1.2 MB 23:08 ETA python36-colcon-cmake-0.2.15-1 FAILED (10/173): python36-colcon- 0% [ ] 106 kB/s | 1.2 MB 23:08 ETA python36-colcon-cmake-0.2.15-1 FAILED (10/173): python36-colcon- 0% [ ] 106 kB/s | 1.2 MB 23:08 ETA python36-colcon-core-0.4.1-2.e FAILED (10/173): python36-colcon- 0% [ ] 106 kB/s | 1.2 MB 23:08 ETA python36-colcon-core-0.4.1-2.e FAILED (10/173): python36-colcon- 0% [ ] 106 kB/s | 1.2 MB 23:08 ETA python36-colcon-notification-0 FAILED (10/173): python36-colcon- 0% [ ] 106 kB/s | 1.2 MB 23:08 ETA python36-colcon-notification-0 FAILED (10/173): python36-colcon- 0% [ ] 106 kB/s | 1.2 MB 23:08 ETA python36-colcon-output-0.2.6-1 FAILED (10/173): python36-colcon- 0% [ ] 106 kB/s | 1.2 MB 23:08 ETA python36-colcon-output-0.2.6-1 FAILED (10/173): python36-colcon- 0% [ ] 106 kB/s | 1.2 MB 23:08 ETA python36-colcon-package-inform FAILED (10/173): python36-colcon- 0% [ ] 106 kB/s | 1.2 MB 23:08 ETA python36-colcon-package-inform FAILED (10/173): python36-colcon- 0% [ ] 106 kB/s | 1.2 MB 23:08 ETA python36-colcon-ros-0.3.13-1.e FAILED (10/173): python36-colcon- 0% [ ] 106 kB/s | 1.2 MB 23:08 ETA python36-colcon-ros-0.3.13-1.e FAILED (10/173): python36-colcon- 0% [ ] 106 kB/s | 1.2 MB 23:08 ETA python36-colcon-test-result-0. FAILED (10/173): python36-colcon- 0% [ ] 106 kB/s | 1.2 MB 23:08 ETA python36-colcon-test-result-0. FAILED (10/173): python36-colcon- 0% [ ] 106 kB/s | 1.2 MB 23:08 ETA python36-ecdsa-0.13.3-1.el7.no FAILED (10/173): python36-ecdsa-0 0% [ ] 106 kB/s | 1.2 MB 23:08 ETA python36-ecdsa-0.13.3-1.el7.no FAILED (10/173): python36-ecdsa-0 0% [ ] 106 kB/s | 1.2 MB 23:08 ETA python36-fedfind-4.2.8-1.el7.n FAILED (10/173): python36-fedfind 0% [ ] 106 kB/s | 1.2 MB 23:08 ETA python36-fedfind-4.2.8-1.el7.n FAILED (10/173): python36-fedfind 0% [ ] 106 kB/s | 1.2 MB 23:08 ETA python36-fmf-0.10-1.el7.noarch FAILED (10/173): python36-fmf-0.1 0% [ ] 106 kB/s | 1.2 MB 23:08 ETA python36-fmf-0.10-1.el7.noarch FAILED (10/173): python36-fmf-0.1 0% [ ] 106 kB/s | 1.2 MB 23:08 ETA python36-html5lib-0.999-7.el7. FAILED (10/173): python36-html5li 0% [ ] 106 kB/s | 1.2 MB 23:08 ETA python36-html5lib-0.999-7.el7. FAILED (10/173): python36-html5li 0% [ ] 106 kB/s | 1.2 MB 23:08 ETA python36-ldap3-2.6.1-1.el7.noa FAILED (10/173): python36-ldap3-2 0% [ ] 106 kB/s | 1.2 MB 23:08 ETA python36-ldap3-2.6.1-1.el7.noa FAILED (10/173): python36-ldap3-2 0% [ ] 106 kB/s | 1.2 MB 23:08 ETA python36-ns1-python-0.12.0-1.e FAILED (10/173): python36-ns1-pyt 0% [ ] 106 kB/s | 1.2 MB 23:08 ETA python36-ns1-python-0.12.0-1.e FAILED (10/173): python36-ns1-pyt 0% [ ] 106 kB/s | 1.2 MB 23:08 ETA python36-osrf-pycommon-0.1.8-1 FAILED (10/173): python36-osrf-py 0% [ ] 106 kB/s | 1.2 MB 23:08 ETA python36-osrf-pycommon-0.1.8-1 FAILED (10/173): python36-osrf-py 0% [ ] 106 kB/s | 1.2 MB 23:08 ETA python36-pathspec-0.6.0-1.el7. FAILED (10/173): python36-pathspe 0% [ ] 106 kB/s | 1.2 MB 23:08 ETA python36-pathspec-0.6.0-1.el7. FAILED (10/173): python36-pathspe 0% [ ] 106 kB/s | 1.2 MB 23:08 ETA python36-pluginlib-0.6.2-1.el7 FAILED (10/173): python36-pluginl 0% [ ] 106 kB/s | 1.2 MB 23:08 ETA python36-pluginlib-0.6.2-1.el7 FAILED (10/173): python36-pluginl 0% [ ] 106 kB/s | 1.2 MB 23:08 ETA (10/173): python36-pylint- 0% [ ] 39 kB/s | 1.3 MB 63:00 ETA (10/173): python36-pylint-1.6.5-7.el7.noarch.rpm | 437 kB 00:00 (11/173): python36-pylint-gui-1.6.5-7.el7.noarch.rpm | 23 kB 00:00 python36-rosdep-0.16.1-2.el7.n FAILED (12/173): python36-rosdep- 0% [ ] 39 kB/s | 1.3 MB 63:00 ETA python36-rosdep-0.16.1-2.el7.n FAILED (12/173): python36-rosdep- 0% [ ] 39 kB/s | 1.3 MB 63:00 ETA python36-rosdistro-0.7.5-1.el7 FAILED (12/173): python36-rosdist 0% [ ] 39 kB/s | 1.3 MB 63:00 ETA python36-rosdistro-0.7.5-1.el7 FAILED (12/173): python36-rosdist 0% [ ] 39 kB/s | 1.3 MB 63:00 ETA python36-scapy-2.4.3-2.el7.noa FAILED (12/173): python36-scapy-2 0% [ ] 39 kB/s | 1.3 MB 63:00 ETA python36-scapy-2.4.3-2.el7.noa FAILED (12/173): python36-scapy-2 0% [ ] 39 kB/s | 1.3 MB 63:00 ETA python36-vcstools-0.1.42-1.el7 FAILED (12/173): python36-vcstool 0% [ ] 39 kB/s | 1.3 MB 63:00 ETA python36-vcstools-0.1.42-1.el7 FAILED (12/173): python36-vcstool 0% [ ] 39 kB/s | 1.3 MB 63:00 ETA python36-wstool-0.1.18-1.el7.n FAILED (12/173): python36-wstool- 0% [ ] 39 kB/s | 1.3 MB 63:00 ETA python36-wstool-0.1.18-1.el7.n FAILED (12/173): python36-wstool- 0% [ ] 39 kB/s | 1.3 MB 63:00 ETA qpid-dispatch-console-1.9.0-1. FAILED (12/173): qpid-dispatch-co 0% [ ] 39 kB/s | 1.3 MB 63:00 ETA qpid-dispatch-console-1.9.0-1. FAILED (12/173): qpid-dispatch-co 0% [ ] 39 kB/s | 1.3 MB 63:00 ETA qpid-dispatch-docs-1.9.0-1.el7 FAILED (12/173): qpid-dispatch-do 0% [ ] 39 kB/s | 1.3 MB 63:00 ETA qpid-dispatch-docs-1.9.0-1.el7 FAILED (12/173): qpid-dispatch-do 0% [ ] 39 kB/s | 1.3 MB 63:00 ETA qpid-dispatch-tools-1.9.0-1.el FAILED (12/173): qpid-dispatch-to 0% [ ] 39 kB/s | 1.3 MB 63:00 ETA qpid-dispatch-tools-1.9.0-1.el FAILED (12/173): qpid-dispatch-to 0% [ ] 39 kB/s | 1.3 MB 63:00 ETA qpid-proton-c-docs-0.29.0-1.el FAILED (12/173): qpid-proton-c-do 0% [ ] 39 kB/s | 1.3 MB 63:00 ETA qpid-proton-c-docs-0.29.0-1.el FAILED (12/173): qpid-proton-c-do 0% [ ] 39 kB/s | 1.3 MB 63:00 ETA qpid-proton-cpp-docs-0.29.0-1. FAILED (12/173): qpid-proton-cpp- 0% [ ] 39 kB/s | 1.3 MB 63:00 ETA qpid-proton-cpp-docs-0.29.0-1. FAILED (12/173): qpid-proton-cpp- 0% [ ] 39 kB/s | 1.3 MB 63:00 ETA qpid-proton-tests-0.29.0-1.el7 FAILED (12/173): qpid-proton-test 0% [ ] 39 kB/s | 1.3 MB 63:00 ETA qpid-proton-tests-0.29.0-1.el7 FAILED (12/173): qpid-proton-test 0% [ ] 39 kB/s | 1.3 MB 63:00 ETA relval-2.4.8-1.el7.noarch.rpm FAILED (12/173): relval-2.4.8-1.e 0% [ ] 39 kB/s | 1.3 MB 63:00 ETA relval-2.4.8-1.el7.noarch.rpm FAILED (12/173): relval-2.4.8-1.e 0% [ ] 39 kB/s | 1.3 MB 63:00 ETA rubygem-qpid_proton-doc-0.29.0 FAILED (12/173): rubygem-qpid_pro 0% [ ] 39 kB/s | 1.3 MB 63:00 ETA rubygem-qpid_proton-doc-0.29.0 FAILED (12/173): rubygem-qpid_pro 0% [ ] 39 kB/s | 1.3 MB 63:00 ETA snapd-devel-2.42-2.el7.noarch. FAILED (12/173): snapd-devel-2.42 0% [ ] 39 kB/s | 1.3 MB 63:00 ETA snapd-devel-2.42-2.el7.noarch. FAILED (12/173): snapd-devel-2.42 0% [ ] 39 kB/s | 1.3 MB 63:00 ETA snapd-selinux-2.42-2.el7.noarc FAILED (12/173): snapd-selinux-2. 0% [ ] 39 kB/s | 1.3 MB 63:00 ETA snapd-selinux-2.42-2.el7.noarc FAILED (12/173): snapd-selinux-2. 0% [ ] 39 kB/s | 1.3 MB 63:00 ETA wordpress-5.1.3-1.el7.noarch.r FAILED (12/173): wordpress-5.1.3- 0% [ ] 39 kB/s | 1.3 MB 63:00 ETA wordpress-5.1.3-1.el7.noarch.r FAILED (12/173): wordpress-5.1.3- 0% [ ] 39 kB/s | 1.3 MB 63:00 ETA (12/173): xrootd-doc-4.11. 1% [ ] 88 kB/s | 1.8 MB 27:41 ETA (12/173): xrootd-doc-4.11. 1% [ ] 157 kB/s | 2.1 MB 15:29 ETA (12/173): xrootd-doc-4.11. 1% [ ] 257 kB/s | 2.7 MB 09:24 ETA (12/173): xrootd-doc-4.11. 2% [ ] 456 kB/s | 3.7 MB 05:15 ETA (12/173): xrootd-doc-4.11. 3% [- ] 824 kB/s | 5.7 MB 02:52 ETA (12/173): xrootd-doc-4.11. 7% [= ] 1.6 MB/s | 10 MB 01:21 ETA (12/173): xrootd-doc-4.11. 10% [=- ] 2.7 MB/s | 16 MB 00:48 ETA (12/173): xrootd-doc-4.11. 14% [== ] 3.7 MB/s | 22 MB 00:33 ETA (12/173): xrootd-doc-4.11. 19% [=== ] 4.7 MB/s | 28 MB 00:24 ETA (12/173): xrootd-doc-4.11. 23% [===- ] 5.5 MB/s | 33 MB 00:20 ETA (12/173): xrootd-doc-4.11. 26% [==== ] 6.1 MB/s | 38 MB 00:17 ETA (12/173): xrootd-doc-4.11. 29% [====- ] 6.6 MB/s | 43 MB 00:15 ETA (12/173): xrootd-doc-4.11. 32% [===== ] 7.1 MB/s | 47 MB 00:13 ETA (12/173): xrootd-doc-4.11. 35% [=====- ] 7.5 MB/s | 51 MB 00:12 ETA (12/173): xrootd-doc-4.11. 38% [====== ] 7.9 MB/s | 56 MB 00:11 ETA (12/173): xrootd-doc-4.11. 41% [======- ] 8.3 MB/s | 60 MB 00:10 ETA (12/173): xrootd-doc-4.11. 44% [======= ] 8.6 MB/s | 64 MB 00:09 ETA (12/173): xrootd-doc-4.11. 46% [======= ] 8.7 MB/s | 67 MB 00:08 ETA (12/173): xrootd-doc-4.11. 49% [=======- ] 8.9 MB/s | 71 MB 00:08 ETA (12/173): xrootd-doc-4.11. 50% [======== ] 8.2 MB/s | 73 MB 00:08 ETA (12/173): xrootd-doc-4.11.0-1.el7.noarch.rpm | 73 MB 00:07 (13/173): xrootd-selinux-4.11.0-1.el7.noarch.rpm | 26 kB 00:00 yamllint-1.18.0-1.el7.noarch.r FAILED (14/173): yamllint-1.18.0- 50% [======== ] 8.2 MB/s | 73 MB 00:08 ETA yamllint-1.18.0-1.el7.noarch.r FAILED (14/173): yamllint-1.18.0- 50% [======== ] 8.2 MB/s | 73 MB 00:08 ETA yara-doc-3.11.0-1.el7.noarch.r FAILED (14/173): yara-doc-3.11.0- 50% [======== ] 8.2 MB/s | 73 MB 00:08 ETA yara-doc-3.11.0-1.el7.noarch.r FAILED (14/173): yara-doc-3.11.0- 50% [======== ] 8.2 MB/s | 73 MB 00:08 ETA youtube-dl-2019.09.28-1.el7.no FAILED (14/173): youtube-dl-2019. 50% [======== ] 8.2 MB/s | 73 MB 00:08 ETA youtube-dl-2019.09.28-1.el7.no FAILED (14/173): youtube-dl-2019. 50% [======== ] 8.2 MB/s | 73 MB 00:08 ETA python2-certbot-dns-dnsmadeeasy-0.39.0-1.el7.noarch: [Errno 256] No more mirrors to try. python2-koji-cli-plugins-1.18.1-1.el7.noarch: [Errno 256] No more mirrors to try. koji-hub-plugins-1.18.1-1.el7.noarch: [Errno 256] No more mirrors to try. php-horde-Horde-Text-Diff-2.2.1-1.el7.noarch: [Errno 256] No more mirrors to try. golang-src-1.13.1-1.el7.noarch: [Errno 256] No more mirrors to try. mirrormanager2-0.11-1.el7.noarch: [Errno 256] No more mirrors to try. nordugrid-arc6-archery-manage-6.3.0-1.el7.noarch: [Errno 256] No more mirrors to try. python2-dns-lexicon+henet-3.3.4-2.el7.noarch: [Errno 256] No more mirrors to try. python2-fedfind-4.2.8-1.el7.noarch: [Errno 256] No more mirrors to try. qpid-dispatch-docs-1.9.0-1.el7.noarch: [Errno 256] No more mirrors to try. yara-doc-3.11.0-1.el7.noarch: [Errno 256] No more mirrors to try. relval-2.4.8-1.el7.noarch: [Errno 256] No more mirrors to try. python36-colcon-package-information-0.2.4-1.el7.noarch: [Errno 256] No more mirrors to try. python2-dns-lexicon+easyname-3.3.4-2.el7.noarch: [Errno 256] No more mirrors to try. python36-colcon-ros-0.3.13-1.el7.noarch: [Errno 256] No more mirrors to try. python2-dns-lexicon+route53-3.3.4-2.el7.noarch: [Errno 256] No more mirrors to try. koan-2.8.5-0.3.el7.noarch: [Errno 256] No more mirrors to try. koji-builder-plugins-1.18.1-1.el7.noarch: [Errno 256] No more mirrors to try. fmf-0.10-1.el7.noarch: [Errno 256] No more mirrors to try. qpid-dispatch-tools-1.9.0-1.el7.noarch: [Errno 256] No more mirrors to try. python2-rosdistro-0.7.5-1.el7.noarch: [Errno 256] No more mirrors to try. golang-docs-1.13.1-1.el7.noarch: [Errno 256] No more mirrors to try. python-rosdistro-doc-0.7.5-1.el7.noarch: [Errno 256] No more mirrors to try. koji-1.18.1-1.el7.noarch: [Errno 256] No more mirrors to try. python-qpid-proton-docs-0.29.0-1.el7.noarch: [Errno 256] No more mirrors to try. python2-ecdsa-0.13.3-1.el7.noarch: [Errno 256] No more mirrors to try. perl-Image-ExifTool-11.70-1.el7.noarch: [Errno 256] No more mirrors to try. koji-vm-1.18.1-1.el7.noarch: [Errno 256] No more mirrors to try. python2-apprise-0.8.1-1.el7.noarch: [Errno 256] No more mirrors to try. snapd-devel-2.42-2.el7.noarch: [Errno 256] No more mirrors to try. python36-ns1-python-0.12.0-1.el7.noarch: [Errno 256] No more mirrors to try. python2-wstool-0.1.18-1.el7.noarch: [Errno 256] No more mirrors to try. python36-argh-0.26.1-6.el7.noarch: [Errno 256] No more mirrors to try. yamllint-1.18.0-1.el7.noarch: [Errno 256] No more mirrors to try. perl-MCE-1.862-1.el7.noarch: [Errno 256] No more mirrors to try. qpid-proton-tests-0.29.0-1.el7.noarch: [Errno 256] No more mirrors to try. python2-rosdep-0.16.1-2.el7.noarch: [Errno 256] No more mirrors to try. nordugrid-arc-nagios-plugins-doc-2.0.0~rc2-1.el7.noarch: [Errno 256] No more mirrors to try. python-osrf-pycommon-doc-0.1.8-1.el7.noarch: [Errno 256] No more mirrors to try. python-copr-doc-1.98-1.el7.noarch: [Errno 256] No more mirrors to try. python2-scapy-2.4.3-2.el7.noarch: [Errno 256] No more mirrors to try. python2-ldap3-2.6.1-1.el7.noarch: [Errno 256] No more mirrors to try. pidgin-mattermost-1.2-6.20190826gite21f18c.el7.noarch: [Errno 256] No more mirrors to try. python36-pluginlib-0.6.2-1.el7.noarch: [Errno 256] No more mirrors to try. mock-1.4.20-1.el7.noarch: [Errno 256] No more mirrors to try. python2-dictdiffer-0.7.1-8.el7.noarch: [Errno 256] No more mirrors to try. dmlite-puppet-dpm-1.13.2-2.el7.noarch: [Errno 256] No more mirrors to try. koji-web-1.18.1-1.el7.noarch: [Errno 256] No more mirrors to try. nordugrid-arc6-nordugridmap-6.3.0-1.el7.noarch: [Errno 256] No more mirrors to try. python2-certbot-dns-ovh-0.39.0-1.el7.noarch: [Errno 256] No more mirrors to try. python36-colcon-output-0.2.6-1.el7.noarch: [Errno 256] No more mirrors to try. golang-misc-1.13.1-1.el7.noarch: [Errno 256] No more mirrors to try. python2-copr-1.98-1.el7.noarch: [Errno 256] No more mirrors to try. qpid-proton-c-docs-0.29.0-1.el7.noarch: [Errno 256] No more mirrors to try. snapd-selinux-2.42-2.el7.noarch: [Errno 256] No more mirrors to try. etckeeper-1.18.10-4.el7.noarch: [Errno 256] No more mirrors to try. python36-scapy-2.4.3-2.el7.noarch: [Errno 256] No more mirrors to try. mirrormanager2-client-0.11-1.el7.noarch: [Errno 256] No more mirrors to try. mirrormanager2-crawler-0.11-1.el7.noarch: [Errno 256] No more mirrors to try. gromacs-doc-2018.8-1.el7.noarch: [Errno 256] No more mirrors to try. apprise-0.8.1-1.el7.noarch: [Errno 256] No more mirrors to try. etckeeper-dnf-1.18.10-4.el7.noarch: [Errno 256] No more mirrors to try. python2-certbot-dns-route53-0.39.0-1.el7.noarch: [Errno 256] No more mirrors to try. kmodtool-1-37.el7.noarch: [Errno 256] No more mirrors to try. mirrormanager2-statistics-0.11-1.el7.noarch: [Errno 256] No more mirrors to try. koji-utils-1.18.1-1.el7.noarch: [Errno 256] No more mirrors to try. lxqt-themes-0.14.0-3.el7.noarch: [Errno 256] No more mirrors to try. python36-fmf-0.10-1.el7.noarch: [Errno 256] No more mirrors to try. python2-vcstools-0.1.42-1.el7.noarch: [Errno 256] No more mirrors to try. python36-rosdistro-0.7.5-1.el7.noarch: [Errno 256] No more mirrors to try. nordugrid-arc6-acix-scanner-6.3.0-1.el7.noarch: [Errno 256] No more mirrors to try. python36-pathspec-0.6.0-1.el7.noarch: [Errno 256] No more mirrors to try. wordpress-5.1.3-1.el7.noarch: [Errno 256] No more mirrors to try. openbox-theme-mistral-thin-0-6.20170125.el7.noarch: [Errno 256] No more mirrors to try. mirrormanager2-mirrorlist-0.11-1.el7.noarch: [Errno 256] No more mirrors to try. nordugrid-arc6-acix-index-6.3.0-1.el7.noarch: [Errno 256] No more mirrors to try. youtube-dl-2019.09.28-1.el7.noarch: [Errno 256] No more mirrors to try. python2-koji-1.18.1-1.el7.noarch: [Errno 256] No more mirrors to try. python36-colcon-test-result-0.3.8-1.el7.noarch: [Errno 256] No more mirrors to try. mock-lvm-1.4.20-1.el7.noarch: [Errno 256] No more mirrors to try. python36-rosdep-0.16.1-2.el7.noarch: [Errno 256] No more mirrors to try. koji-builder-1.18.1-1.el7.noarch: [Errno 256] No more mirrors to try. python2-kubernetes-9.0.1-1.el7.noarch: [Errno 256] No more mirrors to try. koji-hub-1.18.1-1.el7.noarch: [Errno 256] No more mirrors to try. python2-acme-0.39.0-1.el7.noarch: [Errno 256] No more mirrors to try. python2-pathspec-0.6.0-1.el7.noarch: [Errno 256] No more mirrors to try. etckeeper-bzr-1.18.10-4.el7.noarch: [Errno 256] No more mirrors to try. python2-certbot-dns-digitalocean-0.39.0-1.el7.noarch: [Errno 256] No more mirrors to try. python2-certbot-dns-gehirn-0.39.0-1.el7.noarch: [Errno 256] No more mirrors to try. rubygem-qpid_proton-doc-0.29.0-1.el7.noarch: [Errno 256] No more mirrors to try. python2-certbot-0.39.0-1.el7.noarch: [Errno 256] No more mirrors to try. python2-certbot-dns-cloudflare-0.39.0-1.el7.noarch: [Errno 256] No more mirrors to try. python36-colcon-core-0.4.1-2.el7.noarch: [Errno 256] No more mirrors to try. perl-MCE-tools-1.862-1.el7.noarch: [Errno 256] No more mirrors to try. python-paho-mqtt-1.4.0-1.el7.noarch: [Errno 256] No more mirrors to try. python-rosdep-doc-0.16.1-2.el7.noarch: [Errno 256] No more mirrors to try. mirrormanager2-backend-0.11-1.el7.noarch: [Errno 256] No more mirrors to try. 1:nginx-all-modules-1.16.1-1.el7.noarch: [Errno 256] No more mirrors to try. python2-certbot-apache-0.39.0-1.el7.noarch: [Errno 256] No more mirrors to try. python2-certbot-nginx-0.39.0-1.el7.noarch: [Errno 256] No more mirrors to try. python2-certbot-dns-dnsimple-0.39.0-1.el7.noarch: [Errno 256] No more mirrors to try. python2-dns-lexicon+gratisdns-3.3.4-2.el7.noarch: [Errno 256] No more mirrors to try. copr-cli-1.82-1.el7.noarch: [Errno 256] No more mirrors to try. nordugrid-arc-nagios-plugins-egi-2.0.0~rc2-1.el7.noarch: [Errno 256] No more mirrors to try. mock-core-configs-31.6-1.el7.noarch: [Errno 256] No more mirrors to try. python2-certbot-dns-sakuracloud-0.39.0-1.el7.noarch: [Errno 256] No more mirrors to try. gromacs-common-2018.8-1.el7.noarch: [Errno 256] No more mirrors to try. qpid-dispatch-console-1.9.0-1.el7.noarch: [Errno 256] No more mirrors to try. python2-certbot-dns-cloudxns-0.39.0-1.el7.noarch: [Errno 256] No more mirrors to try. golang-github-google-go-genproto-devel-0-0.3.git411e09b.el7.noarch: [Errno 256] No more mirrors to try. meson-0.47.2-2.el7.noarch: [Errno 256] No more mirrors to try. python2-certbot-dns-rfc2136-0.39.0-1.el7.noarch: [Errno 256] No more mirrors to try. mirrormanager2-lib-0.11-1.el7.noarch: [Errno 256] No more mirrors to try. python36-colcon-notification-0.2.10-1.el7.noarch: [Errno 256] No more mirrors to try. python2-koji-hub-1.18.1-1.el7.noarch: [Errno 256] No more mirrors to try. lxqt-build-tools-0.6.0-3.el7.noarch: [Errno 256] No more mirrors to try. python2-certbot-dns-luadns-0.39.0-1.el7.noarch: [Errno 256] No more mirrors to try. php-horde-Horde-Imap-Client-2.30.0-1.el7.noarch: [Errno 256] No more mirrors to try. 1:python2-openshift-0.9.2-1.el7.noarch: [Errno 256] No more mirrors to try. mock-scm-1.4.20-1.el7.noarch: [Errno 256] No more mirrors to try. python2-certbot-dns-linode-0.39.0-1.el7.noarch: [Errno 256] No more mirrors to try. python36-fedfind-4.2.8-1.el7.noarch: [Errno 256] No more mirrors to try. python2-kubernetes-tests-9.0.1-1.el7.noarch: [Errno 256] No more mirrors to try. did-0.13-1.el7.noarch: [Errno 256] No more mirrors to try. python2-argh-0.26.1-6.el7.noarch: [Errno 256] No more mirrors to try. qpid-proton-cpp-docs-0.29.0-1.el7.noarch: [Errno 256] No more mirrors to try. python2-dns-lexicon-3.3.4-2.el7.noarch: [Errno 256] No more mirrors to try. python36-ecdsa-0.13.3-1.el7.noarch: [Errno 256] No more mirrors to try. 1:python-html5lib-0.999-7.el7.noarch: [Errno 256] No more mirrors to try. akmods-0.5.6-23.el7.noarch: [Errno 256] No more mirrors to try. 1:python36-html5lib-0.999-7.el7.noarch: [Errno 256] No more mirrors to try. perl-Date-Holidays-DE-2.03-1.el7.noarch: [Errno 256] No more mirrors to try. python36-vcstools-0.1.42-1.el7.noarch: [Errno 256] No more mirrors to try. python36-colcon-bash-0.4.1-1.el7.noarch: [Errno 256] No more mirrors to try. git-publish-1.5.1-1.el7.noarch: [Errno 256] No more mirrors to try. python36-wstool-0.1.18-1.el7.noarch: [Errno 256] No more mirrors to try. python36-colcon-cmake-0.2.15-1.el7.noarch: [Errno 256] No more mirrors to try. nodejs-rhea-1.0.10-1.el7.noarch: [Errno 256] No more mirrors to try. python2-koji-web-1.18.1-1.el7.noarch: [Errno 256] No more mirrors to try. python2-pluginlib-0.6.2-1.el7.noarch: [Errno 256] No more mirrors to try. cobbler-web-2.8.5-0.3.el7.noarch: [Errno 256] No more mirrors to try. python2-certbot-dns-google-0.39.0-1.el7.noarch: [Errno 256] No more mirrors to try. nordugrid-arc6-infosys-ldap-6.3.0-1.el7.noarch: [Errno 256] No more mirrors to try. lxqt-themes-fedora-0.14.0-3.el7.noarch: [Errno 256] No more mirrors to try. python2-dns-lexicon+plesk-3.3.4-2.el7.noarch: [Errno 256] No more mirrors to try. certbot-0.39.0-1.el7.noarch: [Errno 256] No more mirrors to try. python36-osrf-pycommon-0.1.8-1.el7.noarch: [Errno 256] No more mirrors to try. python2-ns1-python-0.12.0-1.el7.noarch: [Errno 256] No more mirrors to try. python3-other-rpm-macros-3-26.el7.noarch: [Errno 256] No more mirrors to try. python2-certbot-dns-nsone-0.39.0-1.el7.noarch: [Errno 256] No more mirrors to try. python2-osrf-pycommon-0.1.8-1.el7.noarch: [Errno 256] No more mirrors to try. python2-koji-hub-plugins-1.18.1-1.el7.noarch: [Errno 256] No more mirrors to try. 1:nginx-filesystem-1.16.1-1.el7.noarch: [Errno 256] No more mirrors to try. fedfind-4.2.8-1.el7.noarch: [Errno 256] No more mirrors to try. fpaste-0.4.0.0-1.el7.noarch: [Errno 256] No more mirrors to try. python36-ldap3-2.6.1-1.el7.noarch: [Errno 256] No more mirrors to try. mirrormanager2-filesystem-0.11-1.el7.noarch: [Errno 256] No more mirrors to try. golang-tests-1.13.1-1.el7.noarch: [Errno 256] No more mirrors to try. nordugrid-arc6-acix-core-6.3.0-1.el7.noarch: [Errno 256] No more mirrors to try. nordugrid-arc6-monitor-6.3.0-1.el7.noarch: [Errno 256] No more mirrors to try. Build step 'Execute shell' marked build as failure

1 14

Container-based CI backend for oVirt
by Barak Korren 14 Nov '19

14 Nov '19

*What are we talking about exactly?* The CI team had been doing work over the last few weeks to create and enable a container-based CI backend that is usable as an alternative for the legacy VM-and-chroot backend we've been using so far. *Why?* 1. *You asked for it: *We've been approached by several developer teams asking for this kind of functionality 2. *Faster:* The new backend requires far less setup overhead then the legacy one, and therefore would allow jobs to start and finish faster 3. *More flexible: *The old backend allowed specifying build/test dependencies in terms of RPM packages, the container based one uses container images for this which are far more flexible 4. *More versatile:* There were some limits to what could be done reliably with chroots. The greater isolation provided by containers would provide better testing capabilities 5. *Less maintenance:* With the legacy backend, the CI team had to take the time and provide support for every new release of a target distribution, the new backend is designed to allow using upstream container images directly therefore letting developers use them as soon as they are released instead of having to wait for the CI team to provide support. *Tell me more!* A pending documentation update describing the new features and how to use them can be found here: - 104660 <https://gerrit.ovirt.org/104660>: Document the new STDCI containers syntax *Great! so can I use this now?* Unfortunately this is not yet enabled in production, while most of the functionality had already been developed and tested, code review efforts are still ongoing. If you'd like to help us move this along, please take the time and help reviewing the following patches: - 103937 <https://gerrit.ovirt.org/103937>: Adda an STDCI DSL option for using containers - 104066 <https://gerrit.ovirt.org/104066>: Add STDCI DSL `podspecs` pseudo option - 104164 <https://gerrit.ovirt.org/104164>: stdci_runner: Support container-based threads I'd like to thank @Marcin Sobczyk <msobczyk(a)redhat.com> and @Miguel Duarte de Mora Barroso <mdbarroso(a)redhat.com> for helping with the review effort so far, further work is needed as changes had been made following the reviews. *Hey, it's nice and all, but I think you forgot to make it do X* Hold on! we are not done yet! While we want to put an initial set of features in the hands of developers as soon as possible, work is already under way to provide more functionality. To check out what is coming down the line (And perhaps help it along), please have a look at the following patches: - 104668 <https://gerrit.ovirt.org/104668>: Document source cloning extension for containers - 104213 <https://gerrit.ovirt.org/104213>: Implement STDCI DSL support for initContainers - 104590 <https://gerrit.ovirt.org/104590>: STDCI DSL: Add the `decorate` option - 104273 <https://gerrit.ovirt.org/104273>: STDCI PODS: Unique UID for each job build's POD -- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted

1 0

[oVirt Jenkins] deploy-to-gated-ovirt-4.3 - Build #25 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 14 Nov '19

14 Nov '19

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

1 0

[CQ]: 104489, 4 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 14 Nov '19

14 Nov '19

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

1 0

[CQ]: 104522,3 (ovirt-system-tests) failed "ovirt-4.3" system tests
by oVirt Jenkins 14 Nov '19

14 Nov '19

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

1 0

[oVirt Jenkins] deploy-to-gated-ovirt-master - Build #19 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 14 Nov '19

14 Nov '19

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

1 0

[CQ]: 103943, 17 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 13 Nov '19

13 Nov '19

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

1 0

oVirt infra daily report - unstable production jobs - 1008
by jenkins＠jenkins.phx.ovirt.org 13 Nov '19

13 Nov '19

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

1 0

[CQ]: 104499, 2 (ovirt-system-tests) failed "ovirt-master" system tests
by oVirt Jenkins 13 Nov '19

13 Nov '19

Change 104499,2 (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/104499/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/16889/

1 0

[JIRA] (OVIRT-2827) Building vdsm with standard-manual-runner fails to clone the repo
by Nir Soffer (oVirt JIRA) 13 Nov '19

13 Nov '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2827?page=com.atlassian.jira.… ] Nir Soffer commented on OVIRT-2827: ----------------------------------- On Tue, Nov 12, 2019 at 5:48 PM Nir Soffer (oVirt JIRA) <jira(a)ovirt-jira.atlassian.net> wrote: > > Nir Soffer created OVIRT-2827: > --------------------------------- > > Summary: Building vdsm with standard-manual-runner fails to clone the repo > Key: OVIRT-2827 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2827 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > > Building vdsm using standard-manual-runner fails now with: > > ERROR: Error cloning remote repo 'origin' > > hudson.plugins.git.GitException: Command "git fetch --tags --progress > https://gerrit.ovirt.org/jenkins +refs/heads/*:refs/remotes/origin/*" > returned status code 128: > stdout: > stderr: error: RPC failed; result=22, HTTP code = 503 > fatal: The remote end hung up unexpectedly > > https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… > https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… > > Can someone look into this? Few hours later running the same builds worked, so this must have been a temporary issue. Would be nice to understand what was the issue if possible. > Building vdsm with standard-manual-runner fails to clone the repo > ----------------------------------------------------------------- > > Key: OVIRT-2827 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2827 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > Building vdsm using standard-manual-runner fails now with: > ERROR: Error cloning remote repo 'origin' > hudson.plugins.git.GitException: Command "git fetch --tags --progress > https://gerrit.ovirt.org/jenkins +refs/heads/*:refs/remotes/origin/*" > returned status code 128: > stdout: > stderr: error: RPC failed; result=22, HTTP code = 503 > fatal: The remote end hung up unexpectedly > https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… > https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… > Can someone look into this? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100114)

1 0

[JIRA] (OVIRT-2827) Building vdsm with standard-manual-runner fails to clone the repo
by Nir Soffer (oVirt JIRA) 13 Nov '19

13 Nov '19

Nir Soffer created OVIRT-2827: --------------------------------- Summary: Building vdsm with standard-manual-runner fails to clone the repo Key: OVIRT-2827 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2827 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Nir Soffer Assignee: infra Building vdsm using standard-manual-runner fails now with: ERROR: Error cloning remote repo 'origin' hudson.plugins.git.GitException: Command "git fetch --tags --progress https://gerrit.ovirt.org/jenkins +refs/heads/*:refs/remotes/origin/*" returned status code 128: stdout: stderr: error: RPC failed; result=22, HTTP code = 503 fatal: The remote end hung up unexpectedly https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… Can someone look into this? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100114)

2 1

[JIRA] (OVIRT-2832) Add Fedora 31 support in the CI
by Nir Soffer (oVirt JIRA) 13 Nov '19

13 Nov '19

Nir Soffer created OVIRT-2832: --------------------------------- Summary: Add Fedora 31 support in the CI Key: OVIRT-2832 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2832 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Nir Soffer Assignee: infra Vdsm want to support only Fedora 31 at this point. Having Fedora 31 available, we can simplify the code since we have same versions of lvm and other packages in Fedora 31 and RHEL 8. We need: - mirrors for fedora 31 repos - mock config for fedora 31 Thanks, Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100114)

1 0

Build failed in Jenkins: system-sync_mirrors-centos-base-el7-x86_64 #3157
by jenkins＠jenkins.phx.ovirt.org 13 Nov '19

13 Nov '19

See <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-base-el7-x86_64/315…> Changes: ------------------------------------------ Started by timer Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-base-el7-x86_64/ws/> No credentials specified > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -fdx # timeout=10 Pruning obsolete local branches Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git > git --version # timeout=10 > git fetch --tags --progress --prune http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* ERROR: Error fetching remote repo 'origin' hudson.plugins.git.GitException: Failed to fetch from http://gerrit.ovirt.org/jenkins.git at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:894) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1161) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1192) at hudson.scm.SCM.checkout(SCM.java:504) at hudson.model.AbstractProject.checkout(AbstractProject.java:1208) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499) at hudson.model.Run.execute(Run.java:1815) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) Caused by: hudson.plugins.git.GitException: Command "git fetch --tags --progress --prune http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/*" returned status code 128: stdout: stderr: error: RPC failed; result=22, HTTP code = 503 fatal: The remote end hung up unexpectedly at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2172) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1864) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$500(CliGitAPIImpl.java:78) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:545) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:153) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:146) at hudson.remoting.UserRequest.perform(UserRequest.java:212) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:369) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to mirrors.phx.ovirt.org at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1743) at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357) at hudson.remoting.Channel.call(Channel.java:957) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:146) at sun.reflect.GeneratedMethodAccessor458.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:132) at com.sun.proxy.$Proxy85.execute(Unknown Source) at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:892) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1161) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1192) at hudson.scm.SCM.checkout(SCM.java:504) at hudson.model.AbstractProject.checkout(AbstractProject.java:1208) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499) at hudson.model.Run.execute(Run.java:1815) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) ERROR: Error fetching remote repo 'origin'

1 1

[JIRA] (OVIRT-2831) cloning of jenkins repo fails with 503: remote hung up unexpectedly
by Dusan Fodor (oVirt JIRA) 13 Nov '19

13 Nov '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2831?page=com.atlassian.jira.… ] Dusan Fodor reassigned OVIRT-2831: ---------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > cloning of jenkins repo fails with 503: remote hung up unexpectedly > ------------------------------------------------------------------- > > Key: OVIRT-2831 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2831 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dusan Fodor > Assignee: Evgheni Dereveanchin > > https://jenkins.ovirt.org/job/standard-manual-runner/830/console > ??~Cloning repository https://gerrit.ovirt.org/jenkins > > git init /home/jenkins/agent/workspace/standard-manual-runner/jenkins # timeout=10 > Fetching upstream changes from https://gerrit.ovirt.org/jenkins > > git --version # timeout=10 > > git fetch --tags --progress https://gerrit.ovirt.org/jenkins +refs/heads/*:refs/remotes/origin/* # timeout=20 > ERROR: Error cloning remote repo 'origin' > hudson.plugins.git.GitException: Command "git fetch --tags --progress https://gerrit.ovirt.org/jenkins +refs/heads/*:refs/remotes/origin/*" returned status code 128: > stdout: > stderr: error: RPC failed; result=22, HTTP code = 503 > fatal: The remote end hung up unexpectedly > at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2172) > ....~?? > It happened around Nov 12 16:24:23 > Can you please check this? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100114)

1 0

[JIRA] (OVIRT-2831) cloning of jenkins repo fails with 503: remote hung up unexpectedly
by Dusan Fodor (oVirt JIRA) 13 Nov '19

13 Nov '19

Dusan Fodor created OVIRT-2831: ---------------------------------- Summary: cloning of jenkins repo fails with 503: remote hung up unexpectedly Key: OVIRT-2831 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2831 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Dusan Fodor Assignee: infra https://jenkins.ovirt.org/job/standard-manual-runner/830/console ??~Cloning repository https://gerrit.ovirt.org/jenkins > git init /home/jenkins/agent/workspace/standard-manual-runner/jenkins # timeout=10 Fetching upstream changes from https://gerrit.ovirt.org/jenkins > git --version # timeout=10 > git fetch --tags --progress https://gerrit.ovirt.org/jenkins +refs/heads/*:refs/remotes/origin/* # timeout=20 ERROR: Error cloning remote repo 'origin' hudson.plugins.git.GitException: Command "git fetch --tags --progress https://gerrit.ovirt.org/jenkins +refs/heads/*:refs/remotes/origin/*" returned status code 128: stdout: stderr: error: RPC failed; result=22, HTTP code = 503 fatal: The remote end hung up unexpectedly at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2172) ....~?? It happened around Nov 12 16:24:23 Can you please check this? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100114)

1 0

[CQ]: 104572, 2 (imgbased) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 13 Nov '19

13 Nov '19

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

1 0

[JIRA] (OVIRT-2830) Create an infra user for Krapali
by Evgheni Dereveanchin (oVirt JIRA) 13 Nov '19

13 Nov '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2830?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-2830: ------------------------------------------- Assignee: Krapali Rai (was: infra) > Create an infra user for Krapali > -------------------------------- > > Key: OVIRT-2830 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2830 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Evgheni Dereveanchin > Assignee: Krapali Rai > > Krapali is the new team member so an infra user needs to be created -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100114)

1 0

[JIRA] (OVIRT-2830) Create an infra user for Krapali
by Evgheni Dereveanchin (oVirt JIRA) 13 Nov '19

13 Nov '19

Evgheni Dereveanchin created OVIRT-2830: ------------------------------------------- Summary: Create an infra user for Krapali Key: OVIRT-2830 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2830 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Evgheni Dereveanchin Assignee: infra Krapali is the new team member so an infra user needs to be created -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100114)

1 0

[JIRA] (OST-137) OST: test for host being in up state should have retries
by Anton Marchukov (oVirt JIRA) 13 Nov '19

13 Nov '19

[ https://ovirt-jira.atlassian.net/browse/OST-137?page=com.atlassian.jira.plu… ] Anton Marchukov reassigned OST-137: ----------------------------------- Assignee: Anton Marchukov (was: infra) > OST: test for host being in up state should have retries > -------------------------------------------------------- > > Key: OST-137 > URL: https://ovirt-jira.atlassian.net/browse/OST-137 > Project: oVirt system tests > Issue Type: Bug > Reporter: Dusan Fodor > Assignee: Anton Marchukov > > When host goes up after installation, it first goes up, then it falls back into (iirc) unknown state, then it goes up for good. > This confuses multiple tests that require host to be up (e.g. add storage domain), which wait for at least one host being up, and when they get past the condition, meanwhile host falls back to the unknown state, so following operation which requires host to be up fails. Then it tries fencing, but it cannot start fencing since there is no up host at the moment, which issues more errors... > It's same pattern in all such failure, i will paste console output & link to job next time i'll see this. > The resolution would be to wait if the host is REALLY up, so e.g. ask if it's up, wait a bit, ask again and if it's up both times, continue with operation. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100114)

1 0

[JIRA] (OST-137) OST: test for host being in up state should have retries
by Dusan Fodor (oVirt JIRA) 13 Nov '19

13 Nov '19

[ https://ovirt-jira.atlassian.net/browse/OST-137?page=com.atlassian.jira.plu… ] Dusan Fodor moved OVIRT-2821 to OST-137: ---------------------------------------- Components: (was: OST) Project: oVirt system tests (was: oVirt - virtualization made easy) Workflow: Workflow for Project OST (was: Task Management Workflow) Key: OST-137 (was: OVIRT-2821) > OST: test for host being in up state should have retries > -------------------------------------------------------- > > Key: OST-137 > URL: https://ovirt-jira.atlassian.net/browse/OST-137 > Project: oVirt system tests > Issue Type: Bug > Reporter: Dusan Fodor > Assignee: infra > > When host goes up after installation, it first goes up, then it falls back into (iirc) unknown state, then it goes up for good. > This confuses multiple tests that require host to be up (e.g. add storage domain), which wait for at least one host being up, and when they get past the condition, meanwhile host falls back to the unknown state, so following operation which requires host to be up fails. Then it tries fencing, but it cannot start fencing since there is no up host at the moment, which issues more errors... > It's same pattern in all such failure, i will paste console output & link to job next time i'll see this. > The resolution would be to wait if the host is REALLY up, so e.g. ask if it's up, wait a bit, ask again and if it's up both times, continue with operation. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100114)

1 0

[CQ]: 104534, 2 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 13 Nov '19

13 Nov '19

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

1 0

[CQ]: 6ef3445 (ovirt-ansible-vm-infra) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 13 Nov '19

13 Nov '19

A system test invoked by the "ovirt-4.3" change queue including change 6ef3445 (ovirt-ansible-vm-infra) failed. However, this change seems not to be the root cause for this failure. Change 4e4aca6 (ovirt-ansible-vm-infra) 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 4e4aca6 (ovirt-ansible-vm- infra) 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://github.com/oVirt/ovirt-ansible-vm-infra/commit/6ef34455c9ca61088419… For further details about the change that seems to be the root cause behind the testing failures see: https://github.com/oVirt/ovirt-ansible-vm-infra/commit/4e4aca6f3c3b2f124da9… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/2454/

1 0

[CQ]: 4aa656b (ovirt-ansible-vm-infra) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 13 Nov '19

13 Nov '19

A system test invoked by the "ovirt-4.3" change queue including change 4aa656b (ovirt-ansible-vm-infra) failed. However, this change seems not to be the root cause for this failure. Change 4e4aca6 (ovirt-ansible-vm-infra) 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 4e4aca6 (ovirt-ansible-vm- infra) 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://github.com/oVirt/ovirt-ansible-vm-infra/commit/4aa656b17752ff4feed9… For further details about the change that seems to be the root cause behind the testing failures see: https://github.com/oVirt/ovirt-ansible-vm-infra/commit/4e4aca6f3c3b2f124da9… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/2452/

1 0

[JIRA] (OVIRT-2829) gmail can't verify emails sent from ovirt.org
by Anton Marchukov (oVirt JIRA) 13 Nov '19

13 Nov '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2829?page=com.atlassian.jira.… ] Anton Marchukov reassigned OVIRT-2829: -------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > gmail can't verify emails sent from ovirt.org > --------------------------------------------- > > Key: OVIRT-2829 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2829 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Emil Natan > Assignee: Evgheni Dereveanchin > > It seems like something that started in the last few days, I see Gmail > marks email sent from gerrit.ovirt.org with "?" saying it could not verify > the emails are sent from ovirt.org domain. It could be related to bad SPF > record. > From the email header: Received-SPF: softfail (google.com: domain of > transitioning gerrit(a)ovirt.org does not designate 66.187.233.88 as > permitted sender) client-ip=66.187.233.88; > -- > Emil Natan > RHV/CNV DevOps -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100114)

1 0

[JIRA] (OVIRT-2829) gmail can't verify emails sent from ovirt.org
by Emil Natan (oVirt JIRA) 13 Nov '19

13 Nov '19

Emil Natan created OVIRT-2829: --------------------------------- Summary: gmail can't verify emails sent from ovirt.org Key: OVIRT-2829 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2829 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Emil Natan Assignee: infra It seems like something that started in the last few days, I see Gmail marks email sent from gerrit.ovirt.org with "?" saying it could not verify the emails are sent from ovirt.org domain. It could be related to bad SPF record. From the email header: Received-SPF: softfail (google.com: domain of transitioning gerrit(a)ovirt.org does not designate 66.187.233.88 as permitted sender) client-ip=66.187.233.88; -- Emil Natan RHV/CNV DevOps -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100114)

1 0

[CQ]: 104579,2 (ovirt-release) failed "ovirt-master" system tests
by oVirt Jenkins 13 Nov '19

13 Nov '19

Change 104579,2 (ovirt-release) 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/104579/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/16873/

1 0

[CQ]: 104196, 6 (ovirt-engine-api-model) failed "ovirt-master" system tests
by oVirt Jenkins 12 Nov '19

12 Nov '19

Change 104196,6 (ovirt-engine-api-model) 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/104196/6 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/16868/

1 0

Build failed in Jenkins: system-sync_mirrors-fedora-updates-fc29-x86_64 #1105
by jenkins＠jenkins.phx.ovirt.org 12 Nov '19

12 Nov '19

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

1 1

oVirt infra daily report - unstable production jobs - 1007
by jenkins＠jenkins.phx.ovirt.org 12 Nov '19

12 Nov '19

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

1 0