[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #3983 - SUCCESS!

2016-12-06 Thread jenkins
Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/3983/,
Build Number: 3983,
Build Status: SUCCESS___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra


[oVirt Jenkins] test-repo_ovirt_experimental_4.0 - Build #3414 - FAILURE!

2016-12-06 Thread jenkins
Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.0/3414/,
Build Number: 3414,
Build Status: FAILURE___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra


[oVirt Jenkins] test-repo_ovirt_experimental_4.0 - Build #3413 - FAILURE!

2016-12-06 Thread jenkins
Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.0/3413/,
Build Number: 3413,
Build Status: FAILURE___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra


[oVirt Jenkins] test-repo_ovirt_experimental_4.0 - Build #3412 - FAILURE!

2016-12-06 Thread jenkins
Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.0/3412/,
Build Number: 3412,
Build Status: FAILURE___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra


[oVirt Jenkins] test-repo_ovirt_experimental_4.0 - Build #3411 - FAILURE!

2016-12-06 Thread jenkins
Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.0/3411/,
Build Number: 3411,
Build Status: FAILURE___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra


[oVirt Jenkins] test-repo_ovirt_experimental_4.0 - Build #3410 - FAILURE!

2016-12-06 Thread jenkins
Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.0/3410/,
Build Number: 3410,
Build Status: FAILURE___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra


Build failed in Jenkins: ovirt_4.0_system-tests #730

2016-12-06 Thread jenkins
See 

Changes:

[Yaniv Kaul] Temporarily move Master to 4.0 DC level.

[Sandro Bonazzola] repo_closure_check: drop fc22 support

[Barak Korren] Remove 'groupinstall' from mock config files

--
[...truncated 632 lines...]
##  rc = 1
##
##! ERROR v
##! Last 20 log entries: 
logs/mocker-epel-7-x86_64.el7.basic_suite_4.0.sh/basic_suite_4.0.sh.log
##!
+ 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
+ exit
Took 231 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=4.0
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_4.0_system-tests] $ /bin/bash -xe /tmp/hudson1547577089412013445.sh
+ echo shell_scripts/system_tests.collect_logs.sh
shell_scripts/system_tests.collect_logs.sh
+ VERSION=4.0
+ SUITE_TYPE=
+ WORKSPACE=
+ OVIRT_SUITE=4.0
+ 
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 ]]
+ for log in '"${logs[@]}"'
+ echo 'Copying ./ovirt-system-tests/logs to exported-artifacts'
Copying ./ovirt-system-tests/logs to exported-artifacts
+ mv ./ovirt-system-tests/logs exported-artifacts/
+ failed=false
+ mock_confs=("$WORKSPACE"/*/mocker*)
+ for mock_conf_file in '"${mock_confs[@]}"'
+ [[ -n 

 ]]
+ echo 'Cleaning up mock '
Cleaning up mock 
+ mock_root=mocker-epel-7-x86_64.el7.cfg
+ mock_root=mocker-epel-7-x86_64.el7
+ my_mock=/usr/bin/mock
+ my_mock+=' 
--configdir=
+ my_mock+=' --root=mocker-epel-7-x86_64.el7'
+ my_mock+=' 
--resultdir=
+ echo 'Killing all mock orphan processes, if any.'
Killing all mock orphan processes, if any.
+ /usr/bin/mock 
--configdir=
 --root=mocker-epel-7-x86_64.el7 
--resultdir= 
--orphanskill
WARNING: Could not find required logging config file: 

Build failed in Jenkins: ovirt_4.0_he-system-tests #584

2016-12-06 Thread jenkins
See 

Changes:

[Yaniv Kaul] Temporarily move Master to 4.0 DC level.

[Sandro Bonazzola] repo_closure_check: drop fc22 support

[Barak Korren] Remove 'groupinstall' from mock config files

--
[...truncated 664 lines...]
##  rc = 127
##
##! ERROR v
##! Last 20 log entries: 
logs/mocker-epel-7-x86_64.el7.he_basic_suite_4.0.sh/he_basic_suite_4.0.sh.log
##!
+ 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
+ exit
Took 345 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=4.0
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_4.0_he-system-tests] $ /bin/bash -xe /tmp/hudson15064946044288893.sh
+ echo shell_scripts/system_tests.collect_logs.sh
shell_scripts/system_tests.collect_logs.sh
+ VERSION=4.0
+ SUITE_TYPE=
+ WORKSPACE=
+ OVIRT_SUITE=4.0
+ 
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 ]]
+ for log in '"${logs[@]}"'
+ echo 'Copying ./ovirt-system-tests/logs to exported-artifacts'
Copying ./ovirt-system-tests/logs to exported-artifacts
+ mv ./ovirt-system-tests/logs exported-artifacts/
+ failed=false
+ mock_confs=("$WORKSPACE"/*/mocker*)
+ for mock_conf_file in '"${mock_confs[@]}"'
+ [[ -n 

 ]]
+ echo 'Cleaning up mock '
Cleaning up mock 
+ mock_root=mocker-epel-7-x86_64.el7.cfg
+ mock_root=mocker-epel-7-x86_64.el7
+ my_mock=/usr/bin/mock
+ my_mock+=' 
--configdir=
+ my_mock+=' --root=mocker-epel-7-x86_64.el7'
+ my_mock+=' 
--resultdir=
+ echo 'Killing all mock orphan processes, if any.'
Killing all mock orphan processes, if any.
+ /usr/bin/mock 
--configdir=
 --root=mocker-epel-7-x86_64.el7 
--resultdir= 
--orphanskill
WARNING: Could not find required logging config 

oVirt infra daily report - unstable production jobs - 160

2016-12-06 Thread 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/160//artifact/exported-artifacts/upstream_report.html

Cheers,
Jenkins

 
 
 
 RHEVM CI Jenkins Daily Report - 06/12/2016
 
00 Unstable Jobs (Production)
 
   
   cockpit-ovirt_ovirt-4.1_build-artifacts-fc23-x86_64
   
   This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the 
jenkins repo.

   
   
   
   fabric-ovirt_master_check-merged-el7-x86_64
   
   This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the 
jenkins repo.

   
   
   
   ovirt-appliance_ovirt-4.0-snapshot_build-artifacts-el7-x86_64
   
   This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the 
jenkins repo.

   
   
   
   ovirt-engine-api-explorer_master_build-artifacts-fc23-x86_64
   
   This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the 
jenkins repo.

   
   
   
   ovirt-engine_3.6_build-artifacts-el6-x86_64
   
   This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the 
jenkins repo.

   
   
   
   ovirt-guest-agent_master_build-artifacts-el6-x86_64
   
   This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the 
jenkins repo.

   
   
   
   ovirt-guest-agent_master_build-artifacts-fc23-x86_64
   
   This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the 
jenkins repo.

   
   
   
   ovirt-hosted-engine-ha_master_build-artifacts-fc24-x86_64
   
   This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the 
jenkins repo.

   
   
   
   ovirt-live_master_experimental_create-iso-el7-x86_64
   
   This job generates a nightly iso of ovirt-live using experimental repos

   
   
   
   ovirt-node-ng_master_build-artifacts-el7-x86_64
   
   This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the 
jenkins repo.

   
   
   
   ovirt-node-ng_ovirt-3.6_build-artifacts-el7-x86_64
   
   This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the 
jenkins repo.

   
   
   
   ovirt-node-ng_ovirt-4.0-pre_build-artifacts-el7-x86_64
   
   This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the 
jenkins repo.

   
   
   
   ovirt-node-ng_ovirt-4.0_build-artifacts-el7-x86_64
   
   This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the 
jenkins repo.

   
   
   
 

[JIRA] (OVIRT-909) Several git errors in several jobs

2016-12-06 Thread Barak Korren (oVirt JIRA)

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Barak Korren reassigned OVIRT-909:
--

Assignee: Barak Korren  (was: infra)

> Several git errors in several jobs
> --
>
> Key: OVIRT-909
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-909
> Project: oVirt - virtualization made easy
>  Issue Type: Bug
>  Components: Jenkins
>Reporter: Fabian Deutsch
>Assignee: Barak Korren
>Priority: Highest
>
> The following jobs all had the same git issue, first cloning then cleaning:
> * * 
> http://jenkins.ovirt.org/user/fabiand/my-views/view/Unstable/job/ovirt-node-ng_ovirt-3.6_build-artifacts-el7-x86_64/138/console
> * 
> http://jenkins.ovirt.org/user/fabiand/my-views/view/Unstable/job/ovirt-node-ng_ovirt-4.1-pre_build-artifacts-el7-x86_64/6/console
> * 
> http://jenkins.ovirt.org/user/fabiand/my-views/view/Unstable/job/ovirt-node-ng_ovirt-master-experimental_build-artifacts-el7-x86_64/19/console
> This happened several times in the last weeks.



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


[JIRA] (OVIRT-909) Several git errors in several jobs

2016-12-06 Thread Barak Korren (oVirt JIRA)

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=23931#comment-23931
 ] 

Barak Korren commented on OVIRT-909:


[~fdeutsch] sudo rm will just mean you need to re-clone everything from Gerrit 
every time the job runs, its a waste of time...

I will try to send a patch for this soon

> Several git errors in several jobs
> --
>
> Key: OVIRT-909
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-909
> Project: oVirt - virtualization made easy
>  Issue Type: Bug
>  Components: Jenkins
>Reporter: Fabian Deutsch
>Assignee: infra
>Priority: Highest
>
> The following jobs all had the same git issue, first cloning then cleaning:
> * * 
> http://jenkins.ovirt.org/user/fabiand/my-views/view/Unstable/job/ovirt-node-ng_ovirt-3.6_build-artifacts-el7-x86_64/138/console
> * 
> http://jenkins.ovirt.org/user/fabiand/my-views/view/Unstable/job/ovirt-node-ng_ovirt-4.1-pre_build-artifacts-el7-x86_64/6/console
> * 
> http://jenkins.ovirt.org/user/fabiand/my-views/view/Unstable/job/ovirt-node-ng_ovirt-master-experimental_build-artifacts-el7-x86_64/19/console
> This happened several times in the last weeks.



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


[JIRA] (OVIRT-909) Several git errors in several jobs

2016-12-06 Thread eyal edri [Administrator] (oVirt JIRA)

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=23930#comment-23930
 ] 

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

[~bkor...@redhat.com] can you help with the patch to fix mock cleanup? I'm not 
sure [~ederevea] is familiar enough with standard ci and we need it fixed soon 
so node jobs can run

> Several git errors in several jobs
> --
>
> Key: OVIRT-909
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-909
> Project: oVirt - virtualization made easy
>  Issue Type: Bug
>  Components: Jenkins
>Reporter: Fabian Deutsch
>Assignee: infra
>Priority: Highest
>
> The following jobs all had the same git issue, first cloning then cleaning:
> * * 
> http://jenkins.ovirt.org/user/fabiand/my-views/view/Unstable/job/ovirt-node-ng_ovirt-3.6_build-artifacts-el7-x86_64/138/console
> * 
> http://jenkins.ovirt.org/user/fabiand/my-views/view/Unstable/job/ovirt-node-ng_ovirt-4.1-pre_build-artifacts-el7-x86_64/6/console
> * 
> http://jenkins.ovirt.org/user/fabiand/my-views/view/Unstable/job/ovirt-node-ng_ovirt-master-experimental_build-artifacts-el7-x86_64/19/console
> This happened several times in the last weeks.



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


[JIRA] (OVIRT-911) Move repo closure to run in STD-CI

2016-12-06 Thread Gil Shinar (oVirt JIRA)
Gil Shinar created OVIRT-911:


 Summary: Move repo closure to run in STD-CI
 Key: OVIRT-911
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-911
 Project: oVirt - virtualization made easy
  Issue Type: Task
Reporter: Gil Shinar
Assignee: infra


Repo closure jobs are currently running on VMs.
We would like to change these jobs to run inside mocks as STD-CI.



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


[JIRA] (OVIRT-910) mock_runner.sh seems to run slower on newer slaves

2016-12-06 Thread Barak Korren (oVirt JIRA)

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=23926#comment-23926
 ] 

Barak Korren commented on OVIRT-910:


the problem with logs is that you need to get then "hot" be cause they may 
disappear fast...

Older slave log (fc24-vm15.phx.ovirt.org):
http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc24-x86_64/5915/
{code}
...
12:01:51 Start: unpacking root cache
12:02:06 Finish: unpacking root cache
...
12:02:07 Init took 17 seconds
{code}


Newer slave log (vm0125.workers-phx.ovirt.org):
http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc24-x86_64/5916/
{code}
...
12:04:19 Start: unpacking root cache
12:05:15 Finish: unpacking root cache
...
12:05:16 Init took 57 seconds
{code}

Then again, on (newer) vm0130.workers-phx.ovirt.org:
http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc24-x86_64/5916/
{code}
...
12:02:45 Start: unpacking root cache
12:03:09 Finish: unpacking root cache
...
12:03:09 Init took 24 seconds
{code}

So not a 100% consistent result, still, we should find out how to get those 40 
seconds back...

BTW I was sure the local disk was mounted on older slaves with noatime, looks 
like that is not the case, maybe we should fix that...

> mock_runner.sh seems to run slower on newer slaves
> --
>
> Key: OVIRT-910
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-910
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: Jenkins
>Reporter: Barak Korren
>Assignee: infra
>
> After implementing speedup improvements for mock_runner.sh (Specifically 
> enabling it to deploy the chroot by extracting a tarball as opposed to 
> installing it with yum every time), I started monitoring run times for vdsm 
> check_patch jobs.
> I've noticed that jobs that are running on the old slaves (fc24-vm*) seem to 
> initialize mock faster then ones running on new slaves (vm*) - 17seconds vs 
> 57 seconds respectively.
> I suspect this may be because the older slaves have a different FS mounted on 
> /var/cache/mock



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


[JIRA] (OVIRT-904) False CI-1 due to unreachable copr-be.cloud.fedoraproject.org

2016-12-06 Thread Greg Sheremeta (oVirt JIRA)

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=23923#comment-23923
 ] 

Greg Sheremeta commented on OVIRT-904:
--

I maintain patternfly on copr. No one else uses it, so we can move it anywhere 
that makes sense.

> False CI-1 due to unreachable copr-be.cloud.fedoraproject.org
> -
>
> Key: OVIRT-904
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-904
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: danken
>Assignee: infra
>
> Many patches on
> https://gerrit.ovirt.org/#/q/topic:passthroughMigration fail CI due to
> failure: repodata/repomd.xml from patternfly: [Errno 256] No more
> mirrors to try.
> http://copr-be.cloud.fedoraproject.org/results/patternfly/patternfly1/epel-7-x86_64/repodata/repomd.xml:
> [Errno 14] curl#7 - "Failed connect to
> copr-be.cloud.fedoraproject.org:80; No route to host"
> http://copr-be.cloud.fedoraproject.org/results/patternfly/patternfly1/epel-7-x86_64



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


[JIRA] (OVIRT-910) mock_runner.sh seems to run slower on newer slaves

2016-12-06 Thread Evgheni Dereveanchin (oVirt JIRA)

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=23920#comment-23920
 ] 

Evgheni Dereveanchin commented on OVIRT-910:


[~bkor...@redhat.com] some logs would be helpful :)

Older slaves with local disk hook use ext4 on the secondary disk while newer 
ones write to rootfs which is XFS. I can try launching a dozen ext4 VMs so that 
we can compare performance.

> mock_runner.sh seems to run slower on newer slaves
> --
>
> Key: OVIRT-910
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-910
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: Jenkins
>Reporter: Barak Korren
>Assignee: infra
>
> After implementing speedup improvements for mock_runner.sh (Specifically 
> enabling it to deploy the chroot by extracting a tarball as opposed to 
> installing it with yum every time), I started monitoring run times for vdsm 
> check_patch jobs.
> I've noticed that jobs that are running on the old slaves (fc24-vm*) seem to 
> initialize mock faster then ones running on new slaves (vm*) - 17seconds vs 
> 57 seconds respectively.
> I suspect this may be because the older slaves have a different FS mounted on 
> /var/cache/mock



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


[JIRA] (OVIRT-910) mock_runner.sh seems to run slower on newer slaves

2016-12-06 Thread Barak Korren (oVirt JIRA)

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Barak Korren updated OVIRT-910:
---
Description: 
After implementing speedup improvements for mock_runner.sh (Specifically 
enabling it to deploy the chroot by extracting a tarball as opposed to 
installing it with yum every time), I started monitoring run times for vdsm 
check_patch jobs.

I've noticed that jobs that are running on the old slaves (fc24-vm*) seem to 
initialize mock faster then ones running on new slaves (vm*) - 17seconds vs 57 
seconds respectively.

I suspect this may be because the older slaves have a different FS mounted on 
/var/cache/mock

  was:
After implementing speedup improvements for mock_runner.sh (Specifically 
enabling it to deploy the chroot by extracting a tarball as opposed to 
installing it with yum every time), I started monitoring run times for vdsm 
check_patch jobs.

I've noticed that jobs that are running on the old slaves (fc24-vm*) seem to 
initialize mock faster then ones running on new slaves (vm*) - 17seconds vs 57 
seconds respectively.

I suspect this may be because the older slaves have a different FS mounted on 
/var/lib/mock


> mock_runner.sh seems to run slower on newer slaves
> --
>
> Key: OVIRT-910
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-910
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: Jenkins
>Reporter: Barak Korren
>Assignee: infra
>
> After implementing speedup improvements for mock_runner.sh (Specifically 
> enabling it to deploy the chroot by extracting a tarball as opposed to 
> installing it with yum every time), I started monitoring run times for vdsm 
> check_patch jobs.
> I've noticed that jobs that are running on the old slaves (fc24-vm*) seem to 
> initialize mock faster then ones running on new slaves (vm*) - 17seconds vs 
> 57 seconds respectively.
> I suspect this may be because the older slaves have a different FS mounted on 
> /var/cache/mock



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


[JIRA] (OVIRT-910) mock_runner.sh seems to run slower on newer slaves

2016-12-06 Thread Barak Korren (oVirt JIRA)

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Barak Korren updated OVIRT-910:
---
Epic Link: OVIRT-400

> mock_runner.sh seems to run slower on newer slaves
> --
>
> Key: OVIRT-910
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-910
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: Jenkins
>Reporter: Barak Korren
>Assignee: infra
>
> After implementing speedup improvements for mock_runner.sh (Specifically 
> enabling it to deploy the chroot by extracting a tarball as opposed to 
> installing it with yum every time), I started monitoring run times for vdsm 
> check_patch jobs.
> I've noticed that jobs that are running on the old slaves (fc24-vm*) seem to 
> initialize mock faster then ones running on new slaves (vm*) - 17seconds vs 
> 57 seconds respectively.
> I suspect this may be because the older slaves have a different FS mounted on 
> /var/lib/mock



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


[JIRA] (OVIRT-910) mock_runner.sh seems to run slower on newer slaves

2016-12-06 Thread Barak Korren (oVirt JIRA)
Barak Korren created OVIRT-910:
--

 Summary: mock_runner.sh seems to run slower on newer slaves
 Key: OVIRT-910
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-910
 Project: oVirt - virtualization made easy
  Issue Type: Improvement
  Components: Jenkins
Reporter: Barak Korren
Assignee: infra


After implementing speedup improvements for mock_runner.sh (Specifically 
enabling it to deploy the chroot by extracting a tarball as opposed to 
installing it with yum every time), I started monitoring run times for vdsm 
check_patch jobs.

I've noticed that jobs that are running on the old slaves (fc24-vm*) seem to 
initialize mock faster then ones running on new slaves (vm*) - 17seconds vs 57 
seconds respectively.

I suspect this may be because the older slaves have a different FS mounted on 
/var/lib/mock



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


[JIRA] (OVIRT-909) Several git errors in several jobs

2016-12-06 Thread Barak Korren (oVirt JIRA)

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=23915#comment-23915
 ] 

Barak Korren commented on OVIRT-909:


Hmm... I can make an educated guess that what we're seeing here is that some 
files in the local git clone belong to the root user as opposed to the jenkins 
user.
This could happen if something from inside mock is running any git commands 
that write to the repo...

I guess what we could do is make mock_cleanup.sh ensure that no file are left 
in $WORKSPACE that do not belong the 'jenkins'

> Several git errors in several jobs
> --
>
> Key: OVIRT-909
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-909
> Project: oVirt - virtualization made easy
>  Issue Type: Bug
>  Components: Jenkins
>Reporter: Fabian Deutsch
>Assignee: infra
>Priority: Highest
>
> The following jobs all had the same git issue, first cloning then cleaning:
> * * 
> http://jenkins.ovirt.org/user/fabiand/my-views/view/Unstable/job/ovirt-node-ng_ovirt-3.6_build-artifacts-el7-x86_64/138/console
> * 
> http://jenkins.ovirt.org/user/fabiand/my-views/view/Unstable/job/ovirt-node-ng_ovirt-4.1-pre_build-artifacts-el7-x86_64/6/console
> * 
> http://jenkins.ovirt.org/user/fabiand/my-views/view/Unstable/job/ovirt-node-ng_ovirt-master-experimental_build-artifacts-el7-x86_64/19/console
> This happened several times in the last weeks.



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


[JIRA] (OVIRT-904) False CI-1 due to unreachable copr-be.cloud.fedoraproject.org

2016-12-06 Thread eyal edri [Administrator] (oVirt JIRA)

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=23914#comment-23914
 ] 

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

[~sbonazo...@redhat.com][~mperina][~gsher...@redhat.com] is it possible to get 
pattenfly from other place than Copr?
We're seeing more and more failures on repos hosted by copr, we might want to 
find a more stable repo on other services.
Who is building/maintaining those builds?

> False CI-1 due to unreachable copr-be.cloud.fedoraproject.org
> -
>
> Key: OVIRT-904
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-904
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: danken
>Assignee: infra
>
> Many patches on
> https://gerrit.ovirt.org/#/q/topic:passthroughMigration fail CI due to
> failure: repodata/repomd.xml from patternfly: [Errno 256] No more
> mirrors to try.
> http://copr-be.cloud.fedoraproject.org/results/patternfly/patternfly1/epel-7-x86_64/repodata/repomd.xml:
> [Errno 14] curl#7 - "Failed connect to
> copr-be.cloud.fedoraproject.org:80; No route to host"
> http://copr-be.cloud.fedoraproject.org/results/patternfly/patternfly1/epel-7-x86_64



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


[JIRA] (OVIRT-904) False CI-1 due to unreachable copr-be.cloud.fedoraproject.org

2016-12-06 Thread Barak Korren (oVirt JIRA)

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=23913#comment-23913
 ] 

Barak Korren commented on OVIRT-904:


Which projects are coming from Copr? Maybe they would like us to host their 
artifacts on resources.ovirt.org (And would happily make their CI systems 
update it with new builds)? Or perhaps they would push into Fedora? or EPEL? or 
CentOS? Or even just GitHub?

I guess if we setup out own mirrors for stuff it will solve our problems, but a 
project that only releases on copr has a problem IMO


> False CI-1 due to unreachable copr-be.cloud.fedoraproject.org
> -
>
> Key: OVIRT-904
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-904
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: danken
>Assignee: infra
>
> Many patches on
> https://gerrit.ovirt.org/#/q/topic:passthroughMigration fail CI due to
> failure: repodata/repomd.xml from patternfly: [Errno 256] No more
> mirrors to try.
> http://copr-be.cloud.fedoraproject.org/results/patternfly/patternfly1/epel-7-x86_64/repodata/repomd.xml:
> [Errno 14] curl#7 - "Failed connect to
> copr-be.cloud.fedoraproject.org:80; No route to host"
> http://copr-be.cloud.fedoraproject.org/results/patternfly/patternfly1/epel-7-x86_64



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


[JIRA] (OVIRT-904) False CI-1 due to unreachable copr-be.cloud.fedoraproject.org

2016-12-06 Thread Evgheni Dereveanchin (oVirt JIRA)

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=23911#comment-23911
 ] 

Evgheni Dereveanchin commented on OVIRT-904:


I do not think there are mirrors for COPR as its content changes too often and 
isn't used by a lot of people.

> False CI-1 due to unreachable copr-be.cloud.fedoraproject.org
> -
>
> Key: OVIRT-904
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-904
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: danken
>Assignee: infra
>
> Many patches on
> https://gerrit.ovirt.org/#/q/topic:passthroughMigration fail CI due to
> failure: repodata/repomd.xml from patternfly: [Errno 256] No more
> mirrors to try.
> http://copr-be.cloud.fedoraproject.org/results/patternfly/patternfly1/epel-7-x86_64/repodata/repomd.xml:
> [Errno 14] curl#7 - "Failed connect to
> copr-be.cloud.fedoraproject.org:80; No route to host"
> http://copr-be.cloud.fedoraproject.org/results/patternfly/patternfly1/epel-7-x86_64



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


[JIRA] (OVIRT-904) False CI-1 due to unreachable copr-be.cloud.fedoraproject.org

2016-12-06 Thread eyal edri [Administrator] (oVirt JIRA)

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=23908#comment-23908
 ] 

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

This won't prevent it from failing in the future.
[~ederevea] is it possible to add more mirrors here as you did for std ci?

> False CI-1 due to unreachable copr-be.cloud.fedoraproject.org
> -
>
> Key: OVIRT-904
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-904
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: danken
>Assignee: infra
>
> Many patches on
> https://gerrit.ovirt.org/#/q/topic:passthroughMigration fail CI due to
> failure: repodata/repomd.xml from patternfly: [Errno 256] No more
> mirrors to try.
> http://copr-be.cloud.fedoraproject.org/results/patternfly/patternfly1/epel-7-x86_64/repodata/repomd.xml:
> [Errno 14] curl#7 - "Failed connect to
> copr-be.cloud.fedoraproject.org:80; No route to host"
> http://copr-be.cloud.fedoraproject.org/results/patternfly/patternfly1/epel-7-x86_64



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


[oVirt Jenkins] test-repo_ovirt_experimental_3.6 - Build #4285 - SUCCESS!

2016-12-06 Thread jenkins
Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_3.6/4285/,
Build Number: 4285,
Build Status: SUCCESS___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra


[JIRA] (OVIRT-909) Several git errors in several jobs

2016-12-06 Thread eyal edri [Administrator] (oVirt JIRA)

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=23907#comment-23907
 ] 

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

[~ederevea] I think you have another ticket on it, need to find it, but as it 
continuous to happen on multiple jobs, please give it high priority, 
We can do a more aggressive cleanup before git clone or shutdown problematic 
slaves if it happens only on specific ones, but let's address it now even with 
the cost of adding a few more seconds to runtime until we have a proper 
solution.

> Several git errors in several jobs
> --
>
> Key: OVIRT-909
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-909
> Project: oVirt - virtualization made easy
>  Issue Type: Bug
>  Components: Jenkins
>Reporter: Fabian Deutsch
>Assignee: infra
>Priority: Highest
>
> The following jobs all had the same git issue, first cloning then cleaning:
> * * 
> http://jenkins.ovirt.org/user/fabiand/my-views/view/Unstable/job/ovirt-node-ng_ovirt-3.6_build-artifacts-el7-x86_64/138/console
> * 
> http://jenkins.ovirt.org/user/fabiand/my-views/view/Unstable/job/ovirt-node-ng_ovirt-4.1-pre_build-artifacts-el7-x86_64/6/console
> * 
> http://jenkins.ovirt.org/user/fabiand/my-views/view/Unstable/job/ovirt-node-ng_ovirt-master-experimental_build-artifacts-el7-x86_64/19/console
> This happened several times in the last weeks.



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


[JIRA] (OVIRT-909) Several git errors in several jobs

2016-12-06 Thread Fabian Deutsch (oVirt JIRA)
Fabian Deutsch created OVIRT-909:


 Summary: Several git errors in several jobs
 Key: OVIRT-909
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-909
 Project: oVirt - virtualization made easy
  Issue Type: Bug
  Components: Jenkins
Reporter: Fabian Deutsch
Assignee: infra
Priority: Highest


The following jobs all had the same git issue, first cloning then cleaning:

* * 
http://jenkins.ovirt.org/user/fabiand/my-views/view/Unstable/job/ovirt-node-ng_ovirt-3.6_build-artifacts-el7-x86_64/138/console
* 
http://jenkins.ovirt.org/user/fabiand/my-views/view/Unstable/job/ovirt-node-ng_ovirt-4.1-pre_build-artifacts-el7-x86_64/6/console
* 
http://jenkins.ovirt.org/user/fabiand/my-views/view/Unstable/job/ovirt-node-ng_ovirt-master-experimental_build-artifacts-el7-x86_64/19/console

This happened several times in the last weeks.



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


[JIRA] (OVIRT-908) jenkins failures

2016-12-06 Thread eyal edri [Administrator] (oVirt JIRA)

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=23905#comment-23905
 ] 

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

[~sbend...@redhat.com] please check why the jobs isn't archiving logs and then 
we need to see what the error was to determine if its false or not.

> jenkins failures
> 
>
> Key: OVIRT-908
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-908
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Martin Polednik
>Assignee: infra
>
> Hi,
> after pushing update to my patch series[1], I've been greeted with
> unhealthy amount of jenkins failures. Actually, it's a single fail
> that affected all but one(!) patch.
> The failure: ERROR: Command failed. See logs for output. [2]
> Can we get these issues solved or have some
> false-positive/false-negative protection (preferably both)?
> [1] https://gerrit.ovirt.org/#/q/topic:hostdev-caching
> [2] 
> http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc24-x86_64/5788/console
> Regards,
> mpolednik



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


[JIRA] (OVIRT-908) jenkins failures

2016-12-06 Thread eyal edri [Administrator] (oVirt JIRA)

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=23906#comment-23906
 ] 

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

What makes you think its false positives?
We need to look at the logs ( which I can't see in the build, and needs to
be fixed ).


On Tue, Dec 6, 2016 at 1:02 PM, Martin Polednik (oVirt JIRA) <




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

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


> jenkins failures
> 
>
> Key: OVIRT-908
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-908
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Martin Polednik
>Assignee: infra
>
> Hi,
> after pushing update to my patch series[1], I've been greeted with
> unhealthy amount of jenkins failures. Actually, it's a single fail
> that affected all but one(!) patch.
> The failure: ERROR: Command failed. See logs for output. [2]
> Can we get these issues solved or have some
> false-positive/false-negative protection (preferably both)?
> [1] https://gerrit.ovirt.org/#/q/topic:hostdev-caching
> [2] 
> http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc24-x86_64/5788/console
> Regards,
> mpolednik



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


Re: [JIRA] (OVIRT-908) jenkins failures

2016-12-06 Thread Eyal Edri
What makes you think its false positives?
We need to look at the logs ( which I can't see in the build, and needs to
be fixed ).


On Tue, Dec 6, 2016 at 1:02 PM, Martin Polednik (oVirt JIRA) <
j...@ovirt-jira.atlassian.net> wrote:

> Martin Polednik created OVIRT-908:
> -
>
>  Summary: jenkins failures
>  Key: OVIRT-908
>  URL: https://ovirt-jira.atlassian.net/browse/OVIRT-908
>  Project: oVirt - virtualization made easy
>   Issue Type: By-EMAIL
> Reporter: Martin Polednik
> Assignee: infra
>
>
> Hi,
>
> after pushing update to my patch series[1], I've been greeted with
> unhealthy amount of jenkins failures. Actually, it's a single fail
> that affected all but one(!) patch.
>
> The failure: ERROR: Command failed. See logs for output. [2]
>
> Can we get these issues solved or have some
> false-positive/false-negative protection (preferably both)?
>
> [1] https://gerrit.ovirt.org/#/q/topic:hostdev-caching
> [2] http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc24-
> x86_64/5788/console
>
> Regards,
> mpolednik
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v1000.610.2#100023)
> ___
> Infra mailing list
> Infra@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra
>



-- 
Eyal Edri
Associate Manager
RHV DevOps
EMEA ENG Virtualization R
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


[JIRA] (OVIRT-908) jenkins failures

2016-12-06 Thread Martin Polednik (oVirt JIRA)
Martin Polednik created OVIRT-908:
-

 Summary: jenkins failures
 Key: OVIRT-908
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-908
 Project: oVirt - virtualization made easy
  Issue Type: By-EMAIL
Reporter: Martin Polednik
Assignee: infra


Hi,

after pushing update to my patch series[1], I've been greeted with
unhealthy amount of jenkins failures. Actually, it's a single fail
that affected all but one(!) patch.

The failure: ERROR: Command failed. See logs for output. [2]

Can we get these issues solved or have some
false-positive/false-negative protection (preferably both)?

[1] https://gerrit.ovirt.org/#/q/topic:hostdev-caching
[2] 
http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc24-x86_64/5788/console

Regards,
mpolednik



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


[JIRA] (OVIRT-907) Add CI for mock_runner.sh

2016-12-06 Thread Barak Korren (oVirt JIRA)

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Barak Korren updated OVIRT-907:
---
Epic Link: OVIRT-400

> Add CI for mock_runner.sh
> -
>
> Key: OVIRT-907
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-907
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: Jenkins
>Reporter: Barak Korren
>Assignee: infra
>
> We have some CI jobs running on our "Jenkins" repo right now. Those jobs 
> mostly check YAML, but they are also useful for checking changes to 
> mock_runner.sh because they are running inside it. However:
> # These jobs do a full YAML check even when it is not needed.
> # We're not actually checking mock_runner.sh for all the platforms it 
> simulates.
> We've already seem some regressions happen in the CI system because we don't 
> have enough tests for mock_runner.sh
> This ticket is for creating good CI coverage for mock_runner.sh, all that is 
> needed to be done in practice is make some changes to the check_patch.sh 
> script and the YAML so that:
> * YAML checking is skipped if no JJB-related changes were done
> * Various features of mock_runner like the installation of packages for the 
> *.packages files are checked.
> * The tests are ran for all platforms that mock_runner.sh supports.



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


[JIRA] (OVIRT-907) Add CI for mock_runner.sh

2016-12-06 Thread Barak Korren (oVirt JIRA)
Barak Korren created OVIRT-907:
--

 Summary: Add CI for mock_runner.sh
 Key: OVIRT-907
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-907
 Project: oVirt - virtualization made easy
  Issue Type: Improvement
  Components: Jenkins
Reporter: Barak Korren
Assignee: infra


We have some CI jobs running on our "Jenkins" repo right now. Those jobs mostly 
check YAML, but they are also useful for checking changes to mock_runner.sh 
because they are running inside it. However:
# These jobs do a full YAML check even when it is not needed.
# We're not actually checking mock_runner.sh for all the platforms it simulates.

We've already seem some regressions happen in the CI system because we don't 
have enough tests for mock_runner.sh

This ticket is for creating good CI coverage for mock_runner.sh, all that is 
needed to be done in practice is make some changes to the check_patch.sh script 
and the YAML so that:
* YAML checking is skipped if no JJB-related changes were done
* Various features of mock_runner like the installation of packages for the 
*.packages files are checked.
* The tests are ran for all platforms that mock_runner.sh supports.




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


Re: engine 3.6 build fails

2016-12-06 Thread Barak Korren
>
> Here, this should fix this:
> https://gerrit.ovirt.org/#/c/67860/
>
> Lets merge it quickly (and then I'll have to erase the mock cache on
> the slave to get the chroot rebuilt)

Ok.
Patch merged and cache erased - please try rerunning the engine build.


-- 
Barak Korren
bkor...@redhat.com
RHCE, RHCi, RHV-DevOps Team
https://ifireball.wordpress.com/
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra


[JIRA] (OVIRT-906) Permissions to new user

2016-12-06 Thread Shlomo Ben David (oVirt JIRA)

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Shlomo Ben David reassigned OVIRT-906:
--

Assignee: Shlomo Ben David  (was: infra)

> Permissions to new user
> ---
>
> Key: OVIRT-906
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-906
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Benny Zlotnik
>Assignee: Shlomo Ben David
>
> Hi,
> Please grant my Jenkins user (bzlotnik) the dev permissions
> Thanks!



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


[JIRA] (OVIRT-906) Permissions to new user

2016-12-06 Thread Shlomo Ben David (oVirt JIRA)

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=23902#comment-23902
 ] 

Shlomo Ben David commented on OVIRT-906:


Hi Benny,

I added your user to the dev role in Jenkins.
Please sign out and  sign back into Jenkins to apply the new role.


Best Regards,

Shlomi Ben-David | DevOps Engineer | Red Hat ISRAEL
RHCSA | RHCE
IRC: shlomibendavid (on #rhev-integ, #rhev-dev, #rhev-ci)

OPEN SOURCE - 1 4 011 && 011 4 1

On Tue, Dec 6, 2016 at 10:44 AM, Benny Zlotnik (oVirt JIRA) <



> Permissions to new user
> ---
>
> Key: OVIRT-906
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-906
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Benny Zlotnik
>Assignee: infra
>
> Hi,
> Please grant my Jenkins user (bzlotnik) the dev permissions
> Thanks!



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


Re: [JIRA] (OVIRT-906) Permissions to new user

2016-12-06 Thread Shlomo Ben David
Hi Benny,

I added your user to the dev role in Jenkins.
Please sign out and  sign back into Jenkins to apply the new role.


Best Regards,

Shlomi Ben-David | DevOps Engineer | Red Hat ISRAEL
RHCSA | RHCE
IRC: shlomibendavid (on #rhev-integ, #rhev-dev, #rhev-ci)

OPEN SOURCE - 1 4 011 && 011 4 1

On Tue, Dec 6, 2016 at 10:44 AM, Benny Zlotnik (oVirt JIRA) <
j...@ovirt-jira.atlassian.net> wrote:

> Benny Zlotnik created OVIRT-906:
> ---
>
>  Summary: Permissions to new user
>  Key: OVIRT-906
>  URL: https://ovirt-jira.atlassian.net/browse/OVIRT-906
>  Project: oVirt - virtualization made easy
>   Issue Type: By-EMAIL
> Reporter: Benny Zlotnik
> Assignee: infra
>
>
> Hi,
>
> Please grant my Jenkins user (bzlotnik) the dev permissions
>
> Thanks!
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v1000.610.2#100023)
> ___
> Infra mailing list
> Infra@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra
>
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra


[oVirt Jenkins] test-repo_ovirt_experimental_4.0 - Build #3390 - SUCCESS!

2016-12-06 Thread jenkins
Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.0/3390/,
Build Number: 3390,
Build Status: SUCCESS___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra


Re: engine 3.6 build fails

2016-12-06 Thread Barak Korren
On 6 December 2016 at 10:16, Barak Korren  wrote:
>>
>> I think that the issue could be related to this change:
>> https://gerrit.ovirt.org/#/c/67801
>>
>> adding Barak
>
> Hmm... yes my bad... it has to do with the el6 chroots using
> "groupsinstall" to setup things instead of "install"... I'll try to
> see if I can work around that... (I'm thinking I can get away with
> moving el6 to use "install" b/c the 'yum' doing the setup is the one
> on the host which should be el7 or newer)

Here, this should fix this:
https://gerrit.ovirt.org/#/c/67860/

Lets merge it quickly (and then I'll have to erase the mock cache on
the slave to get the chroot rebuilt)

One more thing - please make sure to address such emails to infra as
well next time so other infra members know what is going on...

-- 
Barak Korren
bkor...@redhat.com
RHCE, RHCi, RHV-DevOps Team
https://ifireball.wordpress.com/
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra


[JIRA] (OVIRT-906) Permissions to new user

2016-12-06 Thread Benny Zlotnik (oVirt JIRA)
Benny Zlotnik created OVIRT-906:
---

 Summary: Permissions to new user
 Key: OVIRT-906
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-906
 Project: oVirt - virtualization made easy
  Issue Type: By-EMAIL
Reporter: Benny Zlotnik
Assignee: infra


Hi,

Please grant my Jenkins user (bzlotnik) the dev permissions

Thanks!



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


Re: Permissions for the manual trigger

2016-12-06 Thread Eyal Edri
You need to create a new user in Jenkins and after that you can get the
'dev' role that will grant you access.
Please reply here or open a ticket on jira.ovirt.org (
infra-supp...@ovirt.org) once you are logged in and we'll update the
permissions.

On Tue, Dec 6, 2016 at 10:18 AM, Benny Zlotnik  wrote:

> Hi,
>
> I am new in the oVirt storage team and I am getting this error:
> "bzlotnik is missing the Gerrit/ManualTrigger permission"
>
> Can anyone please grant me the permission? My username is bzlotnik
>
> Thanks!
>
> ___
> Infra mailing list
> Infra@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra
>
>


-- 
Eyal Edri
Associate Manager
RHV DevOps
EMEA ENG Virtualization R
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


[JIRA] (OVIRT-905) lago_master_check jobs still require fc23 slaves

2016-12-06 Thread Nadav Goldin (oVirt JIRA)

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=23901#comment-23901
 ] 

Nadav Goldin commented on OVIRT-905:


No problem to change it, think it is just old left-overs, we test fc24 anyways.


> lago_master_check jobs still require fc23 slaves
> 
>
> Key: OVIRT-905
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-905
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>Reporter: Evgheni Dereveanchin
>Assignee: infra
>
> Lago check jobs require "nested && fc23" labels, and as Fedora 23 will be EOL 
> in a couple of weeks we need to check if we can change this to newer Fedora 
> versions or CentOS



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


Permissions for the manual trigger

2016-12-06 Thread Benny Zlotnik
Hi,

I am new in the oVirt storage team and I am getting this error:
"bzlotnik is missing the Gerrit/ManualTrigger permission"

Can anyone please grant me the permission? My username is bzlotnik

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


[oVirt Jenkins] test-repo_ovirt_experimental_4.0 - Build #3389 - FAILURE!

2016-12-06 Thread jenkins
Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.0/3389/,
Build Number: 3389,
Build Status: FAILURE___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra