- Infra - oVirt List Archives

[CQ]: 104234, 4 (ovirt-system-tests) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 31 Oct '19

31 Oct '19

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

1 0

[oVirt Jenkins] deploy-to-gated-ovirt-4.3 - Build #1 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 31 Oct '19

31 Oct '19

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

1 3

[CQ]: 104234, 4 (ovirt-system-tests) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 31 Oct '19

31 Oct '19

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

1 0

[CQ]: 104234, 4 (ovirt-system-tests) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 31 Oct '19

31 Oct '19

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

1 0

[CQ]: 104234, 4 (ovirt-system-tests) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 31 Oct '19

31 Oct '19

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

1 0

[CQ]: 104312, 1 (ovirt-hosted-engine-setup) failed "ovirt-master" system tests
by oVirt Jenkins 30 Oct '19

30 Oct '19

Change 104312,1 (ovirt-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://gerrit.ovirt.org/#/c/104312/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/16697/

1 0

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

30 Oct '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/994//artifact/exported-a… Cheers, Jenkins

1 0

Planned restart of production services
by Evgheni Dereveanchin 30 Oct '19

30 Oct '19

Hi everyone, I'll be restarting several production systems today to apply security updates. The following services may be unreachable for short periods of time: - resources.ovirt.org - software repositories - jenkins.ovirt.org - CI master No new builds will be started during this period. I will announce you once maintenance is complete. -- Regards, Evgheni Dereveanchin

1 1

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

30 Oct '19

Change ec3a765 (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/ec3a76526… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/16694/

1 0

[oVirt CI] standard-enqueue - Build #24731 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 30 Oct '19

30 Oct '19

Build: http://jenkins.ovirt.org/job/standard-enqueue/24731/ Build Name: #24731 Build Description: Gerrit: 103570 - ovirt-engine (master) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/103570 - title: webadmin: fix datacenter edit versions list - project: ovirt-engine - branch: master - author: Ahmad Khiet <akhiet(a)redhat.com>

1 0

[JIRA] (OVIRT-2821) OST: test for host being in up state should have retries
by Ehud Yonasi (oVirt JIRA) 30 Oct '19

30 Oct '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2821?page=com.atlassian.jira.… ] Ehud Yonasi commented on OVIRT-2821: ------------------------------------ I agree, IMO it sounds like an issue with the API that needs to be checked. > OST: test for host being in up state should have retries > -------------------------------------------------------- > > Key: OVIRT-2821 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2821 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: OST > 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

[JIRA] (OVIRT-2821) OST: test for host being in up state should have retries
by Dusan Fodor (oVirt JIRA) 30 Oct '19

30 Oct '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2821?page=com.atlassian.jira.… ] Dusan Fodor commented on OVIRT-2821: ------------------------------------ On OST meeting we heard valid points against the suggested resolution, since it’s hiding the actual bug (that host doesn’t stay up after first going up) instead of resolving it. Probably a compromise would be to report the bug in bugzilla to engine and then bypass this in tests, so this failure wouldn’t mask other possible issues. Thoughts are welcome. Also note that the bug itself is not trivial, Marcin already spend significant time trying to get why the host doesn’t stay up for good. > OST: test for host being in up state should have retries > -------------------------------------------------------- > > Key: OVIRT-2821 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2821 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: OST > 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

[JIRA] (OVIRT-2821) OST: test for host being in up state should have retries
by Dusan Fodor (oVirt JIRA) 30 Oct '19

30 Oct '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2821?page=com.atlassian.jira.… ] Dusan Fodor updated OVIRT-2821: ------------------------------- Summary: OST: test for host being in up state should have retries (was: OST: test for host being in up state should have a retry) > OST: test for host being in up state should have retries > -------------------------------------------------------- > > Key: OVIRT-2821 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2821 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: OST > 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

[JIRA] (OVIRT-2821) OST: test for host being in up state should have a retry
by Dusan Fodor (oVirt JIRA) 30 Oct '19

30 Oct '19

Dusan Fodor created OVIRT-2821: ---------------------------------- Summary: OST: test for host being in up state should have a retry Key: OVIRT-2821 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2821 Project: oVirt - virtualization made easy Issue Type: Bug Components: OST 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

Fwd: Fedora 31 is officially here!
by Sandro Bonazzola 30 Oct '19

30 Oct '19

I guess we can start adding mock env for it. ---------- Forwarded message --------- Da: Matthew Miller <mattdm(a)fedoraproject.org> Date: mar 29 ott 2019 alle ore 17:00 Subject: Fedora 31 is officially here! To: <announce(a)lists.fedoraproject.org> Cc: <devel-announce(a)lists.fedoraproject.org> Thank you to the entire community of Fedora contributors who collaborated to create, once again, our best operating system release yet. Read the official announcement at: * https://fedoramagazine.org/announcing-fedora-31/ or just go ahead and grab it from: * https://getfedora.org/ -- Matthew Miller <mattdm(a)fedoraproject.org> Fedora Project Leader _______________________________________________ announce mailing list -- announce(a)lists.fedoraproject.org To unsubscribe send an email to announce-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/announce@lists.fedoraproject.… _______________________________________________ devel-announce mailing list -- devel-announce(a)lists.fedoraproject.org To unsubscribe send an email to devel-announce-leave(a)lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedorapr… -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/>*Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours. <https://mojo.redhat.com/docs/DOC-1199578>*

2 1

[CQ]: 104234, 4 (ovirt-system-tests) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 30 Oct '19

30 Oct '19

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

1 0

[CQ]: 104234, 4 (ovirt-system-tests) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 30 Oct '19

30 Oct '19

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

1 0

oVirt infra daily report - unstable production jobs - 993
by jenkins＠jenkins.phx.ovirt.org 29 Oct '19

29 Oct '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/993//artifact/exported-a… Cheers, Jenkins

1 0

Build failed in Jenkins: system-sync_mirrors-centos-extras-7.6-el7-x86_64 #19
by jenkins＠jenkins.phx.ovirt.org 29 Oct '19

29 Oct '19

See <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-extras-7.6-el7-x86_…> ------------------------------------------ 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-extras-7.6-el7-x86_…> 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 > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision 230de1f90e9e206fe913d4aff5c0749a860eb84a (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 230de1f90e9e206fe913d4aff5c0749a860eb84a Commit message: "Revert "ovirt-node-ng: add disto:fc30 for ovirt-node-ng-image builds"" > git rev-list --no-walk 230de1f90e9e206fe913d4aff5c0749a860eb84a # timeout=10 [system-sync_mirrors-centos-extras-7.6-el7-x86_64] $ /bin/bash -xe /tmp/jenkins6337929031691671301.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror centos-extras-7.6-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-extras-7.6-el7 x86_64 jenkins/data/mirrors-reposync.conf + local command=resync_yum_mirror + command_args=("${@:2}") + local command_args + cmd_resync_yum_mirror centos-extras-7.6-el7 x86_64 jenkins/data/mirrors-reposync.conf + local repo_name=centos-extras-7.6-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-extras-7.6-el7 yum + local repo_name=centos-extras-7.6-el7 + local repo_type=yum + sudo install -o jenkins -d /var/www/html/repos/yum /var/www/html/repos/yum/centos-extras-7.6-el7 /var/www/html/repos/yum/centos-extras-7.6-el7/base + check_yum_sync_needed centos-extras-7.6-el7 x86_64 jenkins/data/mirrors-reposync.conf sync_needed + local repo_name=centos-extras-7.6-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-extras-7.6-el7 ++ IFS=, ++ echo x86_64 + for arch in '$(IFS=,; echo $repo_archs)' ++ run_reposync centos-extras-7.6-el7 x86_64 jenkins/data/mirrors-reposync.conf --urls --quiet ++ local repo_name=centos-extras-7.6-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-extras-7.6-el7 --arch=x86_64 --cachedir=/home/jenkins/mirrors_cache --download_path=/var/www/html/repos/yum/centos-extras-7.6-el7/base --norepopath --newest-only --urls --quiet Traceback (most recent call last): File "/usr/bin/reposync", line 373, in <module> main() File "/usr/bin/reposync", line 185, 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 1468, in _commonLoadRepoXML local = self.cachedir + '/repomd.xml' File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 777, in <lambda> cachedir = property(lambda self: self._dirGetAttr('cachedir')) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 760, in _dirGetAttr self.dirSetup() File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 738, in dirSetup self._dirSetupMkdir_p(dir) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 715, in _dirSetupMkdir_p raise Errors.RepoError, msg yum.Errors.RepoError: Error making cache directory: /home/jenkins/mirrors_cache/centos-extras-7.6-el7 error was: [Errno 17] File exists: '/home/jenkins/mirrors_cache/centos-extras-7.6-el7' + reposync_out= Build step 'Execute shell' marked build as failure

1 1

[CQ]: 103556,4 (ovirt-system-tests) failed "ovirt-4.3" system tests
by oVirt Jenkins 29 Oct '19

29 Oct '19

Change 103556,4 (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/103556/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/2355/

1 0

[CQ]: 103556, 4 (ovirt-system-tests) failed "ovirt-master" system tests
by oVirt Jenkins 29 Oct '19

29 Oct '19

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

1 0

[JIRA] (OVIRT-2814) reposync fails syncing repos on completely unrelated paths (concurrency issue?)
by Anton Marchukov (oVirt JIRA) 29 Oct '19

29 Oct '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2814?page=com.atlassian.jira.… ] Anton Marchukov reassigned OVIRT-2814: -------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > reposync fails syncing repos on completely unrelated paths (concurrency issue?) > ------------------------------------------------------------------------------- > > Key: OVIRT-2814 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2814 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Components: CI Mirrors > Reporter: Sandro Bonazzola > Assignee: Evgheni Dereveanchin > > About job > https://jenkins.ovirt.org/job/system-sync_mirrors-centos-kvm-common-el7-x86… > As you can see below > 05:35:07 ++ reposync --config=jenkins/data/mirrors-reposync.conf > --repoid=centos-kvm-common-el7 --arch=x86_64 > --cachedir=/home/jenkins/mirrors_cache > --download_path=/var/www/html/repos/yum/centos-kvm-common-el7/base > --norepopath --newest-only --urls --quiet > the sync is related to "/var/www/html/repos/yum/centos-kvm-common-el7/base" > using as cache directory "/home/jenkins/mirrors_cache" > but in "/home/jenkins/mirrors_cache" there's > "/home/jenkins/mirrors_cache/fedora-base-fc29": > 05:35:16 Traceback (most recent call last): > 05:35:16 File "/usr/bin/reposync", line 373, in <module> > 05:35:16 main() > 05:35:16 File "/usr/bin/reposync", line 185, in main > 05:35:16 my.doRepoSetup() > 05:35:16 File "/usr/lib/python2.7/site-packages/yum/__init__.py", line > 681, in doRepoSetup > 05:35:16 return self._getRepos(thisrepo, True) > 05:35:16 File "/usr/lib/python2.7/site-packages/yum/__init__.py", line > 721, in _getRepos > 05:35:16 self._repos.doSetup(thisrepo) > 05:35:16 File "/usr/lib/python2.7/site-packages/yum/repos.py", line 157, > in doSetup > 05:35:16 self.retrieveAllMD() > 05:35:16 File "/usr/lib/python2.7/site-packages/yum/repos.py", line 88, > in retrieveAllMD > 05:35:16 dl = repo._async and repo._commonLoadRepoXML(repo) > 05:35:16 File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line > 1468, in _commonLoadRepoXML > 05:35:16 local = self.cachedir + '/repomd.xml' > 05:35:16 File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line > 777, in <lambda> > 05:35:16 cachedir = property(lambda self: self._dirGetAttr('cachedir')) > 05:35:16 File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line > 760, in _dirGetAttr > 05:35:16 self.dirSetup() > 05:35:16 File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line > 738, in dirSetup > 05:35:16 self._dirSetupMkdir_p(dir) > 05:35:16 File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line > 715, in _dirSetupMkdir_p > 05:35:16 raise Errors.RepoError, msg > 05:35:16 yum.Errors.RepoError: Error making cache directory: > /home/jenkins/mirrors_cache/fedora-base-fc29 error was: [Errno 17] File > exists: '/home/jenkins/mirrors_cache/fedora-base-fc29' > this looks like a concurrency issue, a lock should be used in order to > prevent two instances to use the same cache directory at the same time or > use separate cache directories for different repos. > -- > Sandro Bonazzola -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100114)

1 0

[JIRA] (OVIRT-2814) reposync fails syncing repos on completely unrelated paths (concurrency issue?)
by Anton Marchukov (oVirt JIRA) 29 Oct '19

29 Oct '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2814?page=com.atlassian.jira.… ] Anton Marchukov reopened OVIRT-2814: ------------------------------------ > reposync fails syncing repos on completely unrelated paths (concurrency issue?) > ------------------------------------------------------------------------------- > > Key: OVIRT-2814 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2814 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Components: CI Mirrors > Reporter: Sandro Bonazzola > Assignee: infra > > About job > https://jenkins.ovirt.org/job/system-sync_mirrors-centos-kvm-common-el7-x86… > As you can see below > 05:35:07 ++ reposync --config=jenkins/data/mirrors-reposync.conf > --repoid=centos-kvm-common-el7 --arch=x86_64 > --cachedir=/home/jenkins/mirrors_cache > --download_path=/var/www/html/repos/yum/centos-kvm-common-el7/base > --norepopath --newest-only --urls --quiet > the sync is related to "/var/www/html/repos/yum/centos-kvm-common-el7/base" > using as cache directory "/home/jenkins/mirrors_cache" > but in "/home/jenkins/mirrors_cache" there's > "/home/jenkins/mirrors_cache/fedora-base-fc29": > 05:35:16 Traceback (most recent call last): > 05:35:16 File "/usr/bin/reposync", line 373, in <module> > 05:35:16 main() > 05:35:16 File "/usr/bin/reposync", line 185, in main > 05:35:16 my.doRepoSetup() > 05:35:16 File "/usr/lib/python2.7/site-packages/yum/__init__.py", line > 681, in doRepoSetup > 05:35:16 return self._getRepos(thisrepo, True) > 05:35:16 File "/usr/lib/python2.7/site-packages/yum/__init__.py", line > 721, in _getRepos > 05:35:16 self._repos.doSetup(thisrepo) > 05:35:16 File "/usr/lib/python2.7/site-packages/yum/repos.py", line 157, > in doSetup > 05:35:16 self.retrieveAllMD() > 05:35:16 File "/usr/lib/python2.7/site-packages/yum/repos.py", line 88, > in retrieveAllMD > 05:35:16 dl = repo._async and repo._commonLoadRepoXML(repo) > 05:35:16 File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line > 1468, in _commonLoadRepoXML > 05:35:16 local = self.cachedir + '/repomd.xml' > 05:35:16 File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line > 777, in <lambda> > 05:35:16 cachedir = property(lambda self: self._dirGetAttr('cachedir')) > 05:35:16 File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line > 760, in _dirGetAttr > 05:35:16 self.dirSetup() > 05:35:16 File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line > 738, in dirSetup > 05:35:16 self._dirSetupMkdir_p(dir) > 05:35:16 File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line > 715, in _dirSetupMkdir_p > 05:35:16 raise Errors.RepoError, msg > 05:35:16 yum.Errors.RepoError: Error making cache directory: > /home/jenkins/mirrors_cache/fedora-base-fc29 error was: [Errno 17] File > exists: '/home/jenkins/mirrors_cache/fedora-base-fc29' > this looks like a concurrency issue, a lock should be used in order to > prevent two instances to use the same cache directory at the same time or > use separate cache directories for different repos. > -- > Sandro Bonazzola -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100114)

1 0

[JIRA] (OVIRT-2814) reposync fails syncing repos on completely unrelated paths (concurrency issue?)
by Anton Marchukov (oVirt JIRA) 29 Oct '19

29 Oct '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2814?page=com.atlassian.jira.… ] Anton Marchukov closed OVIRT-2814. ---------------------------------- > reposync fails syncing repos on completely unrelated paths (concurrency issue?) > ------------------------------------------------------------------------------- > > Key: OVIRT-2814 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2814 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Components: CI Mirrors > Reporter: Sandro Bonazzola > Assignee: infra > > About job > https://jenkins.ovirt.org/job/system-sync_mirrors-centos-kvm-common-el7-x86… > As you can see below > 05:35:07 ++ reposync --config=jenkins/data/mirrors-reposync.conf > --repoid=centos-kvm-common-el7 --arch=x86_64 > --cachedir=/home/jenkins/mirrors_cache > --download_path=/var/www/html/repos/yum/centos-kvm-common-el7/base > --norepopath --newest-only --urls --quiet > the sync is related to "/var/www/html/repos/yum/centos-kvm-common-el7/base" > using as cache directory "/home/jenkins/mirrors_cache" > but in "/home/jenkins/mirrors_cache" there's > "/home/jenkins/mirrors_cache/fedora-base-fc29": > 05:35:16 Traceback (most recent call last): > 05:35:16 File "/usr/bin/reposync", line 373, in <module> > 05:35:16 main() > 05:35:16 File "/usr/bin/reposync", line 185, in main > 05:35:16 my.doRepoSetup() > 05:35:16 File "/usr/lib/python2.7/site-packages/yum/__init__.py", line > 681, in doRepoSetup > 05:35:16 return self._getRepos(thisrepo, True) > 05:35:16 File "/usr/lib/python2.7/site-packages/yum/__init__.py", line > 721, in _getRepos > 05:35:16 self._repos.doSetup(thisrepo) > 05:35:16 File "/usr/lib/python2.7/site-packages/yum/repos.py", line 157, > in doSetup > 05:35:16 self.retrieveAllMD() > 05:35:16 File "/usr/lib/python2.7/site-packages/yum/repos.py", line 88, > in retrieveAllMD > 05:35:16 dl = repo._async and repo._commonLoadRepoXML(repo) > 05:35:16 File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line > 1468, in _commonLoadRepoXML > 05:35:16 local = self.cachedir + '/repomd.xml' > 05:35:16 File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line > 777, in <lambda> > 05:35:16 cachedir = property(lambda self: self._dirGetAttr('cachedir')) > 05:35:16 File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line > 760, in _dirGetAttr > 05:35:16 self.dirSetup() > 05:35:16 File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line > 738, in dirSetup > 05:35:16 self._dirSetupMkdir_p(dir) > 05:35:16 File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line > 715, in _dirSetupMkdir_p > 05:35:16 raise Errors.RepoError, msg > 05:35:16 yum.Errors.RepoError: Error making cache directory: > /home/jenkins/mirrors_cache/fedora-base-fc29 error was: [Errno 17] File > exists: '/home/jenkins/mirrors_cache/fedora-base-fc29' > this looks like a concurrency issue, a lock should be used in order to > prevent two instances to use the same cache directory at the same time or > use separate cache directories for different repos. > -- > Sandro Bonazzola -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100114)

1 0

Fwd: IMPORTANT: OST is now gated.
by Ehud Yonasi 29 Oct '19

29 Oct '19

We are going to merge the patch to enable the gating today [1]. Please watch carefully for OST patches if they don't pass the gate and find out why. [1]: https://gerrit.ovirt.org/#/c/103556/ ---------- Forwarded message --------- From: Milan Zamazal <mzamazal(a)redhat.com> Date: Wed, Sep 25, 2019 at 4:48 PM Subject: Re: IMPORTANT: OST is now gated. To: Ehud Yonasi <eyonasi(a)redhat.com> Cc: devel <devel(a)ovirt.org> Ehud Yonasi <eyonasi(a)redhat.com> writes: > Hey everyone, > OST project is now enabled for patch gating. Hi, it's cool, but before enabling it for other projects, please make sure pending OST problems are fixed. AFAIK the random failures related to add_master_storage_domain in basic-suite-master and discussed here recently haven't been fixed yet (and I think this was the random failure I observed when running OST on my computer yesterday). While random failures may not look that urgent as regular failures, they are still incompatible with patch gating and will cause trouble in projects with more frequent merges and/or longer patch series. Thanks, Milan > What is the meaning of this? > > 1. The gating process will start when Code-Review +2, CI +1 and > Verified +1 labels are turned on. > 2. Every patch before merging will have to pass the following suites: > - > > *oVirt-master* > > *oVirt-4.3* > > basic_suite > > basic_suite > > upgrade-from-release > > upgrade-from-release > > > upgrade-from-prevrelease > 3. Patches should no longer be manually merged in OST, they will be > merged automatically when passing the gate. > > *NOTE: *Maintainers are still able to merge manually, but it is not > recommended if the gate is not passing. > > *NOTE:* For additional information regarding the gating I've sent FAQ mail > - 'Patch Gating summary + FAQ' > > Regards, > Ehud. > _______________________________________________ > Devel mailing list -- devel(a)ovirt.org > To unsubscribe send an email to devel-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/devel@ovirt.org/message/ZES5BD3FXCKHD…

1 0

[CQ]: 4d9fdcd (ovirt-engine-sdk-go) failed "ovirt-4.3" system tests
by oVirt Jenkins 29 Oct '19

29 Oct '19

Change 4d9fdcd (ovirt-engine-sdk-go) 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://github.com/oVirt/ovirt-engine-sdk-go/commit/4d9fdcd42d8317a66234fe2… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/2349/

1 0

[CQ]: 3e18995 (ovirt-engine-sdk-go) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 28 Oct '19

28 Oct '19

A system test invoked by the "ovirt-master" change queue including change 3e18995 (ovirt-engine-sdk-go) failed. However, this change seems not to be the root cause for this failure. Change fbbe965 (ovirt-engine-sdk-go) 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 fbbe965 (ovirt-engine-sdk-go) 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-engine-sdk-go/commit/3e189957a5bd4eeb9c6a3c6… For further details about the change that seems to be the root cause behind the testing failures see: https://github.com/oVirt/ovirt-engine-sdk-go/commit/fbbe96561752bb82969ddd6… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/16674/

1 0

[CQ]: 9725eea (ovirt-engine-sdk-go) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 28 Oct '19

28 Oct '19

A system test invoked by the "ovirt-master" change queue including change 9725eea (ovirt-engine-sdk-go) failed. However, this change seems not to be the root cause for this failure. Change fbbe965 (ovirt-engine-sdk-go) 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 fbbe965 (ovirt-engine-sdk-go) 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-engine-sdk-go/commit/9725eea12cfc6fac2405db3… For further details about the change that seems to be the root cause behind the testing failures see: https://github.com/oVirt/ovirt-engine-sdk-go/commit/fbbe96561752bb82969ddd6… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/16672/

1 0

oVirt infra daily report - unstable production jobs - 992
by jenkins＠jenkins.phx.ovirt.org 28 Oct '19

28 Oct '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/992//artifact/exported-a… Cheers, Jenkins

1 0

[CQ]: 104263, 2 (ovirt-node-ng-image) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 28 Oct '19

28 Oct '19

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

1 0

[CQ]: 104261, 1 (ovirt-node-ng-image) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 28 Oct '19

28 Oct '19

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

1 0

[CQ]: 104267, 3 (ovirt-engine-metrics) failed "ovirt-master" system tests
by oVirt Jenkins 28 Oct '19

28 Oct '19

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

1 0

[CQ]: 103154,3 (jenkins) failed "dummy-master" system tests
by oVirt Jenkins 28 Oct '19

28 Oct '19

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

1 0

[CQ]: 104223, 19 (ovirt-node-ng-image) failed "ovirt-master" system tests
by oVirt Jenkins 28 Oct '19

28 Oct '19

Change 104223,19 (ovirt-node-ng-image) 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/104223/19 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/16660/

1 0

[CQ]: 23a42fa (ovirt-engine-sdk-go) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 28 Oct '19

28 Oct '19

A system test invoked by the "ovirt-master" change queue including change 23a42fa (ovirt-engine-sdk-go) failed. However, this change seems not to be the root cause for this failure. Change fbbe965 (ovirt-engine-sdk-go) 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 fbbe965 (ovirt-engine-sdk-go) 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-engine-sdk-go/commit/23a42fad096795c9649d160… For further details about the change that seems to be the root cause behind the testing failures see: https://github.com/oVirt/ovirt-engine-sdk-go/commit/fbbe96561752bb82969ddd6… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/16658/

1 0

oVirt infra daily report - unstable production jobs - 991
by jenkins＠jenkins.phx.ovirt.org 27 Oct '19

27 Oct '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/991//artifact/exported-a… Cheers, Jenkins

1 0

[CQ]: 104225,1 (ovirt-engine) failed "ovirt-4.3" system tests
by oVirt Jenkins 27 Oct '19

27 Oct '19

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

1 0

oVirt infra daily report - unstable production jobs - 990
by jenkins＠jenkins.phx.ovirt.org 26 Oct '19

26 Oct '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/990//artifact/exported-a… Cheers, Jenkins

1 0

[oVirt] [CQ weekly status] [26-10-2019]
by Dusan Fodor 26 Oct '19

26 Oct '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.3*: GREEN (#1) Last failure was on 25-10 for ovirt-host due to dependency issue. Patch ( 104248 <https://gerrit.ovirt.org/104248>) is pending to fix this. *CQ-Master:* YELLOW (#1 Last failure was on 25-10 caused by known, random add storage domain failure (test issue). Current running jobs for 4.3 [1] and master [2] can be found here: [1] https://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.3_change-q… [2] http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-master_change… Have a nice week! Dusan ------------------------------------------------------------------------------------------------------------------- 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) _______________________________________________ Devel mailing list -- devel(a)ovirt.org To unsubscribe send an email to devel-leave(a)ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/message/YCNCKRK3G4EJX…

1 0

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

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

1 0

[CQ]: 103761,8 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 25 Oct '19

25 Oct '19

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

1 0

[CQ]: 104239, 1 (ovirt-host) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 25 Oct '19

25 Oct '19

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

1 0

[CQ]: 103450, 67 (vdsm-jsonrpc-java) failed "ovirt-master" system tests
by oVirt Jenkins 25 Oct '19

25 Oct '19

Change 103450,67 (vdsm-jsonrpc-java) 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/103450/67 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/16646/

1 0

[CQ]: 104238, 1 (ovirt-host) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 25 Oct '19

25 Oct '19

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

1 0

[CQ]: 103764, 2 (ovirt-host) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 25 Oct '19

25 Oct '19

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

1 0

[CQ]: 104081,3 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 25 Oct '19

25 Oct '19

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

1 0

[CQ]: 103450,67 (vdsm-jsonrpc-java) failed "ovirt-4.3" system tests
by oVirt Jenkins 25 Oct '19

25 Oct '19

Change 103450,67 (vdsm-jsonrpc-java) 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/103450/67 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/2333/

1 0

[CQ]: 104138,3 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 25 Oct '19

25 Oct '19

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

1 0

[CQ]: 104224,2 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 25 Oct '19

25 Oct '19

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

1 0

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

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

1 0