July 2017 - Infra - oVirt List Archives

[JIRA] (OVIRT-886) Yum install does not throw error on missing package
by eedri (oVirt JIRA) 04 Jul '17

04 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-886?page=com.atlassian.jira.p… ] eedri reopened OVIRT-886: ------------------------- > Yum install does not throw error on missing package > --------------------------------------------------- > > Key: OVIRT-886 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-886 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Gil Shinar > Assignee: infra > > When running el7 mock on fc24 (not necessary the issue) and one of the required packages is missing because a repository in .repos hadn't been added, yum will not fail and the package will not be installed -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-886) Yum install does not throw error on missing package
by Gil Shinar (oVirt JIRA) 04 Jul '17

04 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-886?page=com.atlassian.jira.p… ] Gil Shinar commented on OVIRT-886: ---------------------------------- It happened to me yesterday > Yum install does not throw error on missing package > --------------------------------------------------- > > Key: OVIRT-886 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-886 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Gil Shinar > Assignee: infra > > When running el7 mock on fc24 (not necessary the issue) and one of the required packages is missing because a repository in .repos hadn't been added, yum will not fail and the package will not be installed -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-1500) CI on ovirt-engine patch succeeded, but didn't mark CI=+1 on gerrit
by Gil Shinar (oVirt JIRA) 04 Jul '17

04 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1500?page=com.atlassian.jira.… ] Gil Shinar commented on OVIRT-1500: ----------------------------------- [~mureinik] As I mentioned in the first comment, if you'll wait with a certain new patchset (2 in ths case) for the votes of the current patchset (1 in this case), you'll probably never hit this issue anymore. The only cases I have encountered this issue before is that when one has sent another patchset before the Jenkins jobs of the former patchset has completed and set their votes (ci) in gerrit > CI on ovirt-engine patch succeeded, but didn't mark CI=+1 on gerrit > ------------------------------------------------------------------- > > Key: OVIRT-1500 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1500 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Gerrit/git, oVirt CI > Reporter: Allon Mureinik > Assignee: infra > Priority: Low > > In my recent engine patch https://gerrit.ovirt.org/#/c/78911 the CI passed, but was not marked as so in gerrit. > Looking through gerrit's history, here's what I *think* is going on: > 08:41 - patchset #1 is submitted > 08:41 - CI (check-patch) starts for both EL7 and fc25 > _At this point I noticed a typo in the commit method. I fixed it and posted patchset #2_ > 08:42 - patchset #2 is submitted > _CI was never triggered for patchset #2. Is this because the only difference between it and patchset #1 is the commit message?_ > 09:15 - CI for patchset #1 completes, and marks *patchset #1* with CI=+1. This is not inherited to patchset #2 for some reason. > Expected behavior: > If CI for patchset #1 passed and the only difference is the commit message (not the parent commit and not the content), I'd expect the CI score to be inherited. -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-713) Clean reposync directory after n times of sync failure
by eedri (oVirt JIRA) 04 Jul '17

04 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-713?page=com.atlassian.jira.p… ] eedri updated OVIRT-713: ------------------------ Resolution: Cannot Reproduce Status: Done (was: To Do) > Clean reposync directory after n times of sync failure > ------------------------------------------------------ > > Key: OVIRT-713 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-713 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: Gal Ben Haim > Assignee: infra > > Sometimes reposync fail to sync rpms that already been synced. > To resolve this issue, lago removes those rpms, and runs reposync again. > This resolution doesn't always work, and then we need to clean all the rpms that were synced. > We want lago to clear the cached rpms after n times of sync failure, and then try to sync again. -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

Change 78967,2 (ovirt-engine) failed system tests
by oVirt Jenkins 04 Jul '17

04 Jul '17

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

1 0

Change 78703,6 (vdsm) failed system tests
by oVirt Jenkins 04 Jul '17

04 Jul '17

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

1 0

oVirt infra daily report - unstable production jobs - 372
by jenkins＠jenkins.phx.ovirt.org 04 Jul '17

04 Jul '17

------=_Part_161_1745765684.1499122801872 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit 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/372//artifact/exported-a… Cheers, Jenkins ------=_Part_161_1745765684.1499122801872 Content-Type: text/html; charset=us-ascii; name=upstream_report.html Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=upstream_report.html Content-ID: <upstream_report.html> <!DOCTYPE html><head><style type="text/css"> table.gridtable { border-collapse: collapse; table-layout:fixed; width:1600px; font-family: monospace; font-size:13px; } .head { font-size:20px; font-family: arial; } .sub { font-size:18px; background-color:#e5e5e5; font-family: arial; } pre { font-family: monospace; display: inline; white-space: pre-wrap; white-space: -moz-pre-wrap !important; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word; } </style> </head> <body> <table class="gridtable" border=2> <tr><th colspan=2 class=head> RHEVM CI Jenkins Daily Report - 03/07/2017 </th></tr><tr><th colspan=2 class=sub> <font color="blue"><a href="http://jenkins.ovirt.org/">00 Unstable Critical</a></font> </th></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/">test-repo_ovirt_experimental_master</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> ------=_Part_161_1745765684.1499122801872--

1 0

[JIRA] (OVIRT-713) Clean reposync directory after n times of sync failure
by ngoldin＠redhat.com (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-713?page=com.atlassian.jira.p… ] ngoldin(a)redhat.com commented on OVIRT-713: ------------------------------------------ I didn't see any failures with this at least in the past 2 months. We added some fixes to reposync flow, but that was a while ago. > Clean reposync directory after n times of sync failure > ------------------------------------------------------ > > Key: OVIRT-713 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-713 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: Gal Ben Haim > Assignee: infra > > Sometimes reposync fail to sync rpms that already been synced. > To resolve this issue, lago removes those rpms, and runs reposync again. > This resolution doesn't always work, and then we need to clean all the rpms that were synced. > We want lago to clear the cached rpms after n times of sync failure, and then try to sync again. -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

Change 78631,13 (vdsm) failed system tests
by oVirt Jenkins 03 Jul '17

03 Jul '17

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

1 0

Change 78837,4 (vdsm) failed system tests
by oVirt Jenkins 03 Jul '17

03 Jul '17

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

1 0