August 2019 - Infra - oVirt List Archives

[ovirt-devel] [OST Failure Report] [oVirt master&4.3] [09-08-2019] [verify_glance_import]
by Dusan Fodor 12 Aug '19

12 Aug '19

Hi, we have failures in test verify glance import appearing in both 4.3 and master. Api call to get the disk status times out. Example of failed job can be seen here: https://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.3_change-q… Can you please take a look?

3 3

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

12 Aug '19

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

1 0

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

12 Aug '19

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

1 0

Build failed in Jenkins: system-sync_mirrors-centos-kvm-common-el7-x86_64 #2737
by jenkins＠jenkins.phx.ovirt.org 12 Aug '19

12 Aug '19

See <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-kvm-common-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-kvm-common-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/changes/59/95959/1:test --prune > git rev-parse origin/test^{commit} # timeout=10 > git rev-parse test^{commit} # timeout=10 Checking out Revision 05b40dfb4ec43a82530e8c471395d1858e5c59e1 (test) > git config core.sparsecheckout # timeout=10 > git checkout -f 05b40dfb4ec43a82530e8c471395d1858e5c59e1 Commit message: "mirror-reposync: remove gluster-3.10 mirror" > git rev-list --no-walk 05b40dfb4ec43a82530e8c471395d1858e5c59e1 # timeout=10 [system-sync_mirrors-centos-kvm-common-el7-x86_64] $ /bin/bash -xe /tmp/jenkins7477368550401470113.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror centos-kvm-common-el7 x86_64 jenkins/data/mirrors-reposync.conf Checking if mirror needs a resync 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/fedora-base-fc29/gen error was: [Errno 17] File exists: '/home/jenkins/mirrors_cache/fedora-base-fc29/gen' Build step 'Execute shell' marked build as failure

1 1

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

12 Aug '19

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

1 0

oVirt infra daily report - unstable production jobs - 914
by jenkins＠jenkins.phx.ovirt.org 11 Aug '19

11 Aug '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/914//artifact/exported-a… Cheers, Jenkins

1 0

[CQ]: 102098,29 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 11 Aug '19

11 Aug '19

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

1 0

[JIRA] (OVIRT-2773) verify_glance_import test failing in both 4.3 and master suites
by Eyal Edri (oVirt JIRA) 11 Aug '19

11 Aug '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2773?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2773: ---------------------------------- [~accountid:557058:caa507e4-2696-4f45-8da5-d2585a4bb794] looked into it today and its most likely an error to download a large image of 800MB over the bad network we have outside PHX, now affecting also our connecting with OSAS and not just with AWS. For now, we’ll revert to use the old Glance which is in PHX until we’ll fix the networking problem. > verify_glance_import test failing in both 4.3 and master suites > --------------------------------------------------------------- > > Key: OVIRT-2773 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2773 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dusan Fodor > Assignee: infra > > Example of failed job can be found here: > https://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-master_chang… > Thread [ovirt-devel] [OST Failure Report] [oVirt master&4.3] [09-08-2019] [verify_glance_import] was opened for investigation -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100107)

1 0

[ovirt-devel] [Ovirt] [CQ weekly status] [10-08-2019]
by Dusan Fodor 11 Aug '19

11 Aug '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 (#3) No failure during this week. *CQ-4.3*: RED (#1) Last failure was on 10-08 for ovirt-ansible-image-template in verify_glance_import. This issue is ongoing, investigation will continue under thread [OST Failure Report] [oVirt master&4.3] [09-08-2019] [verify_glance_import] *CQ-Master:* RED (#1) Last failure was on 10-08 for ovirt-ansible-image-template in verify_glance_import. This issue is ongoing, investigation will continue under thread [OST Failure Report] [oVirt master&4.3] [09-08-2019] [verify_glance_import] Current running jobs for 4.2 [1], 4.3 [2] and master [3] can be found here: [1] http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt -4.2_change-queue-tester/ [2] https://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt -4.3_change-queue-tester/ [3] http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt -master_change-queue-tester/ 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/YCNCKRK3G4EJXA3OCYAUS4VMKRDA67F4/

2 1

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

11 Aug '19

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

1 0