date:20170105

Future of the oVirt website

2017-01-05 Thread Duck

Quack,

So I just discovered this thread:
  http://lists.ovirt.org/pipermail/devel/2017-January/029097.html

First, it would be nice if the infra team was involved directly, because
not everyone is also an oVirt developer (and on this list). Also there
are already plans to improve the site system and build and this
side-initiative feels like an unexpected and rude disruption of energy
already invested.

It seems people forget how things were in the past, which leads to going
back and forth between a new solution and the previous one. People wish
for an easy way to contribute, and this is a legitimate goal. After some
time an easy solution make things complicated because it is such a mess
and there is no review, so no quality checks, and people wish to have
workflows. Then they find it to cumbersome and wish to go back to a
marvelous past. And so on again and again.

This said, this does not mean the current solution is perfect and we
should not think about a better one, but we should recall why we
abandoned a wiki to switch to the current solution, so we don't fall
into the same traps.

What I can say on the topic is that migrating is painful, so we should
be cautious. OSAS is not here to force a solution upon you, but the
infra team (and the OSAS folks too), have a limited workforce to
dedicate to this project, so let's make something realistic. Also we
just finish another pass of cleanup of the current site, with migration
bugs from the previous Mediawiki solution, so keep in mind it would
probably take _years_ to really get something clean. Who's gonna do this?

I also wanted to say I totally disagree on someone's remark (somewhere
in the thread) about doc not being as important as code. A lot of
content is obsolete or mistaken in the current site already, and this
means giving a very bad image of the project, raising the number of
silly questions people come to bother you with on ML or IRC, so I think
doc should really be taken seriously. As a user it is often I have to
dig in the code to find undocumented features, or why a documented one
does not work as said, and that's fu^Wutterly boring.

So this was to gather all related parties.

\_o<



signature.asc
Description: OpenPGP digital signature
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Build failed in Jenkins: ovirt_3.6_he-system-tests #803

2017-01-05 Thread jenkins

See 

Changes:

[Yaniv Kaul] Allow discard for storage

--
[...truncated 653 lines...]
Finish: shell
@@
@@ Fri Jan  6 03:00:01 UTC 2017 automation/he_basic_suite_3.6.sh chroot finished
@@  took 410 seconds
@@  rc = 1
@@
== Scrubbing chroot
mock \

--configdir="
 \
--root="mocker-epel-7-x86_64.el7" \
--resultdir="./mock_logs.FJcynAI8/mocker-epel-7-x86_64.el7.scrub" \
--scrub=chroot
WARNING: Could not find required logging config file: 

 Using default...
INFO: mock.py version 1.2.21 starting (python version = 3.5.1)...
Start: init plugins
INFO: selinux enabled
Finish: init plugins
Start: run
Start: scrub ['chroot']
INFO: scrubbing chroot for mocker-epel-7-x86_64.el7
Finish: scrub ['chroot']
Finish: run
Scrub chroot took 6 seconds

##
## Fri Jan  6 03:00:07 UTC 2017 Finished env: el7:epel-7-x86_64
##  took 416 seconds
##  rc = 1
##
find: 'logs': No such file or directory
No log files found, check command output
##!
Collecting mock logs
'./mock_logs.FJcynAI8/mocker-epel-7-x86_64.el7.clean_rpmdb' -> 
'exported-artifacts/mock_logs/mocker-epel-7-x86_64.el7.clean_rpmdb'
'./mock_logs.FJcynAI8/mocker-epel-7-x86_64.el7.he_basic_suite_3.6.sh' -> 
'exported-artifacts/mock_logs/mocker-epel-7-x86_64.el7.he_basic_suite_3.6.sh'
'./mock_logs.FJcynAI8/mocker-epel-7-x86_64.el7.init' -> 
'exported-artifacts/mock_logs/mocker-epel-7-x86_64.el7.init'
##
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=3.6
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_3.6_he-system-tests] $ /bin/bash -xe /tmp/hudson5037284079566254380.sh
+ echo shell_scripts/system_tests.collect_logs.sh
shell_scripts/system_tests.collect_logs.sh
+ VERSION=3.6
+ SUITE_TYPE=
+ WORKSPACE=
+ OVIRT_SUITE=3.6
+ 
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"

# 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+="

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

2017-01-05 Thread jenkins

See 

Changes:

[Yaniv Kaul] Allow discard for storage

[Eyal Edri] gamification: enable jenkins integration for more projects

[ngoldin] Move lago jobs to use VMs only

[Eyal Edri] fixing bug in repoversion for 4.1 and dropping fc23

--
[...truncated 883 lines...]
logout
Finish: shell
@@
@@ Fri Jan  6 02:44:36 UTC 2017 automation/basic_suite_4.1.sh chroot finished
@@  took 2006 seconds
@@  rc = 1
@@
== Scrubbing chroot
mock \

--configdir="
 \
--root="mocker-epel-7-x86_64.el7" \
--resultdir="./mock_logs.izAuPaHz/mocker-epel-7-x86_64.el7.scrub" \
--scrub=chroot
WARNING: Could not find required logging config file: 

 Using default...
INFO: mock.py version 1.2.21 starting (python version = 3.4.3)...
Start: init plugins
INFO: selinux enabled
Finish: init plugins
Start: run
Start: scrub ['chroot']
INFO: scrubbing chroot for mocker-epel-7-x86_64.el7
Finish: scrub ['chroot']
Finish: run
Scrub chroot took 6 seconds

##
## Fri Jan  6 02:44:42 UTC 2017 Finished env: el7:epel-7-x86_64
##  took 2012 seconds
##  rc = 1
##
find: 'logs': No such file or directory
No log files found, check command output
##!
Collecting mock logs
'./mock_logs.izAuPaHz/mocker-epel-7-x86_64.el7.basic_suite_4.1.sh' -> 
'exported-artifacts/mock_logs/mocker-epel-7-x86_64.el7.basic_suite_4.1.sh'
'./mock_logs.izAuPaHz/mocker-epel-7-x86_64.el7.clean_rpmdb' -> 
'exported-artifacts/mock_logs/mocker-epel-7-x86_64.el7.clean_rpmdb'
'./mock_logs.izAuPaHz/mocker-epel-7-x86_64.el7.init' -> 
'exported-artifacts/mock_logs/mocker-epel-7-x86_64.el7.init'
##
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/hudson2734950992350213073.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

oVirt infra daily report - unstable production jobs - 191

2017-01-05 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/191//artifact/exported-artifacts/upstream_report.html

Cheers,
Jenkins

RHEVM CI Jenkins Daily Report - 05/01/2017

00 Unstable Critical

deploy-to-ovirt_experimental_3.6