December 2017 - Infra - oVirt List Archives

[CQ]: 85797, 2 (ovirt-provider-ovn) failed "ovirt-master" system tests
by oVirt Jenkins 28 Dec '17

28 Dec '17

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

1 0

[JIRA] (OVIRT-1820) ioporcess build-artifacts fails on fedora/ppc64le
by Nir Soffer (oVirt JIRA) 28 Dec '17

28 Dec '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1820?page=com.atlassian.jira.… ] Nir Soffer commented on OVIRT-1820: ----------------------------------- On Thu, Dec 28, 2017 at 9:57 AM Yaniv Lavi <ylavi(a)redhat.com> wrote: > What is the RCA? > CI does not support Fedora/ppc64le yet. If we want to support it we need to open RFE for that. I don't think that users will run fedora on a ppc64 machine, but it may help us to support the next rhel version. > > YANIV LAVI > > SENIOR TECHNICAL PRODUCT MANAGER > > Red Hat Israel Ltd. <https://www.redhat.com/> > > 34 Jerusalem Road, Building A, 1st floor > > Ra'anana, Israel 4350109 > > ylavi(a)redhat.com T: +972-9-7692306/8272306 F: +972-9-7692223 IM: ylavi > <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> > @redhatnews <https://twitter.com/redhatnews> Red Hat <https://www.linkedin.com/company/red-hat> Red Hat <https://www.facebook.com/RedHatInc> > > > On Wed, Dec 27, 2017 at 10:27 PM, Nir Soffer <nsoffer(a)redhat.com> wrote: > >> I posted this for removing the fedora/ppc64le jobs: >> https://gerrit.ovirt.org/#/c/85786/ >> >> On Wed, Dec 27, 2017 at 10:20 PM Nir Soffer <nsoffer(a)redhat.com> wrote: >> >>> We added recently build-artifacts jobs for ioprocess on fedora/ppc64le. >>> >>> I merge a patch today, and build-artifacts fail: >>> >>> http://jenkins.ovirt.org/job/ioprocess_master_build-artifacts-fc26-ppc64le/… >>> >>> http://jenkins.ovirt.org/job/ioprocess_master_build-artifacts-fc27-ppc64le/… >>> >>> http://jenkins.ovirt.org/job/ioprocess_master_build-artifacts-fcraw-ppc64le… >>> >>> So it seems that we cannot support fedora on ppc64le now, and we >>> need to remove these jobs. >>> >>> Nir >>> >> > > ioporcess build-artifacts fails on fedora/ppc64le > ------------------------------------------------- > > Key: OVIRT-1820 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1820 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > Fix For: OVIRT-INFRA-DEC-2017 > > > We added recently build-artifacts jobs for ioprocess on fedora/ppc64le. > I merge a patch today, and build-artifacts fail: > http://jenkins.ovirt.org/job/ioprocess_master_build-artifacts-fc26-ppc64le/… > http://jenkins.ovirt.org/job/ioprocess_master_build-artifacts-fc27-ppc64le/… > http://jenkins.ovirt.org/job/ioprocess_master_build-artifacts-fcraw-ppc64le… > So it seems that we cannot support fedora on ppc64le now, and we > need to remove these jobs. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

ioporcess build-artifacts fails on fedora/ppc64le
by Nir Soffer 28 Dec '17

28 Dec '17

We added recently build-artifacts jobs for ioprocess on fedora/ppc64le. I merge a patch today, and build-artifacts fail: http://jenkins.ovirt.org/job/ioprocess_master_build-artifacts-fc26-ppc64le/… http://jenkins.ovirt.org/job/ioprocess_master_build-artifacts-fc27-ppc64le/… http://jenkins.ovirt.org/job/ioprocess_master_build-artifacts-fcraw-ppc64le… So it seems that we cannot support fedora on ppc64le now, and we need to remove these jobs. Nir

2 3

[CQ]: 85787,4 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 28 Dec '17

28 Dec '17

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

1 0

[CQ]: 85812, 1 (ovirt-engine-api-model) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 28 Dec '17

28 Dec '17

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

1 0

[CQ]: 85797, 2 (ovirt-provider-ovn) failed "ovirt-master" system tests
by oVirt Jenkins 28 Dec '17

28 Dec '17

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

1 0

[JIRA] (OVIRT-1812) [Gerrit Hooks] bug-url hook should not verify bugs w/o bug-url: prefix
by eyal edri (oVirt JIRA) 28 Dec '17

28 Dec '17

This is a multi-part message in MIME format... ------------=_1514473065-28079-151 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1812?page=com.atlassian.jira.… ] eyal edri updated OVIRT-1812: ----------------------------- Summary: [Gerrit Hooks] bug-url hook should not verify bugs w/o bug-url: prefix (was: Gerrit bug check is buggy) > [Gerrit Hooks] bug-url hook should not verify bugs w/o bug-url: prefix > ---------------------------------------------------------------------- > > Key: OVIRT-1812 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1812 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Nir Soffer > Assignee: Anton Marchukov > > Gerrit bug check code is treating unrelated urls as Bug-Url: > Patch Set 1: Verified-1 > - Check Bug-Url::1520068::WARN, failed to get bug info (private bug or > bug doesn't exist) > - Check Bug-Url::1527827::OK, classification: 'Red Hat', product: 'Red > Hat Enterprise Virtualization Manager' (-1) > - Check Product::WARN, failed to get bug info (private bug or bug > doesn't exist) > - Check TM::WARN, failed to get bug info (private bug or bug doesn't > exist) > - Check Backport::OK, The patch backported to all the relevant stable > branches. > - Set POST::#1520068::WARN, failed to get bug info (private bug or bug > doesn't exist) > - Update Tracker::#1520068::WARN, failed to get bug info (private bug or > bug doesn't exist) > - Update Tracker::#1527827::OK, tracker status: POST > The commit message is: > commit 1b666da534c50321ada448e4bf397cab0306fcf1 > Author: Nir Soffer <nsoffer(a)redhat.com> > Date: Tue Dec 5 23:47:24 2017 +0200 > fileSD: Use InterruptibleDirectFile backend > FileStorgeDomainManifest uses now InterruptibleDirectFile for the > external leases backend. This ensure that the process does not become > uninterruptible if storage is non-responsive. > This change bypass the python bug[1] causing the entire process to hang > when opening the special xleases volume. Now the operation is done in > the child process outside of Vdsm. > [1] https://bugzilla.redhat.com/1520068 > Change-Id: I8a0eb42baa73b6c0a877ad9acbe53ac51f31bfea > Bug-Url: https://bugzilla.redhat.com/1527827 > Signed-off-by: Nir Soffer <nsoffer(a)redhat.com> > There is exactly one Bur-Url. The other url is a bugzilla url but it should > be consumed only by humans, not by machines. Machines should use > only the Bug-Url. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075) ------------=_1514473065-28079-151 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1812?page=com.atlassian.jira.… ]</pre> <h3>eyal edri updated OVIRT-1812:</h3> <pre>Summary: [Gerrit Hooks] bug-url hook should not verify bugs w/o bug-url: prefix (was: Gerrit bug check is buggy)</pre> <blockquote><h3>[Gerrit Hooks] bug-url hook should not verify bugs w/o bug-url: prefix</h3> <pre> Key: OVIRT-1812 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1812 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Nir Soffer Assignee: Anton Marchukov</pre> <p>Gerrit bug check code is treating unrelated urls as Bug-Url: Patch Set 1: Verified-1</p> <pre>- Check Bug-Url::1520068::WARN, failed to get bug info (private bug or bug doesn't exist) - Check Bug-Url::1527827::OK, classification: 'Red Hat', product: 'Red Hat Enterprise Virtualization Manager' (-1) - Check Product::WARN, failed to get bug info (private bug or bug doesn't exist) - Check TM::WARN, failed to get bug info (private bug or bug doesn't exist) - Check Backport::OK, The patch backported to all the relevant stable branches. - Set POST::#1520068::WARN, failed to get bug info (private bug or bug doesn't exist) - Update Tracker::#1520068::WARN, failed to get bug info (private bug or bug doesn't exist) - Update Tracker::#1527827::OK, tracker status: POST</pre> <p>The commit message is: commit 1b666da534c50321ada448e4bf397cab0306fcf1 Author: Nir Soffer <nsoffer(a)redhat.com> Date: Tue Dec 5 23:47:24 2017 +0200</p> <pre>fileSD: Use InterruptibleDirectFile backend FileStorgeDomainManifest uses now InterruptibleDirectFile for the external leases backend. This ensure that the process does not become uninterruptible if storage is non-responsive. This change bypass the python bug[1] causing the entire process to hang when opening the special xleases volume. Now the operation is done in the child process outside of Vdsm. [1] https://bugzilla.redhat.com/1520068 Change-Id: I8a0eb42baa73b6c0a877ad9acbe53ac51f31bfea Bug-Url: https://bugzilla.redhat.com/1527827 Signed-off-by: Nir Soffer <nsoffer(a)redhat.com></pre> <p>There is exactly one Bur-Url. The other url is a bugzilla url but it should be consumed only by humans, not by machines. Machines should use only the Bug-Url. Nir</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)</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> ------------=_1514473065-28079-151--

1 0

[JIRA] (OVIRT-1818) ioprocess build fail on ppc64le
by eyal edri (oVirt JIRA) 28 Dec '17

28 Dec '17

This is a multi-part message in MIME format... ------------=_1514473021-29568-160 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1818?page=com.atlassian.jira.… ] eyal edri commented on OVIRT-1818: ---------------------------------- I'm guessing this is a duplicate of another ticket we already closed? I believe that until we know that ppc64le should be supported on Fedora ( including and RFE ) we can probably close this. > ioprocess build fail on ppc64le > ------------------------------- > > Key: OVIRT-1818 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1818 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: oVirt CI > Reporter: Nir Soffer > Assignee: Barak Korren > Labels: ppc64le, standard-ci > > The new builds for ppc64le fail with the errors below. > 1. > http://jenkins.ovirt.org/job/ioprocess_master_check-patch-fc26-ppc64le/1/co… > *00:00:42.499* ERROR: Command failed: *00:00:42.500* # /usr/bin/yum > --installroot /var/lib/mock/fedora-26-ppc64le-881f89337ffa51754418efa2ad261881-16706/root/ > --releasever 26 install @buildsys-build autoconf automake git > glib2-devel python-pip python-six python-subprocess32 python2-devel > python3-devel python3-six util-linux yajl-devel > --setopt=tsflags=nocontexts*00:00:42.500* Failed to set locale, > defaulting to C*00:00:42.500* No package git available.*00:00:42.501* > No package glib2-devel available.*00:00:42.501* No package > python-subprocess32 available.*00:00:42.501* No package python2-devel > available.*00:00:42.501* No package python3-devel > available.*00:00:42.501* No package util-linux > available.*00:00:42.501* No package yajl-devel available. > 2. > http://jenkins.ovirt.org/job/ioprocess_master_check-patch-fc27-ppc64le/1/co… > *00:00:18.335* + > /home/jenkins/workspace/ioprocess_master_check-patch-fc27-ppc64le/jenkins/mock_configs/mock_runner.sh > --patch-only --mock-confs-dir > /home/jenkins/workspace/ioprocess_master_check-patch-fc27-ppc64le/jenkins/mock_configs > --secrets-file /home/jenkins/workspace/ioprocess_master_check-patch-fc27-ppc64le/std_ci_secrets.yaml > --try-proxy --try-mirrors > http://mirrors.phx.ovirt.org/repos/yum/all_latest.json > 'fc27.*ppc64le'*00:00:18.347* Unable to find mock env > fc27.*ppc64le*00:00:18.351* Collecting mock logs*00:00:18.352* mv: > missing destination file operand after 'exported-artifacts/mock_logs' > 3. > http://jenkins.ovirt.org/job/ioprocess_master_check-patch-fcraw-ppc64le/1/c… > *00:00:26.701* + > /home/jenkins/workspace/ioprocess_master_check-patch-fcraw-ppc64le/jenkins/mock_configs/mock_runner.sh > --patch-only --mock-confs-dir > /home/jenkins/workspace/ioprocess_master_check-patch-fcraw-ppc64le/jenkins/mock_configs > --secrets-file /home/jenkins/workspace/ioprocess_master_check-patch-fcraw-ppc64le/std_ci_secrets.yaml > --try-proxy --try-mirrors > http://mirrors.phx.ovirt.org/repos/yum/all_latest.json > 'fcraw.*ppc64le'*00:00:26.702* Unable to find mock env > fcraw.*ppc64le*00:00:26.703* Collecting mock logs > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075) ------------=_1514473021-29568-160 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1818?page=com.atlassian.jira.… ]</pre> <h3>eyal edri commented on OVIRT-1818:</h3> <p>I'm guessing this is a duplicate of another ticket we already closed?</p> <p>I believe that until we know that ppc64le should be supported on Fedora ( including and RFE ) we can probably close this.</p> <blockquote><h3>ioprocess build fail on ppc64le</h3> <pre> Key: OVIRT-1818 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1818 Project: oVirt - virtualization made easy Issue Type: Bug Components: oVirt CI Reporter: Nir Soffer Assignee: Barak Korren Labels: ppc64le, standard-ci</pre> <p>The new builds for ppc64le fail with the errors below. 1. <a href="http://jenkins.ovirt.org/job/ioprocess_master_check-patch-fc26-ppc64le/1/co…">http://jenkins.ovirt.org/job/ioprocess_master_check-patch-fc26-ppc64le/1/co…</a> <strong>00:00:42.499</strong> ERROR: Command failed: <strong>00:00:42.500</strong> # /usr/bin/yum --installroot /var/lib/mock/fedora-26-ppc64le-881f89337ffa51754418efa2ad261881-16706/root/ --releasever 26 install @buildsys-build autoconf automake git glib2-devel python-pip python-six python-subprocess32 python2-devel python3-devel python3-six util-linux yajl-devel --setopt=tsflags=nocontexts*00:00:42.500* Failed to set locale, defaulting to C*00:00:42.500* No package git available.*00:00:42.501* No package glib2-devel available.*00:00:42.501* No package python-subprocess32 available.*00:00:42.501* No package python2-devel available.*00:00:42.501* No package python3-devel available.*00:00:42.501* No package util-linux available.*00:00:42.501* No package yajl-devel available. 2. <a href="http://jenkins.ovirt.org/job/ioprocess_master_check-patch-fc27-ppc64le/1/co…">http://jenkins.ovirt.org/job/ioprocess_master_check-patch-fc27-ppc64le/1/co…</a> <strong>00:00:18.335</strong> + /home/jenkins/workspace/ioprocess_master_check-patch-fc27-ppc64le/jenkins/mock_configs/mock_runner.sh --patch-only --mock-confs-dir /home/jenkins/workspace/ioprocess_master_check-patch-fc27-ppc64le/jenkins/mock_configs --secrets-file /home/jenkins/workspace/ioprocess_master_check-patch-fc27-ppc64le/std_ci_secrets.yaml --try-proxy --try-mirrors <a href="http://mirrors.phx.ovirt.org/repos/yum/all_latest.json">http://mirrors.phx.ovirt.org/repos/yum/all_latest.json</a> ‘fc27.*ppc64le'*00:00:18.347* Unable to find mock env fc27.*ppc64le*00:00:18.351* Collecting mock logs*00:00:18.352* mv: missing destination file operand after 'exported-artifacts/mock_logs’ 3. <a href="http://jenkins.ovirt.org/job/ioprocess_master_check-patch-fcraw-ppc64le/1/c…">http://jenkins.ovirt.org/job/ioprocess_master_check-patch-fcraw-ppc64le/1/c…</a> <strong>00:00:26.701</strong> + /home/jenkins/workspace/ioprocess_master_check-patch-fcraw-ppc64le/jenkins/mock_configs/mock_runner.sh --patch-only --mock-confs-dir /home/jenkins/workspace/ioprocess_master_check-patch-fcraw-ppc64le/jenkins/mock_configs --secrets-file /home/jenkins/workspace/ioprocess_master_check-patch-fcraw-ppc64le/std_ci_secrets.yaml --try-proxy --try-mirrors <a href="http://mirrors.phx.ovirt.org/repos/yum/all_latest.json">http://mirrors.phx.ovirt.org/repos/yum/all_latest.json</a> 'fcraw.*ppc64le'*00:00:26.702* Unable to find mock env fcraw.*ppc64le*00:00:26.703* Collecting mock logs Nir</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)</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> ------------=_1514473021-29568-160--

1 0

[JIRA] (OVIRT-1745) Make upstream source collection and polling code usable for pipelines
by Barak Korren (oVirt JIRA) 28 Dec '17

28 Dec '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1745?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1745: -------------------------------- Resolution: Fixed Status: Done (was: To Do) > Make upstream source collection and polling code usable for pipelines > --------------------------------------------------------------------- > > Key: OVIRT-1745 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1745 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: poll-upstream-sources, upstream-source-collector > > The upstream source collection and polling code is currently only suitable for use in Free-Style jobs. This is because: > # We support having 'jenkins' repositories (Where jobs expect STDCI code to be found) use the upstream sources mechanism to get the actual code from the main 'jenkins' repo in gerrit.ovirt.org > # This creates a situation where in order to get the STDCI code we need to run the upstream sources code > # This creates a chicken and and egg problem because the upstream sources code is part of the STDCI code > # To solve this issue we simply embedded the upstream sources code into the job code by using '{{#include}}' in JJB rather then running it as a stand-alone script. > # This technique is not usable for pipelines, so we need to come with a different solution and make the required adjustments to the source collection and polling code. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[JIRA] (OVIRT-1745) Make upstream source collection and polling code usable for pipelines
by Barak Korren (oVirt JIRA) 28 Dec '17

28 Dec '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1745?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1745: ------------------------------------- Work done in OVIRT-1746 provided stand-alone tools that are usable from pipelines. No further work is needed in this ticket. > Make upstream source collection and polling code usable for pipelines > --------------------------------------------------------------------- > > Key: OVIRT-1745 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1745 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: poll-upstream-sources, upstream-source-collector > > The upstream source collection and polling code is currently only suitable for use in Free-Style jobs. This is because: > # We support having 'jenkins' repositories (Where jobs expect STDCI code to be found) use the upstream sources mechanism to get the actual code from the main 'jenkins' repo in gerrit.ovirt.org > # This creates a situation where in order to get the STDCI code we need to run the upstream sources code > # This creates a chicken and and egg problem because the upstream sources code is part of the STDCI code > # To solve this issue we simply embedded the upstream sources code into the job code by using '{{#include}}' in JJB rather then running it as a stand-alone script. > # This technique is not usable for pipelines, so we need to come with a different solution and make the required adjustments to the source collection and polling code. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0