- Infra - oVirt List Archives

[JIRA] (OVIRT-1911) RFE: Add relevant git commit messages as comments in the relevant Bugzillas
by eyal edri (oVirt JIRA) 25 Feb '18

25 Feb '18

This is a multi-part message in MIME format... ------------=_1519573284-30715-140 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1911?page=com.atlassian.jira.… ] eyal edri reassigned OVIRT-1911: -------------------------------- Assignee: Anton Marchukov (was: infra) Anton, how much effort do you think this will need to add it to Gerrit Hooks? [~ykaul] I also think this should be communicated before adding, people sometimes don't like new automatic info added to bugs without a good reason. We'll also need to think what do you do in case there are multiple external trackers attached to the bug, which is the case most of the time, do you start "spamming" the bug with commit messages from each tracker? sometimes it can be as much as 10 different patches. What about if there are trackers from multiple projects, a quite common scenario with oVirt bugs (e.g vdsm + engine + jsonrpc) , do you add all the commit messages then? We've seen issues with current new comments added to bugs when they can't move to ON_QA, it has the potential of causing more noise than good, so we really need to think if and how we want to implement this before moving forward. cc [~dfodor] > RFE: Add relevant git commit messages as comments in the relevant Bugzillas > --------------------------------------------------------------------------- > > Key: OVIRT-1911 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1911 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Gerrit/git > Reporter: Yaniv Kaul > Assignee: Anton Marchukov > > When a bug moves to MODIFIED, can we add the relevant commit message(s) to the bug? > I see it happening in RHEL from time to time, and I think it's easier (for us and QE) then clicking on the link to Gerrit. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100080) ------------=_1519573284-30715-140 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1911?page=com.atlassian.jira.… ]</pre> <h3>eyal edri reassigned OVIRT-1911:</h3> <pre>Assignee: Anton Marchukov (was: infra)</pre> <p>Anton, how much effort do you think this will need to add it to Gerrit Hooks?</p> <p>[~ykaul] I also think this should be communicated before adding, people sometimes don't like new automatic info added to bugs without a good reason.</p> <p>We'll also need to think what do you do in case there are multiple external trackers attached to the bug, which is the case most of the time, do you start “spamming” the bug with commit messages from each tracker? sometimes it can be as much as 10 different patches.</p> <p>What about if there are trackers from multiple projects, a quite common scenario with oVirt bugs (e.g vdsm + engine + jsonrpc) , do you add all the commit messages then?</p> <p>We've seen issues with current new comments added to bugs when they can't move to ON_QA, it has the potential of causing more noise than good, so we really need to think if and how we want to implement this before moving forward.</p> <p>cc [~dfodor]</p> <blockquote><h3>RFE: Add relevant git commit messages as comments in the relevant Bugzillas</h3> <pre> Key: OVIRT-1911 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1911 Project: oVirt - virtualization made easy Issue Type: New Feature Components: Gerrit/git Reporter: Yaniv Kaul Assignee: Anton Marchukov</pre> <p>When a bug moves to MODIFIED, can we add the relevant commit message(s) to the bug? I see it happening in RHEL from time to time, and I think it's easier (for us and QE) then clicking on the link to Gerrit.</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100080)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1519573284-30715-140--

1 0

[JIRA] (OVIRT-1911) RFE: Add relevant git commit messages as comments in the relevant Bugzillas
by Yaniv Kaul (oVirt JIRA) 25 Feb '18

25 Feb '18

This is a multi-part message in MIME format... ------------=_1519571950-30813-109 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Yaniv Kaul created OVIRT-1911: --------------------------------- Summary: RFE: Add relevant git commit messages as comments in the relevant Bugzillas Key: OVIRT-1911 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1911 Project: oVirt - virtualization made easy Issue Type: New Feature Components: Gerrit/git Reporter: Yaniv Kaul Assignee: infra When a bug moves to MODIFIED, can we add the relevant commit message(s) to the bug? I see it happening in RHEL from time to time, and I think it's easier (for us and QE) then clicking on the link to Gerrit. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100080) ------------=_1519571950-30813-109 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <h3>Yaniv Kaul created OVIRT-1911:</h3> <pre> Summary: RFE: Add relevant git commit messages as comments in the relevant Bugzillas Key: OVIRT-1911 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1911 Project: oVirt - virtualization made easy Issue Type: New Feature Components: Gerrit/git Reporter: Yaniv Kaul Assignee: infra</pre> <p>When a bug moves to MODIFIED, can we add the relevant commit message(s) to the bug? I see it happening in RHEL from time to time, and I think it's easier (for us and QE) then clicking on the link to Gerrit.</p> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100080)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1519571950-30813-109--

1 0

[JIRA] (OVIRT-1911) RFE: Add relevant git commit messages as comments in the relevant Bugzillas
by Yaniv Kaul (oVirt JIRA) 25 Feb '18

25 Feb '18

This is a multi-part message in MIME format... ------------=_1519571950-26090-115 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1911?page=com.atlassian.jira.… ] Yaniv Kaul updated OVIRT-1911: ------------------------------ Epic Link: OVIRT-411 > RFE: Add relevant git commit messages as comments in the relevant Bugzillas > --------------------------------------------------------------------------- > > Key: OVIRT-1911 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1911 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Gerrit/git > Reporter: Yaniv Kaul > Assignee: infra > > When a bug moves to MODIFIED, can we add the relevant commit message(s) to the bug? > I see it happening in RHEL from time to time, and I think it's easier (for us and QE) then clicking on the link to Gerrit. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100080) ------------=_1519571950-26090-115 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1911?page=com.atlassian.jira.… ]</pre> <h3>Yaniv Kaul updated OVIRT-1911:</h3> <pre>Epic Link: OVIRT-411</pre> <blockquote><h3>RFE: Add relevant git commit messages as comments in the relevant Bugzillas</h3> <pre> Key: OVIRT-1911 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1911 Project: oVirt - virtualization made easy Issue Type: New Feature Components: Gerrit/git Reporter: Yaniv Kaul Assignee: infra</pre> <p>When a bug moves to MODIFIED, can we add the relevant commit message(s) to the bug? I see it happening in RHEL from time to time, and I think it's easier (for us and QE) then clicking on the link to Gerrit.</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100080)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1519571950-26090-115--

1 0

[JIRA] (OVIRT-1910) Strange Lago CI test failure
by Barak Korren (oVirt JIRA) 25 Feb '18

25 Feb '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1910?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1910: -------------------------------- Epic Link: OVIRT-400 > Strange Lago CI test failure > ---------------------------- > > Key: OVIRT-1910 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1910 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Components: Standard CI (Freestyle) > Reporter: Yaniv Kaul > Assignee: infra > > My patch[1] is failing, but I'm not sure why. > See [2] for the job - the issues seems to be with the pusher - see its > log[3]: > 2018-02-23 12:42:16,222:DEBUG:__main__:Executing command: 'git log -1 > --pretty=format:%H' > 2018-02-23 12:42:16,230:DEBUG:__main__:Git exited with status: 0 > 2018-02-23 12:42:16,230:DEBUG:__main__: ---- stderr ---- > 2018-02-23 12:42:16,230:DEBUG:__main__: ---- stdout ---- > 2018-02-23 12:42:16,230:DEBUG:__main__: > c26adc01449d97899aac18406298374de0e7dd73 > 2018-02-23 12:42:16,231:DEBUG:__main__:Executing command: 'git > rev-parse jenkins-lago_master_github_check-patch-el7-x86_64-711^{commit}' > 2018-02-23 12:42:16,237:DEBUG:__main__:Git exited with status: 128 > 2018-02-23 12:42:16,237:DEBUG:__main__: ---- stderr ---- > 2018-02-23 12:42:16,237:DEBUG:__main__: fatal: ambiguous argument > 'jenkins-lago_master_github_check-patch-el7-x86_64-711^{commit}': > unknown revision or path not in the working tree. > Any ideas? > TIA, > Y. > [1] https://github.com/lago-project/lago/pull/695 > [2] > http://jenkins.ovirt.org/job/lago_master_github_check-patch-el7-x86_64/711/ > [3] > http://jenkins.ovirt.org/job/lago_master_github_check-patch-el7-x86_64/711/… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100080)

1 0

[JIRA] (OVIRT-1910) Strange Lago CI test failure
by Barak Korren (oVirt JIRA) 25 Feb '18

25 Feb '18

This is a multi-part message in MIME format... ------------=_1519559357-18891-124 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1910?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1910: ----------------------------------- Assignee: Barak Korren (was: infra) Component/s: Standard CI (Freestyle) Epic Link: OVIRT-400 Issue Type: Bug (was: By-EMAIL) Priority: Highest (was: Medium) > Strange Lago CI test failure > ---------------------------- > > Key: OVIRT-1910 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1910 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Standard CI (Freestyle) > Reporter: Yaniv Kaul > Assignee: Barak Korren > Priority: Highest > > My patch[1] is failing, but I'm not sure why. > See [2] for the job - the issues seems to be with the pusher - see its > log[3]: > 2018-02-23 12:42:16,222:DEBUG:__main__:Executing command: 'git log -1 > --pretty=format:%H' > 2018-02-23 12:42:16,230:DEBUG:__main__:Git exited with status: 0 > 2018-02-23 12:42:16,230:DEBUG:__main__: ---- stderr ---- > 2018-02-23 12:42:16,230:DEBUG:__main__: ---- stdout ---- > 2018-02-23 12:42:16,230:DEBUG:__main__: > c26adc01449d97899aac18406298374de0e7dd73 > 2018-02-23 12:42:16,231:DEBUG:__main__:Executing command: 'git > rev-parse jenkins-lago_master_github_check-patch-el7-x86_64-711^{commit}' > 2018-02-23 12:42:16,237:DEBUG:__main__:Git exited with status: 128 > 2018-02-23 12:42:16,237:DEBUG:__main__: ---- stderr ---- > 2018-02-23 12:42:16,237:DEBUG:__main__: fatal: ambiguous argument > 'jenkins-lago_master_github_check-patch-el7-x86_64-711^{commit}': > unknown revision or path not in the working tree. > Any ideas? > TIA, > Y. > [1] https://github.com/lago-project/lago/pull/695 > [2] > http://jenkins.ovirt.org/job/lago_master_github_check-patch-el7-x86_64/711/ > [3] > http://jenkins.ovirt.org/job/lago_master_github_check-patch-el7-x86_64/711/… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100080) ------------=_1519559357-18891-124 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1910?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren reassigned OVIRT-1910:</h3> <pre> Assignee: Barak Korren (was: infra) Component/s: Standard CI (Freestyle) Epic Link: OVIRT-400 Issue Type: Bug (was: By-EMAIL) Priority: Highest (was: Medium)</pre> <blockquote><h3>Strange Lago CI test failure</h3> <pre> Key: OVIRT-1910 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1910 Project: oVirt - virtualization made easy Issue Type: Bug Components: Standard CI (Freestyle) Reporter: Yaniv Kaul Assignee: Barak Korren Priority: Highest</pre> <p>My patch[1] is failing, but I'm not sure why. See [2] for the job – the issues seems to be with the pusher – see its log[3]: 2018-02-23 12:42:16,222:DEBUG:__main__:Executing command: ‘git log -1 --pretty=format:%H’ 2018-02-23 12:42:16,230:DEBUG:__main__:Git exited with status: 0 2018-02-23 12:42:16,230:DEBUG:__main__: ---- stderr ---- 2018-02-23 12:42:16,230:DEBUG:__main__: ---- stdout ---- 2018-02-23 12:42:16,230:DEBUG:__main__: c26adc01449d97899aac18406298374de0e7dd73 2018-02-23 12:42:16,231:DEBUG:__main__:Executing command: ‘git rev-parse jenkins-lago_master_github_check-patch-el7-x86_64-711^{commit}’ 2018-02-23 12:42:16,237:DEBUG:__main__:Git exited with status: 128 2018-02-23 12:42:16,237:DEBUG:__main__: ---- stderr ---- 2018-02-23 12:42:16,237:DEBUG:__main__: fatal: ambiguous argument ‘jenkins-lago_master_github_check-patch-el7-x86_64-711^{commit}’: unknown revision or path not in the working tree. Any ideas? TIA, Y. [1] <a href="https://github.com/lago-project/lago/pull/695">https://github.com/lago-project/lago/pull/695</a> [2] <a href="http://jenkins.ovirt.org/job/lago_master_github_check-patch-el7-x86_64/711/">http://jenkins.ovirt.org/job/lago_master_github_check-patch-el7-x86_64/711/</a> [3] <a href="http://jenkins.ovirt.org/job/lago_master_github_check-patch-el7-x86_64/711/…">http://jenkins.ovirt.org/job/lago_master_github_check-patch-el7-x86_64/711/…</a></p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100080)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1519559357-18891-124--

1 0

[JIRA] (OVIRT-1910) Strange Lago CI test failure
by Yaniv Kaul (oVirt JIRA) 25 Feb '18

25 Feb '18

Yaniv Kaul created OVIRT-1910: --------------------------------- Summary: Strange Lago CI test failure Key: OVIRT-1910 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1910 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Yaniv Kaul Assignee: infra My patch[1] is failing, but I'm not sure why. See [2] for the job - the issues seems to be with the pusher - see its log[3]: 2018-02-23 12:42:16,222:DEBUG:__main__:Executing command: 'git log -1 --pretty=format:%H' 2018-02-23 12:42:16,230:DEBUG:__main__:Git exited with status: 0 2018-02-23 12:42:16,230:DEBUG:__main__: ---- stderr ---- 2018-02-23 12:42:16,230:DEBUG:__main__: ---- stdout ---- 2018-02-23 12:42:16,230:DEBUG:__main__: c26adc01449d97899aac18406298374de0e7dd73 2018-02-23 12:42:16,231:DEBUG:__main__:Executing command: 'git rev-parse jenkins-lago_master_github_check-patch-el7-x86_64-711^{commit}' 2018-02-23 12:42:16,237:DEBUG:__main__:Git exited with status: 128 2018-02-23 12:42:16,237:DEBUG:__main__: ---- stderr ---- 2018-02-23 12:42:16,237:DEBUG:__main__: fatal: ambiguous argument 'jenkins-lago_master_github_check-patch-el7-x86_64-711^{commit}': unknown revision or path not in the working tree. Any ideas? TIA, Y. [1] https://github.com/lago-project/lago/pull/695 [2] http://jenkins.ovirt.org/job/lago_master_github_check-patch-el7-x86_64/711/ [3] http://jenkins.ovirt.org/job/lago_master_github_check-patch-el7-x86_64/711/… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100080)

1 0

[JIRA] (OVIRT-1909) GetBadges is not working anymore
by eyal edri (oVirt JIRA) 25 Feb '18

25 Feb '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1909?page=com.atlassian.jira.… ] eyal edri commented on OVIRT-1909: ---------------------------------- Yep, the Jenkins plugin stopped working and we didn't get a reply from them on the ticket. Evgheni, I suggest to try and ping them again and if there is no reply, let's remove the Jenkins integration for now. On Thu, Feb 22, 2018 at 11:23 PM, sbonazzo (oVirt JIRA) < -- Eyal edri MANAGER RHV DevOps EMEA VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ) > GetBadges is not working anymore > -------------------------------- > > Key: OVIRT-1909 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1909 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > Not sure what happened 3 months ago but GetBadges is not receiving data > anymore. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100080)

1 0

[JIRA] (OVIRT-1909) GetBadges is not working anymore
by sbonazzo (oVirt JIRA) 25 Feb '18

25 Feb '18

sbonazzo created OVIRT-1909: ------------------------------- Summary: GetBadges is not working anymore Key: OVIRT-1909 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1909 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: sbonazzo Assignee: infra Not sure what happened 3 months ago but GetBadges is not receiving data anymore. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100080)

2 1

The importance of fixing failed build-artifacts jobs
by Dafna Ron 25 Feb '18

25 Feb '18

Hi All, We have been seeing a large amount of changes that are not deployed into tested lately because of failed build-artifacts jobs so we decided that perhaps we need to explain the importance of fixing a failed build-artifacts job. If a change failed a build-artifacts job, no matter what platform/arch it failed in, the change will not be deployed to tested. Here is an example of a change that will not be added to tested: [image: Inline image 1] As you can see, only one of the build-artifacts jobs failed but since the project specify that it requires all of these arches/platforms, the change will not be added to tested until all of the jobs are fixed. So what can we do? 1. Add the code which builds-artifacts to 'check-patch' so you'll get a -1 if a build failed (assuming you will not merge with -1 from CI). 2. post merge - look for emails on failed artifacts on your change (you will have to fix the job and then re-trigger the change) 3. you can see all current broken failed artifacts jobs in jenkins under 'unstable critical' view [1] and you will know if your project is being deployed. 4. Remove the broken OS from your project ( either from Jenkins or from your automation dir if you're using V2 ) - ask us for help! this should be an easy patch 5.Don't add new OS builds until you're absolutly sure they work ( you can add check-patch to keep testing it, but don't add build-artifacts until its stable ). Please contact myself or anyone else from the CI team for assistance or questions and we would be happy to help. [1] http://jenkins.ovirt.org/ Thank you, Dafna

4 3

Build failed in Jenkins: system-sync_mirrors-centos-updates-el7-x86_64 #1305
by jenkins＠jenkins.phx.ovirt.org 24 Feb '18

24 Feb '18

See <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-updates-el7-x86_64/…> ------------------------------------------ Started by timer [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-updates-el7-x86_64/…> > 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 969a8aab0fd2334b47c2c55e7867b2f4248a8b90 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 969a8aab0fd2334b47c2c55e7867b2f4248a8b90 Commit message: "ovirt-image-uploader: drop master jobs" > git rev-list --no-walk 969a8aab0fd2334b47c2c55e7867b2f4248a8b90 # timeout=10 [system-sync_mirrors-centos-updates-el7-x86_64] $ /bin/bash -xe /tmp/jenkins606789742611228443.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror centos-updates-el7 x86_64 jenkins/data/mirrors-reposync.conf Checking if mirror needs a resync 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 1474, in _commonLoadRepoXML if self._latestRepoXML(local): File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1452, in _latestRepoXML repomd = self.metalink_data.repomd File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 918, in <lambda> metalink_data = property(fget=lambda self: self._getMetalink(), File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 914, in _getMetalink self._metalink = metalink.MetaLinkRepoMD(self.metalink_filename) File "/usr/lib/python2.7/site-packages/yum/metalink.py", line 189, in __init__ raise MetaLinkRepoErrorParseFail, "File %s is not XML" % filename yum.metalink.MetaLinkRepoErrorParseFail: File /home/jenkins/mirrors_cache/fedora-base-fcraw/metalink.xml is not XML Build step 'Execute shell' marked build as failure

1 1

[CQ]: 87803, 2 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 24 Feb '18

24 Feb '18

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

1 0

[CQ]: 88015, 2 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 24 Feb '18

24 Feb '18

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

1 0

[CQ]: 87858, 3 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 24 Feb '18

24 Feb '18

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

1 0

[oVirt Jenkins] ovirt-system-tests_he-basic-ansible-suite-master - Build # 47 - Failure!
by jenkins＠jenkins.phx.ovirt.org 23 Feb '18

23 Feb '18

------=_Part_45_1872337951.1519352989993 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-ansible-suite-mast… Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-ansible-suite-mast… Build Number: 47 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #47 [Your Name] networking: Introducing mac pools and overlap range usage tests [Barak Korren] Install/Update mock from global_setup.sh [Sandro Bonazzola] ovirt-image-uploader: drop master jobs ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_45_1872337951.1519352989993--

3 4

OST Failure - Weekly update [17/02/2018-23/02/2018]
by Dafna Ron 23 Feb '18

23 Feb '18

Hello, I would like to update on this week's failures and OST current status. I am happy to say at the end of this week we do not have any failed changes. We had 5 reported failed changes this week: 1. replace vdsm stats with collectd virt plugin - https://gerrit.ovirt.org/#/c/87310/ - date: 20-02-2018 - version: Ovirt 4.2 - test failed: 003_00_metrics_bootstrap.metrics_and_log_collector - fix: fixed bug in initial validations - https://gerrit.ovirt.org/#/c/87919/ 2. replace vdsm stats with collectd virt plugin - https://gerrit.ovirt.org/#/c/87310/ - date: 21-02-2018 - version: Ovirt Master - test failed: 098_ovirt_provider_ovn.use_ovn_provider - NO FIX WAS REPORTED 3. ansible: End playbook based on initial validations - https://gerrit.ovirt.org/#/c/88062/ - date: 22-02-2018 - version: Ovirt Master - Test failed: 003_00_metrics_bootstrap.metrics_and_log_collector - Fix: bug reported: https://bugzilla.redhat.com/show_bug.cgi?id=1548087 4. momIF: change the way we connect to MOM - https://gerrit.ovirt.org/#/c/87944/ - date: 22-02-2018 - version: Ovirt Master - Test failed: 002_bootstrap.verify_add_hosts + 002_bootstrap.add_hosts - Fix: change was reverted until its fixed 5. Require collectd-virt plugin - https://gerrit.ovirt.org/#/c/87311/ - date: 22-02-2018 - version: Ovirt Master - Test: failed: 002_bootstrap.add_hosts - Fix: Require collectd-virt plugin - https://gerrit.ovirt.org/#/c/87311/ *Below you can see the chart for this week's resolved issues but cause of failure: * Code= regression of working components/functionalities Configurations - package related issues Other = failed build artifacts Infra = infrastructure/OST/Lago related issues [image: Inline image 1] [image: Inline image 2] *Below is a chart of resolved failures based on ovirt version* *[image: Inline image 3]* *[image: Inline image 4]* *Below is a chart showing failures by suite type: * * Suite type None means that it was a failure that did not result in a failed test such artificts related or packaging related. [image: Inline image 5] We are currently working on creating more statistics and defining the type of information it would be interesting to present. if there is anything specific that you would be interested in please let us know and we would add that to our plans. Many thanks, Dafna Ron

1 0

[oVirt Jenkins] ovirt-appliance_master_build-artifacts-el7-x86_64 - Build # 713 - Failure!
by jenkins＠jenkins.phx.ovirt.org 23 Feb '18

23 Feb '18

------=_Part_39_108743293.1519309369239 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-appliance_master_build-artifacts-el7-x86… Build: http://jenkins.ovirt.org/job/ovirt-appliance_master_build-artifacts-el7-x86… Build Number: 713 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #713 [dfodor] Added Dafna Hirschfeld to jenkins whitelist [Barak Korren] Make OST timed jobs congifure Git user and Email [Barak Korren] Install/Update mock from global_setup.sh [Sandro Bonazzola] ovirt-image-uploader: drop master jobs [Yuval Turgeman] appliance-report: try to mount /var ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_39_108743293.1519309369239--

1 1

Build failed in Jenkins: system-sync_mirrors-epel-el6-x86_64 #1227
by jenkins＠jenkins.phx.ovirt.org 23 Feb '18

23 Feb '18

See <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/1227/displ…> ------------------------------------------ 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-epel-el6-x86_64/ws/> > 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 969a8aab0fd2334b47c2c55e7867b2f4248a8b90 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 969a8aab0fd2334b47c2c55e7867b2f4248a8b90 Commit message: "ovirt-image-uploader: drop master jobs" > git rev-list --no-walk 969a8aab0fd2334b47c2c55e7867b2f4248a8b90 # timeout=10 [system-sync_mirrors-epel-el6-x86_64] $ /bin/bash -xe /tmp/jenkins4743645426874000219.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror epel-el6 x86_64 jenkins/data/mirrors-reposync.conf Checking if mirror needs a resync 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 1474, in _commonLoadRepoXML if self._latestRepoXML(local): File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1452, in _latestRepoXML repomd = self.metalink_data.repomd File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 918, in <lambda> metalink_data = property(fget=lambda self: self._getMetalink(), File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 914, in _getMetalink self._metalink = metalink.MetaLinkRepoMD(self.metalink_filename) File "/usr/lib/python2.7/site-packages/yum/metalink.py", line 189, in __init__ raise MetaLinkRepoErrorParseFail, "File %s is not XML" % filename yum.metalink.MetaLinkRepoErrorParseFail: File /home/jenkins/mirrors_cache/fedora-updates-fc26/metalink.xml is not XML Build step 'Execute shell' marked build as failure

1 1

Is CI broken on 3.6 branch?
by Ala Hino 23 Feb '18

23 Feb '18

Hi, I have a patch on 3.6 branch and CI seems to be broken: CI: http://jenkins.ovirt.org/job/vdsm_3.6_check-patch-el7-x86_64/292/ Patch: https://gerrit.ovirt.org/88045 Another CI triggered yesterday by Francesco but not completed yet. Please advice.

2 1

[oVirt Jenkins] ovirt-system-tests_performance-suite-master - Build # 105 - Failure!
by jenkins＠jenkins.phx.ovirt.org 22 Feb '18

22 Feb '18

------=_Part_15_1173894515.1519180818940 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Project: http://jenkins.ovirt.org/job/ovirt-system-tests_performance-suite-= master/=20 Build: http://jenkins.ovirt.org/job/ovirt-system-tests_performance-suite-ma= ster/105/ Build Number: 105 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #105 [Gal Ben Haim] master: Update reposync-config [Daniel Belenky] std enqueue: Add env.GERRIT_TRIGGER_CI_VOTE_LABEL [Daniel Belenky] cleanup: Fix race when unmounting dirs in chroot [Daniel Belenky] Add a tool to check if a change is merged [Sandro Bonazzola] ovirt-provider-ovn: drop manual jobs [Dafna Ron] jenkins: adding infra(a)ovirt.org to the alert list [Barak Korren] Run `pusher.py` on non-Gerrit events [Daniel Belenky] Utilize stdci_dsl api in standard-stage ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 040_add_hosts_vms.verify_add_hosts Error Message: 1 hosts failed installation: lago-performance-suite-master-host-0: install_failed -------------------- >> begin captured logging << -------------------- ovirtlago.testlib: ERROR: * Unhandled exception in <function <lambda> a= t 0x459ba28> Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 219, i= n assert_equals_within res =3D func() File "/home/jenkins/workspace/ovirt-system-tests_performance-suite-master= /ovirt-system-tests/performance-suite-master/test-scenarios/040_add_hosts_v= ms.py", line 293, in <lambda> lambda: _single_host_up(hosts_service, total_hosts) File "/home/jenkins/workspace/ovirt-system-tests_performance-suite-master= /ovirt-system-tests/performance-suite-master/test-scenarios/040_add_hosts_v= ms.py", line 166, in _single_host_up _check_problematic_hosts(hosts_service) File "/home/jenkins/workspace/ovirt-system-tests_performance-suite-master= /ovirt-system-tests/performance-suite-master/test-scenarios/040_add_hosts_v= ms.py", line 175, in _check_problematic_hosts raise RuntimeError(dump_hosts) RuntimeError: 1 hosts failed installation: lago-performance-suite-master-host-0: install_failed --------------------- >> end captured logging << --------------------- Stack Trace: 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 runTes= t self.test(*self.arg) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 129, i= n wrapped_test test() File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 59, in= wrapper return func(get_test_prefix(), *args, **kwargs) File "/home/jenkins/workspace/ovirt-system-tests_performance-suite-master= /ovirt-system-tests/performance-suite-master/test-scenarios/040_add_hosts_v= ms.py", line 285, in verify_add_hosts verify_add_hosts_4(api) File "/home/jenkins/workspace/ovirt-system-tests_performance-suite-master= /ovirt-system-tests/performance-suite-master/test-scenarios/040_add_hosts_v= ms.py", line 293, in verify_add_hosts_4 lambda: _single_host_up(hosts_service, total_hosts) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 271, i= n assert_true_within_long assert_equals_within_long(func, True, allowed_exceptions) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 258, i= n assert_equals_within_long func, value, LONG_TIMEOUT, allowed_exceptions=3Dallowed_exceptions File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 219, i= n assert_equals_within res =3D func() File "/home/jenkins/workspace/ovirt-system-tests_performance-suite-master= /ovirt-system-tests/performance-suite-master/test-scenarios/040_add_hosts_v= ms.py", line 293, in <lambda> lambda: _single_host_up(hosts_service, total_hosts) File "/home/jenkins/workspace/ovirt-system-tests_performance-suite-master= /ovirt-system-tests/performance-suite-master/test-scenarios/040_add_hosts_v= ms.py", line 166, in _single_host_up _check_problematic_hosts(hosts_service) File "/home/jenkins/workspace/ovirt-system-tests_performance-suite-master= /ovirt-system-tests/performance-suite-master/test-scenarios/040_add_hosts_v= ms.py", line 175, in _check_problematic_hosts raise RuntimeError(dump_hosts) '1 hosts failed installation:\nlago-performance-suite-master-host-0: instal= l_failed\n\n-------------------- >> begin captured logging << -------------= -------\novirtlago.testlib: ERROR: * Unhandled exception in <function <= lambda> at 0x459ba28>\nTraceback (most recent call last):\n File "/usr/lib= /python2.7/site-packages/ovirtlago/testlib.py", line 219, in assert_equals_= within\n res =3D func()\n File "/home/jenkins/workspace/ovirt-system-te= sts_performance-suite-master/ovirt-system-tests/performance-suite-master/te= st-scenarios/040_add_hosts_vms.py", line 293, in <lambda>\n lambda: _sin= gle_host_up(hosts_service, total_hosts)\n File "/home/jenkins/workspace/ov= irt-system-tests_performance-suite-master/ovirt-system-tests/performance-su= ite-master/test-scenarios/040_add_hosts_vms.py", line 166, in _single_host_= up\n _check_problematic_hosts(hosts_service)\n File "/home/jenkins/work= space/ovirt-system-tests_performance-suite-master/ovirt-system-tests/perfor= mance-suite-master/test-scenarios/040_add_hosts_vms.py", line 175, in _chec= k_problematic_hosts\n raise RuntimeError(dump_hosts)\nRuntimeError: 1 ho= sts failed installation:\nlago-performance-suite-master-host-0: install_fai= led\n\n--------------------- >> end captured logging << -------------------= --' ------=_Part_15_1173894515.1519180818940--

1 2

[CQ]: 87909, 3 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 22 Feb '18

22 Feb '18

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

1 0

[ OST Failure Report ] [ oVirt Master (vdsm) ] [ 22-02-2018 ] [ 002_bootstrap.verify_add_hosts + 002_bootstrap.add_hosts ]
by Dafna Ron 22 Feb '18

22 Feb '18

Hi, We had two failed tests reported in vdsm project last evening the patch reported seems to be related to the issue. *Link and headline of suspected patches: momIF: change the way we connect to MOM - https://gerrit.ovirt.org/#/c/87944/ <https://gerrit.ovirt.org/#/c/87944/>Link to Job:http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5823/ <http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5823/>Link to all logs:http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5823/art… <http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5823/artifacts>(Relevant) error snippet from the log: <error>* 2018-02-21 14:15:47,576-0500 INFO (MainThread) [vdsm.api] FINISH prepareForShutdown return=None from=internal, task_id=7d37a33b-0215-40c0-a821-9b94707caca6 (api:52) 2018-02-21 14:15:47,576-0500 ERROR (MainThread) [vds] Exception raised (vdsmd:158) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/vdsmd.py", line 156, in run serve_clients(log) File "/usr/lib/python2.7/site-packages/vdsm/vdsmd.py", line 103, in serve_clients cif = clientIF.getInstance(irs, log, scheduler) File "/usr/lib/python2.7/site-packages/vdsm/clientIF.py", line 251, in getInstance cls._instance = clientIF(irs, log, scheduler) File "/usr/lib/python2.7/site-packages/vdsm/clientIF.py", line 121, in __init__ self.mom = MomClient(config.get("mom", "socket_path")) File "/usr/lib/python2.7/site-packages/vdsm/momIF.py", line 51, in __init__ raise MomNotAvailableError() MomNotAvailableError *</error>*

2 2

[CQ]: 87861, 7 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 22 Feb '18

22 Feb '18

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

1 0

[oVirt Jenkins] ovirt-system-tests_he-basic-suite-4.1 - Build # 193 - Failure!
by jenkins＠jenkins.phx.ovirt.org 22 Feb '18

22 Feb '18

------=_Part_35_942998134.1519270042875 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-4.1= /=20 Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-4.1/1= 93/ Build Number: 193 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #193 [Eyal Edri] 4.2: replace python-ioprocess with python2-ioprocess [Daniel Belenky] Add production pipeline jobs for Jenkins project [Daniel Belenky] Add data normalizer param to nested config [Eyal Edri] remove vdsm 3.6 build-artifacts [Barak Korren] Fix '.git' bug in `pushe.py` [Barak Korren] Make OST timed jobs congifure Git user and Email ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 002_bootstrap.add_secondary_storage_domains Error Message: Fault reason is "Operation Failed". Fault detail is "[Network error during = communication with the Host.]". HTTP response code is 400. -------------------- >> begin captured logging << -------------------- lago.utils: ERROR: Error while running thread Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/lago/utils.py", line 58, in _ret_v= ia_queue queue.put({'return': func()}) File "/home/jenkins/workspace/ovirt-system-tests_he-basic-suite-4.1/ovirt= -system-tests/he-basic-suite-4.1/test-scenarios/002_bootstrap.py", line 637= , in add_templates_storage_domain add_generic_nfs_storage_domain(prefix, SD_TEMPLATES_NAME, SD_TEMPLATES_= HOST_NAME, SD_TEMPLATES_PATH, sd_format=3D'v1', sd_type=3D'export') File "/home/jenkins/workspace/ovirt-system-tests_he-basic-suite-4.1/ovirt= -system-tests/he-basic-suite-4.1/test-scenarios/002_bootstrap.py", line 496= , in add_generic_nfs_storage_domain add_generic_nfs_storage_domain_4(prefix, sd_nfs_name, nfs_host_name, mo= unt_path, sd_format, sd_type, nfs_version) File "/home/jenkins/workspace/ovirt-system-tests_he-basic-suite-4.1/ovirt= -system-tests/he-basic-suite-4.1/test-scenarios/002_bootstrap.py", line 552= , in add_generic_nfs_storage_domain_4 _add_storage_domain_4(api, p) File "/home/jenkins/workspace/ovirt-system-tests_he-basic-suite-4.1/ovirt= -system-tests/he-basic-suite-4.1/test-scenarios/002_bootstrap.py", line 447= , in _add_storage_domain_4 sd =3D sds_service.add(p) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 238= 95, in add return self._internal_add(storage_domain, headers, query, wait) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 232,= in _internal_add return future.wait() if wait else future File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 55, = in wait return self._code(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 229,= in callback self._check_fault(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 132,= in _check_fault self._raise_error(response, body) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 118,= in _raise_error raise error Error: Fault reason is "Operation Failed". Fault detail is "[Network error = during communication with the Host.]". HTTP response code is 400. --------------------- >> end captured logging << --------------------- Stack Trace: 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 runTes= t self.test(*self.arg) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 129, i= n wrapped_test test() File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 59, in= wrapper return func(get_test_prefix(), *args, **kwargs) File "/home/jenkins/workspace/ovirt-system-tests_he-basic-suite-4.1/ovirt= -system-tests/he-basic-suite-4.1/test-scenarios/002_bootstrap.py", line 577= , in add_secondary_storage_domains vt.join_all() File "/usr/lib/python2.7/site-packages/lago/utils.py", line 58, in _ret_v= ia_queue queue.put({'return': func()}) File "/home/jenkins/workspace/ovirt-system-tests_he-basic-suite-4.1/ovirt= -system-tests/he-basic-suite-4.1/test-scenarios/002_bootstrap.py", line 637= , in add_templates_storage_domain add_generic_nfs_storage_domain(prefix, SD_TEMPLATES_NAME, SD_TEMPLATES_= HOST_NAME, SD_TEMPLATES_PATH, sd_format=3D'v1', sd_type=3D'export') File "/home/jenkins/workspace/ovirt-system-tests_he-basic-suite-4.1/ovirt= -system-tests/he-basic-suite-4.1/test-scenarios/002_bootstrap.py", line 496= , in add_generic_nfs_storage_domain add_generic_nfs_storage_domain_4(prefix, sd_nfs_name, nfs_host_name, mo= unt_path, sd_format, sd_type, nfs_version) File "/home/jenkins/workspace/ovirt-system-tests_he-basic-suite-4.1/ovirt= -system-tests/he-basic-suite-4.1/test-scenarios/002_bootstrap.py", line 552= , in add_generic_nfs_storage_domain_4 _add_storage_domain_4(api, p) File "/home/jenkins/workspace/ovirt-system-tests_he-basic-suite-4.1/ovirt= -system-tests/he-basic-suite-4.1/test-scenarios/002_bootstrap.py", line 447= , in _add_storage_domain_4 sd =3D sds_service.add(p) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 238= 95, in add return self._internal_add(storage_domain, headers, query, wait) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 232,= in _internal_add return future.wait() if wait else future File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 55, = in wait return self._code(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 229,= in callback self._check_fault(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 132,= in _check_fault self._raise_error(response, body) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 118,= in _raise_error raise error 'Fault reason is "Operation Failed". Fault detail is "[Network error during= communication with the Host.]". HTTP response code is 400.\n--------------= ------ >> begin captured logging << --------------------\nlago.utils: ERROR= : Error while running thread\nTraceback (most recent call last):\n File "/= usr/lib/python2.7/site-packages/lago/utils.py", line 58, in _ret_via_queue\= n queue.put({\'return\': func()})\n File "/home/jenkins/workspace/ovirt= -system-tests_he-basic-suite-4.1/ovirt-system-tests/he-basic-suite-4.1/test= -scenarios/002_bootstrap.py", line 637, in add_templates_storage_domain\n = add_generic_nfs_storage_domain(prefix, SD_TEMPLATES_NAME, SD_TEMPLATES_HO= ST_NAME, SD_TEMPLATES_PATH, sd_format=3D\'v1\', sd_type=3D\'export\')\n Fi= le "/home/jenkins/workspace/ovirt-system-tests_he-basic-suite-4.1/ovirt-sys= tem-tests/he-basic-suite-4.1/test-scenarios/002_bootstrap.py", line 496, in= add_generic_nfs_storage_domain\n add_generic_nfs_storage_domain_4(prefi= x, sd_nfs_name, nfs_host_name, mount_path, sd_format, sd_type, nfs_version)= \n File "/home/jenkins/workspace/ovirt-system-tests_he-basic-suite-4.1/ovi= rt-system-tests/he-basic-suite-4.1/test-scenarios/002_bootstrap.py", line 5= 52, in add_generic_nfs_storage_domain_4\n _add_storage_domain_4(api, p)\= n File "/home/jenkins/workspace/ovirt-system-tests_he-basic-suite-4.1/ovir= t-system-tests/he-basic-suite-4.1/test-scenarios/002_bootstrap.py", line 44= 7, in _add_storage_domain_4\n sd =3D sds_service.add(p)\n File "/usr/li= b64/python2.7/site-packages/ovirtsdk4/services.py", line 23895, in add\n = return self._internal_add(storage_domain, headers, query, wait)\n File "/= usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 232, in _inte= rnal_add\n return future.wait() if wait else future\n File "/usr/lib64/= python2.7/site-packages/ovirtsdk4/service.py", line 55, in wait\n return= self._code(response)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4= /service.py", line 229, in callback\n self._check_fault(response)\n Fil= e "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 132, in _= check_fault\n self._raise_error(response, body)\n File "/usr/lib64/pyth= on2.7/site-packages/ovirtsdk4/service.py", line 118, in _raise_error\n r= aise error\nError: Fault reason is "Operation Failed". Fault detail is "[Ne= twork error during communication with the Host.]". HTTP response code is 40= 0.\n--------------------- >> end captured logging << ---------------------' ------=_Part_35_942998134.1519270042875--

1 1

[CQ]: 84106, 6 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 22 Feb '18

22 Feb '18

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

1 0

[ OST Failure Report ] [ oVirt Master (ovirt-engine-metrics) ] [ 22-02-2018 ] [ 003_00_metrics_bootstrap.metrics_and_log_collector ]
by Dafna Ron 22 Feb '18

22 Feb '18

hi, We are failing test 003_00_metrics_bootstrap.metrics_and_log_collector for basic suite. *Link and headline of suspected patches: * *ansible: End playbook based on initial validations - https://gerrit.ovirt.org/#/c/88062/ <https://gerrit.ovirt.org/#/c/88062/>Link to Job:http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5829/ <http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5829/>Link to all logs:http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5829/art… <http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5829/artifacts>(Relevant) error snippet from the log: <error>* /var/tmp: drwxr-x--x. root abrt system_u:object_r:abrt_var_cache_t:s0 abrt -rw-------. root root unconfined_u:object_r:user_tmp_t:s0 rpm-tmp.aLitM7 -rw-------. root root unconfined_u:object_r:user_tmp_t:s0 rpm-tmp.G2r7IM -rw-------. root root unconfined_u:object_r:user_tmp_t:s0 rpm-tmp.kVymZE -rw-------. root root unconfined_u:object_r:user_tmp_t:s0 rpm-tmp.uPDvvU drwx------. root root system_u:object_r:tmp_t:s0 systemd-private-cd49c74726d5463f8d6f6502380e5e12-chronyd.service-i1T5IE drwx------. root root system_u:object_r:tmp_t:s0 systemd-private-cd49c74726d5463f8d6f6502380e5e12-systemd-timedated.service-lhoUsS /var/tmp/abrt: -rw-------. root root system_u:object_r:abrt_var_cache_t:s0 last-via-server /var/tmp/systemd-private-cd49c74726d5463f8d6f6502380e5e12-chronyd.service-i1T5IE: drwxrwxrwt. root root system_u:object_r:tmp_t:s0 tmp /var/tmp/systemd-private-cd49c74726d5463f8d6f6502380e5e12-chronyd.service-i1T5IE/tmp: /var/tmp/systemd-private-cd49c74726d5463f8d6f6502380e5e12-systemd-timedated.service-lhoUsS: drwxrwxrwt. root root system_u:object_r:tmp_t:s0 tmp /var/tmp/systemd-private-cd49c74726d5463f8d6f6502380e5e12-systemd-timedated.service-lhoUsS/tmp: /var/yp: ) 2018-02-22 07:24:05::DEBUG::__main__::251::root:: STDERR(/bin/ls: cannot open directory /rhev/data-center/mnt/blockSD/6babba93-09c8-4846-9ccb-07728f72eecb/master/tasks/bd563276-5092-4d28-86c4-63aa6c0b4344.temp: No such file or directory ) 2018-02-22 07:24:05::ERROR::__main__::832::root:: Failed to collect logs from: lago-basic-suite-master-host-0; /bin/ls: cannot open directory /rhev/data-center/mnt/blockSD/6babba93-09c8-4846-9ccb-07728f72eecb/master/tasks/bd563276-5092-4d28-86c4-63aa6c0b4344.temp: No such file or directory *</error>*

2 1

Re: Change in ovirt-engine[master]: packaging: setup: postgres95: Fixes
by Yedidyah Bar David 22 Feb '18

22 Feb '18

On Tue, Feb 20, 2018 at 12:04 PM, Code Review <gerrit(a)ovirt.org> wrote: > Jenkins CI posted comments on this change. > > View Change > > Patch set 9: > > Build Failed > > http://jenkins.ovirt.org/job/ovirt-engine_master_check-merged-fc27-x86_64/1… > : FAILURE > > http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-el7-x86_64… > : FAILURE 09:07:32 > git clean -fdx # timeout=10 09:07:36 ERROR: Error fetching remote repo 'origin' 09:07:36 hudson.plugins.git.GitException: Failed to fetch from git://gerrit.ovirt.org/ovirt-engine.git ... 09:07:36 stderr: warning: failed to remove exported-artifacts/tests: Permission denied 09:07:36 warning: failed to remove output/ovirt-engine-4.3.0-0.0.master.20180220072827.git1987ee4.el7.centos.src.rpm: Permission denied 09:07:36 warning: failed to remove rpmbuild/SPECS/ovirt-engine.spec: Permission denied 09:07:36 warning: failed to remove rpmbuild/SOURCES/ovirt-engine-4.3.0_master.tar.gz: Permission denied 09:07:36 warning: failed to remove rpmbuild/BUILD/ovirt-engine-4.3.0/.gitignore: Permission denied 09:07:36 warning: failed to remove rpmbuild/BUILD/ovirt-engine-4.3.0/.gitreview: Permission denied ... Known issue? Bad permissions in some slave(s)? > > http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-fcraw-x86_… > : SUCCESS > > http://jenkins.ovirt.org/job/ovirt-engine_master_check-merged-el7-x86_64/75… > : SUCCESS > > http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-fc27-x86_6… > : SUCCESS > > http://jenkins.ovirt.org/job/ovirt-engine_master_check-merged-fcraw-x86_64/… > : SUCCESS > > http://jenkins.ovirt.org/job/standard-enqueue/10362/ : > This change was successfully submitted to the change queue(s) for system > testing. > > To view, visit change 85543. To unsubscribe, visit settings. > > Gerrit-Project: ovirt-engine > Gerrit-Branch: master > Gerrit-MessageType: comment > Gerrit-Change-Id: I5b4430bfe79df9a4c0e0ffc1696c821e20584eb3 > Gerrit-Change-Number: 85543 > Gerrit-PatchSet: 9 > Gerrit-Owner: Yedidyah Bar David <didi(a)redhat.com> > Gerrit-Reviewer: Ido Rosenzwig <irosenzw(a)redhat.com> > Gerrit-Reviewer: Jenkins CI > Gerrit-Reviewer: Lev Veyde <lveyde(a)redhat.com> > Gerrit-Reviewer: Rafael Martins <rafael(a)rafaelmartins.eng.br> > Gerrit-Reviewer: Sandro Bonazzola <sbonazzo(a)redhat.com> > Gerrit-Reviewer: Simone Tiraboschi <stirabos(a)redhat.com> > Gerrit-Reviewer: Yedidyah Bar David <didi(a)redhat.com> > Gerrit-Reviewer: gerrit-hooks <automation(a)ovirt.org> > Gerrit-Comment-Date: Tue, 20 Feb 2018 10:04:20 +0000 > Gerrit-HasComments: No -- Didi

1 0

[CQ]: 88062, 6 (ovirt-engine-metrics) failed "ovirt-master" system tests
by oVirt Jenkins 22 Feb '18

22 Feb '18

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

1 0

[ OST Failure Report ] [ oVirt Master (ovirt-host) ] [ 22-02-2018 ] [002_bootstrap.add_hosts ]
by Dafna Ron 22 Feb '18

22 Feb '18

hi, we have a failed test for ovirt-host in upgrade suite. *Link and headline of suspected patches: * *Require collectd-virt plugin - https://gerrit.ovirt.org/#/c/87311/ <https://gerrit.ovirt.org/#/c/87311/>Link to Job: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5827/ <http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5827/>Link to all logs:http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5827/art… <http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5827/artifacts>(Relevant) error snippet from the log: <error>* 2018-02-22 05:38:47,587-05 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (VdsDeploy) [546df98d] EVENT_ID: VDS_INSTALL_IN_PROGRESS(509), Installing Host lago-upgrade-from-release-suite-master-host0. Setting kernel arguments. 2018-02-22 05:38:47,858-05 ERROR [org.ovirt.engine.core.uutils.ssh.SSHDialog] (EE-ManagedThreadFactory-engine-Thread-1) [546df98d] Swallowing exception as preferring stderr 2018-02-22 05:38:47,859-05 ERROR [org.ovirt.engine.core.uutils.ssh.SSHDialog] (EE-ManagedThreadFactory-engine-Thread-1) [546df98d] SSH error running command root@lago-upgrade-from-release-suite-master-host0:'umask 0077; MYTMP="$(TMPDIR="${OVIRT_TMPDIR}" mktemp -d -t ovirt-XXXXXXXXXX)"; trap "chmod -R u+rwX \"${MYTMP}\" > /dev/null 2>&1; rm -fr \"${MYTMP}\" > /dev/null 2>&1" 0; tar --warning=no-timestamp -C "${MYTMP}" -x && "${MYTMP}"/ovirt-host-deploy DIALOG/dialect=str:machine DIALOG/customization=bool:True': RuntimeException: Unexpected error during execution: bash: line 1: 1395 Segmentation fault "${MYTMP}"/ovirt-host-deploy DIALOG/dialect=str:machine DIALOG/customization=bool:True 2018-02-22 05:38:47,859-05 ERROR [org.ovirt.engine.core.bll.hostdeploy.VdsDeployBase] (VdsDeploy) [546df98d] Error during deploy dialog 2018-02-22 05:38:47,860-05 ERROR [org.ovirt.engine.core.bll.hostdeploy.VdsDeployBase] (EE-ManagedThreadFactory-engine-Thread-1) [546df98d] Error during host lago-upgrade-from-release-suite-master-host0 install 2018-02-22 05:38:47,864-05 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-1) [546df98d] EVENT_ID: VDS_INSTALL_IN_PROGRESS_ERROR(511), An error has occurred during installation of Host lago-upgrade-from-release-suite-master-host0: Unexpected error during execution: bash: line 1: 1395 Segmentation fault "${MYTMP}"/ovirt-host-deploy DIALOG/dialect=str:machine DIALOG/customization=bool:True . 2018-02-22 05:38:47,864-05 ERROR [org.ovirt.engine.core.bll.hostdeploy.VdsDeployBase] (EE-ManagedThreadFactory-engine-Thread-1) [546df98d] Error during host lago-upgrade-from-release-suite-master-host0 install, preferring first exception: Unexpected connection termination 2018-02-22 05:38:47,864-05 ERROR [org.ovirt.engine.core.bll.hostdeploy.InstallVdsInternalCommand] (EE-ManagedThreadFactory-engine-Thread-1) [546df98d] Host installation failed for host '65c048e5-a97a-422d-88b8-abe1fd925602', 'lago-upgrade-from-release-suite-master-host0': Unexpected connection termination 2018-02-22 05:38:47,869-05 INFO [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (EE-ManagedThreadFactory-engine-Thread-1) [546df98d] START, SetVdsStatusVDSCommand(HostName = lago-upgrade-from-release-suite-master-host0, SetVdsStatusVDSCommandParameters:{hostId='65c048e5-a97a-422d-88b8-abe1fd925602', status='InstallFailed', nonOperationalReason='NONE', stopSpmFailureLogged='false', maintenanceReason='null'}), log id: 1973b09c 2018-02-22 05:38:47,898-05 INFO [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (EE-ManagedThreadFactory-engine-Thread-1) [546df98d] FINISH, SetVdsStatusVDSCommand, log id: 1973b09c 2018-02-22 05:38:47,911-05 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-1) [546df98d] EVENT_ID: VDS_INSTALL_FAILED(505), Host lago-upgrade-from-release-suite-master-host0 installation failed. Unexpected connection termination. 2018-02-22 05:38:47,920-05 INFO [org.ovirt.engine.core.bll.hostdeploy.InstallVdsInternalCommand] (EE-ManagedThreadFactory-engine-Thread-1) [546df98d] Lock freed to object 'EngineLock:{exclusiveLocks='[65c048e5-a97a-422d-88b8-abe1fd925602=VDS]', sharedLocks=''}' *</error>*

1 0

[CQ]: 87311, 2 (ovirt-host) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 22 Feb '18

22 Feb '18

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

1 0

ovirt-engine-api-model jenkins jobs
by Sandro Bonazzola 22 Feb '18

22 Feb '18

Hi, I'm investigating on a failure[2 <http://jenkins.ovirt.org/job/ovirt-engine-api-model_master_build-artifacts-…>] on jenkins jobs for ovirt-engine-api-model[1 <http://jenkins.ovirt.org/search/?q=ovirt-engine-api-model_master_build-arti…>] on el7. Before I further invest time on it, I'd like to understand the purpose of the job. As far as I can tell the project is building some documentation in different formats and a tarball with the sources: asciidoctor.css 28.92 KB model.adoc 1.24 MB model.csv 264.77 KB model.html 3.37 MB model.json 7.39 MB model.xml 6.09 MB ovirt-engine-api-model-4.3.8.20180213gita1f6d9a.tar.gz 246.48 KB I think that some way the output may be used by http://ovirt.github.io/ovirt-engine-api-model/ but I don't feel like this is really done. I also see that artifacts are published on https://search.maven.org/#artifactdetails%7Corg.ovirt.engine.api%7Cmodel%7C… <https://search.maven.org/#artifactdetails%7Corg.ovirt.engine.api%7Cmodel%7C…> but this is also not done by the jenkins jobs. I see this artifacts is required in ovirt-engine pom.xml: <model.version>4.3.7</model.version> So I would expect the job to prepare a rpm including this jar and pom to be required in ovirt-engine spec file, at least if we follow Fedora packaging guidelines. As is, this jobs seams meaningless. What should we do here? Drop the job? Fix it for building rpms? [1] http://jenkins.ovirt.org/search/?q=ovirt-engine-api-model_master_build-arti… [2] http://jenkins.ovirt.org/job/ovirt-engine-api-model_master_build-artifacts-… -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

2 2

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

21 Feb '18

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

1 0

oVirt infra weekly meeting notes 21.02.2018
by Evgheni Dereveanchin 21 Feb '18

21 Feb '18

Hi everyone, Please find the topics of this week's infra meeting below: We had Sahil join the meeting who volunteered to help with the infra - we can start working on improving ovirt-infra-docs.readthedocs.io - patches can be sent to gerrit: https://gerrit.ovirt.org/#/admin/projects/infra-docs *PHX DC - Jenkins updated, puppet bug caused service restarts- Several VMs had ipv6 disabled - fixed- Resources was slow due to a VM imposing load on storage- Cockpit QA requested 2 PPC VMs for testingAI - Split global_setup patch into individual functions and merge one by one- Update mirror snapshots to get the new mock* -- Regards, Evgheni Dereveanchin

1 0

CentOS Virt SIG - oVirt 4.3 repositories
by Sandro Bonazzola 21 Feb '18

21 Feb '18

Hi, tags have been created for oVirt 4.3 development. I'm going to cross tag dependencies from oVirt 4.2 to oVirt 4.3 in the next weeks. Once done, I'll push patches to oVirt System Test master and oVirt Release master switching from oVirt 4.2 to oVirt 4.3. Repositories that will contain 4.3 related stuff while I'm working on it: https://cbs.centos.org/repos/virt7-ovirt-43-candidate https://cbs.centos.org/repos/virt7-ovirt-common-candidate Once I'll be sure master works with these, I'll tag for testing switching to: https://cbs.centos.org/repos/virt7-ovirt-43-testing https://cbs.centos.org/repos/virt7-ovirt-common-testing Once repoclosure passes, I'll ask to start signing and publishing rpms for testing getting the rpms into final testing destination: https://buildlogs.centos.org/centos/7/virt/$basearch/ovirt-4.3/ This will be the repo that will be added to OST and ovirt-release. If new dependencies needs to be added to 4.3 repo during this process, please let me know. Thanks -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

1 0

[JIRA] (OVIRT-1908) jenkins_master_check-patch: Can't find push details for remote URL in the push map file
by Evgheni Dereveanchin (oVirt JIRA) 21 Feb '18

21 Feb '18

This is a multi-part message in MIME format... ------------=_1519215898-32323-211 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1908?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-1908: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > jenkins_master_check-patch: Can't find push details for remote URL in the push map file > --------------------------------------------------------------------------------------- > > Key: OVIRT-1908 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1908 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > > check-patch is failing for the jenkins repo with a strange error: > 17:55:49 + /home/jenkins/workspace/jenkins_master_check-patch-fc25-x86_64/jenkins/scripts/pusher.py --log=/home/jenkins/workspace/jenkins_master_check-patch-fc25-x86_64/exported-artifacts/pusher_logs/push_jenkins.log push --if-not-exists --unless-hash=jenkins-jenkins_master_check-patch-fc25-x86_64-3415 master > 17:55:49 Can't find push details for remote URL: 'git://gerrit.ovirt.org/jenkins.git' in the push map file. > 17:55:49 Build step 'Execute shell' marked build as failure > Example failed jobs: > http://jenkins.ovirt.org/job/jenkins_master_check-patch-fc25-x86_64/3415/ > http://jenkins.ovirt.org/job/jenkins_master_check-patch-fcraw-x86_64/1072/ > http://jenkins.ovirt.org/job/jenkins_master_check-patch-fc27-x86_64/1051/ > http://jenkins.ovirt.org/job/jenkins_master_check-patch-el7-x86_64/3841/ > http://jenkins.ovirt.org/job/jenkins_master_check-patch-el7-ppc64le/960/ > http://jenkins.ovirt.org/job/jenkins_master_check-patch-fc24-x86_64/3572/ > http://jenkins.ovirt.org/job/jenkins_master_check-patch-fc26-x86_64/2293/ > http://jenkins.ovirt.org/job/jenkins_master_check-patch-el6-x86_64/3567/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100080) ------------=_1519215898-32323-211 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1908?page=com.atlassian.jira.… ]</pre> <h3>Evgheni Dereveanchin reassigned OVIRT-1908:</h3> <pre>Assignee: Evgheni Dereveanchin (was: infra)</pre> <blockquote><h3>jenkins_master_check-patch: Can't find push details for remote URL in the push map file</h3> <pre> Key: OVIRT-1908 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1908 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Evgheni Dereveanchin Assignee: Evgheni Dereveanchin</pre> <p>check-patch is failing for the jenkins repo with a strange error: 17:55:49 + /home/jenkins/workspace/jenkins_master_check-patch-fc25-x86_64/jenkins/scripts/pusher.py --log=/home/jenkins/workspace/jenkins_master_check-patch-fc25-x86_64/exported-artifacts/pusher_logs/push_jenkins.log push --if-not-exists --unless-hash=jenkins-jenkins_master_check-patch-fc25-x86_64-3415 master 17:55:49 Can't find push details for remote URL: ‘git://gerrit.ovirt.org/jenkins.git’ in the push map file. 17:55:49 Build step ‘Execute shell’ marked build as failure Example failed jobs: <a href="http://jenkins.ovirt.org/job/jenkins_master_check-patch-fc25-x86_64/3415/">http://jenkins.ovirt.org/job/jenkins_master_check-patch-fc25-x86_64/3415/</a> <a href="http://jenkins.ovirt.org/job/jenkins_master_check-patch-fcraw-x86_64/1072/">http://jenkins.ovirt.org/job/jenkins_master_check-patch-fcraw-x86_64/1072/</a> <a href="http://jenkins.ovirt.org/job/jenkins_master_check-patch-fc27-x86_64/1051/">http://jenkins.ovirt.org/job/jenkins_master_check-patch-fc27-x86_64/1051/</a> <a href="http://jenkins.ovirt.org/job/jenkins_master_check-patch-el7-x86_64/3841/">http://jenkins.ovirt.org/job/jenkins_master_check-patch-el7-x86_64/3841/</a> <a href="http://jenkins.ovirt.org/job/jenkins_master_check-patch-el7-ppc64le/960/">http://jenkins.ovirt.org/job/jenkins_master_check-patch-el7-ppc64le/960/</a> <a href="http://jenkins.ovirt.org/job/jenkins_master_check-patch-fc24-x86_64/3572/">http://jenkins.ovirt.org/job/jenkins_master_check-patch-fc24-x86_64/3572/</a> <a href="http://jenkins.ovirt.org/job/jenkins_master_check-patch-fc26-x86_64/2293/">http://jenkins.ovirt.org/job/jenkins_master_check-patch-fc26-x86_64/2293/</a> <a href="http://jenkins.ovirt.org/job/jenkins_master_check-patch-el6-x86_64/3567/">http://jenkins.ovirt.org/job/jenkins_master_check-patch-el6-x86_64/3567/</a></p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100080)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1519215898-32323-211--

1 0

[ OST Failure Report ] [ oVirt $VER (ovirt-log-collector) ] [ 21-02-2018 ] [ 098_ovirt_provider_ovn.use_ovn_provider ]
by Dafna Ron 21 Feb '18

21 Feb '18

Hi, We failed test on duplicate network name. I don't think that the change is related. I can see that we are importing network_1 and then trying to create a network by the same name. I don't think there was a change made to ovn before this failure that could have cause this to fail but adding Dan in case he is aware of any changes. *Link and headline of suspected patches: failed change: * inventory: handle to postgresql dumps from sosreport - https://gerrit.ovirt.org/#/c/88010/ *Change reported as root cause of failure: *collector: fix list function - https://gerrit.ovirt.org/#/c/87798/ *Link to Job:http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5805 <http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5805>Link to all logs:* http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5805/artifacts *(Relevant) error snippet from the log: <error>* 2018-02-20 23:51:03,179-05 DEBUG [org.ovirt.engine.core.dal.dbbroker.PostgresDbEngineDialect$PostgresSimpleJdbcCall] (default task-19) [4a0a588a-e606-4151-936a-f66a8c580a78] Compiled stored procedure. Call string is [{call getdcidbyexternalnetworkid(?)}] 2018-02-20 23:51:03,179-05 DEBUG [org.ovirt.engine.core.dal.dbbroker.PostgresDbEngineDialect$PostgresSimpleJdbcCall] (default task-19) [4a0a588a-e606-4151-936a-f66a8c580a78] SqlCall for procedure [GetDcIdByExternalNetworkId] compiled 2018-02-20 23:51:03,180-05 DEBUG [org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor] (default task-19) [4a0a588a-e606-4151-936a-f66a8c580a78] method: runQuery, params: [GetAllExternalNetworksOnProvider, IdQueryParameters:{refresh='false', filtered='false'}], timeElapsed: 266ms 2018-02-20 23:51:03,187-05 INFO [org.ovirt.engine.core.bll.network.dc.AddNetworkCommand] (default task-19) [4a0a588a-e606-4151-936a-f66a8c580a78] Lock Acquired to object 'EngineLock:{exclusiveLocks='[network_1=NETWORK, 94fc81b9-fbf2-4262-a877-32a066a573c2=PROVIDER]', sharedLocks=''}' 2018-02-20 23:51:03,190-05 WARN [org.ovirt.engine.core.bll.network.dc.AddNetworkCommand] (default task-19) [4a0a588a-e606-4151-936a-f66a8c580a78] Validation of action 'AddNetwork' failed for user admin@internal-authz. Reasons: VAR__TYPE__NETWORK,VAR__ACTION__ADD,ACTION_TYPE_FAILED_NETWORK_NAME_IN_USE,$NetworkName network_1 2018-02-20 23:51:03,190-05 INFO [org.ovirt.engine.core.bll.network.dc.AddNetworkCommand] (default task-19) [4a0a588a-e606-4151-936a-f66a8c580a78] Lock freed to object 'EngineLock:{exclusiveLocks='[network_1=NETWORK, 94fc81b9-fbf2-4262-a877-32a066a573c2=PROVIDER]', sharedLocks=''}' 2018-02-20 23:51:03,191-05 DEBUG [org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor] (default task-19) [4a0a588a-e606-4151-936a-f66a8c580a78] method: runAction, params: [AddNetwork, AddNetworkStoragePoolParameters:{commandId='41c44658-04e5-4aeb-9f65-cc2ad76e0c42', user='null', commandType='Unknown'}], timeElapsed: 10ms 2018-02-20 23:51:03,196-05 ERROR [org.ovirt.engine.api.restapi.resource.AbstractBackendResource] (default task-19) [] Operation Failed: [Cannot add Network. The name of the logical network 'network_1' is already used by an existing logical network in the same data-center. -Please choose a different name.] 2018-02-20 23:51:03,346-05 DEBUG [org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor] (EE-ManagedThreadFactory-engineScheduled-Thread-47) [] method: get, params: [da0bebdb-cb83-415f-bcba-8920126e31a4], timeElapsed: 6ms 2018-02-20 23:51:03,346-05 DEBUG [org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring] (EE-ManagedThreadFactory-engineScheduled-Thread-47) [] vdsManager::refreshVdsStats entered, host='lago-basic-suite-master-host-1'(da0bebdb-cb83-415f-bcba-8920126e31a4) 2018-02-20 23:51:03,365-05 DEBUG [org.ovirt.engine.core.vdsbroker.vdsbroker.GetStatsAsyncVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-47) [] START, GetStatsAsyncVDSCommand(HostName = lago-basic-suite-master-host-1, VdsIdAndVdsVDSCommandParametersBase:{hostId='da0bebdb-cb83-415f-bcba-8920126e31a4', vds='Host[lago-basic-suite-master-host-1,da0bebdb-cb83-415f-bcba-8920126e31a4]'}), log id: 279de334 2018-02-20 23:51:03,365-05 DEBUG [org.ovirt.vdsm.jsonrpc.client.reactors.stomp.impl.Message] (EE-ManagedThreadFactory-engineScheduled-Thread-47) [] SEND destination:jms.topic.vdsm_requests reply-to:jms.topic.vdsm_responses content-length:98 *</error>*

1 0

[JIRA] (OVIRT-1908) jenkins_master_check-patch: Can't find push details for remote URL in the push map file
by Barak Korren (oVirt JIRA) 21 Feb '18

21 Feb '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1908?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1908: ------------------------------------- The issue is that your jobs are running with an older version of {{pusher.py}} that is included in your patch that does not know how to properly resolve annotated tags into commit checksums. Please rebase your patch on the latest master. > jenkins_master_check-patch: Can't find push details for remote URL in the push map file > --------------------------------------------------------------------------------------- > > Key: OVIRT-1908 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1908 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Evgheni Dereveanchin > Assignee: infra > > check-patch is failing for the jenkins repo with a strange error: > 17:55:49 + /home/jenkins/workspace/jenkins_master_check-patch-fc25-x86_64/jenkins/scripts/pusher.py --log=/home/jenkins/workspace/jenkins_master_check-patch-fc25-x86_64/exported-artifacts/pusher_logs/push_jenkins.log push --if-not-exists --unless-hash=jenkins-jenkins_master_check-patch-fc25-x86_64-3415 master > 17:55:49 Can't find push details for remote URL: 'git://gerrit.ovirt.org/jenkins.git' in the push map file. > 17:55:49 Build step 'Execute shell' marked build as failure > Example failed jobs: > http://jenkins.ovirt.org/job/jenkins_master_check-patch-fc25-x86_64/3415/ > http://jenkins.ovirt.org/job/jenkins_master_check-patch-fcraw-x86_64/1072/ > http://jenkins.ovirt.org/job/jenkins_master_check-patch-fc27-x86_64/1051/ > http://jenkins.ovirt.org/job/jenkins_master_check-patch-el7-x86_64/3841/ > http://jenkins.ovirt.org/job/jenkins_master_check-patch-el7-ppc64le/960/ > http://jenkins.ovirt.org/job/jenkins_master_check-patch-fc24-x86_64/3572/ > http://jenkins.ovirt.org/job/jenkins_master_check-patch-fc26-x86_64/2293/ > http://jenkins.ovirt.org/job/jenkins_master_check-patch-el6-x86_64/3567/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100080)

1 0

[JIRA] (OVIRT-1907) mock: $STD_CI_YUMREPOS is declared even when --try-mirrors isn't specified
by Barak Korren (oVirt JIRA) 21 Feb '18

21 Feb '18

This is a multi-part message in MIME format... ------------=_1519210669-27720-153 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1907?page=com.atlassian.jira.… ] Barak Korren edited comment on OVIRT-1907 at 2/21/18 10:57 AM: --------------------------------------------------------------- Also the point of STD_CI_YUMREPOS is to make code able to find the yumrepos file regardless of wither it was injected into or not - so this is not really a bug. was (Author: bkorren(a)redhat.com) Also the point of STD_CI_YUMREPOS is to make code able to find the yumrepos file regardless of wither it was injected into or not - so this is not really a bog. > mock: $STD_CI_YUMREPOS is declared even when --try-mirrors isn't specified > -------------------------------------------------------------------------- > > Key: OVIRT-1907 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1907 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: CI Mirrors, mock_runner > Reporter: Gal Ben Haim > Assignee: infra > > This issue makes it hard to determine if mirrors injection occurred or not (from within the mock env). -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100080) ------------=_1519210669-27720-153 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1907?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren edited comment on OVIRT-1907 at 2/21/18 10:57 AM:</h3> <p>Also the point of STD_CI_YUMREPOS is to make code able to find the yumrepos file regardless of wither it was injected into or not – so this is not really a bug.</p> <p>was (Author: bkorren(a)redhat.com) Also the point of STD_CI_YUMREPOS is to make code able to find the yumrepos file regardless of wither it was injected into or not – so this is not really a bog.</p> <blockquote><h3>mock: $STD_CI_YUMREPOS is declared even when --try-mirrors isn't specified</h3> <pre> Key: OVIRT-1907 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1907 Project: oVirt - virtualization made easy Issue Type: Bug Components: CI Mirrors, mock_runner Reporter: Gal Ben Haim Assignee: infra</pre> <p>This issue makes it hard to determine if mirrors injection occurred or not (from within the mock env).</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100080)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1519210669-27720-153--

1 0

[JIRA] (OVIRT-1907) mock: $STD_CI_YUMREPOS is declared even when --try-mirrors isn't specified
by Barak Korren (oVirt JIRA) 21 Feb '18

21 Feb '18

This is a multi-part message in MIME format... ------------=_1519210649-31442-138 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1907?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1907: ------------------------------------- Also the point of STD_CI_YUMREPOS is to make code able to find the yumrepos file regardless of wither it was injected into or not - so this is not really a bog. > mock: $STD_CI_YUMREPOS is declared even when --try-mirrors isn't specified > -------------------------------------------------------------------------- > > Key: OVIRT-1907 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1907 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: CI Mirrors, mock_runner > Reporter: Gal Ben Haim > Assignee: infra > > This issue makes it hard to determine if mirrors injection occurred or not (from within the mock env). -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100080) ------------=_1519210649-31442-138 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1907?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren commented on OVIRT-1907:</h3> <p>Also the point of STD_CI_YUMREPOS is to make code able to find the yumrepos file regardless of wither it was injected into or not – so this is not really a bog.</p> <blockquote><h3>mock: $STD_CI_YUMREPOS is declared even when --try-mirrors isn't specified</h3> <pre> Key: OVIRT-1907 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1907 Project: oVirt - virtualization made easy Issue Type: Bug Components: CI Mirrors, mock_runner Reporter: Gal Ben Haim Assignee: infra</pre> <p>This issue makes it hard to determine if mirrors injection occurred or not (from within the mock env).</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100080)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1519210649-31442-138--

1 0

[JIRA] (OVIRT-1907) mock: $STD_CI_YUMREPOS is declared even when --try-mirrors isn't specified
by Barak Korren (oVirt JIRA) 21 Feb '18

21 Feb '18

This is a multi-part message in MIME format... ------------=_1519210595-21534-138 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1907?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1907: ------------------------------------- Mirror injection is supposed to be transparent to the test/build code, why do you need to know? > mock: $STD_CI_YUMREPOS is declared even when --try-mirrors isn't specified > -------------------------------------------------------------------------- > > Key: OVIRT-1907 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1907 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: CI Mirrors, mock_runner > Reporter: Gal Ben Haim > Assignee: infra > > This issue makes it hard to determine if mirrors injection occurred or not (from within the mock env). -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100080) ------------=_1519210595-21534-138 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1907?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren commented on OVIRT-1907:</h3> <p>Mirror injection is supposed to be transparent to the test/build code, why do you need to know?</p> <blockquote><h3>mock: $STD_CI_YUMREPOS is declared even when --try-mirrors isn't specified</h3> <pre> Key: OVIRT-1907 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1907 Project: oVirt - virtualization made easy Issue Type: Bug Components: CI Mirrors, mock_runner Reporter: Gal Ben Haim Assignee: infra</pre> <p>This issue makes it hard to determine if mirrors injection occurred or not (from within the mock env).</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100080)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1519210595-21534-138--

1 0

[JIRA] (OVIRT-1908) jenkins_master_check-patch: Can't find push details for remote URL in the push map file
by Evgheni Dereveanchin (oVirt JIRA) 21 Feb '18

21 Feb '18

This is a multi-part message in MIME format... ------------=_1519209892-27815-144 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Evgheni Dereveanchin created OVIRT-1908: ------------------------------------------- Summary: jenkins_master_check-patch: Can't find push details for remote URL in the push map file Key: OVIRT-1908 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1908 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Evgheni Dereveanchin Assignee: infra check-patch is failing for the jenkins repo with a strange error: 17:55:49 + /home/jenkins/workspace/jenkins_master_check-patch-fc25-x86_64/jenkins/scripts/pusher.py --log=/home/jenkins/workspace/jenkins_master_check-patch-fc25-x86_64/exported-artifacts/pusher_logs/push_jenkins.log push --if-not-exists --unless-hash=jenkins-jenkins_master_check-patch-fc25-x86_64-3415 master 17:55:49 Can't find push details for remote URL: 'git://gerrit.ovirt.org/jenkins.git' in the push map file. 17:55:49 Build step 'Execute shell' marked build as failure Example failed jobs: http://jenkins.ovirt.org/job/jenkins_master_check-patch-fc25-x86_64/3415/ http://jenkins.ovirt.org/job/jenkins_master_check-patch-fcraw-x86_64/1072/ http://jenkins.ovirt.org/job/jenkins_master_check-patch-fc27-x86_64/1051/ http://jenkins.ovirt.org/job/jenkins_master_check-patch-el7-x86_64/3841/ http://jenkins.ovirt.org/job/jenkins_master_check-patch-el7-ppc64le/960/ http://jenkins.ovirt.org/job/jenkins_master_check-patch-fc24-x86_64/3572/ http://jenkins.ovirt.org/job/jenkins_master_check-patch-fc26-x86_64/2293/ http://jenkins.ovirt.org/job/jenkins_master_check-patch-el6-x86_64/3567/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100080) ------------=_1519209892-27815-144 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <h3>Evgheni Dereveanchin created OVIRT-1908:</h3> <pre> Summary: jenkins_master_check-patch: Can't find push details for remote URL in the push map file Key: OVIRT-1908 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1908 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Evgheni Dereveanchin Assignee: infra</pre> <p>check-patch is failing for the jenkins repo with a strange error:</p> <p>17:55:49 + /home/jenkins/workspace/jenkins_master_check-patch-fc25-x86_64/jenkins/scripts/pusher.py --log=/home/jenkins/workspace/jenkins_master_check-patch-fc25-x86_64/exported-artifacts/pusher_logs/push_jenkins.log push --if-not-exists --unless-hash=jenkins-jenkins_master_check-patch-fc25-x86_64-3415 master 17:55:49 Can't find push details for remote URL: ‘git://gerrit.ovirt.org/jenkins.git’ in the push map file. 17:55:49 Build step ‘Execute shell’ marked build as failure</p> <p>Example failed jobs: <a href="http://jenkins.ovirt.org/job/jenkins_master_check-patch-fc25-x86_64/3415/">http://jenkins.ovirt.org/job/jenkins_master_check-patch-fc25-x86_64/3415/</a> <a href="http://jenkins.ovirt.org/job/jenkins_master_check-patch-fcraw-x86_64/1072/">http://jenkins.ovirt.org/job/jenkins_master_check-patch-fcraw-x86_64/1072/</a> <a href="http://jenkins.ovirt.org/job/jenkins_master_check-patch-fc27-x86_64/1051/">http://jenkins.ovirt.org/job/jenkins_master_check-patch-fc27-x86_64/1051/</a> <a href="http://jenkins.ovirt.org/job/jenkins_master_check-patch-el7-x86_64/3841/">http://jenkins.ovirt.org/job/jenkins_master_check-patch-el7-x86_64/3841/</a> <a href="http://jenkins.ovirt.org/job/jenkins_master_check-patch-el7-ppc64le/960/">http://jenkins.ovirt.org/job/jenkins_master_check-patch-el7-ppc64le/960/</a> <a href="http://jenkins.ovirt.org/job/jenkins_master_check-patch-fc24-x86_64/3572/">http://jenkins.ovirt.org/job/jenkins_master_check-patch-fc24-x86_64/3572/</a> <a href="http://jenkins.ovirt.org/job/jenkins_master_check-patch-fc26-x86_64/2293/">http://jenkins.ovirt.org/job/jenkins_master_check-patch-fc26-x86_64/2293/</a> <a href="http://jenkins.ovirt.org/job/jenkins_master_check-patch-el6-x86_64/3567/">http://jenkins.ovirt.org/job/jenkins_master_check-patch-el6-x86_64/3567/</a></p> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100080)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1519209892-27815-144--

1 0

[JIRA] (OVIRT-1907) mock: $STD_CI_YUMREPOS is declared even when --try-mirrors isn't specified
by Gal Ben Haim (oVirt JIRA) 21 Feb '18

21 Feb '18

Gal Ben Haim created OVIRT-1907: ----------------------------------- Summary: mock: $STD_CI_YUMREPOS is declared even when --try-mirrors isn't specified Key: OVIRT-1907 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1907 Project: oVirt - virtualization made easy Issue Type: Bug Components: CI Mirrors, mock_runner Reporter: Gal Ben Haim Assignee: infra This issue makes it hard to determine if mirrors injection occurred or not (from within the mock env). -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100080)

1 0

[JIRA] (OVIRT-1906) Manual Trigger permission
by eyal edri (oVirt JIRA) 21 Feb '18

21 Feb '18

This is a multi-part message in MIME format... ------------=_1519203805-32558-186 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1906?page=com.atlassian.jira.… ] eyal edri reassigned OVIRT-1906: -------------------------------- Assignee: Dusan Dodor (was: infra) > Manual Trigger permission > ------------------------- > > Key: OVIRT-1906 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1906 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Ales Musil > Assignee: Dusan Dodor > > Hi, > please add me (amusil) manual trigger permission. > Thanks. > Regards, > Ales. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100080) ------------=_1519203805-32558-186 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1906?page=com.atlassian.jira.… ]</pre> <h3>eyal edri reassigned OVIRT-1906:</h3> <pre>Assignee: Dusan Dodor (was: infra)</pre> <blockquote><h3>Manual Trigger permission</h3> <pre> Key: OVIRT-1906 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1906 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Ales Musil Assignee: Dusan Dodor</pre> <p>Hi, please add me (amusil) manual trigger permission. Thanks. Regards, Ales.</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100080)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1519203805-32558-186--

1 0

[JIRA] (OVIRT-1906) Manual Trigger permission
by eyal edri (oVirt JIRA) 21 Feb '18

21 Feb '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1906?page=com.atlassian.jira.… ] eyal edri commented on OVIRT-1906: ---------------------------------- Hi, You need to register first to Jenkins and then ask for the developer permission. Can you tell us which team you're from and who is the project maintainer? also we'll need your jenkins username. > Manual Trigger permission > ------------------------- > > Key: OVIRT-1906 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1906 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Ales Musil > Assignee: infra > > Hi, > please add me (amusil) manual trigger permission. > Thanks. > Regards, > Ales. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100080)

1 0

[JIRA] (OVIRT-1906) Manual Trigger permission
by Ales Musil (oVirt JIRA) 21 Feb '18

21 Feb '18

Ales Musil created OVIRT-1906: --------------------------------- Summary: Manual Trigger permission Key: OVIRT-1906 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1906 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Ales Musil Assignee: infra Hi, please add me (amusil) manual trigger permission. Thanks. Regards, Ales. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100080)

1 0

[CQ]: 87847, 4 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 21 Feb '18

21 Feb '18

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

1 0

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

21 Feb '18

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

1 0

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

21 Feb '18

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

1 0

[CQ]: 87986, 2 (ovirt-engine-sdk-ruby) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 21 Feb '18

21 Feb '18

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

1 0

[CQ]: 87985, 2 (ovirt-engine-sdk-ruby) failed "ovirt-4.2" system tests
by oVirt Jenkins 21 Feb '18

21 Feb '18

Change 87985,2 (ovirt-engine-sdk-ruby) 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://gerrit.ovirt.org/#/c/87985/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/893/

1 0

[oVirt Jenkins] ovirt-node-ng_ovirt-4.1-snapshot_build-artifacts-el7-x86_64 - Build # 417 - Fixed!
by jenkins＠jenkins.phx.ovirt.org 21 Feb '18

21 Feb '18

------=_Part_29_454887601.1519198650759 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.1-snapshot_build-artifac… Build: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.1-snapshot_build-artifac… Build Number: 417 Build Status: Fixed Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #416 [Sandro Bonazzola] Add Javier Coscia [Daniel Belenky] std enqueue: Add env.GERRIT_TRIGGER_CI_VOTE_LABEL [Daniel Belenky] cleanup: Fix race when unmounting dirs in chroot [Daniel Belenky] Add a tool to check if a change is merged [Yuval Turgeman] automation: view install log in console output Changes for Build #417 [Sandro Bonazzola] ovirt-provider-ovn: drop manual jobs [Dafna Ron] jenkins: adding infra(a)ovirt.org to the alert list [Barak Korren] Run `pusher.py` on non-Gerrit events [Daniel Belenky] Utilize stdci_dsl api in standard-stage [Yuval Turgeman] automation: view install log in console output ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_29_454887601.1519198650759--

1 0