- Infra - oVirt List Archives

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

31 Jan '19

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

1 0

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

31 Jan '19

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

1 0

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

31 Jan '19

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

1 0

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

31 Jan '19

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

1 0

[CQ]: 97391,4 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 31 Jan '19

31 Jan '19

Change 97391,4 (vdsm) 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/97391/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12609/

1 0

[JIRA] (OVIRT-2665) certbot broken on engine-phx
by Evgheni Dereveanchin (oVirt JIRA) 31 Jan '19

31 Jan '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2665?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-2665: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > certbot broken on engine-phx > ---------------------------- > > Key: OVIRT-2665 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2665 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > > The PHX engine has a Let'sEncrypt certificate deployed and uses certbot to renew it. > Currently it's broken and displaying a missing requirement for cryptography: > pkg_resources.ContextualVersionConflict: (cryptography 1.7.2 (/usr/lib64/python2.7/site-packages), Requirement.parse('cryptography>=1.9'), set(['PyOpenSSL']) -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2665) certbot broken on engine-phx
by Evgheni Dereveanchin (oVirt JIRA) 31 Jan '19

31 Jan '19

Evgheni Dereveanchin created OVIRT-2665: ------------------------------------------- Summary: certbot broken on engine-phx Key: OVIRT-2665 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2665 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Evgheni Dereveanchin Assignee: infra The PHX engine has a Let'sEncrypt certificate deployed and uses certbot to renew it. Currently it's broken and displaying a missing requirement for cryptography: pkg_resources.ContextualVersionConflict: (cryptography 1.7.2 (/usr/lib64/python2.7/site-packages), Requirement.parse('cryptography>=1.9'), set(['PyOpenSSL']) -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2664) OST runs engine 4.2 by default, misleading developers
by Eyal Edri (oVirt JIRA) 31 Jan '19

31 Jan '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2664?page=com.atlassian.jira.… ] Eyal Edri updated OVIRT-2664: ----------------------------- Resolution: Fixed Status: Done (was: To Do) > OST runs engine 4.2 by default, misleading developers > ----------------------------------------------------- > > Key: OVIRT-2664 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2664 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > When creating OST manual job, the UI select engine version 4.2 by default: > https://jenkins.ovirt.org/job/ovirt-system-tests_manual/build?delay=0sec > A developer that want to test engine master must change the version > manually. > I you forget to change the version, or just do not notice that there is > engine > version to choose, your job may succeed when it actually fail with engine > master. > Watching other developers start OST jobs, they do not notice that engine > version must be selected, and treat it as the other options that most people > do not care about. > This is probably the reason why OST was broken for a week, and nobody > complained about it, since default build used engine 4.2. > How to fix: > - The UI must be changed to require engine version selection. You cannot > have default for this. > The UI should show something like: > ENGINE_VERSION: [select version] *required > - The "Build" button must be disabled if no version was selected. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2664) OST runs engine 4.2 by default, misleading developers
by Eyal Edri (oVirt JIRA) 31 Jan '19

31 Jan '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2664?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2664: ---------------------------------- I'm not sure I agree with the reason for not finding regressions due to the job, the failure was reported on rhev-devel list, with specific relevant people in the 'to' field, including you Nir, on the 23/1. Also, developers are often capable and mindful people and should be aware which version they are testing, regardless of the default values. The default is usually set for the last stable release, hence it was 4.2, I agree it should be the master if its much more common now ( probably 4.3 more relevant once its out ). I sent a patch to update the default to 'master' https://gerrit.ovirt.org/#/c/97451/1/jobs/confs/yaml/parmeters/ost-version-… > OST runs engine 4.2 by default, misleading developers > ----------------------------------------------------- > > Key: OVIRT-2664 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2664 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > When creating OST manual job, the UI select engine version 4.2 by default: > https://jenkins.ovirt.org/job/ovirt-system-tests_manual/build?delay=0sec > A developer that want to test engine master must change the version > manually. > I you forget to change the version, or just do not notice that there is > engine > version to choose, your job may succeed when it actually fail with engine > master. > Watching other developers start OST jobs, they do not notice that engine > version must be selected, and treat it as the other options that most people > do not care about. > This is probably the reason why OST was broken for a week, and nobody > complained about it, since default build used engine 4.2. > How to fix: > - The UI must be changed to require engine version selection. You cannot > have default for this. > The UI should show something like: > ENGINE_VERSION: [select version] *required > - The "Build" button must be disabled if no version was selected. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

Error in SeaBIOS
by LIONS TECNOLOGIA 31 Jan '19

31 Jan '19

Good night! I would like to have a help, I am starting this journey in virtualization and I am having difficulty, I installed the ovirt but when I install a virtual machine to test, it happens that it is black screen as described in the attachment. Anyone who has a little more experience could help?

2 1

[CQ]: 96998, 16 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 31 Jan '19

31 Jan '19

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

1 0

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

31 Jan '19

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

1 0

[JIRA] (OVIRT-2664) OST runs engine 4.2 by default, misleading developers
by Nir Soffer (oVirt JIRA) 30 Jan '19

30 Jan '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2664?page=com.atlassian.jira.… ] Nir Soffer commented on OVIRT-2664: ----------------------------------- On Wed, Jan 30, 2019 at 9:45 PM Dan Kenigsberg <danken(a)redhat.com> wrote: > On Wed, Jan 30, 2019 at 8:55 PM Nir Soffer <nsoffer(a)redhat.com> wrote: > > > > When creating OST manual job, the UI select engine version 4.2 by > default: > > https://jenkins.ovirt.org/job/ovirt-system-tests_manual/build?delay=0sec > > > > A developer that want to test engine master must change the version > manually. > > > > I you forget to change the version, or just do not notice that there is > engine > > version to choose, your job may succeed when it actually fail with > engine master. > > > > Watching other developers start OST jobs, they do not notice that engine > > version must be selected, and treat it as the other options that most > people > > do not care about. > > > > This is probably the reason why OST was broken for a week, and nobody > > complained about it, since default build used engine 4.2. > > "nobody" is an underestimating diminutive for an esteemed group > including Dafna, Raz, Eyal and myself, just to name a few. > Complaining in private mailing list does not count :-) > > > > How to fix: > > > > - The UI must be changed to require engine version selection. You cannot > > have default for this. > > > > The UI should show something like: > > > > ENGINE_VERSION: [select version] *required > > > > - The "Build" button must be disabled if no version was selected. > > I'm not sure about it, as I hate input validation. Regardless, I think > it is time to make master the default for the manual job. > This is better then the current default, but the best is no default. Nir > OST runs engine 4.2 by default, misleading developers > ----------------------------------------------------- > > Key: OVIRT-2664 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2664 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > When creating OST manual job, the UI select engine version 4.2 by default: > https://jenkins.ovirt.org/job/ovirt-system-tests_manual/build?delay=0sec > A developer that want to test engine master must change the version > manually. > I you forget to change the version, or just do not notice that there is > engine > version to choose, your job may succeed when it actually fail with engine > master. > Watching other developers start OST jobs, they do not notice that engine > version must be selected, and treat it as the other options that most people > do not care about. > This is probably the reason why OST was broken for a week, and nobody > complained about it, since default build used engine 4.2. > How to fix: > - The UI must be changed to require engine version selection. You cannot > have default for this. > The UI should show something like: > ENGINE_VERSION: [select version] *required > - The "Build" button must be disabled if no version was selected. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2664) OST runs engine 4.2 by default, misleading developers
by danken (oVirt JIRA) 30 Jan '19

30 Jan '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2664?page=com.atlassian.jira.… ] danken commented on OVIRT-2664: ------------------------------- On Wed, Jan 30, 2019 at 8:55 PM Nir Soffer <nsoffer(a)redhat.com> wrote: > > When creating OST manual job, the UI select engine version 4.2 by default: > https://jenkins.ovirt.org/job/ovirt-system-tests_manual/build?delay=0sec > > A developer that want to test engine master must change the version manually. > > I you forget to change the version, or just do not notice that there is engine > version to choose, your job may succeed when it actually fail with engine master. > > Watching other developers start OST jobs, they do not notice that engine > version must be selected, and treat it as the other options that most people > do not care about. > > This is probably the reason why OST was broken for a week, and nobody > complained about it, since default build used engine 4.2. "nobody" is an underestimating diminutive for an esteemed group including Dafna, Raz, Eyal and myself, just to name a few. > > How to fix: > > - The UI must be changed to require engine version selection. You cannot > have default for this. > > The UI should show something like: > > ENGINE_VERSION: [select version] *required > > - The "Build" button must be disabled if no version was selected. I'm not sure about it, as I hate input validation. Regardless, I think it is time to make master the default for the manual job. > OST runs engine 4.2 by default, misleading developers > ----------------------------------------------------- > > Key: OVIRT-2664 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2664 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > When creating OST manual job, the UI select engine version 4.2 by default: > https://jenkins.ovirt.org/job/ovirt-system-tests_manual/build?delay=0sec > A developer that want to test engine master must change the version > manually. > I you forget to change the version, or just do not notice that there is > engine > version to choose, your job may succeed when it actually fail with engine > master. > Watching other developers start OST jobs, they do not notice that engine > version must be selected, and treat it as the other options that most people > do not care about. > This is probably the reason why OST was broken for a week, and nobody > complained about it, since default build used engine 4.2. > How to fix: > - The UI must be changed to require engine version selection. You cannot > have default for this. > The UI should show something like: > ENGINE_VERSION: [select version] *required > - The "Build" button must be disabled if no version was selected. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2664) OST runs engine 4.2 by default, misleading developers
by Nir Soffer (oVirt JIRA) 30 Jan '19

30 Jan '19

Nir Soffer created OVIRT-2664: --------------------------------- Summary: OST runs engine 4.2 by default, misleading developers Key: OVIRT-2664 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2664 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Nir Soffer Assignee: infra When creating OST manual job, the UI select engine version 4.2 by default: https://jenkins.ovirt.org/job/ovirt-system-tests_manual/build?delay=0sec A developer that want to test engine master must change the version manually. I you forget to change the version, or just do not notice that there is engine version to choose, your job may succeed when it actually fail with engine master. Watching other developers start OST jobs, they do not notice that engine version must be selected, and treat it as the other options that most people do not care about. This is probably the reason why OST was broken for a week, and nobody complained about it, since default build used engine 4.2. How to fix: - The UI must be changed to require engine version selection. You cannot have default for this. The UI should show something like: ENGINE_VERSION: [select version] *required - The "Build" button must be disabled if no version was selected. Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

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

30 Jan '19

See <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-qemu-ev-release-el7…> Changes: [Evgheni Dereveanchin] build Node-NG on VMs with large disk ------------------------------------------ Started by timer [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-qemu-ev-release-el7…> > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -fdx # timeout=10 Pruning obsolete local branches Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git > git --version # timeout=10 > git fetch --tags --progress http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* --prune > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision c2610aa1fe9955226708b5409dfb4802589f96f1 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f c2610aa1fe9955226708b5409dfb4802589f96f1 Commit message: "build Node-NG on VMs with large disk" > git rev-list --no-walk 4d05c05300de853cdd490429b87b43500708d8df # timeout=10 [system-sync_mirrors-centos-qemu-ev-release-el7-x86_64] $ /bin/bash -xe /tmp/jenkins686504261008634855.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 (2/4): qemu-kvm-common-ev- 0% [ ] 0.0 B/s | 0 B --:-- ETA qemu-kvm-common-ev-2.12.0-18.e FAILED (2/4): qemu-kvm-common-ev- 0% [ ] 0.0 B/s | 0 B --:-- ETA qemu-kvm-ev-2.12.0-18.el7_6.3. FAILED (2/4): qemu-kvm-ev-2.12.0- 0% [ ] 0.0 B/s | 0 B --:-- ETA (1/4): qemu-img-ev-2.12.0-18.el7_6.3.1.x86_64.rpm | 1.3 MB 00:00 (2/4): qemu-kvm-tools-ev-2.12.0-18.el7_6.3.1.x86_64.rpm | 518 kB 00:00 10:qemu-kvm-ev-2.12.0-18.el7_6.3.1.x86_64: [Errno 256] No more mirrors to try. 10:qemu-kvm-common-ev-2.12.0-18.el7_6.3.1.x86_64: [Errno 256] No more mirrors to try. Removing qemu-kvm-common-ev-2.12.0-18.el7_6.3.1.x86_64.rpm due to failed signature check. Removing qemu-kvm-ev-2.12.0-18.el7_6.3.1.x86_64.rpm due to failed signature check. Build step 'Execute shell' marked build as failure

1 1

TAISTE: Hyperkitty and Unicode
by Marc Dequènes (Duck) 30 Jan '19

30 Jan '19

Quack, This is a test! 日本語を分かりますか？ \_o<

1 0

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

30 Jan '19

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

1 0

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

30 Jan '19

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

1 0

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

30 Jan '19

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

1 0

[CQ]: 97109, 12 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 30 Jan '19

30 Jan '19

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

1 0

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

30 Jan '19

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

1 0

[JIRA] (OVIRT-2663) Please add ManageIQ Hammer-1 to glance repository
by sbonazzo (oVirt JIRA) 30 Jan '19

30 Jan '19

sbonazzo created OVIRT-2663: ------------------------------- Summary: Please add ManageIQ Hammer-1 to glance repository Key: OVIRT-2663 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2663 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: sbonazzo Assignee: infra In glance latest version available is Gaprindashvili-7. Please update with Hammer-1. Thanks, -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

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

30 Jan '19

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

1 0

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

30 Jan '19

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

1 0

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

30 Jan '19

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

1 0

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

30 Jan '19

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

1 0

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

30 Jan '19

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

1 0

[CQ]: 96903, 16 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 30 Jan '19

30 Jan '19

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

1 0

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

30 Jan '19

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

1 0

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

30 Jan '19

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

1 0

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

30 Jan '19

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

1 0

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

30 Jan '19

Change 5e928a1 (ovirt-ansible-hosted-engine-setup) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://github.com/oVirt/ovirt-ansible-hosted-engine-setup/commit/5e928a1d9… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12590/

1 0

[CQ]: 96815, 29 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 30 Jan '19

30 Jan '19

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

1 0

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

30 Jan '19

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

1 0

[CQ]: 96464, 3 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 29 Jan '19

29 Jan '19

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

1 0

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

29 Jan '19

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

1 0

[CQ]: 97353, 1 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 29 Jan '19

29 Jan '19

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

1 0

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

29 Jan '19

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

1 0

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

29 Jan '19

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

1 0

[CQ]: 97354, 1 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 29 Jan '19

29 Jan '19

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

1 0

Planned infra outage - Saturday February 2
by Evgheni Dereveanchin 29 Jan '19

29 Jan '19

Hi everyone, There's a maintenance window planned for this Saturday, February 2 2019 to upgrade network equipment in the PHX datacenter. The change will be implemented during afternoon hours and several oVirt infra services may be unreachable for short periods of time, specifically: * package repositories * Jenkins CI * glance image repo If you have problems accessing project resources during this period or see CI failures please re-try in a couple of hours. The project website and Gerrit code review are not affected by this outage and will continue to function normally. -- Regards, Evgheni Dereveanchin

1 0

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

29 Jan '19

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

1 0

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

29 Jan '19

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

1 0

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

29 Jan '19

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

1 0

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

29 Jan '19

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

1 0

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

29 Jan '19

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

1 0

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

29 Jan '19

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

1 0

[CQ]: 97262, 1 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 29 Jan '19

29 Jan '19

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

1 0

[CQ]: 97298, 1 (ovirt-log-collector) failed "ovirt-master" system tests
by oVirt Jenkins 29 Jan '19

29 Jan '19

Change 97298,1 (ovirt-log-collector) 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/97298/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12557/

1 0