Build failed in Jenkins: ovirt_master_system-tests #384

[jenkins]

See 

Changes:

[Gal Ben Haim] Removed the hard coded path of the template repo. The template 
repo file

--
[...truncated 708 lines...]
##  took 1103 seconds
##  rc = 1
##
##! ERROR v
##! Last 20 log enties: 
logs/mocker-fedora-24-x86_64.fc24.basic_suite_master.sh/basic_suite_master.sh.log
##!
+ true
+ env_cleanup
+ echo '#'
#
+ local res=0
+ local uuid
+ echo ' Cleaning up'
 Cleaning up
+ [[ -e 

 ]]
+ echo '--- Cleaning with lago'
--- Cleaning with lago
+ lago --workdir 

 destroy --yes --all-prefixes
+ echo '--- Cleaning with lago done'
--- Cleaning with lago done
+ [[ 0 != \0 ]]
+ echo ' Cleanup done'
 Cleanup done
+ exit 0
Took 933 seconds
===
##!
##! ERROR ^^
##!
##
Build step 'Execute shell' marked build as failure
Performing Post build task...
Match found for :.* : True
Logical operation result is TRUE
Running script  : #!/bin/bash -xe
echo 'shell_scripts/system_tests.collect_logs.sh'

#
# Required jjb vars:
#version
#
VERSION=master
SUITE_TYPE=

WORKSPACE="$PWD"
OVIRT_SUITE="$SUITE_TYPE_suite_$VERSION"
TESTS_LOGS="$WORKSPACE/ovirt-system-tests/exported-artifacts"

rm -rf "$WORKSPACE/exported-artifacts"
mkdir -p "$WORKSPACE/exported-artifacts"

if [[ -d "$TESTS_LOGS" ]]; then
mv "$TESTS_LOGS/"* "$WORKSPACE/exported-artifacts/"
fi

[ovirt_master_system-tests] $ /bin/bash -xe /tmp/hudson1331344908423719962.sh
+ echo shell_scripts/system_tests.collect_logs.sh
shell_scripts/system_tests.collect_logs.sh
+ VERSION=master
+ SUITE_TYPE=
+ WORKSPACE=
+ OVIRT_SUITE=master
+ 
TESTS_LOGS=
+ rm -rf 

+ mkdir -p 

+ [[ -d 

 ]]
+ mv 

 

 

 

 

POST BUILD TASK : SUCCESS
END OF POST BUILD TASK : 0
Match found for :.* : True
Logical operation result is TRUE
Running script  : #!/bin/bash -xe
echo "shell-scripts/mock_cleanup.sh"

shopt -s nullglob


WORKSPACE="$PWD"

# Make clear this is the cleanup, helps reading the jenkins logs
cat 
+ cat
___
###
# #
#   CLEANUP   #
# #
###
+ logs=(./*log ./*/logs)
+ [[ -n ./ovirt-system-tests/logs ]]
+ tar cvzf exported-artifacts/logs.tgz ./ovirt-system-tests/logs
./ovirt-system-tests/logs/
./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.init/
./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.init/stdout_stderr.log
./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.init/state.log
./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.init/build.log
./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.init/root.log
./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.install_packages/
./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.install_packages/stdout_stderr.log
./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.install_packages/state.log
./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.install_packages/build.log
./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.install_packages/root.log
.

Re: [ovirt-devel] [vdsm][heads up] planned branches for Vdsm 4.0.3 and 4.0.4+

[Eyal Edri]

Adding Infra,

We'll need to update the gerrit hooks to support these new branches.

On Thu, Aug 11, 2016 at 10:55 AM, Francesco Romani 
wrote:

> Hi all,
>
> due to the need for the fix for https://bugzilla.redhat.com/
> show_bug.cgi?id=1364149
> I created yesterday the branch 4.0.2.
>
> For 4.0.3:
> --
> We will have another branch, should we need more fix.
> The fine details are yet to sort out, but the gist is that we *will* have
> that branch,
> so backports for 4.0.3 will require two 4.0.z patches:
>
> ---+-[...]-> master
>|
>`---+-> ovirt-4.0
>|*- vdsm 4.18.10
>|
>`---> ovirt-4.0.2
>   *- vdsm 4.18.11
>
>
> For 4.0.4:
> --
> We will resume our regular flow, 4.0.4 will be tagged from the ovirt-4.0
> branch, so
> backport for 4.0.4 (and beyond) will require just one backport
>
> Merge to ovirt-4.0 for patches for 4.0.4 will resume this afternoon
>
> Thanks and bests,
>
> --
> Francesco Romani
> RedHat Engineering Virtualization R & D
> Phone: 8261328
> IRC: fromani
> ___
> Devel mailing list
> de...@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
>
>
>


-- 
Eyal Edri
Associate Manager
RHV DevOps
EMEA ENG Virtualization R&D
Red Hat Israel

phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Re: [ovirt-devel] [vdsm][heads up] planned branches for Vdsm 4.0.3 and 4.0.4+

[Francesco Romani]

Thanks Eyal. 

Infra: for the moment please just add hooks for ovirt-4.0.2. We are still 
discussing if we will have the ovirt-4.0.3 branch or if 
we will just use ovirt-4.0.2 also for the next microversion. 

Thanks and bests, 

- Original Message -

> From: "Eyal Edri" 
> To: "Francesco Romani" , "infra" ,
> "Evgheni Dereveanchin" 
> Cc: "devel" 
> Sent: Thursday, August 11, 2016 10:16:37 AM
> Subject: Re: [ovirt-devel] [vdsm][heads up] planned branches for Vdsm 4.0.3
> and 4.0.4+

> Adding Infra,

> We'll need to update the gerrit hooks to support these new branches.

> On Thu, Aug 11, 2016 at 10:55 AM, Francesco Romani < from...@redhat.com >
> wrote:

> > Hi all,
> 

> > due to the need for the fix for
> > https://bugzilla.redhat.com/show_bug.cgi?id=1364149
> 
> > I created yesterday the branch 4.0.2.
> 

> > For 4.0.3:
> 
> > --
> 
> > We will have another branch, should we need more fix.
> 
> > The fine details are yet to sort out, but the gist is that we *will* have
> > that branch,
> 
> > so backports for 4.0.3 will require two 4.0.z patches:
> 

> > ---+-[...]-> master
> 
> > |
> 
> > `---+-> ovirt-4.0
> 
> > |*- vdsm 4.18.10
> 
> > |
> 
> > `---> ovirt-4.0.2
> 
> > *- vdsm 4.18.11
> 

> > For 4.0.4:
> 
> > --
> 
> > We will resume our regular flow, 4.0.4 will be tagged from the ovirt-4.0
> > branch, so
> 
> > backport for 4.0.4 (and beyond) will require just one backport
> 

> > Merge to ovirt-4.0 for patches for 4.0.4 will resume this afternoon
> 

> > Thanks and bests,
> 

> > --
> 
> > Francesco Romani
> 
> > RedHat Engineering Virtualization R & D
> 
> > Phone: 8261328
> 
> > IRC: fromani
> 
> > ___
> 
> > Devel mailing list
> 
> > de...@ovirt.org
> 
> > http://lists.ovirt.org/mailman/listinfo/devel
> 

> --
> Eyal Edri
> Associate Manager
> RHV DevOps
> EMEA ENG Virtualization R&D
> Red Hat Israel

> phone: +972-9-7692018
> irc: eedri (on #tlv #rhev-dev #rhev-integ)

-- 
Francesco Romani 
RedHat Engineering Virtualization R & D 
Phone: 8261328 
IRC: fromani 
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Build failed in Jenkins: ovirt_master_system-tests #385

[jenkins]

See 

Changes:

[Gal Ben Haim] Removed the hard coded path of the template repo. The template 
repo file

[Sharon Naftaly] Moving create-rpms-manual jobs to standard-ci

[Sharon Naftaly] Add ovirt-dwh build-artifact-manual jobs

--
[...truncated 754 lines...]
##  took 1916 seconds
##  rc = 1
##
##! ERROR v
##! Last 20 log enties: 
logs/mocker-fedora-24-x86_64.fc24.basic_suite_master.sh/basic_suite_master.sh.log
##!
+ true
+ env_cleanup
+ echo '#'
#
+ local res=0
+ local uuid
+ echo ' Cleaning up'
 Cleaning up
+ [[ -e 

 ]]
+ echo '--- Cleaning with lago'
--- Cleaning with lago
+ lago --workdir 

 destroy --yes --all-prefixes
+ echo '--- Cleaning with lago done'
--- Cleaning with lago done
+ [[ 0 != \0 ]]
+ echo ' Cleanup done'
 Cleanup done
+ exit 0
Took 1743 seconds
===
##!
##! ERROR ^^
##!
##
Build step 'Execute shell' marked build as failure
Performing Post build task...
Match found for :.* : True
Logical operation result is TRUE
Running script  : #!/bin/bash -xe
echo 'shell_scripts/system_tests.collect_logs.sh'

#
# Required jjb vars:
#version
#
VERSION=master
SUITE_TYPE=

WORKSPACE="$PWD"
OVIRT_SUITE="$SUITE_TYPE_suite_$VERSION"
TESTS_LOGS="$WORKSPACE/ovirt-system-tests/exported-artifacts"

rm -rf "$WORKSPACE/exported-artifacts"
mkdir -p "$WORKSPACE/exported-artifacts"

if [[ -d "$TESTS_LOGS" ]]; then
mv "$TESTS_LOGS/"* "$WORKSPACE/exported-artifacts/"
fi

[ovirt_master_system-tests] $ /bin/bash -xe /tmp/hudson6112408666877301670.sh
+ echo shell_scripts/system_tests.collect_logs.sh
shell_scripts/system_tests.collect_logs.sh
+ VERSION=master
+ SUITE_TYPE=
+ WORKSPACE=
+ OVIRT_SUITE=master
+ 
TESTS_LOGS=
+ rm -rf 

+ mkdir -p 

+ [[ -d 

 ]]
+ mv 

 

 

 

 

POST BUILD TASK : SUCCESS
END OF POST BUILD TASK : 0
Match found for :.* : True
Logical operation result is TRUE
Running script  : #!/bin/bash -xe
echo "shell-scripts/mock_cleanup.sh"

shopt -s nullglob


WORKSPACE="$PWD"

# Make clear this is the cleanup, helps reading the jenkins logs
cat 
+ cat
___
###
# #
#   CLEANUP   #
# #
###
+ logs=(./*log ./*/logs)
+ [[ -n ./ovirt-system-tests/logs ]]
+ tar cvzf exported-artifacts/logs.tgz ./ovirt-system-tests/logs
./ovirt-system-tests/logs/
./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.init/
./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.init/stdout_stderr.log
./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.init/state.log
./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.init/build.log
./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.init/root.log
./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.install_packages/
./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.install_packages/stdout_stderr.log
./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.install_packages/state.log
./ovirt-system-tests/logs/mocker-fedora-

[JIRA] (OVIRT-678) Re: please remove the following jenkins jobs

[ybronhei (oVirt JIRA)]

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=19405#comment-19405
 ] 

ybronhei commented on OVIRT-678:


On Wed, Aug 10, 2016 at 8:06 PM, eyal edri [Administrator] (oVirt JIRA) <



This is related to check-patch, check-path and build-artifacts should run
over all platforms. as many as possible.. Check-merged is a script to test
our functional flows  - we run lago, and fedora vm inside that runs vdsmd
and some functional test. currently lago vm is fedora based, so vdsm rpms
to be installed should be built over *fedora*, therefore the jenkins vm is
fedora as well.

We don't run the functional tests over centos\el7 vm currently, so running
it on jenkins el7 vm is redundant and won't work (the rpms won't fit for
the lago vm inside, and it will only test lago run over el7).

That's why we ask to run check-merged CI only over f24 (as it used to be
not so long ago)






-- 
*Yaniv Bronhaim.*


> Re: please remove the following jenkins jobs
> 
>
> Key: OVIRT-678
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-678
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: sbonazzo
>Assignee: infra
>
> On Wed, Aug 10, 2016 at 3:41 PM, Irit Goihman  wrote:
> > Hi,
> > jobs vdsm_master_build-artifacts-el7-ppc64le and 
> > vdsm_master_check-merged-el7-x86_64
> > keep failing. They were created recently and should be removed.
> >
> The ppc64le should be fixed, not removed.
> We want ppc64le builds now that we have ppc64le slaves.
> The check-merged for el7 is your call, fine for me if you want to remove.
> Just weird since el7 is our main target.
> >
> > Thanks
> >
> > --
> > Irit Goihman
> > Software Engineer
> > Red Hat Israel Ltd.
> >
> > ___
> > Infra mailing list
> > Infra@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/infra
> >
> >
> -- 
> Sandro Bonazzola
> Better technology. Faster innovation. Powered by community collaboration.
> See how it works at redhat.com



--
This message was sent by Atlassian JIRA
(v1000.217.2#18)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-612) Support to FTP files for Kimchi Project

[Paulo Ricardo Paz Vital (oVirt JIRA)]

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=19407#comment-19407
 ] 

Paulo Ricardo Paz Vital commented on OVIRT-612:
---

Hi [~eedri]. Nice documentation, but I still have some questions:

1- I created the project yaml and the scm yaml files in my local repository. 
How can I submit them to review? I planning to configure only one of our 4 
projects to test in a first moment and, in addition, using a specific branch in 
my fork in github that will include the necessary files to CI Standard. If this 
first test works well, is it possible to submit updates (point to projects 
github repository) and improvements in project's files?
2- One of the fields for the project yaml file is the trigger, that can be 
on-change or timed. In case of timed (that is what I want to use) how can I set 
the periodicity to run the job?
3 - Reading the documentation, I could see only references to build artifacts 
to CentOS (EL) and Fedora. We provide artifacts to Ubuntu (Debian) and 
OpenSUSE, also. Is it possible to build for these distros?


> Support to FTP files for Kimchi Project
> ---
>
> Key: OVIRT-612
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-612
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Paulo Ricardo Paz Vital
>Assignee: infra
>
> Hello,
> Kimchi is a sub-project of oVirt and we are planning to make available to 
> users
> simple qcow2 image files of Fedora 23, OpenSUSE 42.1 and Ubuntu 16.04 with 
> Kimchi installed in there.
> We need support to store the files and make them available to download, in a
> service like FTP. Since Kimchi mailing lists already use oVirt infrastructure,
> I'd like to know if it's possible to be supported by oVirt and how to do that.
> Thanks and best regards, Paulo.
> --
> Paulo Ricardo Paz Vital
> Linux Technology Center, IBM Systems
> http://www.ibm.com/linux/ltc/



--
This message was sent by Atlassian JIRA
(v1000.217.2#18)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-612) Support to FTP files for Kimchi Project

[eyal edri [Administrator] (oVirt JIRA)]

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=19408#comment-19408
 ] 

eyal edri [Administrator] commented on OVIRT-612:
-

[~snaft...@redhat.com] can you help Paulo on the basics on how to submit a 
patch to gerrit.ovirt.org to the jenkins repo?

> Support to FTP files for Kimchi Project
> ---
>
> Key: OVIRT-612
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-612
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Paulo Ricardo Paz Vital
>Assignee: infra
>
> Hello,
> Kimchi is a sub-project of oVirt and we are planning to make available to 
> users
> simple qcow2 image files of Fedora 23, OpenSUSE 42.1 and Ubuntu 16.04 with 
> Kimchi installed in there.
> We need support to store the files and make them available to download, in a
> service like FTP. Since Kimchi mailing lists already use oVirt infrastructure,
> I'd like to know if it's possible to be supported by oVirt and how to do that.
> Thanks and best regards, Paulo.
> --
> Paulo Ricardo Paz Vital
> Linux Technology Center, IBM Systems
> http://www.ibm.com/linux/ltc/



--
This message was sent by Atlassian JIRA
(v1000.217.2#18)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-612) Support to FTP files for Kimchi Project

[snaftaly (oVirt JIRA)]

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=19409#comment-19409
 ] 

snaftaly commented on OVIRT-612:


Hi [~pvi...@linux.vnet.ibm.com],
Regarding the first part of your 1'st question, your patch needs to be sent to 
the 'jenkins' project on gerrit.ovirt.org (on the master branch). [~eedri], 
does he need special permissions for that? Also I'm not sure about the second 
part of the question.
Regarding your 2'nd question, all you need is to add a key named 
'trigger-times' in the project yaml, and put the desired value. 
For example: 
- project:
name: kimchi_project
project: kimchi
stage: build-artifacts
trigger-times: 'H H/6 * * *'
...
Regarding question 3, afaik we only support CentOS and Fedora, 
[~ee...@redaht.com] can you confirm that?

> Support to FTP files for Kimchi Project
> ---
>
> Key: OVIRT-612
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-612
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Paulo Ricardo Paz Vital
>Assignee: infra
>
> Hello,
> Kimchi is a sub-project of oVirt and we are planning to make available to 
> users
> simple qcow2 image files of Fedora 23, OpenSUSE 42.1 and Ubuntu 16.04 with 
> Kimchi installed in there.
> We need support to store the files and make them available to download, in a
> service like FTP. Since Kimchi mailing lists already use oVirt infrastructure,
> I'd like to know if it's possible to be supported by oVirt and how to do that.
> Thanks and best regards, Paulo.
> --
> Paulo Ricardo Paz Vital
> Linux Technology Center, IBM Systems
> http://www.ibm.com/linux/ltc/



--
This message was sent by Atlassian JIRA
(v1000.217.2#18)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-612) Support to FTP files for Kimchi Project

[snaftaly (oVirt JIRA)]

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=19409#comment-19409
 ] 

snaftaly edited comment on OVIRT-612 at 8/11/16 6:46 PM:
-

Hi [~pvi...@linux.vnet.ibm.com],
Regarding the first part of your 1'st question, your patch needs to be sent to 
the 'jenkins' project on gerrit.ovirt.org (on the master branch): 
git://gerrit.ovirt.org/jenkins.git. [~eedri], does he need special permissions 
for that? Also I'm not sure about the second part of the question.
Regarding your 2'nd question, all you need is to add a key named 
'trigger-times' in the project yaml, and put the desired value. 
For example: 
- project:
name: kimchi_project
project: kimchi
stage: build-artifacts
trigger-times: 'H H/6 * * *'
...

Regarding question 3, afaik we only support CentOS and Fedora, 
[~ee...@redaht.com] can you confirm that?


was (Author: snaft...@redhat.com):
Hi [~pvi...@linux.vnet.ibm.com],
Regarding the first part of your 1'st question, your patch needs to be sent to 
the 'jenkins' project on gerrit.ovirt.org (on the master branch). [~eedri], 
does he need special permissions for that? Also I'm not sure about the second 
part of the question.
Regarding your 2'nd question, all you need is to add a key named 
'trigger-times' in the project yaml, and put the desired value. 
For example: 
- project:
name: kimchi_project
project: kimchi
stage: build-artifacts
trigger-times: 'H H/6 * * *'
...
Regarding question 3, afaik we only support CentOS and Fedora, 
[~ee...@redaht.com] can you confirm that?

> Support to FTP files for Kimchi Project
> ---
>
> Key: OVIRT-612
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-612
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Paulo Ricardo Paz Vital
>Assignee: infra
>
> Hello,
> Kimchi is a sub-project of oVirt and we are planning to make available to 
> users
> simple qcow2 image files of Fedora 23, OpenSUSE 42.1 and Ubuntu 16.04 with 
> Kimchi installed in there.
> We need support to store the files and make them available to download, in a
> service like FTP. Since Kimchi mailing lists already use oVirt infrastructure,
> I'd like to know if it's possible to be supported by oVirt and how to do that.
> Thanks and best regards, Paulo.
> --
> Paulo Ricardo Paz Vital
> Linux Technology Center, IBM Systems
> http://www.ibm.com/linux/ltc/



--
This message was sent by Atlassian JIRA
(v1000.217.2#18)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Jenkins build is back to normal : ovirt_master_system-tests #386

[jenkins]

See 

___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

oVirt infra daily report - unstable production jobs - 43

[jenkins]

Good morning!

Attached is the HTML page with the jenkins status report. You can see it also 
here:
 - 
http://jenkins.ovirt.org/job/system_jenkins-report/43//artifact/exported-artifacts/upstream_report.html

Cheers,
Jenkins


upstream_report.html
Description: Binary data
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra