[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #4359 - FAILURE!

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


Build failed in Jenkins: ovirt_master_system-tests #879

2016-12-21 Thread jenkins
See 

Changes:

[Yaniv Kaul] Fixes and changes to storage tests

[Sandro Bonazzola] ovirt-appliance: exclude f23 node builders

--
[...truncated 673 lines...]
+ 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 42 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/hudson8432573489038681762.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 -x
echo "shell-scripts/mock_cleanup.sh"
# Make clear this is the cleanup, helps reading the jenkins logs
cat < 0 ]] && sleep "$UMOUNT_RETRY_DELAY"
# Try to umount
sudo umount --lazy "$mount" && return 0
# See if the mount is already not there despite failing
findmnt --kernel --first "$mount" > /dev/null && return 0
done
echo "ERROR:  Failed to umount $mount."
return 1
}

# restore the permissions in the working dir, as sometimes it leaves files
# owned by root and then the 'cleanup workspace' from jenkins job fails to
# clean and breaks the jobs
sudo chown -R "$USER" "$WORKSPACE"

# Archive the logs, we want them anyway
logs=(
./*log
./*/logs
)

if [[ "$logs" ]]; then
for log in "${logs[@]}"; do
[[ "$log" = ./exported-artifacts/* ]] && continue
echo "Copying ${log} to exported-artifacts"
mv $log exported-artifacts/
done
fi

# stop any processes running inside the chroot
failed=false
mock_confs=("$WORKSPACE"/*/mocker*)
# Clean current jobs mockroot if any
for mock_conf_file in "${mock_confs[@]}"; do
[[ "$mock_conf_file" ]] || continue
echo "Cleaning up mock $mock_conf"
mock_root="${mock_conf_file##*/}"
mock_root="${mock_root%.*}"
my_mock="/usr/bin/mock"
my_mock+=" --configdir=${mock_conf_file%/*}"
my_mock+=" --root=${mock_root}"
my_mock+=" --resultdir=$WORKSPACE"

#TODO: investigate why mock --clean fails to umount certain dirs sometimes,
#so we can use it instead of manually doing all this.
echo "Killing all mock orphan processes, if any."
$my_mock \
--orphanskill \
|| {
echo "ERROR:  Failed to kill orphans on $chroot."
failed=true
}

mock_root="$(\
grep \
-Po "(?<=config_opts\['root'\] = ')[^']*" \
"$mock_conf_file" \
)" || :
[[ "$mock_root" ]] || continue
mounts=($(mount | awk '{print $3}' | grep "$mock_root")) || :
if [[ "$mounts" ]]; then
echo "Found mounted dirs inside the chroot $chroot. Trying to umount."
fi
for mount in "${mounts[@]}"; do
safe_umount "$mount" || failed=true
done
done

# Clean any leftover chroot from other jobs
for mock_root in /var/lib/mock/*; do
this_chroot_failed=false
mounts=($(cut -d\  -f2 /proc/mounts | grep "$mock_root" 

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #4358 - FAILURE!

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


[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #4357 - FAILURE!

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


[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #4356 - FAILURE!

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


[JIRA] (OVIRT-968) Import image-tools in gerrit

2016-12-21 Thread sbonazzo (oVirt JIRA)
sbonazzo created OVIRT-968:
--

 Summary: Import image-tools in gerrit
 Key: OVIRT-968
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-968
 Project: oVirt - virtualization made easy
  Issue Type: By-EMAIL
Reporter: sbonazzo
Assignee: infra


Please import https://github.com/fabiand/image-tools.git
in ovirt gerrit.
Thanks,

-- 
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.621.5#100023)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra


[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #4355 - FAILURE!

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


[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #4354 - FAILURE!

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


[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #4353 - FAILURE!

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


[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #4352 - FAILURE!

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


[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #4351 - FAILURE!

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


Build failed in Jenkins: ovirt_master_system-tests #878

2016-12-21 Thread jenkins
See 

Changes:

[Yaniv Kaul] Fixes and changes to storage tests

[Sandro Bonazzola] ovirt-hosted-engine-ha: added 4.1 branch

[Sandro Bonazzola] ovirt-release: move to 4.1 branch

[Sandro Bonazzola] cockpit-ovirt: exclude fc23 from 4.1

[Gil Shinar] Fix bugs in sdk yamls

--
[...truncated 762 lines...]
+ 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 52 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/hudson6460262332536282065.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 -x
echo "shell-scripts/mock_cleanup.sh"
# Make clear this is the cleanup, helps reading the jenkins logs
cat < 0 ]] && sleep "$UMOUNT_RETRY_DELAY"
# Try to umount
sudo umount --lazy "$mount" && return 0
# See if the mount is already not there despite failing
findmnt --kernel --first "$mount" > /dev/null && return 0
done
echo "ERROR:  Failed to umount $mount."
return 1
}

# restore the permissions in the working dir, as sometimes it leaves files
# owned by root and then the 'cleanup workspace' from jenkins job fails to
# clean and breaks the jobs
sudo chown -R "$USER" "$WORKSPACE"

# Archive the logs, we want them anyway
logs=(
./*log
./*/logs
)

if [[ "$logs" ]]; then
for log in "${logs[@]}"; do
[[ "$log" = ./exported-artifacts/* ]] && continue
echo "Copying ${log} to exported-artifacts"
mv $log exported-artifacts/
done
fi

# stop any processes running inside the chroot
failed=false
mock_confs=("$WORKSPACE"/*/mocker*)
# Clean current jobs mockroot if any
for mock_conf_file in "${mock_confs[@]}"; do
[[ "$mock_conf_file" ]] || continue
echo "Cleaning up mock $mock_conf"
mock_root="${mock_conf_file##*/}"
mock_root="${mock_root%.*}"
my_mock="/usr/bin/mock"
my_mock+=" --configdir=${mock_conf_file%/*}"
my_mock+=" --root=${mock_root}"
my_mock+=" --resultdir=$WORKSPACE"

#TODO: investigate why mock --clean fails to umount certain dirs sometimes,
#so we can use it instead of manually doing all this.
echo "Killing all mock orphan processes, if any."
$my_mock \
--orphanskill \
|| {
echo "ERROR:  Failed to kill orphans on $chroot."
failed=true
}

mock_root="$(\
grep \
-Po "(?<=config_opts\['root'\] = ')[^']*" \
"$mock_conf_file" \
)" || :
[[ "$mock_root" ]] || continue
mounts=($(mount | awk '{print $3}' | grep "$mock_root")) || :
if [[ "$mounts" ]]; then
echo "Found mounted dirs inside the chroot $chroot. Trying to umount."
fi
for mount in "${mounts[@]}"; do
safe_umount "$mount" || failed=true
done
done

# Clean any leftover 

Build failed in Jenkins: ovirt_4.1_system-tests #9

2016-12-21 Thread jenkins
See 

Changes:

[Yaniv Kaul] Fixes and changes to storage tests

[Sandro Bonazzola] ovirt-hosted-engine-ha: added 4.1 branch

[Sandro Bonazzola] ovirt-release: move to 4.1 branch

[Sandro Bonazzola] cockpit-ovirt: exclude fc23 from 4.1

[Gil Shinar] Fix bugs in sdk yamls

--
[...truncated 750 lines...]
+ 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 62 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.1
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.1_system-tests] $ /bin/bash -xe /tmp/hudson2115846140055103178.sh
+ echo shell_scripts/system_tests.collect_logs.sh
shell_scripts/system_tests.collect_logs.sh
+ VERSION=4.1
+ SUITE_TYPE=
+ WORKSPACE=
+ OVIRT_SUITE=4.1
+ 
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 -x
echo "shell-scripts/mock_cleanup.sh"
# Make clear this is the cleanup, helps reading the jenkins logs
cat < 0 ]] && sleep "$UMOUNT_RETRY_DELAY"
# Try to umount
sudo umount --lazy "$mount" && return 0
# See if the mount is already not there despite failing
findmnt --kernel --first "$mount" > /dev/null && return 0
done
echo "ERROR:  Failed to umount $mount."
return 1
}

# restore the permissions in the working dir, as sometimes it leaves files
# owned by root and then the 'cleanup workspace' from jenkins job fails to
# clean and breaks the jobs
sudo chown -R "$USER" "$WORKSPACE"

# Archive the logs, we want them anyway
logs=(
./*log
./*/logs
)

if [[ "$logs" ]]; then
for log in "${logs[@]}"; do
[[ "$log" = ./exported-artifacts/* ]] && continue
echo "Copying ${log} to exported-artifacts"
mv $log exported-artifacts/
done
fi

# stop any processes running inside the chroot
failed=false
mock_confs=("$WORKSPACE"/*/mocker*)
# Clean current jobs mockroot if any
for mock_conf_file in "${mock_confs[@]}"; do
[[ "$mock_conf_file" ]] || continue
echo "Cleaning up mock $mock_conf"
mock_root="${mock_conf_file##*/}"
mock_root="${mock_root%.*}"
my_mock="/usr/bin/mock"
my_mock+=" --configdir=${mock_conf_file%/*}"
my_mock+=" --root=${mock_root}"
my_mock+=" --resultdir=$WORKSPACE"

#TODO: investigate why mock --clean fails to umount certain dirs sometimes,
#so we can use it instead of manually doing all this.
echo "Killing all mock orphan processes, if any."
$my_mock \
--orphanskill \
|| {
echo "ERROR:  Failed to kill orphans on $chroot."
failed=true
}

mock_root="$(\
grep \
-Po "(?<=config_opts\['root'\] = ')[^']*" \
"$mock_conf_file" \
)" || :
[[ "$mock_root" ]] || continue
mounts=($(mount | awk '{print $3}' | grep "$mock_root")) || :
if [[ "$mounts" ]]; then
echo "Found mounted dirs inside the chroot $chroot. Trying to umount."
fi
for mount in "${mounts[@]}"; do
safe_umount "$mount" || failed=true
done
done

# Clean any leftover chroot from other jobs
for mock_root in /var/lib/mock/*; 

oVirt infra daily report - unstable production jobs - 175

2016-12-21 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/175//artifact/exported-artifacts/upstream_report.html

Cheers,
Jenkins

 
 
 
 RHEVM CI Jenkins Daily Report - 13/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_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-appliance_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-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-extension-aaa-ldap_4.0_create-rpms-el7-x86_64_merged
   
   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-extension-aaa-ldap_master_create-rpms-el7-x86_64_merged
   
   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-extension-aaa-ldap_master_create-rpms-fc24-x86_64_merged
   
   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_master_find-bugs_merged
   
   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-hosted-engine-ha_3.6_create-rpms-el7-x86_64_merged
   
   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 

oVirt infra daily report - unstable production jobs - 175

2016-12-21 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/175//artifact/exported-artifacts/upstream_report.html

Cheers,
Jenkins

 
 
 
 RHEVM CI Jenkins Daily Report - 13/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_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-appliance_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-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-extension-aaa-ldap_4.0_create-rpms-el7-x86_64_merged
   
   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-extension-aaa-ldap_master_create-rpms-el7-x86_64_merged
   
   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-extension-aaa-ldap_master_create-rpms-fc24-x86_64_merged
   
   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_master_find-bugs_merged
   
   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-hosted-engine-ha_3.6_create-rpms-el7-x86_64_merged
   
   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 

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #4350 - FAILURE!

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


[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #4349 - FAILURE!

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


[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #4348 - FAILURE!

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


[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #4347 - FAILURE!

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


Fwd: Fedora 23 End Of Life

2016-12-21 Thread Sandro Bonazzola
FYI.
-- Messaggio inoltrato --
Da: "Mohan Boddu" 
Data: 21/Dic/2016 04:05
Oggetto: Fedora 23 End Of Life
A: , <
test-annou...@lists.fedoraproject.org>, <
devel-annou...@lists.fedoraproject.org>
Cc:

As of the 20th of December 2016, Fedora 23 has reached its end of life
for updates and support. No further updates, including security
updates, will be available for Fedora 23. A previous reminder was sent
on 28th of November 2016 [0]. Fedora 24 will continue to receive
updates until approximately one month after the release of Fedora 26.
The maintenance schedule of Fedora releases is documented on the
Fedora Project wiki [1]. The Fedora Project wiki also contains
instructions [2] on how to upgrade from a previous release of Fedora
to a version receiving updates.

Mohan Boddu.

[0]https://lists.fedoraproject.org/archives/list/devel@lists.
fedoraproject.org/thread/HLHKRTIB33EDZXP624GHF2OZLHWAGKSJ/#
Q5O44X4BEBOYEKAEVLSXVI44DSNVHBYG
[1]https://fedoraproject.org/wiki/Fedora_Release_Life_
Cycle#Maintenance_Schedule
[2]https://fedoraproject.org/wiki/Upgrading?rd=DistributionUpgrades
___
devel-announce mailing list -- devel-annou...@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra


[JIRA] (OVIRT-938) Fix Jenkins slave connection dying on vdsm check_merged jobs

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

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

Barak Korren commented on OVIRT-938:


Got this from the slave log in Jenkis:
{code}
ERROR: Connection terminated
ESC[8mha:WB+LCP9b85aBtbiIQSmjNKU4P08vOT+vOD8nVc8DzHWtSE4tKMnMz/PLL0ldFVf2c+b/lb5MDAwVRQxSaBqcITRIIQMEMIIUFgAAckCEiWA=ESC[0mjava.io.IOException:
 Unexpected termination of the channel
at 
hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50)
Caused by: java.io.EOFException
at 
java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2353)
at 
java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2822)
at 
java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:804)
at java.io.ObjectInputStream.(ObjectInputStream.java:301)
at 
hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:48)
at 
hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34)
at 
hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48)
Slave JVM has terminated. Exit signal=TERM
[12/21/16 15:23:34] [SSH] Connection closed.
{code}

> Fix Jenkins slave connection dying on vdsm check_merged jobs
> 
>
> Key: OVIRT-938
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-938
> Project: oVirt - virtualization made easy
>  Issue Type: Bug
>  Components: Jenkins
>Reporter: Barak Korren
>Assignee: infra
>
> Something in the vdsm build_artifacs job makes the Jenkins slave disconnect 
> when it is running. This in turn makes the cleanup scripts not run on the 
> slave leaving it dirty enough to make the next job on that slave fail.
> Example of this can be seen here:
> http://jenkins.ovirt.org/job/vdsm_master_check-merged-el7-x86_64/692/console
> Relevant log lines:
> {code}
> 21:49:00 Ran 44 tests in 1231.988s
> 21:49:00 
> 21:49:00 OK
> 21:49:00 + return 0
> 21:49:00 sh: [13086: 1 (255)] tcsetattr: Inappropriate ioctl for device
> 21:49:00 Took 2464 seconds
> 21:49:00 ===
> 21:49:00 logout
> 21:49:01 Slave went offline during the build
> 21:49:01 ERROR: Connection was broken: java.io.IOException: Unexpected 
> termination of the channel
> 21:49:01  at 
> hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50)
> 21:49:01 Caused by: java.io.EOFException
> 21:49:01  at 
> java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2353)
> 21:49:01  at 
> java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2822)
> 21:49:01  at 
> java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:804)
> 21:49:01  at java.io.ObjectInputStream.(ObjectInputStream.java:301)
> 21:49:01  at 
> hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:48)
> 21:49:01  at 
> hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34)
> 21:49:01  at 
> hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48)
> 21:49:01 
> 21:49:01 Build step 'Execute shell' marked build as failure
> 21:49:01 Performing Post build task...
> 21:49:01 Match found for :.* : True
> 21:49:01 Logical operation result is TRUE
> 21:49:01 Running script  : #!/bin/bash -x
> 21:49:01 echo "shell-scripts/mock_cleanup.sh"
> ... SNIP ...
> 21:49:01 Exception when executing the batch command : no workspace from node 
> hudson.slaves.DumbSlave[fc24-vm06.phx.ovirt.org] which is computer 
> hudson.slaves.SlaveComputer@30863c81 and has channel null
> 21:49:01 Build step 'Post build task' marked build as failure
> 21:49:02 ERROR: Step ?Archive the artifacts? failed: no workspace for 
> vdsm_master_check-merged-el7-x86_64 #692
> 21:49:02 ERROR: Failed to evaluate groovy script.
> 21:49:02 java.lang.NullPointerException: Cannot invoke method child() on null 
> object
> 21:49:02  at 
> org.codehaus.groovy.runtime.NullObject.invokeMethod(NullObject.java:77)
> 21:49:02  at 
> org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:45)
> 21:49:02  at 
> org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42)
> 21:49:02  at 
> org.codehaus.groovy.runtime.callsite.NullCallSite.call(NullCallSite.java:32)
> 21:49:02  at 
> org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42)
> 21:49:02  at 
> org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:108)
> 21:49:02  at 
> 

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #4346 - FAILURE!

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


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

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


[JIRA] (OVIRT-954) Fwd: http://lists.ovirt.org/pipermail/announce/ is not reachable

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

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

Evgheni Dereveanchin reassigned OVIRT-954:
--

Assignee: Evgheni Dereveanchin  (was: infra)

> Fwd: http://lists.ovirt.org/pipermail/announce/ is not reachable
> 
>
> Key: OVIRT-954
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-954
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: sbonazzo
>Assignee: Evgheni Dereveanchin
>
> The lists server is not reachable anymore. Looks like a dns issue:
> $ traceroute lists.ovirt.org
> lists.ovirt.org: Name or service not known
> -- 
> 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.621.5#100023)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra


[JIRA] (OVIRT-938) Fix Jenkins slave connection dying on vdsm check_merged jobs

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

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

Barak Korren commented on OVIRT-938:


Trying to get more info about this, here are the journal lines we get on the 
slave when the job fails:
{code}
Dec 21 15:23:34 vm0136.workers-phx.ovirt.org libvirtd[17504]: End of file while 
reading data: Input/output error
Dec 21 15:23:34 vm0136.workers-phx.ovirt.org audit[5410]: USER_END pid=5410 
uid=0 auid=1012 ses=3 subj=system_u:system_r:sshd_t:s0-s0:c0.c1023 
msg='op=login id=1012 exe="/usr/sbin/sshd" hostname=66.187.230.92 
addr=66.187.230.92 terminal=ssh res=success'
Dec 21 15:23:34 vm0136.workers-phx.ovirt.org audit[5410]: USER_LOGOUT pid=5410 
uid=0 auid=1012 ses=3 subj=system_u:system_r:sshd_t:s0-s0:c0.c1023 
msg='op=login id=1012 exe="/usr/sbin/sshd" hostname=66.187.230.92 
addr=66.187.230.92 terminal=ssh res=success'
Dec 21 15:23:34 vm0136.workers-phx.ovirt.org kernel: audit: type=1106 
audit(1482333814.930:3694): pid=5410 uid=0 auid=1012 ses=3 
subj=system_u:system_r:sshd_t:s0-s0:c0.c1023 msg='op=login id=1012 
exe="/usr/sbin/sshd" hostname=66.187.230.92 addr=66.187.230.92 terminal=ssh 
res=success'
Dec 21 15:23:34 vm0136.workers-phx.ovirt.org kernel: audit: type=1113 
audit(1482333814.930:3695): pid=5410 uid=0 auid=1012 ses=3 
subj=system_u:system_r:sshd_t:s0-s0:c0.c1023 msg='op=login id=1012 
exe="/usr/sbin/sshd" hostname=66.187.230.92 addr=66.187.230.92 terminal=ssh 
res=success'
Dec 21 15:23:34 vm0136.workers-phx.ovirt.org kernel: audit: type=1112 
audit(1482333814.952:3696): pid=5410 uid=0 auid=1012 ses=3 
subj=system_u:system_r:sshd_t:s0-s0:c0.c1023 msg='op=login id=1012 
exe="/usr/sbin/sshd" hostname=66.187.230.92 addr=66.187.230.92 terminal=ssh 
res=success'
Dec 21 15:23:34 vm0136.workers-phx.ovirt.org kernel: audit: type=1105 
audit(1482333814.952:3697): pid=5410 uid=0 auid=1012 ses=3 
subj=system_u:system_r:sshd_t:s0-s0:c0.c1023 msg='op=login id=1012 
exe="/usr/sbin/sshd" hostname=66.187.230.92 addr=66.187.230.92 terminal=ssh 
res=success'
Dec 21 15:23:34 vm0136.workers-phx.ovirt.org audit[5410]: USER_LOGIN pid=5410 
uid=0 auid=1012 ses=3 subj=system_u:system_r:sshd_t:s0-s0:c0.c1023 
msg='op=login id=1012 exe="/usr/sbin/sshd" hostname=66.187.230.92 
addr=66.187.230.92 terminal=ssh res=success'
Dec 21 15:23:34 vm0136.workers-phx.ovirt.org audit[5410]: USER_START pid=5410 
uid=0 auid=1012 ses=3 subj=system_u:system_r:sshd_t:s0-s0:c0.c1023 
msg='op=login id=1012 exe="/usr/sbin/sshd" hostname=66.187.230.92 
addr=66.187.230.92 terminal=ssh res=success'
Dec 21 15:23:34 vm0136.workers-phx.ovirt.org audit[5410]: CRYPTO_KEY_USER 
pid=5410 uid=0 auid=1012 ses=3 subj=system_u:system_r:sshd_t:s0-s0:c0.c1023 
msg='op=destroy kind=server 
fp=SHA256:95:42:59:76:99:08:09:ae:94:d8:46:3e:61:7d:53:b6:e5:1e:f5:f5:73:f2:04:87:38:ca:80:4f:44:6d:df:d5
 direction=? spid=25269 suid=1012  exe="/usr/sbin/sshd" hostname=? 
addr=66.187.230.92 terminal=? res=success'
Dec 21 15:23:34 vm0136.workers-phx.ovirt.org kernel: audit: type=2404 
audit(1482333814.953:3698): pid=5410 uid=0 auid=1012 ses=3 
subj=system_u:system_r:sshd_t:s0-s0:c0.c1023 msg='op=destroy kind=server 
fp=SHA256:95:42:59:76:99:08:09:ae:94:d8:46:3e:61:7d:53:b6:e5:1e:f5:f5:73:f2:04:87:38:ca:80:4f:44:6d:df:d5
 direction=? spid=25269 suid=1012  exe="/usr/sbin/sshd" hostname=? 
addr=66.187.230.92 terminal=? res=success'
Dec 21 15:23:34 vm0136.workers-phx.ovirt.org sshd[5421]: Received disconnect 
from 66.187.230.92 port 53024:11: Closed due to user request.
Dec 21 15:23:34 vm0136.workers-phx.ovirt.org kernel: audit: type=2404 
audit(1482333814.989:3699): pid=5410 uid=0 auid=1012 ses=3 
subj=system_u:system_r:sshd_t:s0-s0:c0.c1023 msg='op=destroy kind=server 
fp=SHA256:95:42:59:76:99:08:09:ae:94:d8:46:3e:61:7d:53:b6:e5:1e:f5:f5:73:f2:04:87:38:ca:80:4f:44:6d:df:d5
 direction=? spid=5421 suid=1012  exe="/usr/sbin/sshd" hostname=? 
addr=66.187.230.92 terminal=? res=success'
Dec 21 15:23:34 vm0136.workers-phx.ovirt.org kernel: audit: type=2404 
audit(1482333814.989:3700): pid=5410 uid=0 auid=1012 ses=3 
subj=system_u:system_r:sshd_t:s0-s0:c0.c1023 msg='op=destroy kind=session fp=? 
direction=both spid=5421 suid=1012 rport=53024 laddr=172.19.12.136 lport=22  
exe="/usr/sbin/sshd" hostname=? addr=66.187.230.92 terminal=? res=success'
Dec 21 15:23:34 vm0136.workers-phx.ovirt.org audit[5410]: CRYPTO_KEY_USER 
pid=5410 uid=0 auid=1012 ses=3 subj=system_u:system_r:sshd_t:s0-s0:c0.c1023 
msg='op=destroy kind=server 
fp=SHA256:95:42:59:76:99:08:09:ae:94:d8:46:3e:61:7d:53:b6:e5:1e:f5:f5:73:f2:04:87:38:ca:80:4f:44:6d:df:d5
 direction=? spid=5421 suid=1012  exe="/usr/sbin/sshd" hostname=? 
addr=66.187.230.92 terminal=? res=success'
Dec 21 15:23:34 vm0136.workers-phx.ovirt.org audit[5410]: CRYPTO_KEY_USER 
pid=5410 uid=0 auid=1012 ses=3 subj=system_u:system_r:sshd_t:s0-s0:c0.c1023 
msg='op=destroy kind=session fp=? direction=both spid=5421 

[oVirt Jenkins] test-repo_ovirt_experimental_4.1 - Build #28 - FAILURE!

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


[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #4343 - FAILURE!

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


[oVirt Jenkins] test-repo_ovirt_experimental_4.1 - Build #27 - FAILURE!

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


[JIRA] (OVIRT-967) add support for notification plugin in standard CI

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

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

eyal edri [Administrator] reassigned OVIRT-967:
---

Assignee: eyal edri [Administrator]  (was: infra)

> add support for notification plugin in standard CI
> --
>
> Key: OVIRT-967
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-967
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>Reporter: eyal edri [Administrator]
>Assignee: eyal edri [Administrator]
>




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


[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #4342 - FAILURE!

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


[JIRA] (OVIRT-967) add support for notification plugin in standard CI

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

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

Barak Korren commented on OVIRT-967:


Maybe assign the ticket to yourself if you're handling it

> add support for notification plugin in standard CI
> --
>
> Key: OVIRT-967
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-967
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>Reporter: eyal edri [Administrator]
>Assignee: infra
>




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


[JIRA] (OVIRT-967) add support for notification plugin in standard CI

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

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

Barak Korren commented on OVIRT-967:


n/m saw it, so you're doing everything from YAML, so this is the kind of 
implementation I would call specific, a generic implementation would specify 
soemthing to put in the automation dir so nobody needs to know YAML...

> add support for notification plugin in standard CI
> --
>
> Key: OVIRT-967
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-967
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>Reporter: eyal edri [Administrator]
>Assignee: infra
>




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


[JIRA] (OVIRT-967) add support for notification plugin in standard CI

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

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

Barak Korren commented on OVIRT-967:


which patch? I'm not seeing any patch linked here...

> add support for notification plugin in standard CI
> --
>
> Key: OVIRT-967
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-967
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>Reporter: eyal edri [Administrator]
>Assignee: infra
>




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


[JIRA] (OVIRT-967) add support for notification plugin in standard CI

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

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

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

Not sure I understand, the current patch is as generic as it gets without any 
relation to getbadgets or gamification, 
If its merged nothing will happen on CI (already verified) because the URL for 
the webhook is empty by default.

Only if you provide a URL as param from a project then its activated, for e.g 
for jenkins project:
https://gerrit.ovirt.org/#/c/68903/1/jobs/confs/projects/jenkins/jenkins_standard.yaml

The alternative is to create a new template for it and change multiple projects 
to use it if we want, which I don't see a reason for, if by default the plugin 
is not active.




> add support for notification plugin in standard CI
> --
>
> Key: OVIRT-967
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-967
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>Reporter: eyal edri [Administrator]
>Assignee: infra
>




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


[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #4341 - FAILURE!

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


[JIRA] (OVIRT-955) Re: http://lists.ovirt.org/pipermail/announce/ is not reachable

2016-12-21 Thread Duck

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

Marc Dequènes (Duck) commented on OVIRT-955:


yes, a few days ago. the progress was on the migration ticket.

> Re: http://lists.ovirt.org/pipermail/announce/ is not reachable
> ---
>
> Key: OVIRT-955
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-955
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: sbonazzo
>Assignee: infra
>
> Tested it, I've access forbidden there:
> http://lists.phx.ovirt.org/pipermail/announce/
> archives should be publicly accessible.
> On Mon, Dec 12, 2016 at 2:21 PM, Evgheni Dereveanchin 
> wrote:
> >  I totally agree with Barak on this. The hostname
> > must work as there's a bunch of links indexed
> > by search engine which lead to it.
> >  In general the PHX one should not be used
> > by end users. I've re-added the CNAME and edited
> > the virtualhost on apache so it should be available
> > again once existing DNS caches expire.
> >
> > Regards,
> > Evgheni Dereveanchin
> >
> > - Original Message -
> > From: "Barak Korren" 
> > To: "Eyal Edri" 
> > Cc: "infra" , "Sandro Bonazzola" ,
> > "Evgheni Dereveanchin" , "duck" ,
> > infra-ow...@ovirt.org
> > Sent: Monday, 12 December, 2016 2:05:57 PM
> > Subject: Re: http://lists.ovirt.org/pipermail/announce/ is not reachable
> >
> > It can be reached now at lists.phx.ovirt.org (but we we need a CNAME
> > from the old name)
> >
> > On 12 December 2016 at 15:03, Eyal Edri  wrote:
> > > I'm not sure who gets emails sent to infra-owner list.  best to send it
> > to
> > > infra or infra support.
> > >
> > > Adding Evgheni and Duck who are working on migration of the mm server.
> > >
> > > On Dec 12, 2016 2:58 PM, "Sandro Bonazzola"  wrote:
> > >>
> > >> The lists server is not reachable anymore. Looks like a dns issue:
> > >>
> > >> $ traceroute lists.ovirt.org
> > >> lists.ovirt.org: Name or service not known
> > >>
> > >>
> > >> --
> > >> Sandro Bonazzola
> > >> Better technology. Faster innovation. Powered by community
> > collaboration.
> > >> See how it works at redhat.com
> > >
> > >
> > > ___
> > > Infra mailing list
> > > Infra@ovirt.org
> > > http://lists.phx.ovirt.org/mailman/listinfo/infra
> > >
> >
> >
> >
> > --
> > Barak Korren
> > bkor...@redhat.com
> > RHCE, RHCi, RHV-DevOps Team
> > https://ifireball.wordpress.com/
> >
> -- 
> 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.621.5#100023)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra


[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #4340 - FAILURE!

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


[oVirt Jenkins] test-repo_ovirt_experimental_4.1 - Build #26 - FAILURE!

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


[JIRA] (OVIRT-967) add support for notification plugin in standard CI

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

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

Barak Korren commented on OVIRT-967:


The big question is if we want to have it generic, which will require 
extensions to the CI standard, and some thinking and perhaps some non-trivial 
Jenkins tricks, or, we just want to quickly support GetBadges.


> add support for notification plugin in standard CI
> --
>
> Key: OVIRT-967
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-967
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>Reporter: eyal edri [Administrator]
>Assignee: infra
>




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


[oVirt Jenkins] test-repo_ovirt_experimental_4.1 - Build #25 - FAILURE!

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


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

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


[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #4338 - FAILURE!

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


Re: Gerrit hooks doesn't mark open patches in other branches as -verified

2016-12-21 Thread Eyal Edri
+1 excellent.
Please continue to report any issues you see and we'll follow up with
prompt fixes.

On Wed, Dec 21, 2016 at 2:03 PM, Tal Nisan  wrote:

> OK great, in any way I'm there to solve any false positives as I can
> remove those votes and as you see I notify you team immediately of any
> failure so should be a problem
>
> On Wed, Dec 21, 2016 at 1:40 PM, Eyal Edri  wrote:
>
>>
>>
>> On Wed, Dec 21, 2016 at 1:35 PM, Tal Nisan  wrote:
>>
>>> This is how it always worked, and all due respect to Eyal's opinion I'm
>>> the one handling the branch and the grades are there to help me :)
>>>
>>
>> The reason we didn't grade the new hooks with CR -1 or VERIFY -1 is
>> because we wanted to give the new hooks enough time to see if all is
>> working well, because causing false positives and un-needed noise,
>> nothing to do with my opinions.
>>
>> Since we see now that its working well, we can enable the enforcement
>> back, so if its VERIFY then yea, let's enable it.
>>
>>
>>>
>>> On Wed, Dec 21, 2016 at 1:32 PM, Shlomo Ben David 
>>> wrote:
>>>
 Tal - Ok, so basically I didn't apply the verified grades on any hooks
 accept the check_bug_url hook.

 Eyal - Is it ok to add the verify (+/-)1 grade for the check_backport
 hook?
 (I thought that we'll grade with negative value if something went wrong)

 Best Regards,

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

 OPEN SOURCE - 1 4 011 && 011 4 1

 On Wed, Dec 21, 2016 at 1:20 PM, Tal Nisan  wrote:

> The hook found out that the patch is open in master which precedes
> ovirt-engine-4.1 and thus should have gotten -verified in 4.1
>
> On Wed, Dec 21, 2016 at 12:55 PM, Shlomo Ben David <
> sbend...@redhat.com> wrote:
>
>> Hi Tal,
>>
>> I think that the Check Backport hook is doing exactly what you asking
>> for.
>> Example [1]:
>>
>>- Check Backport::IGNORE, The patch backported to all newer
>>branches.(open in 'master' branch/es) found not relevant branch/es:
>>'ovirt-engine-4.0' (not exist in the newer branches list)
>>
>> patch branch: ovirt-engine-4.1
>> newer branches: 'master' (open)
>> older (not relevant) branches: ovirt-engine-4.0
>>
>> If it's not what you meant, please explain :)
>>
>> [1] - https://gerrit.ovirt.org/#/c/68862
>>
>>
>> Best Regards,
>>
>> Shlomi Ben-David | Software Engineer | Red Hat ISRAEL
>> RHCSA | RHCE
>> IRC: shlomibendavid (on #rhev-integ, #rhev-dev, #rhev-ci)
>>
>> OPEN SOURCE - 1 4 011 && 011 4 1
>>
>> On Wed, Dec 21, 2016 at 12:39 PM, Tal Nisan 
>> wrote:
>>
>>> Check out this patches for instance: https://gerrit.ovirt
>>> .org/#/c/68862 https://gerrit.ovirt.org/#/c/68861
>>> Those are 4.1 and 4.0 patches that are open on master, I'd expect to
>>> see them get -verified from the hooks which they didn't:
>>>
>>>- Update Tracker::#1406042::OK, status: POST
>>>- Check Bug-Url::OK
>>>- Check Product::#1406042::OK, product: ovirt-engine
>>>- Check TM::#1406042::OK, found clone candidate ovirt-4.0.zfor
>>>target milestone: ovirt-4.0.7
>>>- Set POST::#1406042::IGNORE, bug is already in 'POST' status
>>>- Check Backport::IGNORE, The patch backported to all newer
>>>branches.(open in 'master' branch/es) found not relevant branch/es:
>>>'ovirt-engine-4.0' (not exist in the newer branches list)
>>>
>>> This was the flow before and it made my life easier as I didn't have
>>> to actively search for cherry-picks in all other branches to see if it 
>>> can
>>> be merged
>>>
>>> ___
>>> 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 <+972%209-769-2018>
>> irc: eedri (on #tlv #rhev-dev #rhev-integ)
>>
>
>


-- 
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-967) add support for notification plugin in standard CI

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

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

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

Forgot to add the link to the game:  
https://ovirt-ovirt-engine.getbadges.io/activity

> add support for notification plugin in standard CI
> --
>
> Key: OVIRT-967
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-967
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>Reporter: eyal edri [Administrator]
>Assignee: infra
>




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


[JIRA] (OVIRT-967) add support for notification plugin in standard CI

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

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

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

Of course it doesn't only have to serve GetBadgets, we can use it in the future 
to capture events from Jenkins from other systems,
one example will be a reporting system that can aggregate results into a cental 
datawarehouse which we can then create reports from.

> add support for notification plugin in standard CI
> --
>
> Key: OVIRT-967
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-967
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>Reporter: eyal edri [Administrator]
>Assignee: infra
>




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


[JIRA] (OVIRT-967) add support for notification plugin in standard CI

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

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

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

any project which will want to use it need to pass the URL as parameter

> add support for notification plugin in standard CI
> --
>
> Key: OVIRT-967
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-967
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>Reporter: eyal edri [Administrator]
>Assignee: infra
>




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


[JIRA] (OVIRT-967) add support for notification plugin in standard CI

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

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

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

Integration with GetBadges Gamification which is working nice until now with 
the GitHub integration, this will allow oVirt users/developers to get badges / 
points on having 
successful builds ( or lose on failing builds ).

We already got positive feedback from developers on it, and adding another 
integration will increase visibility of the game [1] and hopefully make oVirt 
more fun to use/fix bugs/make ci happy.

Fedora has something similar which works well [1]

[1] https://badges.fedoraproject.org/



> add support for notification plugin in standard CI
> --
>
> Key: OVIRT-967
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-967
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>Reporter: eyal edri [Administrator]
>Assignee: infra
>




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


[JIRA] (OVIRT-967) add support for notification plugin in standard CI

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

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

Barak Korren commented on OVIRT-967:


Why do we want this?

> add support for notification plugin in standard CI
> --
>
> Key: OVIRT-967
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-967
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>Reporter: eyal edri [Administrator]
>Assignee: infra
>




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


[JIRA] (OVIRT-952) CI-1 unrelated to patch

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

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

Barak Korren commented on OVIRT-952:


I can't analyse this now, b/c I don't have the logs any more.
We did not wait for two weeks there was a Jira malfunction that made 
ticket-opening mails to reach the right place for the last two weeks up until a 
few hours ago.

If this was any real infra issue we probably have already resolved it back 
then. If it is a repeating issue we probably have other tickets about it. 

There is no information on this ticket that I can investigate any further.
(An no, just the Jenkins exception is NEVER enough, the real reason is 
typically a few scores of lines above it)

This seems reminiscent on OVIRT-938, I wouldn't mark this as duplicate though 
b/c we're not talking about vdsm check_merged here.

> CI-1 unrelated to patch
> ---
>
> Key: OVIRT-952
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-952
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: danken
>Assignee: infra
>
> An ovirt-engine patch has got -1 for a failing job:
> http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/14621/consoleText
> Triggered by Gerrit: https://gerrit.ovirt.org/67308
> [EnvInject] - Loading node environment variables.
> FATAL: java.io.IOException: Unexpected termination of the channel
> hudson.remoting.RequestAbortedException: java.io.IOException:
> Unexpected termination of the channel
> at hudson.remoting.Request.abort(Request.java:303)
> at hudson.remoting.Channel.terminate(Channel.java:847)
> at 
> hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:69)
> at ..remote call to vm0129.workers-phx.ovirt.org(Native Method)
> at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1416)
> at hudson.remoting.Request.call(Request.java:172)
> at hudson.remoting.Channel.call(Channel.java:780)
> at hudson.FilePath.act(FilePath.java:1074)
> at 
> org.jenkinsci.plugins.envinject.service.EnvironmentVariablesNodeLoader.gatherEnvironmentVariablesNode(EnvironmentVariablesNodeLoader.java:44)
> at 
> org.jenkinsci.plugins.envinject.EnvInjectListener.loadEnvironmentVariablesNode(EnvInjectListener.java:81)
> at 
> org.jenkinsci.plugins.envinject.EnvInjectListener.setUpEnvironment(EnvInjectListener.java:39)
> at 
> hudson.model.AbstractBuild$AbstractBuildExecution.createLauncher(AbstractBuild.java:572)
> at 
> hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:492)
> at hudson.model.Run.execute(Run.java:1738)
> at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
> at hudson.model.ResourceController.execute(ResourceController.java:98)
> at hudson.model.Executor.run(Executor.java:410)
> Caused by: java.io.IOException: Unexpected termination of the channel
> at 
> hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50)
> Caused by: java.io.EOFException
> at 
> java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2353)
> at 
> java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2822)
> at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:804)
> at java.io.ObjectInputStream.(ObjectInputStream.java:301)
> at hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:48)
> at 
> hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34)
> at 
> hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48)
> Performing Post build task...
> Match found for :.* : True



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


[JIRA] (OVIRT-967) add support for notification plugin in standard CI

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

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

eyal edri [Administrator] updated OVIRT-967:

Epic Link: OVIRT-400

> add support for notification plugin in standard CI
> --
>
> Key: OVIRT-967
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-967
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>Reporter: eyal edri [Administrator]
>Assignee: infra
>




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


[JIRA] (OVIRT-967) add support for notification plugin in standard CI

2016-12-21 Thread eyal edri [Administrator] (oVirt JIRA)
eyal edri [Administrator] created OVIRT-967:
---

 Summary: add support for notification plugin in standard CI
 Key: OVIRT-967
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-967
 Project: oVirt - virtualization made easy
  Issue Type: Task
Reporter: eyal edri [Administrator]
Assignee: infra






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


[JIRA] (OVIRT-965) Force check-patch to run on latest-tested

2016-12-21 Thread Daniel Belenky (oVirt JIRA)

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

Daniel Belenky reassigned OVIRT-965:


Assignee: Daniel Belenky  (was: infra)

> Force check-patch to run on latest-tested
> -
>
> Key: OVIRT-965
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-965
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>Reporter: Daniel Belenky
>Assignee: Daniel Belenky
>
> https://gerrit.ovirt.org/#/c/68896/



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


[JIRA] (OVIRT-966) Optimize check-patch.sh

2016-12-21 Thread Daniel Belenky (oVirt JIRA)

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

Daniel Belenky reassigned OVIRT-966:


Assignee: Daniel Belenky  (was: infra)

> Optimize check-patch.sh
> ---
>
> Key: OVIRT-966
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-966
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>Reporter: Daniel Belenky
>Assignee: Daniel Belenky
>
> check-patch.sh is fully automatic, and can recognize new suites automatically.
> The only demand is to follow the standard naming (must end with *-)
> https://gerrit.ovirt.org/#/c/68682/



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


[JIRA] (OVIRT-966) Optimize check-patch.sh

2016-12-21 Thread Daniel Belenky (oVirt JIRA)
Daniel Belenky created OVIRT-966:


 Summary: Optimize check-patch.sh
 Key: OVIRT-966
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-966
 Project: oVirt - virtualization made easy
  Issue Type: Task
Reporter: Daniel Belenky
Assignee: infra


check-patch.sh is fully automatic, and can recognize new suites automatically.
The only demand is to follow the standard naming (must end with *-)

https://gerrit.ovirt.org/#/c/68682/



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


[JIRA] (OVIRT-965) Force check-patch to run on latest-tested

2016-12-21 Thread Daniel Belenky (oVirt JIRA)
Daniel Belenky created OVIRT-965:


 Summary: Force check-patch to run on latest-tested
 Key: OVIRT-965
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-965
 Project: oVirt - virtualization made easy
  Issue Type: Task
Reporter: Daniel Belenky
Assignee: infra


https://gerrit.ovirt.org/#/c/68896/



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


Re: Gerrit hooks doesn't mark open patches in other branches as -verified

2016-12-21 Thread Tal Nisan
OK great, in any way I'm there to solve any false positives as I can remove
those votes and as you see I notify you team immediately of any failure so
should be a problem

On Wed, Dec 21, 2016 at 1:40 PM, Eyal Edri  wrote:

>
>
> On Wed, Dec 21, 2016 at 1:35 PM, Tal Nisan  wrote:
>
>> This is how it always worked, and all due respect to Eyal's opinion I'm
>> the one handling the branch and the grades are there to help me :)
>>
>
> The reason we didn't grade the new hooks with CR -1 or VERIFY -1 is
> because we wanted to give the new hooks enough time to see if all is
> working well, because causing false positives and un-needed noise,
> nothing to do with my opinions.
>
> Since we see now that its working well, we can enable the enforcement
> back, so if its VERIFY then yea, let's enable it.
>
>
>>
>> On Wed, Dec 21, 2016 at 1:32 PM, Shlomo Ben David 
>> wrote:
>>
>>> Tal - Ok, so basically I didn't apply the verified grades on any hooks
>>> accept the check_bug_url hook.
>>>
>>> Eyal - Is it ok to add the verify (+/-)1 grade for the check_backport
>>> hook?
>>> (I thought that we'll grade with negative value if something went wrong)
>>>
>>> Best Regards,
>>>
>>> Shlomi Ben-David | Software Engineer | Red Hat ISRAEL
>>> RHCSA | RHCE
>>> IRC: shlomibendavid (on #rhev-integ, #rhev-dev, #rhev-ci)
>>>
>>> OPEN SOURCE - 1 4 011 && 011 4 1
>>>
>>> On Wed, Dec 21, 2016 at 1:20 PM, Tal Nisan  wrote:
>>>
 The hook found out that the patch is open in master which precedes
 ovirt-engine-4.1 and thus should have gotten -verified in 4.1

 On Wed, Dec 21, 2016 at 12:55 PM, Shlomo Ben David  wrote:

> Hi Tal,
>
> I think that the Check Backport hook is doing exactly what you asking
> for.
> Example [1]:
>
>- Check Backport::IGNORE, The patch backported to all newer
>branches.(open in 'master' branch/es) found not relevant branch/es:
>'ovirt-engine-4.0' (not exist in the newer branches list)
>
> patch branch: ovirt-engine-4.1
> newer branches: 'master' (open)
> older (not relevant) branches: ovirt-engine-4.0
>
> If it's not what you meant, please explain :)
>
> [1] - https://gerrit.ovirt.org/#/c/68862
>
>
> Best Regards,
>
> Shlomi Ben-David | Software Engineer | Red Hat ISRAEL
> RHCSA | RHCE
> IRC: shlomibendavid (on #rhev-integ, #rhev-dev, #rhev-ci)
>
> OPEN SOURCE - 1 4 011 && 011 4 1
>
> On Wed, Dec 21, 2016 at 12:39 PM, Tal Nisan  wrote:
>
>> Check out this patches for instance: https://gerrit.ovirt
>> .org/#/c/68862 https://gerrit.ovirt.org/#/c/68861
>> Those are 4.1 and 4.0 patches that are open on master, I'd expect to
>> see them get -verified from the hooks which they didn't:
>>
>>- Update Tracker::#1406042::OK, status: POST
>>- Check Bug-Url::OK
>>- Check Product::#1406042::OK, product: ovirt-engine
>>- Check TM::#1406042::OK, found clone candidate ovirt-4.0.zfor
>>target milestone: ovirt-4.0.7
>>- Set POST::#1406042::IGNORE, bug is already in 'POST' status
>>- Check Backport::IGNORE, The patch backported to all newer
>>branches.(open in 'master' branch/es) found not relevant branch/es:
>>'ovirt-engine-4.0' (not exist in the newer branches list)
>>
>> This was the flow before and it made my life easier as I didn't have
>> to actively search for cherry-picks in all other branches to see if it 
>> can
>> be merged
>>
>> ___
>> 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 <+972%209-769-2018>
> irc: eedri (on #tlv #rhev-dev #rhev-integ)
>
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra


[oVirt Jenkins] test-repo_ovirt_experimental_4.1 - Build #23 - FAILURE!

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


[JIRA] (OVIRT-952) CI-1 unrelated to patch

2016-12-21 Thread danken (oVirt JIRA)

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

danken commented on OVIRT-952:
--

I reported the issue immediately as it happened. Waiting 2 weeks until a ticket 
is reviewed, and then closing it due to its old age is a sure way to keep the 
low trust the developers have in CI.

We NEED trustworthy CI. We cannot have so many false failures. I'm asking 
everybody not to rant about these failures, but to report them, so CI can 
become worthy of its name.

Please consider finding the root cause of this (and all other issues we 
report). I understand that not every problem can be solved, but an attempt is 
required.

> CI-1 unrelated to patch
> ---
>
> Key: OVIRT-952
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-952
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: danken
>Assignee: infra
>
> An ovirt-engine patch has got -1 for a failing job:
> http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/14621/consoleText
> Triggered by Gerrit: https://gerrit.ovirt.org/67308
> [EnvInject] - Loading node environment variables.
> FATAL: java.io.IOException: Unexpected termination of the channel
> hudson.remoting.RequestAbortedException: java.io.IOException:
> Unexpected termination of the channel
> at hudson.remoting.Request.abort(Request.java:303)
> at hudson.remoting.Channel.terminate(Channel.java:847)
> at 
> hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:69)
> at ..remote call to vm0129.workers-phx.ovirt.org(Native Method)
> at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1416)
> at hudson.remoting.Request.call(Request.java:172)
> at hudson.remoting.Channel.call(Channel.java:780)
> at hudson.FilePath.act(FilePath.java:1074)
> at 
> org.jenkinsci.plugins.envinject.service.EnvironmentVariablesNodeLoader.gatherEnvironmentVariablesNode(EnvironmentVariablesNodeLoader.java:44)
> at 
> org.jenkinsci.plugins.envinject.EnvInjectListener.loadEnvironmentVariablesNode(EnvInjectListener.java:81)
> at 
> org.jenkinsci.plugins.envinject.EnvInjectListener.setUpEnvironment(EnvInjectListener.java:39)
> at 
> hudson.model.AbstractBuild$AbstractBuildExecution.createLauncher(AbstractBuild.java:572)
> at 
> hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:492)
> at hudson.model.Run.execute(Run.java:1738)
> at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
> at hudson.model.ResourceController.execute(ResourceController.java:98)
> at hudson.model.Executor.run(Executor.java:410)
> Caused by: java.io.IOException: Unexpected termination of the channel
> at 
> hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50)
> Caused by: java.io.EOFException
> at 
> java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2353)
> at 
> java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2822)
> at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:804)
> at java.io.ObjectInputStream.(ObjectInputStream.java:301)
> at hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:48)
> at 
> hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34)
> at 
> hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48)
> Performing Post build task...
> Match found for :.* : True



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


[JIRA] (OVIRT-953) mock_genconfig is broken

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

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

Barak Korren updated OVIRT-953:
---
Resolution: Duplicate
  Assignee: Barak Korren  (was: infra)
Status: Done  (was: To Do)

Duplicate of OVIRT-939

> mock_genconfig is broken
> 
>
> Key: OVIRT-953
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-953
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: sbonazzo
>Assignee: Barak Korren
>
> *00:00:06.983*  Generating mock configuration*00:00:06.984* +
> ./mock_genconfig --name=epel-7-x86_64-custom --base=epel-7-x86_64.cfg
> --option=basedir=/home/jenkins/workspace/qemu_3.6_create-rpms-el7-x86_64_merged/mock/
> --try-proxy*00:00:07.177* Traceback (most recent call
> last):*00:00:07.177*   File "./mock_genconfig", line 161, in
> *00:00:07.177* main()*00:00:07.177*   File
> "./mock_genconfig", line 138, in main*00:00:07.177*
> execfile(base_config)*00:00:07.177*   File
> "epel-7-x86_64_proxied.cfg", line 8, in *00:00:07.177*
> config_opts['environment']['http_proxy'] =
> 'http://proxy.phx.ovirt.org:3128'*00:00:07.178* KeyError:
> 'environment'
> http://jenkins.ovirt.org/job/qemu_3.6_create-rpms-el7-x86_64_merged/15/console
> -- 
> 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.621.5#100023)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra


[JIRA] (OVIRT-952) CI-1 unrelated to patch

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

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

Barak Korren updated OVIRT-952:
---
Resolution: Cannot Reproduce
Status: Done  (was: To Do)

This seems to have happened a long time ago, please repoen if problem resumes

> CI-1 unrelated to patch
> ---
>
> Key: OVIRT-952
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-952
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: danken
>Assignee: infra
>
> An ovirt-engine patch has got -1 for a failing job:
> http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/14621/consoleText
> Triggered by Gerrit: https://gerrit.ovirt.org/67308
> [EnvInject] - Loading node environment variables.
> FATAL: java.io.IOException: Unexpected termination of the channel
> hudson.remoting.RequestAbortedException: java.io.IOException:
> Unexpected termination of the channel
> at hudson.remoting.Request.abort(Request.java:303)
> at hudson.remoting.Channel.terminate(Channel.java:847)
> at 
> hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:69)
> at ..remote call to vm0129.workers-phx.ovirt.org(Native Method)
> at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1416)
> at hudson.remoting.Request.call(Request.java:172)
> at hudson.remoting.Channel.call(Channel.java:780)
> at hudson.FilePath.act(FilePath.java:1074)
> at 
> org.jenkinsci.plugins.envinject.service.EnvironmentVariablesNodeLoader.gatherEnvironmentVariablesNode(EnvironmentVariablesNodeLoader.java:44)
> at 
> org.jenkinsci.plugins.envinject.EnvInjectListener.loadEnvironmentVariablesNode(EnvInjectListener.java:81)
> at 
> org.jenkinsci.plugins.envinject.EnvInjectListener.setUpEnvironment(EnvInjectListener.java:39)
> at 
> hudson.model.AbstractBuild$AbstractBuildExecution.createLauncher(AbstractBuild.java:572)
> at 
> hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:492)
> at hudson.model.Run.execute(Run.java:1738)
> at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
> at hudson.model.ResourceController.execute(ResourceController.java:98)
> at hudson.model.Executor.run(Executor.java:410)
> Caused by: java.io.IOException: Unexpected termination of the channel
> at 
> hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50)
> Caused by: java.io.EOFException
> at 
> java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2353)
> at 
> java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2822)
> at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:804)
> at java.io.ObjectInputStream.(ObjectInputStream.java:301)
> at hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:48)
> at 
> hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34)
> at 
> hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48)
> Performing Post build task...
> Match found for :.* : True



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


[JIRA] (OVIRT-954) Fwd: http://lists.ovirt.org/pipermail/announce/ is not reachable

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

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

Barak Korren updated OVIRT-954:
---
Resolution: Cannot Reproduce
Status: Done  (was: To Do)

This seems to have been resolved by now

> Fwd: http://lists.ovirt.org/pipermail/announce/ is not reachable
> 
>
> Key: OVIRT-954
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-954
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: sbonazzo
>Assignee: infra
>
> The lists server is not reachable anymore. Looks like a dns issue:
> $ traceroute lists.ovirt.org
> lists.ovirt.org: Name or service not known
> -- 
> 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.621.5#100023)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra


[JIRA] (OVIRT-955) Re: http://lists.ovirt.org/pipermail/announce/ is not reachable

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

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

Barak Korren updated OVIRT-955:
---
Resolution: Fixed
Status: Done  (was: To Do)

This seems to have been resolved by now

> Re: http://lists.ovirt.org/pipermail/announce/ is not reachable
> ---
>
> Key: OVIRT-955
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-955
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: sbonazzo
>Assignee: infra
>
> Tested it, I've access forbidden there:
> http://lists.phx.ovirt.org/pipermail/announce/
> archives should be publicly accessible.
> On Mon, Dec 12, 2016 at 2:21 PM, Evgheni Dereveanchin 
> wrote:
> >  I totally agree with Barak on this. The hostname
> > must work as there's a bunch of links indexed
> > by search engine which lead to it.
> >  In general the PHX one should not be used
> > by end users. I've re-added the CNAME and edited
> > the virtualhost on apache so it should be available
> > again once existing DNS caches expire.
> >
> > Regards,
> > Evgheni Dereveanchin
> >
> > - Original Message -
> > From: "Barak Korren" 
> > To: "Eyal Edri" 
> > Cc: "infra" , "Sandro Bonazzola" ,
> > "Evgheni Dereveanchin" , "duck" ,
> > infra-ow...@ovirt.org
> > Sent: Monday, 12 December, 2016 2:05:57 PM
> > Subject: Re: http://lists.ovirt.org/pipermail/announce/ is not reachable
> >
> > It can be reached now at lists.phx.ovirt.org (but we we need a CNAME
> > from the old name)
> >
> > On 12 December 2016 at 15:03, Eyal Edri  wrote:
> > > I'm not sure who gets emails sent to infra-owner list.  best to send it
> > to
> > > infra or infra support.
> > >
> > > Adding Evgheni and Duck who are working on migration of the mm server.
> > >
> > > On Dec 12, 2016 2:58 PM, "Sandro Bonazzola"  wrote:
> > >>
> > >> The lists server is not reachable anymore. Looks like a dns issue:
> > >>
> > >> $ traceroute lists.ovirt.org
> > >> lists.ovirt.org: Name or service not known
> > >>
> > >>
> > >> --
> > >> Sandro Bonazzola
> > >> Better technology. Faster innovation. Powered by community
> > collaboration.
> > >> See how it works at redhat.com
> > >
> > >
> > > ___
> > > Infra mailing list
> > > Infra@ovirt.org
> > > http://lists.phx.ovirt.org/mailman/listinfo/infra
> > >
> >
> >
> >
> > --
> > Barak Korren
> > bkor...@redhat.com
> > RHCE, RHCi, RHV-DevOps Team
> > https://ifireball.wordpress.com/
> >
> -- 
> 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.621.5#100023)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra


[JIRA] (OVIRT-959) false CI-1 due to tcsetattr: Inappropriate ioctl for device

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

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

Barak Korren updated OVIRT-959:
---
Resolution: Duplicate
Status: Done  (was: To Do)

Duplicate of OVIRT-938

> false CI-1 due to tcsetattr: Inappropriate ioctl for device
> ---
>
> Key: OVIRT-959
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-959
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: danken
>Assignee: infra
>
> http://jenkins.ovirt.org/job/vdsm_master_check-merged-el7-x86_64/690/console
> has failed for something unrelated to the code or the test. Please look it up.
> 16:22:40 sh: [9520: 1 (255)] tcsetattr: Inappropriate ioctl for device
> 16:22:40 Slave went offline during the build
> 16:22:40 ERROR: Connection was broken: java.io.IOException: Unexpected
> termination of the channel
> 16:22:40 at 
> hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50)
> 16:22:40 Caused by: java.io.EOFException
> 16:22:40 at 
> java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2353)
> 16:22:40 at 
> java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2822)
> 16:22:40 at 
> java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:804)
> 16:22:40 at java.io.ObjectInputStream.(ObjectInputStream.java:301)
> 16:22:40 at 
> hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:48)
> 16:22:40 at 
> hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34)
> 16:22:40 at 
> hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48)



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


Re: Gerrit hooks doesn't mark open patches in other branches as -verified

2016-12-21 Thread Eyal Edri
On Wed, Dec 21, 2016 at 1:35 PM, Tal Nisan  wrote:

> This is how it always worked, and all due respect to Eyal's opinion I'm
> the one handling the branch and the grades are there to help me :)
>

The reason we didn't grade the new hooks with CR -1 or VERIFY -1 is because
we wanted to give the new hooks enough time to see if all is working well,
because causing false positives and un-needed noise,
nothing to do with my opinions.

Since we see now that its working well, we can enable the enforcement back,
so if its VERIFY then yea, let's enable it.


>
> On Wed, Dec 21, 2016 at 1:32 PM, Shlomo Ben David 
> wrote:
>
>> Tal - Ok, so basically I didn't apply the verified grades on any hooks
>> accept the check_bug_url hook.
>>
>> Eyal - Is it ok to add the verify (+/-)1 grade for the check_backport
>> hook?
>> (I thought that we'll grade with negative value if something went wrong)
>>
>> Best Regards,
>>
>> Shlomi Ben-David | Software Engineer | Red Hat ISRAEL
>> RHCSA | RHCE
>> IRC: shlomibendavid (on #rhev-integ, #rhev-dev, #rhev-ci)
>>
>> OPEN SOURCE - 1 4 011 && 011 4 1
>>
>> On Wed, Dec 21, 2016 at 1:20 PM, Tal Nisan  wrote:
>>
>>> The hook found out that the patch is open in master which precedes
>>> ovirt-engine-4.1 and thus should have gotten -verified in 4.1
>>>
>>> On Wed, Dec 21, 2016 at 12:55 PM, Shlomo Ben David 
>>> wrote:
>>>
 Hi Tal,

 I think that the Check Backport hook is doing exactly what you asking
 for.
 Example [1]:

- Check Backport::IGNORE, The patch backported to all newer
branches.(open in 'master' branch/es) found not relevant branch/es:
'ovirt-engine-4.0' (not exist in the newer branches list)

 patch branch: ovirt-engine-4.1
 newer branches: 'master' (open)
 older (not relevant) branches: ovirt-engine-4.0

 If it's not what you meant, please explain :)

 [1] - https://gerrit.ovirt.org/#/c/68862


 Best Regards,

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

 OPEN SOURCE - 1 4 011 && 011 4 1

 On Wed, Dec 21, 2016 at 12:39 PM, Tal Nisan  wrote:

> Check out this patches for instance: https://gerrit.ovirt
> .org/#/c/68862 https://gerrit.ovirt.org/#/c/68861
> Those are 4.1 and 4.0 patches that are open on master, I'd expect to
> see them get -verified from the hooks which they didn't:
>
>- Update Tracker::#1406042::OK, status: POST
>- Check Bug-Url::OK
>- Check Product::#1406042::OK, product: ovirt-engine
>- Check TM::#1406042::OK, found clone candidate ovirt-4.0.zfor
>target milestone: ovirt-4.0.7
>- Set POST::#1406042::IGNORE, bug is already in 'POST' status
>- Check Backport::IGNORE, The patch backported to all newer
>branches.(open in 'master' branch/es) found not relevant branch/es:
>'ovirt-engine-4.0' (not exist in the newer branches list)
>
> This was the flow before and it made my life easier as I didn't have
> to actively search for cherry-picks in all other branches to see if it can
> be merged
>
> ___
> 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


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

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


[JIRA] (OVIRT-958) false CI-1 due to failure to pull surefire-junit

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

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

Barak Korren updated OVIRT-958:
---
Resolution: Cannot Reproduce
  Assignee: Barak Korren  (was: infra)
Status: Done  (was: To Do)

This does not seem to have happened recently, please reopen ticket if this 
resumes.

> false CI-1 due to failure to pull surefire-junit
> 
>
> Key: OVIRT-958
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-958
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: danken
>Assignee: Barak Korren
>
> https://gerrit.ovirt.org/#/c/68339/1 got CI-1 for what seems to me as
> an unrelated infra error. Please look into it.
> http://jenkins.ovirt.org/job/ovirt-engine_4.0_check-patch-el7-x86_64/1071/consoleText
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.7.2:test
> (default-test) on project checkstyles: Error to resolving surefire
> provider dependency: Unable to get dependency information for
> org.apache.maven.surefire:surefire-junit4:jar:2.7.2: Failed to
> retrieve POM for org.apache.maven.surefire:surefire-junit4:jar:2.7.2:
> Could not transfer artifact
> org.apache.maven.surefire:surefire-junit4:pom:2.7.2 from/to
> ovirt-maven-repository
> (http://artifactory.ovirt.org/artifactory/ovirt-mirror): Failed to
> transfer file: 
> http://artifactory.ovirt.org/artifactory/ovirt-mirror/org/apache/maven/surefire/surefire-junit4/2.7.2/surefire-junit4-2.7.2.pom.
> Return code is: 500 , ReasonPhrase:Internal Server Error.
> [ERROR] org.apache.maven.surefire:surefire-junit4:jar:2.7.2



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


[JIRA] (OVIRT-957) list archives are forbidden

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

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

Barak Korren updated OVIRT-957:
---
Resolution: Cannot Reproduce
  Assignee: Barak Korren  (was: infra)
Status: Done  (was: To Do)

Works for me now, message ID changed due to MM migration.
We already have a ticket to try and resolve that for next time: OVIRT-917

> list archives are forbidden
> ---
>
> Key: OVIRT-957
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-957
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Yedidyah Bar David
>Assignee: Barak Korren
>
> E.g. http://lists.ovirt.org/pipermail/users/2016-July/040885.html
> -- 
> Didi



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


[JIRA] (OVIRT-960) Unable to collect logs from a failed check_merge job

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

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

Barak Korren updated OVIRT-960:
---
Resolution: Duplicate
Status: Done  (was: To Do)

Duplicate of OVIRT-938

> Unable to collect logs from a failed check_merge job
> 
>
> Key: OVIRT-960
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-960
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Edward Haas
>Assignee: infra
>
> Hello,
> The following job:
> http://jenkins.ovirt.org/job/vdsm_master_check-merged-el7-x86_64/693/
> has ended with a failure and no system logs are available.
> Thanks,
> Edy.



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


Re: Gerrit hooks doesn't mark open patches in other branches as -verified

2016-12-21 Thread Tal Nisan
This is how it always worked, and all due respect to Eyal's opinion I'm the
one handling the branch and the grades are there to help me :)

On Wed, Dec 21, 2016 at 1:32 PM, Shlomo Ben David 
wrote:

> Tal - Ok, so basically I didn't apply the verified grades on any hooks
> accept the check_bug_url hook.
>
> Eyal - Is it ok to add the verify (+/-)1 grade for the check_backport hook?
> (I thought that we'll grade with negative value if something went wrong)
>
> Best Regards,
>
> Shlomi Ben-David | Software Engineer | Red Hat ISRAEL
> RHCSA | RHCE
> IRC: shlomibendavid (on #rhev-integ, #rhev-dev, #rhev-ci)
>
> OPEN SOURCE - 1 4 011 && 011 4 1
>
> On Wed, Dec 21, 2016 at 1:20 PM, Tal Nisan  wrote:
>
>> The hook found out that the patch is open in master which precedes
>> ovirt-engine-4.1 and thus should have gotten -verified in 4.1
>>
>> On Wed, Dec 21, 2016 at 12:55 PM, Shlomo Ben David 
>> wrote:
>>
>>> Hi Tal,
>>>
>>> I think that the Check Backport hook is doing exactly what you asking
>>> for.
>>> Example [1]:
>>>
>>>- Check Backport::IGNORE, The patch backported to all newer
>>>branches.(open in 'master' branch/es) found not relevant branch/es:
>>>'ovirt-engine-4.0' (not exist in the newer branches list)
>>>
>>> patch branch: ovirt-engine-4.1
>>> newer branches: 'master' (open)
>>> older (not relevant) branches: ovirt-engine-4.0
>>>
>>> If it's not what you meant, please explain :)
>>>
>>> [1] - https://gerrit.ovirt.org/#/c/68862
>>>
>>>
>>> Best Regards,
>>>
>>> Shlomi Ben-David | Software Engineer | Red Hat ISRAEL
>>> RHCSA | RHCE
>>> IRC: shlomibendavid (on #rhev-integ, #rhev-dev, #rhev-ci)
>>>
>>> OPEN SOURCE - 1 4 011 && 011 4 1
>>>
>>> On Wed, Dec 21, 2016 at 12:39 PM, Tal Nisan  wrote:
>>>
 Check out this patches for instance: https://gerrit.ovirt.org/#/c/68862
 https://gerrit.ovirt.org/#/c/68861
 Those are 4.1 and 4.0 patches that are open on master, I'd expect to
 see them get -verified from the hooks which they didn't:

- Update Tracker::#1406042::OK, status: POST
- Check Bug-Url::OK
- Check Product::#1406042::OK, product: ovirt-engine
- Check TM::#1406042::OK, found clone candidate ovirt-4.0.zfor
target milestone: ovirt-4.0.7
- Set POST::#1406042::IGNORE, bug is already in 'POST' status
- Check Backport::IGNORE, The patch backported to all newer
branches.(open in 'master' branch/es) found not relevant branch/es:
'ovirt-engine-4.0' (not exist in the newer branches list)

 This was the flow before and it made my life easier as I didn't have to
 actively search for cherry-picks in all other branches to see if it can be
 merged

 ___
 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


[JIRA] (OVIRT-962) Build failed due to: /usr/bin/python: No such file or directory

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

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

Barak Korren updated OVIRT-962:
---
Resolution: Fixed
  Assignee: Barak Korren  (was: infra)
Status: Done  (was: To Do)

This seems to have been fixed here:
https://gerrit.ovirt.org/#/c/68686/


> Build failed due to: /usr/bin/python: No such file or directory
> ---
>
> Key: OVIRT-962
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-962
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Marcin Mirecki
>Assignee: Barak Korren
>
> The following build: 
> http://jenkins.ovirt.org/job/ovirt-provider-ovn_master_build-artifacts-el7-x86_64/35/
> failed due to:
> /usr/bin/python: No such file or directory
> It used to work fine before this.
> Could you please check this.
> The patch: https://gerrit.ovirt.org/#/c/68473/
> The build: 
> http://jenkins.ovirt.org/job/ovirt-provider-ovn_master_build-artifacts-el7-x86_64/35/
> Thanks,
> Marcin



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


Re: Gerrit hooks doesn't mark open patches in other branches as -verified

2016-12-21 Thread Shlomo Ben David
Tal - Ok, so basically I didn't apply the verified grades on any hooks
accept the check_bug_url hook.

Eyal - Is it ok to add the verify (+/-)1 grade for the check_backport hook?
(I thought that we'll grade with negative value if something went wrong)

Best Regards,

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

OPEN SOURCE - 1 4 011 && 011 4 1

On Wed, Dec 21, 2016 at 1:20 PM, Tal Nisan  wrote:

> The hook found out that the patch is open in master which precedes
> ovirt-engine-4.1 and thus should have gotten -verified in 4.1
>
> On Wed, Dec 21, 2016 at 12:55 PM, Shlomo Ben David 
> wrote:
>
>> Hi Tal,
>>
>> I think that the Check Backport hook is doing exactly what you asking for.
>> Example [1]:
>>
>>- Check Backport::IGNORE, The patch backported to all newer
>>branches.(open in 'master' branch/es) found not relevant branch/es:
>>'ovirt-engine-4.0' (not exist in the newer branches list)
>>
>> patch branch: ovirt-engine-4.1
>> newer branches: 'master' (open)
>> older (not relevant) branches: ovirt-engine-4.0
>>
>> If it's not what you meant, please explain :)
>>
>> [1] - https://gerrit.ovirt.org/#/c/68862
>>
>>
>> Best Regards,
>>
>> Shlomi Ben-David | Software Engineer | Red Hat ISRAEL
>> RHCSA | RHCE
>> IRC: shlomibendavid (on #rhev-integ, #rhev-dev, #rhev-ci)
>>
>> OPEN SOURCE - 1 4 011 && 011 4 1
>>
>> On Wed, Dec 21, 2016 at 12:39 PM, Tal Nisan  wrote:
>>
>>> Check out this patches for instance: https://gerrit.ovirt.org/#/c/68862
>>> https://gerrit.ovirt.org/#/c/68861
>>> Those are 4.1 and 4.0 patches that are open on master, I'd expect to see
>>> them get -verified from the hooks which they didn't:
>>>
>>>- Update Tracker::#1406042::OK, status: POST
>>>- Check Bug-Url::OK
>>>- Check Product::#1406042::OK, product: ovirt-engine
>>>- Check TM::#1406042::OK, found clone candidate ovirt-4.0.zfor
>>>target milestone: ovirt-4.0.7
>>>- Set POST::#1406042::IGNORE, bug is already in 'POST' status
>>>- Check Backport::IGNORE, The patch backported to all newer
>>>branches.(open in 'master' branch/es) found not relevant branch/es:
>>>'ovirt-engine-4.0' (not exist in the newer branches list)
>>>
>>> This was the flow before and it made my life easier as I didn't have to
>>> actively search for cherry-picks in all other branches to see if it can be
>>> merged
>>>
>>> ___
>>> 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


[JIRA] (OVIRT-961) Fwd: Findbugs failures

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

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

Barak Korren updated OVIRT-961:
---
Resolution: Won't Fix
Status: Done  (was: To Do)

Not seeing failing runs there at this point, please link directly to job run or 
to patch next time.

> Fwd: Findbugs failures
> --
>
> Key: OVIRT-961
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-961
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Yevgeny Zaspitsky
>Assignee: infra
>
> Looks like job [1] fails rather then succeeds. IMHO those failures aren't
> related to the patches they try to check.
> [1] http://jenkins.ovirt.org/job/ovirt-engine_master_find



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


[oVirt Jenkins] test-repo_ovirt_experimental_4.1 - Build #22 - FAILURE!

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


Re: how does findbugs work?

2016-12-21 Thread Eyal Edri
You can see from the output the maven plugin is running [1],
Have you checked the filters that are ignoring 'false positives'? maybe
those needs to be updated?

The are in the 'exclude-filters.xml' files under each project and
maintained by the ovirt-engine maintainers.



[1] 08:13:21 [FINDBUGS] Collecting findbugs analysis files...
08:13:23 [FINDBUGS] Finding all files that match the pattern
**/findbugsXml.xml
08:13:23 [FINDBUGS] Parsing 34 files in
/home/jenkins/workspace/ovirt-engine_master_find-bugs_created
08:13:23 [FINDBUGS] Successfully parsed file
/home/jenkins/workspace/ovirt-engine_master_find-bugs_created/ovirt-engine/backend/manager/extensions-tool/target/findbugsXml.xml
with 0 unique warnings and 0 duplicates.
08:13:23 [FINDBUGS] Successfully parsed file
/home/jenkins/workspace/ovirt-engine_master_find-bugs_created/ovirt-engine/backend/manager/modules/aaa/target/findbugsXml.xml
with 0 unique warnings and 0 duplicates.
08:13:23 [FINDBUGS] Successfully parsed file
/home/jenkins/workspace/ovirt-engine_master_find-bugs_created/ovirt-engine/backend/manager/modules/auth-plugin/target/findbugsXml.xml
with 0 unique warnings and 0 duplicates.
08:13:23 [FINDBUGS] Successfully parsed file
/home/jenkins/workspace/ovirt-engine_master_find-bugs_created/ovirt-engine/backend/manager/modules/bll/target/findbugsXml.xml
with 0 unique warnings and 0 duplicates.
08:13:23 [FINDBUGS] Successfully parsed file
/home/jenkins/workspace/ovirt-engine_master_find-bugs_created/ovirt-engine/backend/manager/modules/branding/target/findbugsXml.xml
with 0 unique warnings and 0 duplicates.
08:13:23 [FINDBUGS] Successfully parsed file
/home/jenkins/workspace/ovirt-engine_master_find-bugs_created/ovirt-engine/backend/manager/modules/builtin-extensions/target/findbugsXml.xml
with 0 unique warnings and 0 duplicates.
08:13:23 [FINDBUGS] Successfully parsed file
/home/jenkins/workspace/ovirt-engine_master_find-bugs_created/ovirt-engine/backend/manager/modules/common/target/findbugsXml.xml
with 0 unique warnings and 0 duplicates.
08:13:23 [FINDBUGS] Successfully parsed file
/home/jenkins/workspace/ovirt-engine_master_find-bugs_created/ovirt-engine/backend/manager/modules/compat/target/findbugsXml.xml
with 0 unique warnings and 0 duplicates.
08:13:23 [FINDBUGS] Successfully parsed file
/home/jenkins/workspace/ovirt-engine_master_find-bugs_created/ovirt-engine/backend/manager/modules/dal/target/findbugsXml.xml
with 0 unique warnings and 0 duplicates.
08:13:23 [FINDBUGS] Successfully parsed file
/home/jenkins/workspace/ovirt-engine_master_find-bugs_created/ovirt-engine/backend/manager/modules/docs/target/findbugsXml.xml
with 0 unique warnings and 0 duplicates.
08:13:23 [FINDBUGS] Successfully parsed file
/home/jenkins/workspace/ovirt-engine_master_find-bugs_created/ovirt-engine/backend/manager/modules/enginesso/target/findbugsXml.xml
with 0 unique warnings and 0 duplicates.
08:13:23 [FINDBUGS] Successfully parsed file
/home/jenkins/workspace/ovirt-engine_master_find-bugs_created/ovirt-engine/backend/manager/modules/extensions-api-root/extensions-api/target/findbugsXml.xml
with 0 unique warnings and 0 duplicates.
08:13:23 [FINDBUGS] Successfully parsed file
/home/jenkins/workspace/ovirt-engine_master_find-bugs_created/ovirt-engine/backend/manager/modules/extensions-manager/target/findbugsXml.xml
with 0 unique warnings and 0 duplicates.
08:13:23 [FINDBUGS] Successfully parsed file
/home/jenkins/workspace/ovirt-engine_master_find-bugs_created/ovirt-engine/backend/manager/modules/logger/target/findbugsXml.xml
with 0 unique warnings and 0 duplicates.
08:13:23 [FINDBUGS] Successfully parsed file
/home/jenkins/workspace/ovirt-engine_master_find-bugs_created/ovirt-engine/backend/manager/modules/restapi/interface/common/jaxrs/target/findbugsXml.xml
with 0 unique warnings and 0 duplicates.
08:13:23 [FINDBUGS] Successfully parsed file
/home/jenkins/workspace/ovirt-engine_master_find-bugs_created/ovirt-engine/backend/manager/modules/restapi/interface/definition/target/findbugsXml.xml
with 0 unique warnings and 0 duplicates.
08:13:23 [FINDBUGS] Successfully parsed file
/home/jenkins/workspace/ovirt-engine_master_find-bugs_created/ovirt-engine/backend/manager/modules/restapi/jaxrs/target/findbugsXml.xml
with 0 unique warnings and 0 duplicates.
08:13:23 [FINDBUGS] Successfully parsed file
/home/jenkins/workspace/ovirt-engine_master_find-bugs_created/ovirt-engine/backend/manager/modules/restapi/types/target/findbugsXml.xml
with 0 unique warnings and 0 duplicates.
08:13:23 [FINDBUGS] Successfully parsed file
/home/jenkins/workspace/ovirt-engine_master_find-bugs_created/ovirt-engine/backend/manager/modules/scheduler/target/findbugsXml.xml
with 0 unique warnings and 0 duplicates.
08:13:23 [FINDBUGS] Successfully parsed file
/home/jenkins/workspace/ovirt-engine_master_find-bugs_created/ovirt-engine/backend/manager/modules/searchbackend/target/findbugsXml.xml
with 0 unique warnings and 0 duplicates.
08:13:23 [FINDBUGS] Successfully parsed file

Re: Gerrit hooks doesn't mark open patches in other branches as -verified

2016-12-21 Thread Tal Nisan
The hook found out that the patch is open in master which precedes
ovirt-engine-4.1 and thus should have gotten -verified in 4.1

On Wed, Dec 21, 2016 at 12:55 PM, Shlomo Ben David 
wrote:

> Hi Tal,
>
> I think that the Check Backport hook is doing exactly what you asking for.
> Example [1]:
>
>- Check Backport::IGNORE, The patch backported to all newer
>branches.(open in 'master' branch/es) found not relevant branch/es:
>'ovirt-engine-4.0' (not exist in the newer branches list)
>
> patch branch: ovirt-engine-4.1
> newer branches: 'master' (open)
> older (not relevant) branches: ovirt-engine-4.0
>
> If it's not what you meant, please explain :)
>
> [1] - https://gerrit.ovirt.org/#/c/68862
>
>
> Best Regards,
>
> Shlomi Ben-David | Software Engineer | Red Hat ISRAEL
> RHCSA | RHCE
> IRC: shlomibendavid (on #rhev-integ, #rhev-dev, #rhev-ci)
>
> OPEN SOURCE - 1 4 011 && 011 4 1
>
> On Wed, Dec 21, 2016 at 12:39 PM, Tal Nisan  wrote:
>
>> Check out this patches for instance: https://gerrit.ovirt.org/#/c/68862
>> https://gerrit.ovirt.org/#/c/68861
>> Those are 4.1 and 4.0 patches that are open on master, I'd expect to see
>> them get -verified from the hooks which they didn't:
>>
>>- Update Tracker::#1406042::OK, status: POST
>>- Check Bug-Url::OK
>>- Check Product::#1406042::OK, product: ovirt-engine
>>- Check TM::#1406042::OK, found clone candidate ovirt-4.0.zfor target
>>milestone: ovirt-4.0.7
>>- Set POST::#1406042::IGNORE, bug is already in 'POST' status
>>- Check Backport::IGNORE, The patch backported to all newer
>>branches.(open in 'master' branch/es) found not relevant branch/es:
>>'ovirt-engine-4.0' (not exist in the newer branches list)
>>
>> This was the flow before and it made my life easier as I didn't have to
>> actively search for cherry-picks in all other branches to see if it can be
>> merged
>>
>> ___
>> 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_master - Build #4335 - FAILURE!

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


[oVirt Jenkins] test-repo_ovirt_experimental_4.1 - Build #21 - FAILURE!

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


Re: Gerrit hooks doesn't mark open patches in other branches as -verified

2016-12-21 Thread Shlomo Ben David
Hi Tal,

I think that the Check Backport hook is doing exactly what you asking for.
Example [1]:

   - Check Backport::IGNORE, The patch backported to all newer
   branches.(open in 'master' branch/es) found not relevant branch/es:
   'ovirt-engine-4.0' (not exist in the newer branches list)

patch branch: ovirt-engine-4.1
newer branches: 'master' (open)
older (not relevant) branches: ovirt-engine-4.0

If it's not what you meant, please explain :)

[1] - https://gerrit.ovirt.org/#/c/68862


Best Regards,

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

OPEN SOURCE - 1 4 011 && 011 4 1

On Wed, Dec 21, 2016 at 12:39 PM, Tal Nisan  wrote:

> Check out this patches for instance: https://gerrit.ovirt.org/#/c/68862
> https://gerrit.ovirt.org/#/c/68861
> Those are 4.1 and 4.0 patches that are open on master, I'd expect to see
> them get -verified from the hooks which they didn't:
>
>- Update Tracker::#1406042::OK, status: POST
>- Check Bug-Url::OK
>- Check Product::#1406042::OK, product: ovirt-engine
>- Check TM::#1406042::OK, found clone candidate ovirt-4.0.zfor target
>milestone: ovirt-4.0.7
>- Set POST::#1406042::IGNORE, bug is already in 'POST' status
>- Check Backport::IGNORE, The patch backported to all newer
>branches.(open in 'master' branch/es) found not relevant branch/es:
>'ovirt-engine-4.0' (not exist in the newer branches list)
>
> This was the flow before and it made my life easier as I didn't have to
> actively search for cherry-picks in all other branches to see if it can be
> merged
>
> ___
> 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


how does findbugs work?

2016-12-21 Thread Michal Skrivanek
Hi,
I was trying to see why the recent NPE[1] was not found by findbugs. Typically 
identifying potential NPE is the most easy thing…but it was not reported.
So I triggered the build again on the wrong patch [2] and it doesn’t show 
anything useful[3]
Does it work at all?
There seem to be no artifacts to review that

Thanks,
michal

[1] https://gerrit.ovirt.org/#/c/68731
[2] https://gerrit.ovirt.org/#/c/68400/5
[3] http://jenkins.ovirt.org/job/ovirt-engine_master_find-bugs_created/11732/
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra


Gerrit hooks doesn't mark open patches in other branches as -verified

2016-12-21 Thread Tal Nisan
Check out this patches for instance: https://gerrit.ovirt.org/#/c/68862
https://gerrit.ovirt.org/#/c/68861
Those are 4.1 and 4.0 patches that are open on master, I'd expect to see
them get -verified from the hooks which they didn't:

   - Update Tracker::#1406042::OK, status: POST
   - Check Bug-Url::OK
   - Check Product::#1406042::OK, product: ovirt-engine
   - Check TM::#1406042::OK, found clone candidate ovirt-4.0.zfor target
   milestone: ovirt-4.0.7
   - Set POST::#1406042::IGNORE, bug is already in 'POST' status
   - Check Backport::IGNORE, The patch backported to all newer
   branches.(open in 'master' branch/es) found not relevant branch/es:
   'ovirt-engine-4.0' (not exist in the newer branches list)

This was the flow before and it made my life easier as I didn't have to
actively search for cherry-picks in all other branches to see if it can be
merged
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra


[oVirt Jenkins] test-repo_ovirt_experimental_4.1 - Build #20 - FAILURE!

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


[JIRA] (OVIRT-956) trigger jobs on jenkins

2016-12-21 Thread Gil Shinar (oVirt JIRA)

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

Gil Shinar commented on OVIRT-956:
--

You should have now

> trigger jobs on jenkins
> ---
>
> Key: OVIRT-956
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-956
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Yuval Turgeman
>Assignee: infra
>
> Hi,
> Can I please get permissions to trigger jobs in jenkin ?
> I need to trigger this one:
> http://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.0-pre_build-artifacts-el7-x86_64/56/
> Thanks,
> Yuval.



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


[JIRA] (OVIRT-964) KeyError: 'selinux_enable' while running mock on slaves

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

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

Barak Korren reassigned OVIRT-964:
--

Assignee: Barak Korren  (was: infra)

> KeyError: 'selinux_enable' while running mock on slaves
> ---
>
> Key: OVIRT-964
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-964
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: sbonazzo
>Assignee: Barak Korren
>
> *http://jenkins.ovirt.org/view/01%20Unstable%20Jobs%20(ALL)/job/qemu_3.6_create-rpms-el7-x86_64_merged/16/console
> *
> *00:00:07.167* + /usr/bin/mock
> --configdir=/home/jenkins/workspace/qemu_3.6_create-rpms-el7-x86_64_merged/jenkins/mock_configs
> --root=epel-7-x86_64-ovirt-snapshot
> --resultdir=/home/jenkins/workspace/qemu_3.6_create-rpms-el7-x86_64_merged
> --orphanskill*00:00:07.167* INFO: mock.py version 1.2.21 starting
> (python version = 2.7.5)...*00:00:07.168* ERROR:
> 'selinux_enable'*00:00:07.168* Traceback (most recent call
> last):*00:00:07.168*   File "/usr/sbin/mock", line 844, in
> *00:00:07.168* main()*00:00:07.168*   File
> "/usr/lib/python2.7/site-packages/mockbuild/trace_decorator.py", line
> 88, in trace*00:00:07.168* result = func(*args,
> **kw)*00:00:07.168*   File "/usr/sbin/mock", line 634, in
> main*00:00:07.168* buildroot = Buildroot(config_opts, uidManager,
> state, plugins)*00:00:07.168*   File
> "/usr/lib/python2.7/site-packages/mockbuild/trace_decorator.py", line
> 88, in trace*00:00:07.168* result = func(*args,
> **kw)*00:00:07.168*   File
> "/usr/lib/python2.7/site-packages/mockbuild/buildroot.py", line 47, in
> __init__*00:00:07.168* self.selinux = (not
> self.config['plugin_conf']['selinux_enable']*00:00:07.169* KeyError:
> 'selinux_enable'
> -- 
> 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.621.5#100023)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra


[JIRA] (OVIRT-964) KeyError: 'selinux_enable' while running mock on slaves

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

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

Barak Korren commented on OVIRT-964:


Its failing b/c this line gets into the mock config:
{code}
10:02:07 config_opts["plugin_conf"]={}
{code}

This patch fixed that:
https://gerrit.ovirt.org/#/c/68503

I can see subsequent job run succeeded, so closing this ticket.

> KeyError: 'selinux_enable' while running mock on slaves
> ---
>
> Key: OVIRT-964
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-964
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: sbonazzo
>Assignee: infra
>
> *http://jenkins.ovirt.org/view/01%20Unstable%20Jobs%20(ALL)/job/qemu_3.6_create-rpms-el7-x86_64_merged/16/console
> *
> *00:00:07.167* + /usr/bin/mock
> --configdir=/home/jenkins/workspace/qemu_3.6_create-rpms-el7-x86_64_merged/jenkins/mock_configs
> --root=epel-7-x86_64-ovirt-snapshot
> --resultdir=/home/jenkins/workspace/qemu_3.6_create-rpms-el7-x86_64_merged
> --orphanskill*00:00:07.167* INFO: mock.py version 1.2.21 starting
> (python version = 2.7.5)...*00:00:07.168* ERROR:
> 'selinux_enable'*00:00:07.168* Traceback (most recent call
> last):*00:00:07.168*   File "/usr/sbin/mock", line 844, in
> *00:00:07.168* main()*00:00:07.168*   File
> "/usr/lib/python2.7/site-packages/mockbuild/trace_decorator.py", line
> 88, in trace*00:00:07.168* result = func(*args,
> **kw)*00:00:07.168*   File "/usr/sbin/mock", line 634, in
> main*00:00:07.168* buildroot = Buildroot(config_opts, uidManager,
> state, plugins)*00:00:07.168*   File
> "/usr/lib/python2.7/site-packages/mockbuild/trace_decorator.py", line
> 88, in trace*00:00:07.168* result = func(*args,
> **kw)*00:00:07.168*   File
> "/usr/lib/python2.7/site-packages/mockbuild/buildroot.py", line 47, in
> __init__*00:00:07.168* self.selinux = (not
> self.config['plugin_conf']['selinux_enable']*00:00:07.169* KeyError:
> 'selinux_enable'
> -- 
> 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.621.5#100023)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra


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

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


News from oVirt CI: Introducing 'build-on-demand'

2016-12-21 Thread Eyal Edri
FYI,

Following last announcement on the manual build from patch job [1], we got
some feedback and
requests from developers on ability to improve the flow of building
artifacts from a patch.

I'm happy to announce that after some coding, the infra team was able to
add a new feature
to the 'standard CI' framework, that will allow any oVirt project to build
rpms from any VERSION or OS DISTRO using a single comment in the patch.

Full details can be found on the new oVirt blog 'ci please build' [2], but
to give the TL;DR version here,
All you have to do is write '*ci please build*' on a comment and CI will
trigger a job for you with new RPMs (or tarballs).

The projects which already have this feature enabled are:

   - ovirt-engine
   - vdsm
   - vdsm-jsonrpc-java
   - ovirt-engine-dashboard

Adding new project is a single line of code in the project YAML file and
its fully described on the blog post [2], so feel free to add your project
as well.

So let the builds roll...

Happy Xmas!


[1] http://lists.phx.ovirt.org/pipermail/devel/2016-December/028967.html
[2] https://www.ovirt.org/blog/2016/12/ci-please-build/

-- 
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


[oVirt Jenkins] test-repo_ovirt_experimental_4.1 - Build #19 - FAILURE!

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


[JIRA] (OVIRT-963) broken link to ovirt-devel archives

2016-12-21 Thread danken (oVirt JIRA)
danken created OVIRT-963:


 Summary: broken link to ovirt-devel archives
 Key: OVIRT-963
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-963
 Project: oVirt - virtualization made easy
  Issue Type: By-EMAIL
Reporter: danken
Assignee: infra


http://lists.ovirt.org/mailman/listinfo/devel leads to
http://lists.phx.ovirt.org/pipermail/devel/ which ends up in Forbidden
error.



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


[JIRA] (OVIRT-964) KeyError: 'selinux_enable' while running mock on slaves

2016-12-21 Thread sbonazzo (oVirt JIRA)
sbonazzo created OVIRT-964:
--

 Summary: KeyError: 'selinux_enable' while running mock on slaves
 Key: OVIRT-964
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-964
 Project: oVirt - virtualization made easy
  Issue Type: By-EMAIL
Reporter: sbonazzo
Assignee: infra


*http://jenkins.ovirt.org/view/01%20Unstable%20Jobs%20(ALL)/job/qemu_3.6_create-rpms-el7-x86_64_merged/16/console
*


*00:00:07.167* + /usr/bin/mock
--configdir=/home/jenkins/workspace/qemu_3.6_create-rpms-el7-x86_64_merged/jenkins/mock_configs
--root=epel-7-x86_64-ovirt-snapshot
--resultdir=/home/jenkins/workspace/qemu_3.6_create-rpms-el7-x86_64_merged
--orphanskill*00:00:07.167* INFO: mock.py version 1.2.21 starting
(python version = 2.7.5)...*00:00:07.168* ERROR:
'selinux_enable'*00:00:07.168* Traceback (most recent call
last):*00:00:07.168*   File "/usr/sbin/mock", line 844, in
*00:00:07.168* main()*00:00:07.168*   File
"/usr/lib/python2.7/site-packages/mockbuild/trace_decorator.py", line
88, in trace*00:00:07.168* result = func(*args,
**kw)*00:00:07.168*   File "/usr/sbin/mock", line 634, in
main*00:00:07.168* buildroot = Buildroot(config_opts, uidManager,
state, plugins)*00:00:07.168*   File
"/usr/lib/python2.7/site-packages/mockbuild/trace_decorator.py", line
88, in trace*00:00:07.168* result = func(*args,
**kw)*00:00:07.168*   File
"/usr/lib/python2.7/site-packages/mockbuild/buildroot.py", line 47, in
__init__*00:00:07.168* self.selinux = (not
self.config['plugin_conf']['selinux_enable']*00:00:07.169* KeyError:
'selinux_enable'


-- 
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.621.5#100023)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra


[oVirt Jenkins] test-repo_ovirt_experimental_4.1 - Build #18 - FAILURE!

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


[JIRA] (OVIRT-961) Fwd: Findbugs failures

2016-12-21 Thread Yevgeny Zaspitsky (oVirt JIRA)
Yevgeny Zaspitsky created OVIRT-961:
---

 Summary: Fwd: Findbugs failures
 Key: OVIRT-961
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-961
 Project: oVirt - virtualization made easy
  Issue Type: By-EMAIL
Reporter: Yevgeny Zaspitsky
Assignee: infra


Looks like job [1] fails rather then succeeds. IMHO those failures aren't
related to the patches they try to check.

[1] http://jenkins.ovirt.org/job/ovirt-engine_master_find



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


[JIRA] (OVIRT-961) Fwd: Findbugs failures

2016-12-21 Thread Yevgeny Zaspitsky (oVirt JIRA)

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

Yevgeny Zaspitsky commented on OVIRT-961:
-

Sorry, the right link is
http://jenkins.ovirt.org/job/ovirt-engine_master_find-bugs_created/

On Wed, Dec 14, 2016 at 11:50 AM, Yevgeny Zaspitsky 
wrote:

>
> Looks like job [1] fails rather then succeeds. IMHO those failures aren't
> related to the patches they try to check.
>
> [1] http://jenkins.ovirt.org/job/ovirt-engine_master_find
>
>
>

> Fwd: Findbugs failures
> --
>
> Key: OVIRT-961
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-961
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Yevgeny Zaspitsky
>Assignee: infra
>
> Looks like job [1] fails rather then succeeds. IMHO those failures aren't
> related to the patches they try to check.
> [1] http://jenkins.ovirt.org/job/ovirt-engine_master_find



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


[JIRA] (OVIRT-962) Build failed due to: /usr/bin/python: No such file or directory

2016-12-21 Thread Marcin Mirecki (oVirt JIRA)
Marcin Mirecki created OVIRT-962:


 Summary: Build failed due to: /usr/bin/python: No such file or 
directory
 Key: OVIRT-962
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-962
 Project: oVirt - virtualization made easy
  Issue Type: By-EMAIL
Reporter: Marcin Mirecki
Assignee: infra


The following build: 
http://jenkins.ovirt.org/job/ovirt-provider-ovn_master_build-artifacts-el7-x86_64/35/
failed due to:
/usr/bin/python: No such file or directory

It used to work fine before this.

Could you please check this.

The patch: https://gerrit.ovirt.org/#/c/68473/
The build: 
http://jenkins.ovirt.org/job/ovirt-provider-ovn_master_build-artifacts-el7-x86_64/35/

Thanks,
Marcin



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


[JIRA] (OVIRT-960) Unable to collect logs from a failed check_merge job

2016-12-21 Thread Edward Haas (oVirt JIRA)
Edward Haas created OVIRT-960:
-

 Summary: Unable to collect logs from a failed check_merge job
 Key: OVIRT-960
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-960
 Project: oVirt - virtualization made easy
  Issue Type: By-EMAIL
Reporter: Edward Haas
Assignee: infra


Hello,

The following job:
http://jenkins.ovirt.org/job/vdsm_master_check-merged-el7-x86_64/693/
has ended with a failure and no system logs are available.

Thanks,
Edy.



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


[JIRA] (OVIRT-958) false CI-1 due to failure to pull surefire-junit

2016-12-21 Thread danken (oVirt JIRA)
danken created OVIRT-958:


 Summary: false CI-1 due to failure to pull surefire-junit
 Key: OVIRT-958
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-958
 Project: oVirt - virtualization made easy
  Issue Type: By-EMAIL
Reporter: danken
Assignee: infra


https://gerrit.ovirt.org/#/c/68339/1 got CI-1 for what seems to me as
an unrelated infra error. Please look into it.

http://jenkins.ovirt.org/job/ovirt-engine_4.0_check-patch-el7-x86_64/1071/consoleText

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-surefire-plugin:2.7.2:test
(default-test) on project checkstyles: Error to resolving surefire
provider dependency: Unable to get dependency information for
org.apache.maven.surefire:surefire-junit4:jar:2.7.2: Failed to
retrieve POM for org.apache.maven.surefire:surefire-junit4:jar:2.7.2:
Could not transfer artifact
org.apache.maven.surefire:surefire-junit4:pom:2.7.2 from/to
ovirt-maven-repository
(http://artifactory.ovirt.org/artifactory/ovirt-mirror): Failed to
transfer file: 
http://artifactory.ovirt.org/artifactory/ovirt-mirror/org/apache/maven/surefire/surefire-junit4/2.7.2/surefire-junit4-2.7.2.pom.
Return code is: 500 , ReasonPhrase:Internal Server Error.
[ERROR] org.apache.maven.surefire:surefire-junit4:jar:2.7.2



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


[JIRA] (OVIRT-959) false CI-1 due to tcsetattr: Inappropriate ioctl for device

2016-12-21 Thread danken (oVirt JIRA)
danken created OVIRT-959:


 Summary: false CI-1 due to tcsetattr: Inappropriate ioctl for 
device
 Key: OVIRT-959
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-959
 Project: oVirt - virtualization made easy
  Issue Type: By-EMAIL
Reporter: danken
Assignee: infra


http://jenkins.ovirt.org/job/vdsm_master_check-merged-el7-x86_64/690/console

has failed for something unrelated to the code or the test. Please look it up.

16:22:40 sh: [9520: 1 (255)] tcsetattr: Inappropriate ioctl for device
16:22:40 Slave went offline during the build
16:22:40 ERROR: Connection was broken: java.io.IOException: Unexpected
termination of the channel
16:22:40 at 
hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50)
16:22:40 Caused by: java.io.EOFException
16:22:40 at 
java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2353)
16:22:40 at 
java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2822)
16:22:40 at 
java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:804)
16:22:40 at java.io.ObjectInputStream.(ObjectInputStream.java:301)
16:22:40 at 
hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:48)
16:22:40 at 
hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34)
16:22:40 at 
hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48)



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


[JIRA] (OVIRT-957) list archives are forbidden

2016-12-21 Thread Yedidyah Bar David (oVirt JIRA)
Yedidyah Bar David created OVIRT-957:


 Summary: list archives are forbidden
 Key: OVIRT-957
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-957
 Project: oVirt - virtualization made easy
  Issue Type: By-EMAIL
Reporter: Yedidyah Bar David
Assignee: infra


E.g. http://lists.ovirt.org/pipermail/users/2016-July/040885.html

-- 
Didi



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


[JIRA] (OVIRT-954) Fwd: http://lists.ovirt.org/pipermail/announce/ is not reachable

2016-12-21 Thread sbonazzo (oVirt JIRA)
sbonazzo created OVIRT-954:
--

 Summary: Fwd: http://lists.ovirt.org/pipermail/announce/ is not 
reachable
 Key: OVIRT-954
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-954
 Project: oVirt - virtualization made easy
  Issue Type: By-EMAIL
Reporter: sbonazzo
Assignee: infra


The lists server is not reachable anymore. Looks like a dns issue:

$ traceroute lists.ovirt.org
lists.ovirt.org: Name or service not known


-- 
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.621.5#100023)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra


[JIRA] (OVIRT-956) trigger jobs on jenkins

2016-12-21 Thread Yuval Turgeman (oVirt JIRA)
Yuval Turgeman created OVIRT-956:


 Summary: trigger jobs on jenkins
 Key: OVIRT-956
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-956
 Project: oVirt - virtualization made easy
  Issue Type: By-EMAIL
Reporter: Yuval Turgeman
Assignee: infra


Hi,

Can I please get permissions to trigger jobs in jenkin ?

I need to trigger this one:
http://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.0-pre_build-artifacts-el7-x86_64/56/


Thanks,
Yuval.



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


[JIRA] (OVIRT-955) Re: http://lists.ovirt.org/pipermail/announce/ is not reachable

2016-12-21 Thread sbonazzo (oVirt JIRA)
sbonazzo created OVIRT-955:
--

 Summary: Re: http://lists.ovirt.org/pipermail/announce/ is not 
reachable
 Key: OVIRT-955
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-955
 Project: oVirt - virtualization made easy
  Issue Type: By-EMAIL
Reporter: sbonazzo
Assignee: infra


Tested it, I've access forbidden there:
http://lists.phx.ovirt.org/pipermail/announce/

archives should be publicly accessible.

On Mon, Dec 12, 2016 at 2:21 PM, Evgheni Dereveanchin 
wrote:

>  I totally agree with Barak on this. The hostname
> must work as there's a bunch of links indexed
> by search engine which lead to it.
>  In general the PHX one should not be used
> by end users. I've re-added the CNAME and edited
> the virtualhost on apache so it should be available
> again once existing DNS caches expire.
>
> Regards,
> Evgheni Dereveanchin
>
> - Original Message -
> From: "Barak Korren" 
> To: "Eyal Edri" 
> Cc: "infra" , "Sandro Bonazzola" ,
> "Evgheni Dereveanchin" , "duck" ,
> infra-ow...@ovirt.org
> Sent: Monday, 12 December, 2016 2:05:57 PM
> Subject: Re: http://lists.ovirt.org/pipermail/announce/ is not reachable
>
> It can be reached now at lists.phx.ovirt.org (but we we need a CNAME
> from the old name)
>
> On 12 December 2016 at 15:03, Eyal Edri  wrote:
> > I'm not sure who gets emails sent to infra-owner list.  best to send it
> to
> > infra or infra support.
> >
> > Adding Evgheni and Duck who are working on migration of the mm server.
> >
> > On Dec 12, 2016 2:58 PM, "Sandro Bonazzola"  wrote:
> >>
> >> The lists server is not reachable anymore. Looks like a dns issue:
> >>
> >> $ traceroute lists.ovirt.org
> >> lists.ovirt.org: Name or service not known
> >>
> >>
> >> --
> >> Sandro Bonazzola
> >> Better technology. Faster innovation. Powered by community
> collaboration.
> >> See how it works at redhat.com
> >
> >
> > ___
> > Infra mailing list
> > Infra@ovirt.org
> > http://lists.phx.ovirt.org/mailman/listinfo/infra
> >
>
>
>
> --
> Barak Korren
> bkor...@redhat.com
> RHCE, RHCi, RHV-DevOps Team
> https://ifireball.wordpress.com/
>



-- 
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.621.5#100023)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra


  1   2   >