January 2018 - Infra - oVirt List Archives

[JIRA] (OVIRT-1745) Make upstream source collection and polling code usable for pipelines
by Barak Korren (oVirt JIRA) 10 Jan '18

10 Jan '18

This is a multi-part message in MIME format... ------------=_1515572840-15436-331 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1745?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1745: -------------------------------- Component/s: (was: oVirt CI) usrc.py pusher.py > 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: pusher.py, usrc.py > 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) ------------=_1515572840-15436-331 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1745?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren updated OVIRT-1745:</h3> <pre> Component/s: (was: oVirt CI) usrc.py pusher.py</pre> <blockquote><h3>Make upstream source collection and polling code usable for pipelines</h3> <pre> Key: OVIRT-1745 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1745 Project: oVirt - virtualization made easy Issue Type: New Feature Components: pusher.py, usrc.py Reporter: Barak Korren Assignee: infra Labels: poll-upstream-sources, upstream-source-collector</pre> <p>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.</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> ------------=_1515572840-15436-331--

1 0

[JIRA] (OVIRT-1759) Gerrit patches can reach CQ out-of-order
by Barak Korren (oVirt JIRA) 10 Jan '18

10 Jan '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1759?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1759: -------------------------------- Component/s: (was: oVirt CI) Gerrit/git Change Queue > Gerrit patches can reach CQ out-of-order > ---------------------------------------- > > Key: OVIRT-1759 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1759 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Change Queue, Gerrit/git > Reporter: Barak Korren > Assignee: infra > Priority: High > Labels: change-queue, gerrit > > Is seems that despite the fact that all the jobs involved were designed to preserve proper patch ordering, there can be cases where patches trigger Jenkins jobs in the wrong order, which in turn end up putting the patches in the wrong order into the CQ. This in turn, causes the CQ to fail accurately detecting the patches that cause issues. > Here is en example of such an occurance. The following patches were merged in the order specified below: > # https://gerrit.ovirt.org/c/83917 > # https://gerrit.ovirt.org/c/83918 > # https://gerrit.ovirt.org/c/83919 > # https://gerrit.ovirt.org/c/83920 > The standard-enqueue runs putting them in the CQ however, seem to have run in a different order: > # http://jenkins.ovirt.org/job/standard-enqueue/6712/ (83917) > # http://jenkins.ovirt.org/job/standard-enqueue/6713/ (83919) > # http://jenkins.ovirt.org/job/standard-enqueue/6714/ (83920) > # http://jenkins.ovirt.org/job/standard-enqueue/6715/ (83918) > This resulted in CQ 'add' command running in the wrong order: > # http://jenkins.ovirt.org/job/ovirt-master_change-queue/12200/ (add 83917) > # http://jenkins.ovirt.org/job/ovirt-master_change-queue/12201/ (add 83919) > # http://jenkins.ovirt.org/job/ovirt-master_change-queue/12202/ (add 83920) > # http://jenkins.ovirt.org/job/ovirt-master_change-queue/12203/ (add 83918) > We need to come up with a way to make the system properly preserver order. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[JIRA] (OVIRT-1770) Build on fedora 26 fails, accessing console log extremely slow
by Barak Korren (oVirt JIRA) 10 Jan '18

10 Jan '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1770?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1770: ----------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Build on fedora 26 fails, accessing console log extremely slow > -------------------------------------------------------------- > > Key: OVIRT-1770 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1770 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins Master > Reporter: Nir Soffer > Assignee: Evgheni Dereveanchin > Labels: jenkins > > I wait forever for this url: > http://jenkins.ovirt.org/job/ovirt-imageio_master_check-patch-fc26-x86_64/2… > here example: > $ time curl > http://jenkins.ovirt.org/job/ovirt-imageio_master_check-patch-fc26-x86_64/2… > > /dev/null > % Total % Received % Xferd Average Speed Time Time Time > Current > Dload Upload Total Spent Left > Speed > 100 103k 0 103k 0 0 4814 0 --:--:-- 0:00:22 --:--:-- > 23562 > real 0m22.107s > user 0m0.005s > sys 0m0.009s > Can we fix to be less then a second? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[JIRA] (OVIRT-1770) Build on fedora 26 fails, accessing console log extremely slow
by Barak Korren (oVirt JIRA) 10 Jan '18

10 Jan '18

This is a multi-part message in MIME format... ------------=_1515572133-16023-272 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1770?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1770: -------------------------------- Component/s: (was: oVirt CI) Jenkins Master > Build on fedora 26 fails, accessing console log extremely slow > -------------------------------------------------------------- > > Key: OVIRT-1770 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1770 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins Master > Reporter: Nir Soffer > Assignee: infra > Labels: jenkins > > I wait forever for this url: > http://jenkins.ovirt.org/job/ovirt-imageio_master_check-patch-fc26-x86_64/2… > here example: > $ time curl > http://jenkins.ovirt.org/job/ovirt-imageio_master_check-patch-fc26-x86_64/2… > > /dev/null > % Total % Received % Xferd Average Speed Time Time Time > Current > Dload Upload Total Spent Left > Speed > 100 103k 0 103k 0 0 4814 0 --:--:-- 0:00:22 --:--:-- > 23562 > real 0m22.107s > user 0m0.005s > sys 0m0.009s > Can we fix to be less then a second? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075) ------------=_1515572133-16023-272 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1770?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren updated OVIRT-1770:</h3> <pre> Component/s: (was: oVirt CI) Jenkins Master</pre> <blockquote><h3>Build on fedora 26 fails, accessing console log extremely slow</h3> <pre> Key: OVIRT-1770 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1770 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Jenkins Master Reporter: Nir Soffer Assignee: infra Labels: jenkins</pre> <p>I wait forever for this url: <a href="http://jenkins.ovirt.org/job/ovirt-imageio_master_check-patch-fc26-x86_64/2…">http://jenkins.ovirt.org/job/ovirt-imageio_master_check-patch-fc26-x86_64/2…</a> here example: $ time curl <a href="http://jenkins.ovirt.org/job/ovirt-imageio_master_check-patch-fc26-x86_64/2…">http://jenkins.ovirt.org/job/ovirt-imageio_master_check-patch-fc26-x86_64/2…</a></p> <blockquote><p>/dev/null</p></blockquote> <pre>% Total % Received % Xferd Average Speed Time Time Time</pre> <p>Current</p> <pre>Dload Upload Total Spent Left</pre> <p>Speed 100 103k 0 103k 0 0 4814 0 --:--:-- 0:00:22 --:--:-- 23562 real 0m22.107s user 0m0.005s sys 0m0.009s Can we fix to be less then a second?</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> ------------=_1515572133-16023-272--

1 0

[JIRA] (OVIRT-1774) Upstream source collector can fail to push on multi-branch projects
by Barak Korren (oVirt JIRA) 10 Jan '18

10 Jan '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1774?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1774: -------------------------------- Component/s: (was: oVirt CI) pusher.py > Upstream source collector can fail to push on multi-branch projects > ------------------------------------------------------------------- > > Key: OVIRT-1774 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1774 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: pusher.py > Reporter: Barak Korren > Assignee: infra > Labels: poll-upstream-sources, upstream-source-collector > > When the upstream source collection code looks for similar patches in order to avoid pushing a new patch, it lookes for patches that contain the same change to the '{{upstream-sources.yaml}}' file, regardless of the branch they may belong to. > The code currently ignores the possibility that similar changes might be required for different branches, in which case different patches may need to be pushed. > The way of detecting similar patches should be changed so that either the branch name is included in the checksum that are used to identify a patch, or the query is limited to patches of the branch being handled. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[JIRA] (OVIRT-1781) ci failure due to no space on slave?
by Barak Korren (oVirt JIRA) 10 Jan '18

10 Jan '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1781?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1781: -------------------------------- Component/s: (was: oVirt CI) Jenkins Slaves > ci failure due to no space on slave? > ------------------------------------ > > Key: OVIRT-1781 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1781 > Project: oVirt - virtualization made easy > Issue Type: Outage > Components: Jenkins Slaves > Reporter: danken > Assignee: infra > Priority: High > Labels: vdsm > Fix For: OVIRT-INFRA-DEC-2017 > > > Exception when executing the batch command : no workspace from node > hudson.slaves.DumbSlave[vm0014.workers-phx.ovirt.org] which is > computer hudson.slaves.SlaveComputer@695d3d3c and has channel null > http://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86_64/19901/conso… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[JIRA] (OVIRT-1782) Make sure all VDSM build dependencies for FC27 are met.
by Barak Korren (oVirt JIRA) 10 Jan '18

10 Jan '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1782?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1782: -------------------------------- Component/s: (was: oVirt CI) CI client projects > Make sure all VDSM build dependencies for FC27 are met. > ------------------------------------------------------- > > Key: OVIRT-1782 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1782 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: CI client projects > Reporter: Barak Korren > Assignee: infra > Labels: vdsm > > There had been attempts recently to make VDSM build on FC27. > Those attempts were met with mixed success as issues kept surfacing. > Fro now all the FC27 jobs for VDSM had been disabled. > This ticket is for racking work of debugging issues to re-enable the jobs -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[JIRA] (OVIRT-1836) Optimize options normalization methods in stdci_dsl
by Barak Korren (oVirt JIRA) 10 Jan '18

10 Jan '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1836?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1836: -------------------------------- Component/s: (was: oVirt CI) STDCI DSL > Optimize options normalization methods in stdci_dsl > --------------------------------------------------- > > Key: OVIRT-1836 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1836 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: STDCI DSL > Reporter: Daniel Belenky > Assignee: infra > > Generally, we have 4 kinds of options: script, globals, options that affect host selection and options to configure the runner. > We need to take care of global options first since they affect everything, then take care of script because it tells which vectors to throw away. > Since runners and pipelines care about different sets of options, we need to split the options handling functions. > This will enable us to compose much more efficient pipelines in the API. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[JIRA] (OVIRT-1817) package included in .packages file, missing in check-patch.sh - caching issue?
by Barak Korren (oVirt JIRA) 10 Jan '18

10 Jan '18

This is a multi-part message in MIME format... ------------=_1515571559-19030-310 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1817?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1817: -------------------------------- Component/s: (was: oVirt CI) mock_runner > package included in .packages file, missing in check-patch.sh - caching issue? > ------------------------------------------------------------------------------ > > Key: OVIRT-1817 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1817 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: mock_runner > Reporter: Nir Soffer > Assignee: infra > Fix For: OVIRT-INFRA-DEC-2017 > > > I added 2 packages to ovirt-imageio packages files: > https://gerrit.ovirt.org/#/c/85639/ > The next patch using these packages > https://gerrit.ovirt.org/#/c/85245/ > fail to import the package on some slaves: > *00:02:34.093* ==================================== ERRORS > ====================================*00:02:34.093* > ____________________ ERROR collecting test/qemuimg_test.py > _____________________*00:02:34.093* ImportError while importing test > module '/home/jenkins/workspace/ovirt-imageio_master_check-patch-el7-x86_64/ovirt-imageio/common/test/qemuimg_test.py'.*00:02:34.094* > Hint: make sure your test modules/packages have valid Python > names.*00:02:34.094* Traceback:*00:02:34.094* test/qemuimg_test.py:16: > in <module>*00:02:34.094* from ovirt_imageio_common import > qemuimg*00:02:34.094* ovirt_imageio_common/qemuimg.py:11: in > <module>*00:02:34.094* from . compat import > subprocess*00:02:34.095* ovirt_imageio_common/compat.py:12: in > <module>*00:02:34.095* import subprocess32 as subprocess # NOQA: > F401 (unused import)*00:02:34.095* E ImportError: No module named > subprocess32*00:02:34.095* !!!!!!!!!!!!!!!!!!! Interrupted: 1 errors > during collection !!!!!!!!!!!!!!!!!!!!*00:02:34.096* > =========================== 1 error in 1.06 seconds > ============================ > Do we have a way to invalidate mock cache manually? > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075) ------------=_1515571559-19030-310 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1817?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren updated OVIRT-1817:</h3> <pre> Component/s: (was: oVirt CI) mock_runner</pre> <blockquote><h3>package included in .packages file, missing in check-patch.sh – caching issue?</h3> <pre> Key: OVIRT-1817 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1817 Project: oVirt - virtualization made easy Issue Type: Improvement Components: mock_runner Reporter: Nir Soffer Assignee: infra Fix For: OVIRT-INFRA-DEC-2017</pre> <p>I added 2 packages to ovirt-imageio packages files: <a href="https://gerrit.ovirt.org/#/c/85639/">https://gerrit.ovirt.org/#/c/85639/</a> The next patch using these packages <a href="https://gerrit.ovirt.org/#/c/85245/">https://gerrit.ovirt.org/#/c/85245/</a> fail to import the package on some slaves: <strong>00:02:34.093</strong> ==================================== ERRORS ====================================*00:02:34.093* <em>_________________</em>_ ERROR collecting test/qemuimg_test.py _____________________*00:02:34.093* ImportError while importing test module '/home/jenkins/workspace/ovirt-imageio_master_check-patch-el7-x86_64/ovirt-imageio/common/test/qemuimg_test.py'.*00:02:34.094* Hint: make sure your test modules/packages have valid Python names.*00:02:34.094* Traceback:*00:02:34.094* test/qemuimg_test.py:16: in <module>*00:02:34.094* from ovirt_imageio_common import qemuimg*00:02:34.094* ovirt_imageio_common/qemuimg.py:11: in <module>*00:02:34.094* from . compat import subprocess*00:02:34.095* ovirt_imageio_common/compat.py:12: in <module>*00:02:34.095* import subprocess32 as subprocess # NOQA: F401 (unused import)*00:02:34.095* E ImportError: No module named subprocess32*00:02:34.095* !!!!!!!!!!!!!!!!!!! Interrupted: 1 errors during collection !!!!!!!!!!!!!!!!!!!!*00:02:34.096* =========================== 1 error in 1.06 seconds ============================ Do we have a way to invalidate mock cache manually? 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> ------------=_1515571559-19030-310--

1 0

[JIRA] (OVIRT-1818) ioprocess build fail on ppc64le
by Barak Korren (oVirt JIRA) 10 Jan '18

10 Jan '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1818?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1818: -------------------------------- Component/s: (was: oVirt CI) mock_runner > 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: mock_runner > 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)

1 0