- Infra - oVirt List Archives

[JIRA] (OVIRT-2680) puppetdb on foreman.ovirt.org OOM
by Anton Marchukov (oVirt JIRA) 26 Feb '19

26 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2680?page=com.atlassian.jira.… ] Anton Marchukov reassigned OVIRT-2680: -------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > puppetdb on foreman.ovirt.org OOM > --------------------------------- > > Key: OVIRT-2680 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2680 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Emil Natan > Assignee: Evgheni Dereveanchin > > Pupperdb on forman.ovirt.org went down, it seems because of OOM. Below is the message from puppetdb-daemon.log. Not sure if this is the first time this happens, if yes then maybe just increase memory and swap. > java.lang.OutOfMemoryError: Java heap space > Dumping heap to /var/log/puppetdb/puppetdb-oom.hprof ... > Heap dump file created [285263302 bytes in 2.953 secs] > # > # java.lang.OutOfMemoryError: Java heap space > # -XX:OnOutOfMemoryError="kill -9 %p" > # Executing /bin/sh -c "kill -9 6929"... -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2684) Fwd: Access to resources.ovirt.org
by Anton Marchukov (oVirt JIRA) 26 Feb '19

26 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2684?page=com.atlassian.jira.… ] Anton Marchukov reassigned OVIRT-2684: -------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Fwd: Access to resources.ovirt.org > ---------------------------------- > > Key: OVIRT-2684 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2684 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Anton Marchukov > Assignee: Evgheni Dereveanchin > > Adding infra-support to open a ticket. > > Begin forwarded message: > > > > From: Gal Zaidman <gzaidman(a)redhat.com> > > Subject: Access to resources.ovirt.org > > Date: 26 February 2019 at 10:59:40 CET > > To: Anton Marchukov <amarchuk(a)redhat.com> > > > > Hi Anton, > > > > I need to get access to ssh resources.ovirt.org <http://resources.ovirt.org/>, > > I understood from Sandro that I need a ssh key for that, > > > > can you grant me access? > > > > Thanks, > > Gal Zaidman > -- > Anton Marchukov > Team Lead - Release Management - RHV DevOps - Red Hat -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2684) Fwd: Access to resources.ovirt.org
by Anton Marchukov (oVirt JIRA) 26 Feb '19

26 Feb '19

Anton Marchukov created OVIRT-2684: -------------------------------------- Summary: Fwd: Access to resources.ovirt.org Key: OVIRT-2684 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2684 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Anton Marchukov Assignee: infra Adding infra-support to open a ticket. > Begin forwarded message: > > From: Gal Zaidman <gzaidman(a)redhat.com> > Subject: Access to resources.ovirt.org > Date: 26 February 2019 at 10:59:40 CET > To: Anton Marchukov <amarchuk(a)redhat.com> > > Hi Anton, > > I need to get access to ssh resources.ovirt.org <http://resources.ovirt.org/>, > I understood from Sandro that I need a ssh key for that, > > can you grant me access? > > Thanks, > Gal Zaidman -- Anton Marchukov Team Lead - Release Management - RHV DevOps - Red Hat -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[CQ]: 4604050 (ovirt-ansible-engine-setup) failed "ovirt-master" system tests
by oVirt Jenkins 26 Feb '19

26 Feb '19

Change 4604050 (ovirt-ansible-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-engine-setup/commit/4604050e3aa8b3ba… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13137/

1 0

[CQ]: 4604050 (ovirt-ansible-engine-setup) failed "ovirt-4.2" system tests
by oVirt Jenkins 26 Feb '19

26 Feb '19

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

1 0

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

25 Feb '19

Failed to run project_setup.sh for: #1400 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-3pjd9.

1 0

oVirt infra daily report - unstable production jobs - 747
by jenkins＠jenkins.phx.ovirt.org 25 Feb '19

25 Feb '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/747//artifact/exported-a… Cheers, Jenkins

1 0

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

25 Feb '19

Failed to run project_setup.sh for: #3190 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 vm0039.workers-phx.ovirt.org.

1 0

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

25 Feb '19

Failed to run project_setup.sh for: #1395 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-vwskt.

1 0

[CQ]: 97398, 9 (ovirt-provider-ovn) failed "ovirt-master" system tests
by oVirt Jenkins 25 Feb '19

25 Feb '19

Change 97398,9 (ovirt-provider-ovn) 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/97398/9 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13129/

1 0

[JIRA] (OVIRT-2682) Add Pavel Bar to CI white-list
by Evgheni Dereveanchin (oVirt JIRA) 25 Feb '19

25 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2682?page=com.atlassian.jira.… ] Evgheni Dereveanchin updated OVIRT-2682: ---------------------------------------- Resolution: Done Status: Done (was: To Do) The change was merged, closing the corresponding ticket. > Add Pavel Bar to CI white-list > ------------------------------ > > Key: OVIRT-2682 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2682 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Fred Rolland > Assignee: infra > > https://gerrit.ovirt.org/#/c/97869/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

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

25 Feb '19

Failed to run project_setup.sh for: #3179 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 vm0086.workers-phx.ovirt.org.

1 0

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

25 Feb '19

Failed to run project_setup.sh for: #1392 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-bbjp8.

1 0

[JENKINS] Failed to setup proejct ovirt-provider-ovn_standard-on-merge
by jenkins＠jenkins.phx.ovirt.org 25 Feb '19

25 Feb '19

Failed to run project_setup.sh for: #252 ovirt-provider-ovn [check-merged]. 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

[CQ]: 97969, 11 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 25 Feb '19

25 Feb '19

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

1 0

[CQ]: 98009,1 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 25 Feb '19

25 Feb '19

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

1 0

[oVirt Jenkins] ovirt-system-tests_compat-4.2-suite-master - Build # 494 - Failure!
by jenkins＠jenkins.phx.ovirt.org 24 Feb '19

24 Feb '19

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.2-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.2-suite-master/494/ Build Number: 494 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #494 [Sandro Bonazzola] repos: master: switch to gluster 5 ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 002_bootstrap.get_host_devices_42 Error Message: Could not find block_vda1 device in host devices: Stack Trace: Traceback (most recent call last): File "/usr/lib64/python2.7/unittest/case.py", line 369, in run testMethod() File "/usr/lib/python2.7/site-packages/nose/case.py", line 197, in runTest self.test(*self.arg) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 142, in wrapped_test test() File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 60, in wrapper return func(get_test_prefix(), *args, **kwargs) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 79, in wrapper prefix.virt_env.engine_vm().get_api(api_ver=4), *args, **kwargs File "/home/jenkins/workspace/ovirt-system-tests_compat-4.2-suite-master/ovirt-system-tests/compat-4.2-suite-master/test-scenarios/002_bootstrap.py", line 1016, in get_host_devices raise RuntimeError('Could not find block_vda1 device in host devices: {}'.format(device_list)) RuntimeError: Could not find block_vda1 device in host devices:

1 1

oVirt infra daily report - unstable production jobs - 746
by jenkins＠jenkins.phx.ovirt.org 24 Feb '19

24 Feb '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/746//artifact/exported-a… Cheers, Jenkins

1 0

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

24 Feb '19

Failed to run project_setup.sh for: #1389 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-bxfjq.

1 0

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

24 Feb '19

Failed to run project_setup.sh for: #1390 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-bjd42.

1 0

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

24 Feb '19

Failed to run project_setup.sh for: #1389 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-9xgpc.

1 0

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

24 Feb '19

Failed to run project_setup.sh for: #1388 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-kb8b6.

1 0

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

24 Feb '19

Failed to run project_setup.sh for: #1387 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-rwdl1.

1 0

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

24 Feb '19

See <http://jenkins.ovirt.org/job/system-sync_mirrors-fedora-base-fc29-x86_64/32…> Changes: [Liora Milbaum] master_deploy: versioned_value filter ------------------------------------------ Started by timer [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-fedora-base-fc29-x86_64/ws/> 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 http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* --prune # timeout=10 > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision 798d77b25a396540dd740e97ba9075b6e3926310 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 798d77b25a396540dd740e97ba9075b6e3926310 # timeout=10 Commit message: "master_deploy: versioned_value filter" > git rev-list --no-walk 6d5cd8a6ec82ac556b4c414207b85536d44f39b8 # timeout=10 [system-sync_mirrors-fedora-base-fc29-x86_64] $ /bin/bash -xe /tmp/jenkins1463866524962743710.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror fedora-base-fc29 x86_64 jenkins/data/mirrors-reposync.conf + MIRRORS_MP_BASE=/var/www/html/repos + MIRRORS_HTTP_BASE=http://mirrors.phx.ovirt.org/repos + MIRRORS_CACHE=/home/jenkins/mirrors_cache + MAX_LOCK_ATTEMPTS=120 + LOCK_WAIT_INTERVAL=5 + LOCK_BASE=/home/jenkins + OLD_MD_TO_KEEP=100 + HTTP_SELINUX_TYPE=httpd_sys_content_t + HTTP_FILE_MODE=644 + main resync_yum_mirror fedora-base-fc29 x86_64 jenkins/data/mirrors-reposync.conf + local command=resync_yum_mirror + command_args=("${@:2}") + local command_args + cmd_resync_yum_mirror fedora-base-fc29 x86_64 jenkins/data/mirrors-reposync.conf + local repo_name=fedora-base-fc29 + local repo_archs=x86_64 + local reposync_conf=jenkins/data/mirrors-reposync.conf + local sync_needed + mkdir -p /home/jenkins/mirrors_cache + verify_repo_fs fedora-base-fc29 yum + local repo_name=fedora-base-fc29 + local repo_type=yum + sudo install -o jenkins -d /var/www/html/repos/yum /var/www/html/repos/yum/fedora-base-fc29 /var/www/html/repos/yum/fedora-base-fc29/base + check_yum_sync_needed fedora-base-fc29 x86_64 jenkins/data/mirrors-reposync.conf sync_needed + local repo_name=fedora-base-fc29 + local repo_archs=x86_64 + local reposync_conf=jenkins/data/mirrors-reposync.conf + local p_sync_needed=sync_needed + local reposync_out + echo 'Checking if mirror needs a resync' Checking if mirror needs a resync + rm -rf /home/jenkins/mirrors_cache/fedora-base-fc29 ++ IFS=, ++ echo x86_64 + for arch in '$(IFS=,; echo $repo_archs)' ++ run_reposync fedora-base-fc29 x86_64 jenkins/data/mirrors-reposync.conf --urls --quiet ++ local repo_name=fedora-base-fc29 ++ local repo_arch=x86_64 ++ local reposync_conf=jenkins/data/mirrors-reposync.conf ++ extra_args=("${@:4}") ++ local extra_args ++ reposync --config=jenkins/data/mirrors-reposync.conf --repoid=fedora-base-fc29 --arch=x86_64 --cachedir=/home/jenkins/mirrors_cache --download_path=/var/www/html/repos/yum/fedora-base-fc29/base --norepopath --newest-only --urls --quiet Traceback (most recent call last): File "/usr/bin/reposync", line 343, in <module> main() File "/usr/bin/reposync", line 175, in main my.doRepoSetup() File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 681, in doRepoSetup return self._getRepos(thisrepo, True) File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 721, in _getRepos self._repos.doSetup(thisrepo) File "/usr/lib/python2.7/site-packages/yum/repos.py", line 157, in doSetup self.retrieveAllMD() File "/usr/lib/python2.7/site-packages/yum/repos.py", line 88, in retrieveAllMD dl = repo._async and repo._commonLoadRepoXML(repo) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1465, in _commonLoadRepoXML local = self.cachedir + '/repomd.xml' File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 774, in <lambda> cachedir = property(lambda self: self._dirGetAttr('cachedir')) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 757, in _dirGetAttr self.dirSetup() File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 735, in dirSetup self._dirSetupMkdir_p(dir) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 712, in _dirSetupMkdir_p raise Errors.RepoError, msg yum.Errors.RepoError: Error making cache directory: /home/jenkins/mirrors_cache/centos-kvm-common-el7 error was: [Errno 17] File exists: '/home/jenkins/mirrors_cache/centos-kvm-common-el7' + reposync_out= Build step 'Execute shell' marked build as failure

1 1

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

24 Feb '19

Failed to run project_setup.sh for: #1380 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-41bfd.

1 0

Fwd: [GitHub] Subscribed to oVirt/ovirt-engine-sdk-go notifications
by Yaniv Kaul 24 Feb '19

24 Feb '19

Can we remove amureinin(a)redhat.com and aaviram(a)redhat.com from oVirt community? Both left Red Hat and I receive those notifications. Y. ---------- Forwarded message --------- From: GitHub <noreply(a)github.com> Date: Fri, Feb 22, 2019 at 7:33 PM Subject: [GitHub] Subscribed to oVirt/ovirt-engine-sdk-go notifications To: <amureini(a)redhat.com> Hey there, we’re just writing to let you know that you’ve been automatically subscribed to a repository on GitHub. oVirt/ovirt-engine-sdk-go Go SDK Generator for oVirt 4.x, with the help of oVirt community. https://github.com/oVirt/ovirt-engine-sdk-go You’ll receive notifications for all issues, pull requests, and comments that happen inside the repository. If you would like to stop watching this repository, you can manage your settings here: https://github.com/oVirt/ovirt-engine-sdk-go/subscription You can unwatch this repository immediately by clicking here: https://github.com/oVirt/ovirt-engine-sdk-go/unsubscribe_via_email/AD-wGfa9… You were automatically subscribed because you’ve been given access to the repository. Thanks!

1 0

[oVirt Jenkins] ovirt-system-tests_compat-4.1-suite-master - Build # 493 - Failure!
by jenkins＠jenkins.phx.ovirt.org 23 Feb '19

23 Feb '19

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.1-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.1-suite-master/493/ Build Number: 493 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #493 [Sandro Bonazzola] repos: master: switch to gluster 5 ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 002_bootstrap.get_host_devices_41 Error Message: Could not find block_vda1 device in host devices: Stack Trace: Traceback (most recent call last): File "/usr/lib64/python2.7/unittest/case.py", line 369, in run testMethod() File "/usr/lib/python2.7/site-packages/nose/case.py", line 197, in runTest self.test(*self.arg) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 142, in wrapped_test test() File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 60, in wrapper return func(get_test_prefix(), *args, **kwargs) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 79, in wrapper prefix.virt_env.engine_vm().get_api(api_ver=4), *args, **kwargs File "/home/jenkins/workspace/ovirt-system-tests_compat-4.1-suite-master/ovirt-system-tests/compat-4.1-suite-master/test-scenarios/002_bootstrap.py", line 1016, in get_host_devices raise RuntimeError('Could not find block_vda1 device in host devices: {}'.format(device_list)) RuntimeError: Could not find block_vda1 device in host devices:

1 1

oVirt infra daily report - unstable production jobs - 745
by jenkins＠jenkins.phx.ovirt.org 23 Feb '19

23 Feb '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/745//artifact/exported-a… Cheers, Jenkins

1 0

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

22 Feb '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/744//artifact/exported-a… Cheers, Jenkins

1 0

Fwd: Planned Outage - Fedora Core Services 2019-02-27 20:00 UTC
by Sandro Bonazzola 22 Feb '19

22 Feb '19

FYI ---------- Forwarded message --------- From: Stephen John Smoogen <smooge(a)gmail.com> Date: ven 22 feb 2019 alle ore 20:43 Subject: Planned Outage - Fedora Core Services 2019-02-27 20:00 UTC To: <announce(a)lists.fedoraproject.org>, Development discussions related to Fedora <devel(a)lists.fedoraproject.org>, Fedora Infrastructure < infrastructure(a)lists.fedoraproject.org> There will be an outage starting at 2019-02-27 20:00 UTC, which will last approximately 4-6 hours. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2019-02-27 20:00UTC' Reason for outage: Fedora Infrastructure would like to update and reboot all core systems and services. This will update kernels, glibc, and systemd plus many other services on the affected systems. Affected Services: All systems under fedoraproject.org will be affected. Important databases and authentication will be updated and rebooted first. Then other non-build systems will follow. Then build systems will finalize the update/reboot cycle Ticket Link: https://pagure.io/fedora-infrastructure/issue/7591 Please join #fedora-admin or #fedora-noc on irc.freenode.net or add comments to the ticket for this outage above. -- Stephen J Smoogen. _______________________________________________ devel mailing list -- devel(a)lists.fedoraproject.org To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig>

1 0

[CQ]: 97986,1 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 22 Feb '19

22 Feb '19

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

1 0

[Ovirt] [CQ weekly status] [22-02-2019]
by Dafna Ron 22 Feb '19

22 Feb '19

Hi, This mail is to provide the current status of CQ and allow people to review status before and after the weekend. Please refer to below colour map for further information on the meaning of the colours. *CQ-4.2*: GREEN (#1) 1. rh-postgress was failing to start due to missing selinux policy causing engine to fail installation. Bug: https://bugzilla.redhat.com/show_bug.cgi Issue resolved by didi and Galit by: 1. adding a workaround to add the selinuc poslicy and also a proposed fix (as described in comment #6) 2. created new lago images with new selinux package *CQ-Master:* GREEN (#1) 1. The same issue in 4.2 has effected master (for upgrade suite) Current running jobs for 4.2 [1] and master [2] can be found here: [1] http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.2_change-qu… [2] http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-master_change… Happy week! Dafna ------------------------------------------------------------------------------------------------------------------- COLOUR MAP Green = job has been passing successfully ** green for more than 3 days may suggest we need a review of our test coverage 1. 1-3 days GREEN (#1) 2. 4-7 days GREEN (#2) 3. Over 7 days GREEN (#3) Yellow = intermittent failures for different projects but no lasting or current regressions ** intermittent would be a healthy project as we expect a number of failures during the week ** I will not report any of the solved failures or regressions. 1. Solved job failures YELLOW (#1) 2. Solved regressions YELLOW (#2) Red = job has been failing ** Active Failures. The colour will change based on the amount of time the project/s has been broken. Only active regressions would be reported. 1. 1-3 days RED (#1) 2. 4-7 days RED (#2) 3. Over 7 days RED (#3)

1 0

[CQ]: 1a0df55 (ovirt-ansible-engine-setup) failed "ovirt-4.2" system tests
by oVirt Jenkins 22 Feb '19

22 Feb '19

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

1 0

[oVirt Jenkins] ovirt-system-tests_compat-4.2-suite-master - Build # 491 - Failure!
by jenkins＠jenkins.phx.ovirt.org 21 Feb '19

21 Feb '19

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.2-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.2-suite-master/491/ Build Number: 491 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #491 [jenkins CI] Add missing pkg: collectd-write_syslog [Sandro Bonazzola] ovirt-node-ng: stop building 4.2 and 4.2-pre [Gal Ben Haim] kubevirt-master: Add jobs [Tom�� Golembiovsk��] rename ovirt-ansible-v2v-conversion-host to v2v-conversion-host ----------------- Failed Tests: ----------------- No tests ran.

1 1

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

21 Feb '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/743//artifact/exported-a… Cheers, Jenkins

1 0

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

21 Feb '19

Failed to run project_setup.sh for: #1372 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-hd8jz.

1 0

[CQ]: 92775,10 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 21 Feb '19

21 Feb '19

Change 92775,10 (ovirt-engine) 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/92775/10 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13102/

1 0

[CQ]: 97847,5 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 21 Feb '19

21 Feb '19

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

1 0

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

21 Feb '19

Failed to run project_setup.sh for: #1369 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-69rkd.

1 2

[CQ]: f434bb0 (ovirt-ansible-hosted-engine-setup) failed "ovirt-4.2" system tests
by oVirt Jenkins 21 Feb '19

21 Feb '19

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

1 0

[VDSM] check-patch job fail - Cannot download x86_64/ovirt-imageio-common-1.5.0-0.201901061027.gita4be4ca.fc28.x86_64.rpm: All mirrors were tried
by Nir Soffer 21 Feb '19

21 Feb '19

In this buidl: https://jenkins.ovirt.org/job/vdsm_standard-check-patch/3035/artifact/ci_bu… 2 sub stages failed: This failed without generating any log, but we can see the error in the blue ocean interface: https://jenkins.ovirt.org/job/vdsm_standard-check-patch/3035//artifact/chec… https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa… This failed with this log: https://jenkins.ovirt.org/job/vdsm_standard-check-patch/3035//artifact/chec… Both failed becasue: Cannot download x86_64/ovirt-imageio-common-1.5.0-0.201901061027.gita4be4ca.fc28.x86_64.rpm: All mirrors were tried The other sub stages succeeded, and building the patch on top succeeded: https://gerrit.ovirt.org/c/97847 Looks like temporary error, failing to find a package from tested repository? How can we prevent these errors? Nir

2 3

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

21 Feb '19

Failed to run project_setup.sh for: #1369 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-df90s.

1 0

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

21 Feb '19

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

1 0

[CQ]: 97795,3 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 21 Feb '19

21 Feb '19

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

1 0

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

21 Feb '19

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

1 0

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

21 Feb '19

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

1 0

[CQ]: 97929, 3 (ovirt-engine) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 21 Feb '19

21 Feb '19

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

1 0

[CQ]: 97928, 3 (ovirt-engine) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 21 Feb '19

21 Feb '19

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

1 0

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

21 Feb '19

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

1 0

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

21 Feb '19

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

1 0