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

[jenkins]

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

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

[jenkins]

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

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

[jenkins]

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

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

[jenkins]

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

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

[jenkins]

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

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

[jenkins]

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

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

[jenkins]

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

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

[jenkins]

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

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

[jenkins]

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

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

[jenkins]

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

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

[jenkins]

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

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

[jenkins]

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

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

[jenkins]

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

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

[jenkins]

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

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

[jenkins]

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

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

[jenkins]

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

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

[jenkins]

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

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

[jenkins]

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

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

[jenkins]

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

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

[jenkins]

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

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

[jenkins]

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

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

[jenkins]

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

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

[jenkins]

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

oVirt infra daily report - unstable production jobs - 124

[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/124//artifact/exported-artifacts/upstream_report.html

Cheers,
Jenkins


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

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

[jenkins]

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

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

[jenkins]

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

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

[jenkins]

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

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

[jenkins]

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

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

[jenkins]

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

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

[jenkins]

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

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

[jenkins]

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

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

[jenkins]

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

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

[jenkins]

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

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

[jenkins]

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

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

[jenkins]

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

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

[jenkins]

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

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

[jenkins]

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

[JIRA] (OVIRT-803) [gerrit hooks] enable updating external tracker info for master branch

[Shlomo Ben David (oVirt JIRA)]

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

Shlomo Ben David updated OVIRT-803:
---
Epic Link: OVIRT-403

> [gerrit hooks] enable updating external tracker info for master branch
> --
>
> Key: OVIRT-803
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-803
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>Reporter: Shlomo Ben David
>Assignee: infra
>
> - Currently we are not updating external tracker info for patches in 'master' 
> branch.
> - We should update both 'stable' and 'master' branch patches info in Bugzilla 
> (external tracker)



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

[JIRA] (OVIRT-803) [gerrit hooks] enable updating external tracker info for master branch

[Shlomo Ben David (oVirt JIRA)]

Shlomo Ben David created OVIRT-803:
--

 Summary: [gerrit hooks] enable updating external tracker info for 
master branch
 Key: OVIRT-803
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-803
 Project: oVirt - virtualization made easy
  Issue Type: Task
Reporter: Shlomo Ben David
Assignee: infra


- Currently we are not updating external tracker info for patches in 'master' 
branch.
- We should update both 'stable' and 'master' branch patches info in Bugzilla 
(external tracker)



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

[JIRA] (OVIRT-803) [gerrit hooks] enable updating external tracker info for master branch

[Shlomo Ben David (oVirt JIRA)]

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

Shlomo Ben David reassigned OVIRT-803:
--

Assignee: Shlomo Ben David  (was: infra)

> [gerrit hooks] enable updating external tracker info for master branch
> --
>
> Key: OVIRT-803
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-803
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>Reporter: Shlomo Ben David
>Assignee: Shlomo Ben David
>
> - Currently we are not updating external tracker info for patches in 'master' 
> branch.
> - We should update both 'stable' and 'master' branch patches info in Bugzilla 
> (external tracker)



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

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

[jenkins]

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

Updating email configuration

[Shlomo Ben David]

Hi All,

Due to some restrictions on our email server we need to update our email
configuration to increase the security on it.
To apply the new configuration i will reboot the server today 31/10/2016 at
20:00 IST.

*Downtime EST: ~5 minutes*

Best Regards,

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

OPEN SOURCE - 1 4 011 && 011 4 1
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

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

[jenkins]

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

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

[jenkins]

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

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

[jenkins]

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

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

[jenkins]

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

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

[jenkins]

See 

Changes:

[Yaniv Kaul] Separate log collector run test to its own test.

[Gil Shinar] Fixed bug in test experimental repo emails

--
[...truncated 1267 lines...]
##  rc = 1
##
##! ERROR v
##! Last 20 log entries: 
logs/mocker-fedora-23-x86_64.fc23.he_basic_suite_3.6.sh/he_basic_suite_3.6.sh.log
##!
+ true
+ env_cleanup
+ echo '#'
#
+ local res=0
+ local uuid
+ echo ' Cleaning up'
 Cleaning up
+ [[ -e 

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

 destroy --yes --all-prefixes
+ echo '--- Cleaning with lago done'
--- Cleaning with lago done
+ [[ 0 != \0 ]]
+ echo ' Cleanup done'
 Cleanup done
+ exit 0
Took 1387 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=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/hudson1008738894491318119.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 -xe
echo "shell-scripts/mock_cleanup.sh"

shopt -s nullglob


WORKSPACE="$PWD"

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

[JIRA] (OVIRT-751) Persistent maven caches on the mock slaves

[Gil Shinar (oVirt JIRA)]

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

Gil Shinar reassigned OVIRT-751:


Assignee: Gil Shinar  (was: infra)

> Persistent maven caches on the mock slaves
> --
>
> Key: OVIRT-751
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-751
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>Reporter: Anton Marchukov
>Assignee: Gil Shinar
>
> I think we need to design a way to retain maven caches on the mocked jenkins 
> slaves. Currently it is stored inside the mock and thus maven downloads 
> packages from artifactory server each time. 
> However there is really no reason for that. Maven artifacts are designed to 
> be immutable so once artifact is in the repo there is no trivial way to 
> change it without creating a new version. In fact it should never be needed 
> and the correct solution for that is to always create a new version.
> SNAPSHOOT artifacts are in fact timestamped and each one have different file 
> name. It is just not visible since maven automatically takes the latest one. 
> But it is not related to caching as the new snapshoot will be a new artifact 
> still.
> So based on that point there is no reason to purge maven cache each time, but 
> there are reasons why not to purge. Not purging them will reduce the build 
> times of all java jobs and also reduce the network traffic we have. 



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

[JIRA] (OVIRT-802) ovirt-engine_master_upgrade-from-3.6_el7_merged failing

[Evgheni Dereveanchin (oVirt JIRA)]

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

Evgheni Dereveanchin reassigned OVIRT-802:
--

Assignee: Evgheni Dereveanchin  (was: infra)

> ovirt-engine_master_upgrade-from-3.6_el7_merged failing
> ---
>
> Key: OVIRT-802
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-802
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Greg Sheremeta
>Assignee: Evgheni Dereveanchin
>
> https://gerrit.ovirt.org/#/c/65899/2
> job:
> http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_merged/561/console
> failing.
> + which engine-setup
> + engine-cleanup
> --config-append=/home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_merged/jenkins/jobs/ovirt-engine_upgrade_to_master/cleanup.file.otopi
> [ INFO  ] Stage: Initializing
> [ INFO  ] Stage: Environment setup
>   Configuration files:
> ['/etc/ovirt-engine-setup.conf.d/10-packaging-jboss.conf',
> '/etc/ovirt-engine-setup.conf.d/10-packaging.conf',
> '/home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_merged/jenkins/jobs/ovirt-engine_upgrade_to_master/cleanup.file.otopi']
>   Log file:
> /var/log/ovirt-engine/setup/ovirt-engine-remove-20161031153445-zoq6gr.log
>   Version: otopi-1.6.0_master
> (otopi-1.6.0-0.0.master.20160829151522.git7547b87.el7.centos)
> [ ERROR ] Could not detect a completed product setup
>   Please use the cleanup utility only after a setup or after an
> upgrade from an older installation.
> [ ERROR ] Failed to execute stage 'Environment setup': Could not detect
> product setup
> [ INFO  ] Stage: Clean up
>   Log file is located at
> /var/log/ovirt-engine/setup/ovirt-engine-remove-20161031153445-zoq6gr.log
> [ INFO  ] Generating answer file
> '/var/lib/ovirt-engine/setup/answers/20161031153445-cleanup.conf'
> [ INFO  ] Stage: Pre-termination
> [ INFO  ] Stage: Termination
> [ ERROR ] Execution of cleanup failed
> -- 
> Greg Sheremeta, MBA
> Red Hat, Inc.
> Sr. Software Engineer
> gsher...@redhat.com



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

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

[jenkins]

See 

Changes:

[Yaniv Kaul] Separate log collector run test to its own test.

--
[...truncated 960 lines...]
##  rc = 1
##
##! ERROR v
##! Last 20 log entries: 
logs/mocker-fedora-23-x86_64.fc23.he_basic_suite_4.0.sh/he_basic_suite_4.0.sh.log
##!
+ env_cleanup
+ echo '#'
#
+ local res=0
+ local uuid
+ echo ' Cleaning up'
 Cleaning up
+ [[ -e 

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

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

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

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

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

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

[ovirt_4.0_he-system-tests] $ /bin/bash -xe /tmp/hudson1446614098432568531.sh
+ echo shell_scripts/system_tests.collect_logs.sh
shell_scripts/system_tests.collect_logs.sh
+ VERSION=4.0
+ SUITE_TYPE=
+ WORKSPACE=
+ OVIRT_SUITE=4.0
+ 
TESTS_LOGS=
+ rm -rf 

+ mkdir -p 

+ [[ -d 

 ]]
+ mv 

 

 

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

shopt -s nullglob


WORKSPACE="$PWD"

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

[JIRA] (OVIRT-802) ovirt-engine_master_upgrade-from-3.6_el7_merged failing

[Yedidyah Bar David (oVirt JIRA)]

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

Yedidyah Bar David commented on OVIRT-802:
--

On Mon, Oct 31, 2016 at 5:45 PM, eyal edri [Administrator] (oVirt JIRA) <


No.

setup log has:

2016-10-31 15:34:33 DEBUG
otopi.plugins.ovirt_engine_common.base.system.selinux plugin.execute:926
execute-output: ('/sbin/semanage', 'fcontext', '-a', '-t',
'public_content_rw_t', '/var/lib/exports/iso(/.*)?') stderr:
libsepol.context_from_record: type ovirt_vmconsole_proxy_port_t is not
defined (No such file or directory).
libsepol.context_from_record: could not create context structure (Invalid
argument).
libsepol.port_from_record: could not create port structure for range
: (tcp) (Invalid argument).
libsepol.sepol_port_modify: could not load port range  -  (tcp)
(Invalid argument).
libsemanage.dbase_policydb_modify: could not modify record value (Invalid
argument).
libsemanage.semanage_base_merge_components: could not merge local
modifications into policy (Invalid argument).
ValueError: Could not commit semanage transaction

The type public_content_rw_t should have been created during installation
of ovirt-vmconsole-proxy, by its %post scriptlet. I do not see it installed
in the console output, also on successful builds. How/where/when do you
install this package? Perhaps something changed selinux policy after it was
installed?





-- 
Didi


> ovirt-engine_master_upgrade-from-3.6_el7_merged failing
> ---
>
> Key: OVIRT-802
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-802
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Greg Sheremeta
>Assignee: infra
>
> https://gerrit.ovirt.org/#/c/65899/2
> job:
> http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_merged/561/console
> failing.
> + which engine-setup
> + engine-cleanup
> --config-append=/home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_merged/jenkins/jobs/ovirt-engine_upgrade_to_master/cleanup.file.otopi
> [ INFO  ] Stage: Initializing
> [ INFO  ] Stage: Environment setup
>   Configuration files:
> ['/etc/ovirt-engine-setup.conf.d/10-packaging-jboss.conf',
> '/etc/ovirt-engine-setup.conf.d/10-packaging.conf',
> '/home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_merged/jenkins/jobs/ovirt-engine_upgrade_to_master/cleanup.file.otopi']
>   Log file:
> /var/log/ovirt-engine/setup/ovirt-engine-remove-20161031153445-zoq6gr.log
>   Version: otopi-1.6.0_master
> (otopi-1.6.0-0.0.master.20160829151522.git7547b87.el7.centos)
> [ ERROR ] Could not detect a completed product setup
>   Please use the cleanup utility only after a setup or after an
> upgrade from an older installation.
> [ ERROR ] Failed to execute stage 'Environment setup': Could not detect
> product setup
> [ INFO  ] Stage: Clean up
>   Log file is located at
> /var/log/ovirt-engine/setup/ovirt-engine-remove-20161031153445-zoq6gr.log
> [ INFO  ] Generating answer file
> '/var/lib/ovirt-engine/setup/answers/20161031153445-cleanup.conf'
> [ INFO  ] Stage: Pre-termination
> [ INFO  ] Stage: Termination
> [ ERROR ] Execution of cleanup failed
> -- 
> Greg Sheremeta, MBA
> Red Hat, Inc.
> Sr. Software Engineer
> gsher...@redhat.com



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

[oVirt Jenkins] 'test-repo_ovirt_experimental_master' - Build #2934 - SUCCESS!

[jenkins]

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

[JIRA] (OVIRT-798) outgoing mail failure - SPF fail

[Duck]

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

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


Summary from the mail thread follows.

Gerrit spoof the sender of notifications using the user's address. But Gerrit 
is not allowed to send mails from any domain due to SPF policy. The Red Hat 
policy is getting stricter, and other companies also do so, so we need to 
change this behavior.

According to:
  https://review.openstack.org/Documentation/config-gerrit.html#sendemail
I suggested we could update the sendemail.from setting with the wanted address
instead of USER. I never touched this software so maybe someone more familiar 
could do the change if it looks ok. Also we need to schedule this to avoid 
bothering people.

Evgheni suggested using automat...@ovirt.org as From.

Moreover, to be able to send from the oVirt domain the SPF settings in DNS was 
changed.


> outgoing mail failure - SPF fail
> 
>
> Key: OVIRT-798
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-798
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Yedidyah Bar David
>Assignee: infra
>
> Hi,
> When adding a reviewer to a patch on gerrit, I get an email:
> The original message was received at Mon, 31 Oct 2016 05:07:32 -0400
> from gerrit.ovirt.org [127.0.0.1]
>- The following addresses had permanent fatal errors -
> 
> (reason: 551 5.7.1 SPF fail: 'gerrit.ovirt.org'[107.22.212.69],
> 'redhat.com'; REJECT)
>- Transcript of session follows -
> ... while talking to mx1.redhat.com.:
> >>> DATA
> <<< 551 5.7.1 SPF fail: 'gerrit.ovirt.org'[107.22.212.69], 'redhat.com'; 
> REJECT
> 550 5.1.1 ... User unknown
> <<< 554 5.5.1 Error: no valid recipients
> Final-Recipient: RFC822; sbona...@redhat.com
> Action: failed
> Status: 5.7.1
> Remote-MTA: DNS; mx1.redhat.com
> Diagnostic-Code: SMTP; 551 5.7.1 SPF fail:
> 'gerrit.ovirt.org'[107.22.212.69], 'redhat.com'; REJECT
> Last-Attempt-Date: Mon, 31 Oct 2016 05:07:33 -0400
> Please check/handle. Thanks.
> -- 
> Didi



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

[JIRA] (OVIRT-802) ovirt-engine_master_upgrade-from-3.6_el7_merged failing

[Evgheni Dereveanchin (oVirt JIRA)]

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

Evgheni Dereveanchin commented on OVIRT-802:


[~eedri] first of all, this is not a new slave, second of all SELinux is in 
permissive mode on it:

[ederevea@el7-vm07 ~]$ getenforce 
Permissive

[ederevea@el7-vm07 ~]$ rpm -qa | grep selinux
libselinux-ruby-2.2.2-6.el7.x86_64
selinux-policy-targeted-3.13.1-60.el7_2.3.noarch
selinux-policy-doc-3.13.1-60.el7_2.9.noarch
selinux-policy-3.13.1-60.el7_2.9.noarch
libselinux-2.2.2-6.el7.x86_64
libselinux-utils-2.2.2-6.el7.x86_64
selinux-policy-devel-3.13.1-60.el7_2.9.noarch
libselinux-python-2.2.2-6.el7.x86_64


here's the error from the engine setup log attached to the job:

2016-10-31 15:34:29 DEBUG otopi.plugins.ovirt_engine_common.base.system.selinux 
plugin.executeRaw:813 execute: ('/sbin/semanage', 'fcontext', '-a', '-t', 
'public_content_rw_t', '/var/lib/exports/iso(/.*)?'), executable='None', 
cwd='None', env=None
2016-10-31 15:34:33 DEBUG otopi.plugins.ovirt_engine_common.base.system.selinux 
plugin.executeRaw:863 execute-result: ('/sbin/semanage', 'fcontext', '-a', 
'-t', 'public_content_rw_t', '/var/lib/exports/iso(/.*)?'), rc=1
2016-10-31 15:34:33 DEBUG otopi.plugins.ovirt_engine_common.base.system.selinux 
plugin.execute:921 execute-output: ('/sbin/semanage', 'fcontext', '-a', '-t', 
'public_content_rw_t', '/var/lib/exports/iso(/.*)?') stdout:


2016-10-31 15:34:33 DEBUG otopi.plugins.ovirt_engine_common.base.system.selinux 
plugin.execute:926 execute-output: ('/sbin/semanage', 'fcontext', '-a', '-t', 
'public_content_rw_t', '/var/lib/exports/iso(/.*)?') stderr:
libsepol.context_from_record: type ovirt_vmconsole_proxy_port_t is not defined 
(No such file or directory).
libsepol.context_from_record: could not create context structure (Invalid 
argument).
libsepol.port_from_record: could not create port structure for range : 
(tcp) (Invalid argument).
libsepol.sepol_port_modify: could not load port range  -  (tcp) 
(Invalid argument).
libsemanage.dbase_policydb_modify: could not modify record value (Invalid 
argument).
libsemanage.semanage_base_merge_components: could not merge local modifications 
into policy (Invalid argument).
ValueError: Could not commit semanage transaction

2016-10-31 15:34:33 DEBUG otopi.context context._executeMethod:142 method 
exception
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/otopi/context.py", line 132, in 
_executeMethod
method['method']()
  File 
"/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-common/base/system/selinux.py",
 line 94, in _misc
entry['pattern']
  File "/usr/lib/python2.7/site-packages/otopi/plugin.py", line 931, in execute
command=args[0],
RuntimeError: Command '/sbin/semanage' failed to execute
2016-10-31 15:34:33 ERROR otopi.context context._executeMethod:151 Failed to 
execute stage 'Misc configuration': Command '/sbin/semanage' failed to execute


> ovirt-engine_master_upgrade-from-3.6_el7_merged failing
> ---
>
> Key: OVIRT-802
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-802
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Greg Sheremeta
>Assignee: infra
>
> https://gerrit.ovirt.org/#/c/65899/2
> job:
> http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_merged/561/console
> failing.
> + which engine-setup
> + engine-cleanup
> --config-append=/home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_merged/jenkins/jobs/ovirt-engine_upgrade_to_master/cleanup.file.otopi
> [ INFO  ] Stage: Initializing
> [ INFO  ] Stage: Environment setup
>   Configuration files:
> ['/etc/ovirt-engine-setup.conf.d/10-packaging-jboss.conf',
> '/etc/ovirt-engine-setup.conf.d/10-packaging.conf',
> '/home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_merged/jenkins/jobs/ovirt-engine_upgrade_to_master/cleanup.file.otopi']
>   Log file:
> /var/log/ovirt-engine/setup/ovirt-engine-remove-20161031153445-zoq6gr.log
>   Version: otopi-1.6.0_master
> (otopi-1.6.0-0.0.master.20160829151522.git7547b87.el7.centos)
> [ ERROR ] Could not detect a completed product setup
>   Please use the cleanup utility only after a setup or after an
> upgrade from an older installation.
> [ ERROR ] Failed to execute stage 'Environment setup': Could not detect
> product setup
> [ INFO  ] Stage: Clean up
>   Log file is located at
> /var/log/ovirt-engine/setup/ovirt-engine-remove-20161031153445-zoq6gr.log
> [ INFO  ] Generating answer file
> '/var/lib/ovirt-engine/setup/answers/20161031153445-cleanup.conf'
> [ INFO  ] Stage: Pre-termination
> [ INFO  ] Stage: Termination
> [ ERROR ] Execution of cleanup failed
> -- 
> Greg Sheremeta, MBA
> Red Hat, 

[JIRA] (OVIRT-802) ovirt-engine_master_upgrade-from-3.6_el7_merged failing

[eyal edri [Administrator] (oVirt JIRA)]

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

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

[~ederevea] also, could it be new slaves not configured for SELINUX?

> ovirt-engine_master_upgrade-from-3.6_el7_merged failing
> ---
>
> Key: OVIRT-802
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-802
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Greg Sheremeta
>Assignee: infra
>
> https://gerrit.ovirt.org/#/c/65899/2
> job:
> http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_merged/561/console
> failing.
> + which engine-setup
> + engine-cleanup
> --config-append=/home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_merged/jenkins/jobs/ovirt-engine_upgrade_to_master/cleanup.file.otopi
> [ INFO  ] Stage: Initializing
> [ INFO  ] Stage: Environment setup
>   Configuration files:
> ['/etc/ovirt-engine-setup.conf.d/10-packaging-jboss.conf',
> '/etc/ovirt-engine-setup.conf.d/10-packaging.conf',
> '/home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_merged/jenkins/jobs/ovirt-engine_upgrade_to_master/cleanup.file.otopi']
>   Log file:
> /var/log/ovirt-engine/setup/ovirt-engine-remove-20161031153445-zoq6gr.log
>   Version: otopi-1.6.0_master
> (otopi-1.6.0-0.0.master.20160829151522.git7547b87.el7.centos)
> [ ERROR ] Could not detect a completed product setup
>   Please use the cleanup utility only after a setup or after an
> upgrade from an older installation.
> [ ERROR ] Failed to execute stage 'Environment setup': Could not detect
> product setup
> [ INFO  ] Stage: Clean up
>   Log file is located at
> /var/log/ovirt-engine/setup/ovirt-engine-remove-20161031153445-zoq6gr.log
> [ INFO  ] Generating answer file
> '/var/lib/ovirt-engine/setup/answers/20161031153445-cleanup.conf'
> [ INFO  ] Stage: Pre-termination
> [ INFO  ] Stage: Termination
> [ ERROR ] Execution of cleanup failed
> -- 
> Greg Sheremeta, MBA
> Red Hat, Inc.
> Sr. Software Engineer
> gsher...@redhat.com



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

[JIRA] (OVIRT-802) ovirt-engine_master_upgrade-from-3.6_el7_merged failing

[eyal edri [Administrator] (oVirt JIRA)]

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

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

Looks like real error:

[ INFO  ] Configuring WebSocket Proxy
[ INFO  ] Creating/refreshing Engine 'internal' domain database schema
[ ERROR ] Failed to execute stage 'Misc configuration': Command 
'/sbin/semanage' failed to execute
[ INFO  ] Yum Performing yum transaction rollback
[ INFO  ] Rolling back database schema
[ INFO  ] Clearing Engine database engine


[~sbonazo...@redhat.com][~d...@redhat.com] are you familar with this error? 


> ovirt-engine_master_upgrade-from-3.6_el7_merged failing
> ---
>
> Key: OVIRT-802
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-802
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Greg Sheremeta
>Assignee: infra
>
> https://gerrit.ovirt.org/#/c/65899/2
> job:
> http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_merged/561/console
> failing.
> + which engine-setup
> + engine-cleanup
> --config-append=/home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_merged/jenkins/jobs/ovirt-engine_upgrade_to_master/cleanup.file.otopi
> [ INFO  ] Stage: Initializing
> [ INFO  ] Stage: Environment setup
>   Configuration files:
> ['/etc/ovirt-engine-setup.conf.d/10-packaging-jboss.conf',
> '/etc/ovirt-engine-setup.conf.d/10-packaging.conf',
> '/home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_merged/jenkins/jobs/ovirt-engine_upgrade_to_master/cleanup.file.otopi']
>   Log file:
> /var/log/ovirt-engine/setup/ovirt-engine-remove-20161031153445-zoq6gr.log
>   Version: otopi-1.6.0_master
> (otopi-1.6.0-0.0.master.20160829151522.git7547b87.el7.centos)
> [ ERROR ] Could not detect a completed product setup
>   Please use the cleanup utility only after a setup or after an
> upgrade from an older installation.
> [ ERROR ] Failed to execute stage 'Environment setup': Could not detect
> product setup
> [ INFO  ] Stage: Clean up
>   Log file is located at
> /var/log/ovirt-engine/setup/ovirt-engine-remove-20161031153445-zoq6gr.log
> [ INFO  ] Generating answer file
> '/var/lib/ovirt-engine/setup/answers/20161031153445-cleanup.conf'
> [ INFO  ] Stage: Pre-termination
> [ INFO  ] Stage: Termination
> [ ERROR ] Execution of cleanup failed
> -- 
> Greg Sheremeta, MBA
> Red Hat, Inc.
> Sr. Software Engineer
> gsher...@redhat.com



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

[JIRA] (OVIRT-802) ovirt-engine_master_upgrade-from-3.6_el7_merged failing

[Greg Sheremeta (oVirt JIRA)]

Greg Sheremeta created OVIRT-802:


 Summary: ovirt-engine_master_upgrade-from-3.6_el7_merged failing
 Key: OVIRT-802
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-802
 Project: oVirt - virtualization made easy
  Issue Type: By-EMAIL
Reporter: Greg Sheremeta
Assignee: infra


https://gerrit.ovirt.org/#/c/65899/2

job:
http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_merged/561/console

failing.


+ which engine-setup
+ engine-cleanup
--config-append=/home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_merged/jenkins/jobs/ovirt-engine_upgrade_to_master/cleanup.file.otopi
[ INFO  ] Stage: Initializing
[ INFO  ] Stage: Environment setup
  Configuration files:
['/etc/ovirt-engine-setup.conf.d/10-packaging-jboss.conf',
'/etc/ovirt-engine-setup.conf.d/10-packaging.conf',
'/home/jenkins/workspace/ovirt-engine_master_upgrade-from-3.6_el7_merged/jenkins/jobs/ovirt-engine_upgrade_to_master/cleanup.file.otopi']
  Log file:
/var/log/ovirt-engine/setup/ovirt-engine-remove-20161031153445-zoq6gr.log
  Version: otopi-1.6.0_master
(otopi-1.6.0-0.0.master.20160829151522.git7547b87.el7.centos)
[ ERROR ] Could not detect a completed product setup
  Please use the cleanup utility only after a setup or after an
upgrade from an older installation.
[ ERROR ] Failed to execute stage 'Environment setup': Could not detect
product setup
[ INFO  ] Stage: Clean up
  Log file is located at
/var/log/ovirt-engine/setup/ovirt-engine-remove-20161031153445-zoq6gr.log
[ INFO  ] Generating answer file
'/var/lib/ovirt-engine/setup/answers/20161031153445-cleanup.conf'
[ INFO  ] Stage: Pre-termination
[ INFO  ] Stage: Termination
[ ERROR ] Execution of cleanup failed

-- 
Greg Sheremeta, MBA
Red Hat, Inc.
Sr. Software Engineer
gsher...@redhat.com



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

[JIRA] (OVIRT-801) [gerrit hooks] enable check_bug_url for master branch

[Shlomo Ben David (oVirt JIRA)]

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

Shlomo Ben David reassigned OVIRT-801:
--

Assignee: Shlomo Ben David  (was: infra)

> [gerrit hooks] enable check_bug_url for master branch
> -
>
> Key: OVIRT-801
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-801
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>Reporter: Shlomo Ben David
>Assignee: Shlomo Ben David
>
> - Currently we are not checking bug urls for master branch.
> - We need to enable check_bug_url for master branch and set it to be optional 
> for 'master'
>   branch but mandatory for 'stable' branches.



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

[JIRA] (OVIRT-801) [gerrit hooks] enable check_bug_url for master branch

[Shlomo Ben David (oVirt JIRA)]

Shlomo Ben David created OVIRT-801:
--

 Summary: [gerrit hooks] enable check_bug_url for master branch
 Key: OVIRT-801
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-801
 Project: oVirt - virtualization made easy
  Issue Type: Task
Reporter: Shlomo Ben David
Assignee: infra


- Currently we are not checking bug urls for master branch.
- We need to enable check_bug_url for master branch and set it to be optional 
for 'master'
  branch but mandatory for 'stable' branches.



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

[JIRA] (OVIRT-801) [gerrit hooks] enable check_bug_url for master branch

[Shlomo Ben David (oVirt JIRA)]

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

Shlomo Ben David updated OVIRT-801:
---
Epic Link: OVIRT-403

> [gerrit hooks] enable check_bug_url for master branch
> -
>
> Key: OVIRT-801
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-801
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>Reporter: Shlomo Ben David
>Assignee: infra
>
> - Currently we are not checking bug urls for master branch.
> - We need to enable check_bug_url for master branch and set it to be optional 
> for 'master'
>   branch but mandatory for 'stable' branches.



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

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

[jenkins]

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

[JIRA] (OVIRT-800) Build oVirt 4.0.5 RC5

[sbonazzo (oVirt JIRA)]

sbonazzo created OVIRT-800:
--

 Summary: Build oVirt 4.0.5 RC5
 Key: OVIRT-800
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-800
 Project: oVirt - virtualization made easy
  Issue Type: Task
  Components: Repositories Mgmt
Reporter: sbonazzo
Assignee: infra
Priority: Highest






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

[JIRA] (OVIRT-800) Build oVirt 4.0.5 RC5

[sbonazzo (oVirt JIRA)]

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

sbonazzo updated OVIRT-800:
---
Epic Link: OVIRT-411

> Build oVirt 4.0.5 RC5
> -
>
> Key: OVIRT-800
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-800
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>  Components: Repositories Mgmt
>Reporter: sbonazzo
>Assignee: infra
>Priority: Highest
>




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

[JIRA] (OVIRT-800) Build oVirt 4.0.5 RC5

[sbonazzo (oVirt JIRA)]

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

sbonazzo reassigned OVIRT-800:
--

Assignee: lveyde  (was: infra)

> Build oVirt 4.0.5 RC5
> -
>
> Key: OVIRT-800
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-800
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>  Components: Repositories Mgmt
>Reporter: sbonazzo
>Assignee: lveyde
>Priority: Highest
>




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

Subject: oVirt 4.0.5 RC5 merge / branch / tag / bugzilla reminder

[Sandro Bonazzola]

All stable branch maintainers, please make sure to

   - merge all relevant open bugs until Wednesday morning 11:00 AM TLV time.


For each package that need to be built (i.e oVirt product) please make sure
every bug in MODIFIED has the right Target Release and Target Milestone.
A Target release should state the version of the package you're building
and should include the same version you used for the tag you just used for
this build. (e.g. for ovirt-engine, tag: ovirt-engine-4.0.5, tr: 4.0.5)
A list of bugs that require attention is here:

   -
   
https://bugzilla.redhat.com/buglist.cgi?quicksearch=target_milestone%3A4.0.5%20target_release%3A---%20status%3Amodified%2Cpost


-- 
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.ovirt.org/mailman/listinfo/infra

Re: Gerrit emails - Returned mail: see transcript for details

[Evgheni Dereveanchin]

Martin, this looks like a change in SPF enforcement
on Red Hat side as our Gerrit is effectively spoofing
sender emails. I've logged a JIRA ticket to get this
fixed by not using author's emails for Gerrit notifications:
https://ovirt-jira.atlassian.net/browse/OVIRT-799

Regards, 
Evgheni Dereveanchin 

- Original Message -
From: "Martin Sivak" 
To: "Eyal Edri" , "Anton Marchukov" , 
"infra" 
Sent: Monday, 31 October, 2016 2:28:17 PM
Subject: Gerrit emails - Returned mail: see transcript for details

Hi,

there might be something bad in our SPF config. Please check.

Martin

-- Forwarded message --
From: Mail Delivery Subsystem 
Date: Mon, Oct 31, 2016 at 2:05 PM
Subject: Returned mail: see transcript for details
To: msi...@redhat.com


The original message was received at Mon, 31 Oct 2016 09:05:24 -0400
from gerrit.ovirt.org [127.0.0.1]

   - The following addresses had permanent fatal errors -

(reason: 551 5.7.1 SPF fail: 'gerrit.ovirt.org'[107.22.212.69],
'redhat.com'; REJECT)

(reason: 551 5.7.1 SPF fail: 'gerrit.ovirt.org'[107.22.212.69],
'redhat.com'; REJECT)

(reason: 551 5.7.1 SPF fail: 'gerrit.ovirt.org'[107.22.212.69],
'redhat.com'; REJECT)

   - Transcript of session follows -
... while talking to mx1.redhat.com.:
>>> DATA
<<< 551 5.7.1 SPF fail: 'gerrit.ovirt.org'[107.22.212.69], 'redhat.com'; REJECT
550 5.1.1 ... User unknown
<<< 551 5.7.1 SPF fail: 'gerrit.ovirt.org'[107.22.212.69], 'redhat.com'; REJECT
550 5.1.1 ... User unknown
<<< 551 5.7.1 SPF fail: 'gerrit.ovirt.org'[107.22.212.69], 'redhat.com'; REJECT
550 5.1.1 ... User unknown
<<< 554 5.5.1 Error: no valid recipients

Final-Recipient: RFC822; lara...@redhat.com
Action: failed
Status: 5.7.1
Remote-MTA: DNS; mx1.redhat.com
Diagnostic-Code: SMTP; 551 5.7.1 SPF fail:
'gerrit.ovirt.org'[107.22.212.69], 'redhat.com'; REJECT
Last-Attempt-Date: Mon, 31 Oct 2016 09:05:25 -0400

Final-Recipient: RFC822; akrej...@redhat.com
Action: failed
Status: 5.7.1
Remote-MTA: DNS; mx1.redhat.com
Diagnostic-Code: SMTP; 551 5.7.1 SPF fail:
'gerrit.ovirt.org'[107.22.212.69], 'redhat.com'; REJECT
Last-Attempt-Date: Mon, 31 Oct 2016 09:05:25 -0400

Final-Recipient: RFC822; aha...@redhat.com
Action: failed
Status: 5.7.1
Remote-MTA: DNS; mx1.redhat.com
Diagnostic-Code: SMTP; 551 5.7.1 SPF fail:
'gerrit.ovirt.org'[107.22.212.69], 'redhat.com'; REJECT
Last-Attempt-Date: Mon, 31 Oct 2016 09:05:25 -0400


-- Forwarded message --
From: msi...@redhat.com
To: Arik Hadas 
Cc: Andrej Krejcir , Liron Aravot 
Date: Mon, 31 Oct 2016 09:05:24 -0400
Subject: Change in ovirt-engine[master]: core: Update OVF in storage
domains for HE VM edit
Hello Arik Hadas,

I'd like you to do a code review.  Please visit

https://gerrit.ovirt.org/65085

to review the following change.

Change subject: core: Update OVF in storage domains for HE VM edit
..

core: Update OVF in storage domains for HE VM edit

Updating hosted engine VM saves OVF to storage domain as well as
to the DB.

This patch is complementary to: https://gerrit.ovirt.org/#/c/51842

Change-Id: Ib02d41136458677399428c62c8e475b4cb2fcb79
Bug-Url: https://bugzilla.redhat.com/1372000
Signed-off-by: Andrej Krejcir 
---
M 
backend/manager/modules/bll/src/main/java/org/ovirt/engine/core/bll/UpdateVmCommand.java
M 
backend/manager/modules/bll/src/main/java/org/ovirt/engine/core/bll/storage/ovfstore/OvfDataUpdater.java
2 files changed, 22 insertions(+), 22 deletions(-)


  git pull ssh://gerrit.ovirt.org:29418/ovirt-engine refs/changes/85/65085/3

diff --git 
a/backend/manager/modules/bll/src/main/java/org/ovirt/engine/core/bll/UpdateVmCommand.java
b/backend/manager/modules/bll/src/main/java/org/ovirt/engine/core/bll/UpdateVmCommand.java
index 3c0bada..9c64003 100644
--- 
a/backend/manager/modules/bll/src/main/java/org/ovirt/engine/core/bll/UpdateVmCommand.java
+++ 
b/backend/manager/modules/bll/src/main/java/org/ovirt/engine/core/bll/UpdateVmCommand.java
@@ -22,6 +22,7 @@
 import org.ovirt.engine.core.bll.quota.QuotaConsumptionParameter;
 import org.ovirt.engine.core.bll.quota.QuotaSanityParameter;
 import org.ovirt.engine.core.bll.quota.QuotaVdsDependent;
+import org.ovirt.engine.core.bll.storage.ovfstore.OvfDataUpdater;
 import org.ovirt.engine.core.bll.utils.IconUtils;
 import org.ovirt.engine.core.bll.utils.PermissionSubject;
 import org.ovirt.engine.core.bll.validator.IconValidator;
@@ -37,7 +38,6 @@
 import org.ovirt.engine.core.common.action.LockProperties;
 import org.ovirt.engine.core.common.action.LockProperties.Scope;
 import org.ovirt.engine.core.common.action.PlugAction;
-import 

[JIRA] (OVIRT-799) Gerrit emails - Returned mail: see transcript for details

[Evgheni Dereveanchin (oVirt JIRA)]

Evgheni Dereveanchin created OVIRT-799:
--

 Summary: Gerrit emails - Returned mail: see transcript for details
 Key: OVIRT-799
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-799
 Project: oVirt - virtualization made easy
  Issue Type: Bug
Reporter: Evgheni Dereveanchin
Assignee: infra


Mails coming from Gerrit are rejected by Red Hat due to the change in SPF 
policy enforcement:

<<< 551 5.7.1 SPF fail: 'gerrit.ovirt.org'[107.22.212.69], 'redhat.com'; REJECT

This likely happens due to the fact that Gerrit uses the authors emails in the 
From: field which is likely to be marked as SPAM. We should use a sender 
address in the ovirt.org domain for all mail sent by Gerrit to avoid this.



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

[JIRA] (OVIRT-799) Gerrit emails - Returned mail: see transcript for details

[Evgheni Dereveanchin (oVirt JIRA)]

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

Evgheni Dereveanchin reassigned OVIRT-799:
--

Assignee: Shlomo Ben David  (was: infra)

> Gerrit emails - Returned mail: see transcript for details
> -
>
> Key: OVIRT-799
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-799
> Project: oVirt - virtualization made easy
>  Issue Type: Bug
>Reporter: Evgheni Dereveanchin
>Assignee: Shlomo Ben David
>
> Mails coming from Gerrit are rejected by Red Hat due to the change in SPF 
> policy enforcement:
> <<< 551 5.7.1 SPF fail: 'gerrit.ovirt.org'[107.22.212.69], 'redhat.com'; 
> REJECT
> This likely happens due to the fact that Gerrit uses the authors emails in 
> the From: field which is likely to be marked as SPAM. We should use a sender 
> address in the ovirt.org domain for all mail sent by Gerrit to avoid this.



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

Gerrit emails - Returned mail: see transcript for details

[Martin Sivak]

Hi,

there might be something bad in our SPF config. Please check.

Martin

-- Forwarded message --
From: Mail Delivery Subsystem 
Date: Mon, Oct 31, 2016 at 2:05 PM
Subject: Returned mail: see transcript for details
To: msi...@redhat.com


The original message was received at Mon, 31 Oct 2016 09:05:24 -0400
from gerrit.ovirt.org [127.0.0.1]

   - The following addresses had permanent fatal errors -

(reason: 551 5.7.1 SPF fail: 'gerrit.ovirt.org'[107.22.212.69],
'redhat.com'; REJECT)

(reason: 551 5.7.1 SPF fail: 'gerrit.ovirt.org'[107.22.212.69],
'redhat.com'; REJECT)

(reason: 551 5.7.1 SPF fail: 'gerrit.ovirt.org'[107.22.212.69],
'redhat.com'; REJECT)

   - Transcript of session follows -
... while talking to mx1.redhat.com.:
>>> DATA
<<< 551 5.7.1 SPF fail: 'gerrit.ovirt.org'[107.22.212.69], 'redhat.com'; REJECT
550 5.1.1 ... User unknown
<<< 551 5.7.1 SPF fail: 'gerrit.ovirt.org'[107.22.212.69], 'redhat.com'; REJECT
550 5.1.1 ... User unknown
<<< 551 5.7.1 SPF fail: 'gerrit.ovirt.org'[107.22.212.69], 'redhat.com'; REJECT
550 5.1.1 ... User unknown
<<< 554 5.5.1 Error: no valid recipients

Final-Recipient: RFC822; lara...@redhat.com
Action: failed
Status: 5.7.1
Remote-MTA: DNS; mx1.redhat.com
Diagnostic-Code: SMTP; 551 5.7.1 SPF fail:
'gerrit.ovirt.org'[107.22.212.69], 'redhat.com'; REJECT
Last-Attempt-Date: Mon, 31 Oct 2016 09:05:25 -0400

Final-Recipient: RFC822; akrej...@redhat.com
Action: failed
Status: 5.7.1
Remote-MTA: DNS; mx1.redhat.com
Diagnostic-Code: SMTP; 551 5.7.1 SPF fail:
'gerrit.ovirt.org'[107.22.212.69], 'redhat.com'; REJECT
Last-Attempt-Date: Mon, 31 Oct 2016 09:05:25 -0400

Final-Recipient: RFC822; aha...@redhat.com
Action: failed
Status: 5.7.1
Remote-MTA: DNS; mx1.redhat.com
Diagnostic-Code: SMTP; 551 5.7.1 SPF fail:
'gerrit.ovirt.org'[107.22.212.69], 'redhat.com'; REJECT
Last-Attempt-Date: Mon, 31 Oct 2016 09:05:25 -0400


-- Forwarded message --
From: msi...@redhat.com
To: Arik Hadas 
Cc: Andrej Krejcir , Liron Aravot 
Date: Mon, 31 Oct 2016 09:05:24 -0400
Subject: Change in ovirt-engine[master]: core: Update OVF in storage
domains for HE VM edit
Hello Arik Hadas,

I'd like you to do a code review.  Please visit

https://gerrit.ovirt.org/65085

to review the following change.

Change subject: core: Update OVF in storage domains for HE VM edit
..

core: Update OVF in storage domains for HE VM edit

Updating hosted engine VM saves OVF to storage domain as well as
to the DB.

This patch is complementary to: https://gerrit.ovirt.org/#/c/51842

Change-Id: Ib02d41136458677399428c62c8e475b4cb2fcb79
Bug-Url: https://bugzilla.redhat.com/1372000
Signed-off-by: Andrej Krejcir 
---
M 
backend/manager/modules/bll/src/main/java/org/ovirt/engine/core/bll/UpdateVmCommand.java
M 
backend/manager/modules/bll/src/main/java/org/ovirt/engine/core/bll/storage/ovfstore/OvfDataUpdater.java
2 files changed, 22 insertions(+), 22 deletions(-)


  git pull ssh://gerrit.ovirt.org:29418/ovirt-engine refs/changes/85/65085/3

diff --git 
a/backend/manager/modules/bll/src/main/java/org/ovirt/engine/core/bll/UpdateVmCommand.java
b/backend/manager/modules/bll/src/main/java/org/ovirt/engine/core/bll/UpdateVmCommand.java
index 3c0bada..9c64003 100644
--- 
a/backend/manager/modules/bll/src/main/java/org/ovirt/engine/core/bll/UpdateVmCommand.java
+++ 
b/backend/manager/modules/bll/src/main/java/org/ovirt/engine/core/bll/UpdateVmCommand.java
@@ -22,6 +22,7 @@
 import org.ovirt.engine.core.bll.quota.QuotaConsumptionParameter;
 import org.ovirt.engine.core.bll.quota.QuotaSanityParameter;
 import org.ovirt.engine.core.bll.quota.QuotaVdsDependent;
+import org.ovirt.engine.core.bll.storage.ovfstore.OvfDataUpdater;
 import org.ovirt.engine.core.bll.utils.IconUtils;
 import org.ovirt.engine.core.bll.utils.PermissionSubject;
 import org.ovirt.engine.core.bll.validator.IconValidator;
@@ -37,7 +38,6 @@
 import org.ovirt.engine.core.common.action.LockProperties;
 import org.ovirt.engine.core.common.action.LockProperties.Scope;
 import org.ovirt.engine.core.common.action.PlugAction;
-import 
org.ovirt.engine.core.common.action.ProcessOvfUpdateForStoragePoolParameters;
 import org.ovirt.engine.core.common.action.RngDeviceParameters;
 import org.ovirt.engine.core.common.action.UpdateVmVersionParameters;
 import org.ovirt.engine.core.common.action.VdcActionType;
@@ -178,7 +178,17 @@

 // Trigger OVF update for hosted engine VM only
 if (getVm().isHostedEngine()) {
-registerRollbackHandler(new HostedEngineEditNotifier(getVm()));
+registerRollbackHandler(new TransactionCompletionListener() {
+@Override
+

[JIRA] (OVIRT-776) Re: Build failed in Jenkins: ovirt_4.0_he-system-tests #402

[Evgheni Dereveanchin (oVirt JIRA)]

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

Evgheni Dereveanchin reassigned OVIRT-776:
--

Assignee: Evgheni Dereveanchin  (was: infra)

> Re: Build failed in Jenkins: ovirt_4.0_he-system-tests #402
> ---
>
> Key: OVIRT-776
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-776
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: sbonazzo
>Assignee: Evgheni Dereveanchin
>
> Looks like a network issue, scp fails with a timeout on a socket.
> Can you please have a look?
> On Mon, Oct 17, 2016 at 10:22 PM,  wrote:
> > See 
> >
> > Changes:
> >
> > [Gal Ben Haim] Fix check-patch to collect logs on failure
> >
> > --
> > [...truncated 1897 lines...]
> > ##  took 2809 seconds
> > ##  rc = 1
> > ##
> > ##! ERROR v
> > ##! Last 20 log enties: logs/mocker-fedora-23-x86_64.
> > fc23.he_basic_suite_4.0.sh/he_basic_suite_4.0.sh.log
> > ##!
> > + true
> > + env_cleanup
> > + echo '#'
> > #
> > + local res=0
> > + local uuid
> > + echo ' Cleaning up'
> >  Cleaning up
> > + [[ -e  > ovirt-system-tests/deployment-he_basic_suite_4.0> ]]
> > + echo '--- Cleaning with lago'
> > --- Cleaning with lago
> > + lago --workdir  > ovirt_4.0_he-system-tests/ws/ovirt-system-tests/deployment-
> > he_basic_suite_4.0> destroy --yes --all-prefixes
> > + echo '--- Cleaning with lago done'
> > --- Cleaning with lago done
> > + [[ 0 != \0 ]]
> > + echo ' Cleanup done'
> >  Cleanup done
> > + exit 0
> > Took 2642 seconds
> > ===
> > ##!
> > ##! ERROR ^^
> > ##!
> > ##
> > Build step 'Execute shell' marked build as failure
> > Performing Post build task...
> > Match found for :.* : True
> > Logical operation result is TRUE
> > Running script  : #!/bin/bash -xe
> > echo 'shell_scripts/system_tests.collect_logs.sh'
> >
> > #
> > # Required jjb vars:
> > #version
> > #
> > VERSION=4.0
> > SUITE_TYPE=
> >
> > WORKSPACE="$PWD"
> > OVIRT_SUITE="$SUITE_TYPE_suite_$VERSION"
> > TESTS_LOGS="$WORKSPACE/ovirt-system-tests/exported-artifacts"
> >
> > rm -rf "$WORKSPACE/exported-artifacts"
> > mkdir -p "$WORKSPACE/exported-artifacts"
> >
> > if [[ -d "$TESTS_LOGS" ]]; then
> > mv "$TESTS_LOGS/"* "$WORKSPACE/exported-artifacts/"
> > fi
> >
> > [ovirt_4.0_he-system-tests] $ /bin/bash -xe /tmp/
> > hudson4967817357021364058.sh
> > + echo shell_scripts/system_tests.collect_logs.sh
> > shell_scripts/system_tests.collect_logs.sh
> > + VERSION=4.0
> > + SUITE_TYPE=
> > + WORKSPACE=
> > + OVIRT_SUITE=4.0
> > + TESTS_LOGS= > system-tests/ws/ovirt-system-tests/exported-artifacts>
> > + rm -rf  > artifact/exported-artifacts>
> > + mkdir -p  > artifact/exported-artifacts>
> > + [[ -d  > ovirt-system-tests/exported-artifacts> ]]
> > + mv  > ovirt-system-tests/exported-artifacts/lago_logs> <
> > http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/
> > ovirt-system-tests/exported-artifacts/nosetests-002_bootstrap.py.xml> <
> > http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/
> > ovirt-system-tests/exported-artifacts/nosetests-004_basic_sanity.py.xml> <
> > http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/ws/
> > ovirt-system-tests/exported-artifacts/test_logs> <
> > http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/402/
> > artifact/exported-artifacts/>
> > POST BUILD TASK : SUCCESS
> > END OF POST BUILD TASK : 0
> > Match found for :.* : True
> > Logical operation result is TRUE
> > Running script  : #!/bin/bash -xe
> > echo "shell-scripts/mock_cleanup.sh"
> >
> > shopt -s nullglob
> >
> >
> > WORKSPACE="$PWD"
> >
> > # Make clear this is the cleanup, helps reading the jenkins logs
> > cat < > ___
> > ###
> > #

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

[jenkins]

See 

Changes:

[Yaniv Kaul] Separate log collector run test to its own test.

--
[...truncated 1268 lines...]
##  rc = 1
##
##! ERROR v
##! Last 20 log entries: 
logs/mocker-fedora-23-x86_64.fc23.he_basic_suite_3.6.sh/he_basic_suite_3.6.sh.log
##!
+ true
+ env_cleanup
+ echo '#'
#
+ local res=0
+ local uuid
+ echo ' Cleaning up'
 Cleaning up
+ [[ -e 

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

 destroy --yes --all-prefixes
+ echo '--- Cleaning with lago done'
--- Cleaning with lago done
+ [[ 0 != \0 ]]
+ echo ' Cleanup done'
 Cleanup done
+ exit 0
Took 1415 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=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/hudson5869173016131711975.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 -xe
echo "shell-scripts/mock_cleanup.sh"

shopt -s nullglob


WORKSPACE="$PWD"

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

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

[jenkins]

See 

Changes:

[Yaniv Kaul] Separate log collector run test to its own test.

--
[...truncated 959 lines...]
##  rc = 1
##
##! ERROR v
##! Last 20 log entries: 
logs/mocker-fedora-23-x86_64.fc23.he_basic_suite_4.0.sh/he_basic_suite_4.0.sh.log
##!
+ env_cleanup
+ echo '#'
#
+ local res=0
+ local uuid
+ echo ' Cleaning up'
 Cleaning up
+ [[ -e 

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

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

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

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

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

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

[ovirt_4.0_he-system-tests] $ /bin/bash -xe /tmp/hudson6779640553532406246.sh
+ echo shell_scripts/system_tests.collect_logs.sh
shell_scripts/system_tests.collect_logs.sh
+ VERSION=4.0
+ SUITE_TYPE=
+ WORKSPACE=
+ OVIRT_SUITE=4.0
+ 
TESTS_LOGS=
+ rm -rf 

+ mkdir -p 

+ [[ -d 

 ]]
+ mv 

 

 

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

shopt -s nullglob


WORKSPACE="$PWD"

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

[JIRA] (OVIRT-757) [VDSM] Add Travis CI to vdsm github project

[danken (oVirt JIRA)]

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

danken commented on OVIRT-757:
--


Thanks.

https://travis-ci.org/oVirt/vdsm/jobs/171955938 was triggered
automatically right after I've merged a patch to vdsm's gerrit.


> [VDSM] Add Travis CI to vdsm github project
> ---
>
> Key: OVIRT-757
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-757
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Nir Soffer
>Assignee: Barak Korren
>
> Hi all,
> Vdsm includes now a travis configuration running vdsm tests
> on both Fedora 24 and Centos 7.
> You can see example build shere:
> https://travis-ci.org/nirs/vdsm/builds/166263228
> These builds are currently configured in my private vdsm
> fork on github.
> We want to enable Travis CI service on vdsm github project,
> so each time a patch is merged (sync from gerrit) or each time
> a pull request is submitted, a build is started.
> Developers can use these builds in 2 ways:
> - fork vdsm and enable travis on their fork
> - submit pull requests to get them tested
> When a build fails, travis sends email to the author about the
> failure, this works fine for developers forks without any
> additional configuration.
> You can configure github for us, or give Dan and/or me the
> permissions to configure the github project.
> Cheers,
> Nir



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

Re: [JIRA] (OVIRT-757) [VDSM] Add Travis CI to vdsm github project

[Dan Kenigsberg]

On Mon, Oct 31, 2016 at 11:36:04AM +0200, Barak Korren (oVirt JIRA) wrote:
> 
> [ 
> https://ovirt-jira.atlassian.net/browse/OVIRT-757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=22135#comment-22135
>  ] 
> 
> Barak Korren commented on OVIRT-757:
> 
> 
> Enabled travis on vds repo:
> https://travis-ci.org/oVirt/vdsm
> 
> Please check if it works for you

Thanks.

https://travis-ci.org/oVirt/vdsm/jobs/171955938 was triggered
automatically right after I've merged a patch to vdsm's gerrit.

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

Re: SSL Server Test: www.ovirt.org (Powered by Qualys SSL Labs)

[Eyal Edri]

Adding OSAS.

On Mon, Oct 31, 2016 at 10:46 AM, Sandro Bonazzola 
wrote:

>
>
> On Mon, Oct 31, 2016 at 8:57 AM, Yaniv Kaul  wrote:
>
>> Someone tweeted about our incomplete certificate chain - see
>> https://www.ssllabs.com/ssltest/analyze.html?d=www.ovirt.org
>>
>
> looks like DigiCert SHA2 High Assurance Server CA  requires an extra
> download not being in default trust store.
> Doesn't look too bad to me but I'm not a PKI expert.
>
>
>
>>
>> ___
>> Infra mailing list
>> Infra@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/infra
>>
>>
>
>
> --
> Sandro Bonazzola
> Better technology. Faster innovation. Powered by community collaboration.
> See how it works at redhat.com
> 
>
> ___
> Infra mailing list
> Infra@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra
>
>


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

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

[JIRA] (OVIRT-761) Re: Do we or can we have Mac OS slaves in Jenkins?

[oVirt JIRA]

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

Juan Hernández commented on OVIRT-761:
--

CC [~omach...@redhat.com] Travis CI integration for the Python SDK is now 
enabled. For future releases it would be good to make sure that the build in 
Mac OS X works before actually releasing the new version.

> Re: Do we or can we have Mac OS slaves in Jenkins?
> --
>
> Key: OVIRT-761
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-761
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: sbonazzo
>Assignee: Barak Korren
>
> Opening a ticket.
> On Mon, Oct 10, 2016 at 11:44 AM, Juan Hernández 
> wrote:
> > Hello,
> >
> > Part of the Ruby SDK uses native code that needs to be compiled during
> > installation of the gem. The Ruby SDK is a requirement of ManageIQ, and
> > many ManageIQ developers/users use Mac OS. In the past I had some issues
> > with this environment, as the C compiler there behaves in an slightly
> > different way than GCC. Those issues were discovered only when the SDK
> > was already released. To avoid that I would like to have Jenkins jobs
> > building/testing the SDK for Mac OS. Is that possible? Do we have Mac OS
> > slaves? If not, can we have them?
> >
> > Regards,
> > Juan Hernandez
> >
> > --
> > Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta
> > 3ºD, 28016 Madrid, Spain
> > Inscrita en el Reg. Mercantil de Madrid – C.I.F. B82657941 - Red Hat S.L.
> > ___
> > Infra mailing list
> > Infra@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/infra
> >
> -- 
> Sandro Bonazzola
> Better technology. Faster innovation. Powered by community collaboration.
> See how it works at redhat.com
> 



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

[JIRA] (OVIRT-757) [VDSM] Add Travis CI to vdsm github project

[Barak Korren (oVirt JIRA)]

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

Barak Korren commented on OVIRT-757:


Enabled travis on vds repo:
https://travis-ci.org/oVirt/vdsm

Please check if it works for you

> [VDSM] Add Travis CI to vdsm github project
> ---
>
> Key: OVIRT-757
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-757
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Nir Soffer
>Assignee: Barak Korren
>
> Hi all,
> Vdsm includes now a travis configuration running vdsm tests
> on both Fedora 24 and Centos 7.
> You can see example build shere:
> https://travis-ci.org/nirs/vdsm/builds/166263228
> These builds are currently configured in my private vdsm
> fork on github.
> We want to enable Travis CI service on vdsm github project,
> so each time a patch is merged (sync from gerrit) or each time
> a pull request is submitted, a build is started.
> Developers can use these builds in 2 ways:
> - fork vdsm and enable travis on their fork
> - submit pull requests to get them tested
> When a build fails, travis sends email to the author about the
> failure, this works fine for developers forks without any
> additional configuration.
> You can configure github for us, or give Dan and/or me the
> permissions to configure the github project.
> Cheers,
> Nir



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

[JIRA] (OVIRT-798) outgoing mail failure - SPF fail

[eyal edri [Administrator] (oVirt JIRA)]

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

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

We already got a few reports on this, [~duck][~sbend...@redhat.com] can you 
have a look?

> outgoing mail failure - SPF fail
> 
>
> Key: OVIRT-798
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-798
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Yedidyah Bar David
>Assignee: infra
>
> Hi,
> When adding a reviewer to a patch on gerrit, I get an email:
> The original message was received at Mon, 31 Oct 2016 05:07:32 -0400
> from gerrit.ovirt.org [127.0.0.1]
>- The following addresses had permanent fatal errors -
> 
> (reason: 551 5.7.1 SPF fail: 'gerrit.ovirt.org'[107.22.212.69],
> 'redhat.com'; REJECT)
>- Transcript of session follows -
> ... while talking to mx1.redhat.com.:
> >>> DATA
> <<< 551 5.7.1 SPF fail: 'gerrit.ovirt.org'[107.22.212.69], 'redhat.com'; 
> REJECT
> 550 5.1.1 ... User unknown
> <<< 554 5.5.1 Error: no valid recipients
> Final-Recipient: RFC822; sbona...@redhat.com
> Action: failed
> Status: 5.7.1
> Remote-MTA: DNS; mx1.redhat.com
> Diagnostic-Code: SMTP; 551 5.7.1 SPF fail:
> 'gerrit.ovirt.org'[107.22.212.69], 'redhat.com'; REJECT
> Last-Attempt-Date: Mon, 31 Oct 2016 05:07:33 -0400
> Please check/handle. Thanks.
> -- 
> Didi



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

[JIRA] (OVIRT-798) outgoing mail failure - SPF fail

[Yedidyah Bar David (oVirt JIRA)]

Yedidyah Bar David created OVIRT-798:


 Summary: outgoing mail failure - SPF fail
 Key: OVIRT-798
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-798
 Project: oVirt - virtualization made easy
  Issue Type: By-EMAIL
Reporter: Yedidyah Bar David
Assignee: infra


Hi,

When adding a reviewer to a patch on gerrit, I get an email:

The original message was received at Mon, 31 Oct 2016 05:07:32 -0400
from gerrit.ovirt.org [127.0.0.1]

   - The following addresses had permanent fatal errors -

(reason: 551 5.7.1 SPF fail: 'gerrit.ovirt.org'[107.22.212.69],
'redhat.com'; REJECT)

   - Transcript of session follows -
... while talking to mx1.redhat.com.:
>>> DATA
<<< 551 5.7.1 SPF fail: 'gerrit.ovirt.org'[107.22.212.69], 'redhat.com'; REJECT
550 5.1.1 ... User unknown
<<< 554 5.5.1 Error: no valid recipients

Final-Recipient: RFC822; sbona...@redhat.com
Action: failed
Status: 5.7.1
Remote-MTA: DNS; mx1.redhat.com
Diagnostic-Code: SMTP; 551 5.7.1 SPF fail:
'gerrit.ovirt.org'[107.22.212.69], 'redhat.com'; REJECT
Last-Attempt-Date: Mon, 31 Oct 2016 05:07:33 -0400

Please check/handle. Thanks.
-- 
Didi



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

[JIRA] (OVIRT-757) [VDSM] Add Travis CI to vdsm github project

[Barak Korren (oVirt JIRA)]

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

Barak Korren updated OVIRT-757:
---
Status: In Progress  (was: To Do)

> [VDSM] Add Travis CI to vdsm github project
> ---
>
> Key: OVIRT-757
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-757
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Nir Soffer
>Assignee: Barak Korren
>
> Hi all,
> Vdsm includes now a travis configuration running vdsm tests
> on both Fedora 24 and Centos 7.
> You can see example build shere:
> https://travis-ci.org/nirs/vdsm/builds/166263228
> These builds are currently configured in my private vdsm
> fork on github.
> We want to enable Travis CI service on vdsm github project,
> so each time a patch is merged (sync from gerrit) or each time
> a pull request is submitted, a build is started.
> Developers can use these builds in 2 ways:
> - fork vdsm and enable travis on their fork
> - submit pull requests to get them tested
> When a build fails, travis sends email to the author about the
> failure, this works fine for developers forks without any
> additional configuration.
> You can configure github for us, or give Dan and/or me the
> permissions to configure the github project.
> Cheers,
> Nir



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

[JIRA] (OVIRT-757) [VDSM] Add Travis CI to vdsm github project

[Barak Korren (oVirt JIRA)]

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

Barak Korren reassigned OVIRT-757:
--

Assignee: Barak Korren  (was: infra)

> [VDSM] Add Travis CI to vdsm github project
> ---
>
> Key: OVIRT-757
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-757
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Nir Soffer
>Assignee: Barak Korren
>
> Hi all,
> Vdsm includes now a travis configuration running vdsm tests
> on both Fedora 24 and Centos 7.
> You can see example build shere:
> https://travis-ci.org/nirs/vdsm/builds/166263228
> These builds are currently configured in my private vdsm
> fork on github.
> We want to enable Travis CI service on vdsm github project,
> so each time a patch is merged (sync from gerrit) or each time
> a pull request is submitted, a build is started.
> Developers can use these builds in 2 ways:
> - fork vdsm and enable travis on their fork
> - submit pull requests to get them tested
> When a build fails, travis sends email to the author about the
> failure, this works fine for developers forks without any
> additional configuration.
> You can configure github for us, or give Dan and/or me the
> permissions to configure the github project.
> Cheers,
> Nir



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

[JIRA] (OVIRT-790) 732846953375 infra-support

[eyal edri [Administrator] (oVirt JIRA)]

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

eyal edri [Administrator] deleted OVIRT-790:



> 732846953375 infra-support
> --
>
> Key: OVIRT-790
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-790
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: m@lycos.com
>Assignee: infra
>




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

[JIRA] (OVIRT-761) Re: Do we or can we have Mac OS slaves in Jenkins?

[oVirt JIRA]

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

Juan Hernández commented on OVIRT-761:
--

Thank you very much Barak. I agree, lets test Travis for a while before making 
any other change.

> Re: Do we or can we have Mac OS slaves in Jenkins?
> --
>
> Key: OVIRT-761
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-761
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: sbonazzo
>Assignee: Barak Korren
>
> Opening a ticket.
> On Mon, Oct 10, 2016 at 11:44 AM, Juan Hernández 
> wrote:
> > Hello,
> >
> > Part of the Ruby SDK uses native code that needs to be compiled during
> > installation of the gem. The Ruby SDK is a requirement of ManageIQ, and
> > many ManageIQ developers/users use Mac OS. In the past I had some issues
> > with this environment, as the C compiler there behaves in an slightly
> > different way than GCC. Those issues were discovered only when the SDK
> > was already released. To avoid that I would like to have Jenkins jobs
> > building/testing the SDK for Mac OS. Is that possible? Do we have Mac OS
> > slaves? If not, can we have them?
> >
> > Regards,
> > Juan Hernandez
> >
> > --
> > Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta
> > 3ºD, 28016 Madrid, Spain
> > Inscrita en el Reg. Mercantil de Madrid – C.I.F. B82657941 - Red Hat S.L.
> > ___
> > Infra mailing list
> > Infra@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/infra
> >
> -- 
> Sandro Bonazzola
> Better technology. Faster innovation. Powered by community collaboration.
> See how it works at redhat.com
> 



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

[JIRA] (OVIRT-761) Re: Do we or can we have Mac OS slaves in Jenkins?

[Barak Korren (oVirt JIRA)]

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

Barak Korren updated OVIRT-761:
---
Status: In Progress  (was: To Do)

> Re: Do we or can we have Mac OS slaves in Jenkins?
> --
>
> Key: OVIRT-761
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-761
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: sbonazzo
>Assignee: Barak Korren
>
> Opening a ticket.
> On Mon, Oct 10, 2016 at 11:44 AM, Juan Hernández 
> wrote:
> > Hello,
> >
> > Part of the Ruby SDK uses native code that needs to be compiled during
> > installation of the gem. The Ruby SDK is a requirement of ManageIQ, and
> > many ManageIQ developers/users use Mac OS. In the past I had some issues
> > with this environment, as the C compiler there behaves in an slightly
> > different way than GCC. Those issues were discovered only when the SDK
> > was already released. To avoid that I would like to have Jenkins jobs
> > building/testing the SDK for Mac OS. Is that possible? Do we have Mac OS
> > slaves? If not, can we have them?
> >
> > Regards,
> > Juan Hernandez
> >
> > --
> > Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta
> > 3ºD, 28016 Madrid, Spain
> > Inscrita en el Reg. Mercantil de Madrid – C.I.F. B82657941 - Red Hat S.L.
> > ___
> > Infra mailing list
> > Infra@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/infra
> >
> -- 
> Sandro Bonazzola
> Better technology. Faster innovation. Powered by community collaboration.
> See how it works at redhat.com
> 



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

[JIRA] (OVIRT-761) Re: Do we or can we have Mac OS slaves in Jenkins?

[Barak Korren (oVirt JIRA)]

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

Barak Korren commented on OVIRT-761:


I've enabled Python and Ruby SDKs in Travis:

https://travis-ci.org/oVirt/ovirt-engine-sdk-ruby
https://travis-ci.org/oVirt/ovirt-engine-sdk

To have a Mac OS X slave we'll need buy/have it donated, Lets see of travis is 
good enough for now.
It should be possible to run Standard-CI scripts from travis to avoid some code 
duplication.

> Re: Do we or can we have Mac OS slaves in Jenkins?
> --
>
> Key: OVIRT-761
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-761
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: sbonazzo
>Assignee: Barak Korren
>
> Opening a ticket.
> On Mon, Oct 10, 2016 at 11:44 AM, Juan Hernández 
> wrote:
> > Hello,
> >
> > Part of the Ruby SDK uses native code that needs to be compiled during
> > installation of the gem. The Ruby SDK is a requirement of ManageIQ, and
> > many ManageIQ developers/users use Mac OS. In the past I had some issues
> > with this environment, as the C compiler there behaves in an slightly
> > different way than GCC. Those issues were discovered only when the SDK
> > was already released. To avoid that I would like to have Jenkins jobs
> > building/testing the SDK for Mac OS. Is that possible? Do we have Mac OS
> > slaves? If not, can we have them?
> >
> > Regards,
> > Juan Hernandez
> >
> > --
> > Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta
> > 3ºD, 28016 Madrid, Spain
> > Inscrita en el Reg. Mercantil de Madrid – C.I.F. B82657941 - Red Hat S.L.
> > ___
> > Infra mailing list
> > Infra@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/infra
> >
> -- 
> Sandro Bonazzola
> Better technology. Faster innovation. Powered by community collaboration.
> See how it works at redhat.com
> 



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

[JIRA] (OVIRT-761) Re: Do we or can we have Mac OS slaves in Jenkins?

[Barak Korren (oVirt JIRA)]

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

Barak Korren reassigned OVIRT-761:
--

Assignee: Barak Korren  (was: infra)

> Re: Do we or can we have Mac OS slaves in Jenkins?
> --
>
> Key: OVIRT-761
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-761
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: sbonazzo
>Assignee: Barak Korren
>
> Opening a ticket.
> On Mon, Oct 10, 2016 at 11:44 AM, Juan Hernández 
> wrote:
> > Hello,
> >
> > Part of the Ruby SDK uses native code that needs to be compiled during
> > installation of the gem. The Ruby SDK is a requirement of ManageIQ, and
> > many ManageIQ developers/users use Mac OS. In the past I had some issues
> > with this environment, as the C compiler there behaves in an slightly
> > different way than GCC. Those issues were discovered only when the SDK
> > was already released. To avoid that I would like to have Jenkins jobs
> > building/testing the SDK for Mac OS. Is that possible? Do we have Mac OS
> > slaves? If not, can we have them?
> >
> > Regards,
> > Juan Hernandez
> >
> > --
> > Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta
> > 3ºD, 28016 Madrid, Spain
> > Inscrita en el Reg. Mercantil de Madrid – C.I.F. B82657941 - Red Hat S.L.
> > ___
> > Infra mailing list
> > Infra@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/infra
> >
> -- 
> Sandro Bonazzola
> Better technology. Faster innovation. Powered by community collaboration.
> See how it works at redhat.com
> 



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

Re: SSL Server Test: www.ovirt.org (Powered by Qualys SSL Labs)

[Sandro Bonazzola]

On Mon, Oct 31, 2016 at 8:57 AM, Yaniv Kaul  wrote:

> Someone tweeted about our incomplete certificate chain - see
> https://www.ssllabs.com/ssltest/analyze.html?d=www.ovirt.org
>

looks like DigiCert SHA2 High Assurance Server CA  requires an extra
download not being in default trust store.
Doesn't look too bad to me but I'm not a PKI expert.



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


-- 
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com

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

[JIRA] (OVIRT-761) Re: Do we or can we have Mac OS slaves in Jenkins?

[oVirt JIRA]

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

Juan Hernández commented on OVIRT-761:
--

Not sure what permissions are needed exactly, but I think that those that have 
"admin" access to the "oVirt" organization can just go to travis-ci.org and 
enable/disable the projects, it is just a matter of flipping a switch. I'd 
appreciate someone with that access can do it for the Python and Ruby SDKs, as 
we had already more than one situation where Mac OS X users complained about 
build failures.

I also suggest to reconsider adding support for Mac OS X to Jenkins. I know 
that it isn't possible to have a Mac OS X VM, but maybe we could have at least 
one bare metal Mac OS X slave.

> Re: Do we or can we have Mac OS slaves in Jenkins?
> --
>
> Key: OVIRT-761
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-761
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: sbonazzo
>Assignee: infra
>
> Opening a ticket.
> On Mon, Oct 10, 2016 at 11:44 AM, Juan Hernández 
> wrote:
> > Hello,
> >
> > Part of the Ruby SDK uses native code that needs to be compiled during
> > installation of the gem. The Ruby SDK is a requirement of ManageIQ, and
> > many ManageIQ developers/users use Mac OS. In the past I had some issues
> > with this environment, as the C compiler there behaves in an slightly
> > different way than GCC. Those issues were discovered only when the SDK
> > was already released. To avoid that I would like to have Jenkins jobs
> > building/testing the SDK for Mac OS. Is that possible? Do we have Mac OS
> > slaves? If not, can we have them?
> >
> > Regards,
> > Juan Hernandez
> >
> > --
> > Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta
> > 3ºD, 28016 Madrid, Spain
> > Inscrita en el Reg. Mercantil de Madrid – C.I.F. B82657941 - Red Hat S.L.
> > ___
> > Infra mailing list
> > Infra@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/infra
> >
> -- 
> Sandro Bonazzola
> Better technology. Faster innovation. Powered by community collaboration.
> See how it works at redhat.com
> 



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

[JIRA] (OVIRT-753) ovirt-appliance_master_build-artifacts-el7-x86_64 is ignoring failed commands

[eyal edri [Administrator] (oVirt JIRA)]

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

eyal edri [Administrator] updated OVIRT-753:

Blocked By: pending response from node team
Status: Blocked  (was: To Do)

Should be handled by node team, as the code is in the appliance repo.

> ovirt-appliance_master_build-artifacts-el7-x86_64 is ignoring failed commands
> -
>
> Key: OVIRT-753
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-753
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: sbonazzo
>Assignee: infra
>
> In:
> http://jenkins.ovirt.org/job/ovirt-appliance_master_build-artifacts-el7-x86_64/196/console
> After appliance shutdown:
> *00:15:44.383* [[ -n "1" ]] && [[ "$(virt-sparsify --help)" =~
> --in-place ]] && ( virt-sparsify --in-place
> ovirt-engine-appliance.qcow2 ; ln ovirt-engine-appliance.qcow2
> ovirt-engine-appliance.qcow2.sparse ; )*00:25:53.734* virt-sparsify:
> error: libguestfs error: guestfs_launch failed.*00:25:53.735* This
> usually means the libguestfs appliance failed to start or
> crashed.*00:25:53.735* See
> http://libguestfs.org/guestfs-faq.1.html#debugging-libguestfs*00:25:53.735*
> or run 'libguestfs-test-tool' and post the *complete* output into
> a*00:25:53.735* bug report or message to the libguestfs mailing list.
> The job should have failed here. Instead, the job continues and fails in a
> later stage:
> *00:33:01.284* ls -shal ovirt-engine-appliance.ova*00:33:01.287* 1.4G
> -rwxr-xr-x. 1 root root 1.4G Oct  6 14:13
> ovirt-engine-appliance.ova*00:33:01.288* echo "all" appliance
> done*00:33:01.290* all appliance done*00:33:01.291* + make
> check*00:33:01.299* make -f image-tools/build.mk
> ovirt-engine-appliance-manifest-rpm*00:33:01.305* make[1]: Entering
> directory 
> `/home/jenkins/workspace/ovirt-appliance_master_build-artifacts-el7-x86_64/ovirt-appliance/engine-appliance'*00:33:01.305*
> guestfish --ro -i -a ovirt-engine-appliance.qcow2 sh 'rpm -qa | sort
> -u' > ovirt-engine-appliance-manifest-rpm*00:41:58.044* libguestfs:
> error: appliance closed the connection unexpectedly.*00:41:58.044*
> This usually means the libguestfs appliance crashed.*00:41:58.044* See
> http://libguestfs.org/guestfs-faq.1.html#debugging-libguestfs*00:41:58.045*
> for information about how to debug libguestfs and report
> bugs.*00:41:58.045* libguestfs: error: guestfs_launch
> failed.*00:41:58.045* This usually means the libguestfs appliance
> failed to start or crashed.*00:41:58.045* See
> http://libguestfs.org/guestfs-faq.1.html#debugging-libguestfs*00:41:58.046*
> or run 'libguestfs-test-tool' and post the *complete* output into
> a*00:41:58.046* bug report or message to the libguestfs mailing
> list.*00:41:58.059* make[1]: *** [ovirt-engine-appliance-manifest-rpm]
> Error 1*00:41:58.059* make[1]: Leaving directory
> `/home/jenkins/workspace/ovirt-appliance_master_build-artifacts-el7-x86_64/ovirt-appliance/engine-appliance'*00:41:58.060*
> make: *** [ovirt-engine-appliance-manifest-rpm] Error 2*00:41:58.065*
> Took 2325 seconds
> wasting 20 minutes of jenkins slave time testing something already known
> broken.
> While working on fixing this job, please investigate while it's failing and
> open a separate issue or bugzilla for it.
> -- 
> 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.482.3#100017)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-753) ovirt-appliance_master_build-artifacts-el7-x86_64 is ignoring failed commands

[eyal edri [Administrator] (oVirt JIRA)]

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

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

[~fdeutsch] I'm guessing Tolik wrote this job? can anyone from the node team 
have a look and fail early on the code?

> ovirt-appliance_master_build-artifacts-el7-x86_64 is ignoring failed commands
> -
>
> Key: OVIRT-753
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-753
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: sbonazzo
>Assignee: infra
>
> In:
> http://jenkins.ovirt.org/job/ovirt-appliance_master_build-artifacts-el7-x86_64/196/console
> After appliance shutdown:
> *00:15:44.383* [[ -n "1" ]] && [[ "$(virt-sparsify --help)" =~
> --in-place ]] && ( virt-sparsify --in-place
> ovirt-engine-appliance.qcow2 ; ln ovirt-engine-appliance.qcow2
> ovirt-engine-appliance.qcow2.sparse ; )*00:25:53.734* virt-sparsify:
> error: libguestfs error: guestfs_launch failed.*00:25:53.735* This
> usually means the libguestfs appliance failed to start or
> crashed.*00:25:53.735* See
> http://libguestfs.org/guestfs-faq.1.html#debugging-libguestfs*00:25:53.735*
> or run 'libguestfs-test-tool' and post the *complete* output into
> a*00:25:53.735* bug report or message to the libguestfs mailing list.
> The job should have failed here. Instead, the job continues and fails in a
> later stage:
> *00:33:01.284* ls -shal ovirt-engine-appliance.ova*00:33:01.287* 1.4G
> -rwxr-xr-x. 1 root root 1.4G Oct  6 14:13
> ovirt-engine-appliance.ova*00:33:01.288* echo "all" appliance
> done*00:33:01.290* all appliance done*00:33:01.291* + make
> check*00:33:01.299* make -f image-tools/build.mk
> ovirt-engine-appliance-manifest-rpm*00:33:01.305* make[1]: Entering
> directory 
> `/home/jenkins/workspace/ovirt-appliance_master_build-artifacts-el7-x86_64/ovirt-appliance/engine-appliance'*00:33:01.305*
> guestfish --ro -i -a ovirt-engine-appliance.qcow2 sh 'rpm -qa | sort
> -u' > ovirt-engine-appliance-manifest-rpm*00:41:58.044* libguestfs:
> error: appliance closed the connection unexpectedly.*00:41:58.044*
> This usually means the libguestfs appliance crashed.*00:41:58.044* See
> http://libguestfs.org/guestfs-faq.1.html#debugging-libguestfs*00:41:58.045*
> for information about how to debug libguestfs and report
> bugs.*00:41:58.045* libguestfs: error: guestfs_launch
> failed.*00:41:58.045* This usually means the libguestfs appliance
> failed to start or crashed.*00:41:58.045* See
> http://libguestfs.org/guestfs-faq.1.html#debugging-libguestfs*00:41:58.046*
> or run 'libguestfs-test-tool' and post the *complete* output into
> a*00:41:58.046* bug report or message to the libguestfs mailing
> list.*00:41:58.059* make[1]: *** [ovirt-engine-appliance-manifest-rpm]
> Error 1*00:41:58.059* make[1]: Leaving directory
> `/home/jenkins/workspace/ovirt-appliance_master_build-artifacts-el7-x86_64/ovirt-appliance/engine-appliance'*00:41:58.060*
> make: *** [ovirt-engine-appliance-manifest-rpm] Error 2*00:41:58.065*
> Took 2325 seconds
> wasting 20 minutes of jenkins slave time testing something already known
> broken.
> While working on fixing this job, please investigate while it's failing and
> open a separate issue or bugzilla for it.
> -- 
> 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.482.3#100017)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-750) Issues with mvn central syncrhronization

[eyal edri [Administrator] (oVirt JIRA)]

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

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

does it still happen?

> Issues with mvn central syncrhronization
> 
>
> Key: OVIRT-750
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-750
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Piotr Kliczewski
>Assignee: infra
>
> When I release new version of jsonrpc and update the engine to use it the
> build fails and it is required to manually perform refresh of artifactory
> cache.



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

[JIRA] (OVIRT-751) Persistent maven caches on the mock slaves

[eyal edri [Administrator] (oVirt JIRA)]

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

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

I think we should give it a try for ovirt-engine and be proactive on this, 
since it also serve us as it will reduce load on network and jenkins server and 
also reduce feedback time to check-patch jobs. 
If its a simple patch, lets just send it and check it out, shouldn't take too 
much time. 

> Persistent maven caches on the mock slaves
> --
>
> Key: OVIRT-751
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-751
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>Reporter: Anton Marchukov
>Assignee: infra
>
> I think we need to design a way to retain maven caches on the mocked jenkins 
> slaves. Currently it is stored inside the mock and thus maven downloads 
> packages from artifactory server each time. 
> However there is really no reason for that. Maven artifacts are designed to 
> be immutable so once artifact is in the repo there is no trivial way to 
> change it without creating a new version. In fact it should never be needed 
> and the correct solution for that is to always create a new version.
> SNAPSHOOT artifacts are in fact timestamped and each one have different file 
> name. It is just not visible since maven automatically takes the latest one. 
> But it is not related to caching as the new snapshoot will be a new artifact 
> still.
> So based on that point there is no reason to purge maven cache each time, but 
> there are reasons why not to purge. Not purging them will reduce the build 
> times of all java jobs and also reduce the network traffic we have. 



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

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

[jenkins]

See 

Changes:

[Gal Ben Haim] Changed the mock scripts to support the new naming convention

--
[...truncated 1253 lines...]
##  rc = 1
##
##! ERROR v
##! Last 20 log entries: 
logs/mocker-fedora-23-x86_64.fc23.he_basic_suite_3.6.sh/he_basic_suite_3.6.sh.log
##!
+ true
+ env_cleanup
+ echo '#'
#
+ local res=0
+ local uuid
+ echo ' Cleaning up'
 Cleaning up
+ [[ -e 

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

 destroy --yes --all-prefixes
+ echo '--- Cleaning with lago done'
--- Cleaning with lago done
+ [[ 0 != \0 ]]
+ echo ' Cleanup done'
 Cleanup done
+ exit 0
Took 1332 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=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/hudson2089173143272239733.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 -xe
echo "shell-scripts/mock_cleanup.sh"

shopt -s nullglob


WORKSPACE="$PWD"

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

[JIRA] (OVIRT-752) Fwd: export ovirt-engine-dashboard gerrit repo to github?

[eyal edri [Administrator] (oVirt JIRA)]

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

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

Assignee: Evgheni Dereveanchin  (was: infra)

Evgheni, can you have a look at this?
I think we documented the procedure on how do to do it here:
http://infra-docs.readthedocs.io/en/latest/General/Creating_Gerrit_Projects.html#creating-the-github-repository

> Fwd: export ovirt-engine-dashboard gerrit repo to github?
> -
>
> Key: OVIRT-752
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-752
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: sbonazzo
>Assignee: Evgheni Dereveanchin
>
> Opening a ticket. Looks like we're missing backup on github for
> ovirt-dashboard.
> -- Forwarded message --
> From: Scott Dickerson 
> Date: Thu, Oct 6, 2016 at 5:53 PM
> Subject: export ovirt-engine-dashboard gerrit repo to github?
> To: infra@ovirt.org
> Hi,
> What do we need to do in order to get the ovirt-engine-dashboard gerrit
> repo [1] mirrored/exported out to oVirt's github [2] in the same way
> ovirt-engine does?
> [1] - https://gerrit.ovirt.org/gitweb?p=ovirt-engine-dashboard.git;a=summary
> [2] - https://github.com/oVirt
> Thanks,
> Scott
> -- 
> Scott Dickerson
> Senior Software Engineer
> RHEV-M Engineering - UX Team
> Red Hat, Inc
> ___
> Infra mailing list
> Infra@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra
> -- 
> Sandro Bonazzola
> Better technology. Faster innovation. Powered by community collaboration.
> See how it works at redhat.com
> 



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

[JIRA] (OVIRT-760) Gerrit hooks for ovirt-imageio project

[eyal edri [Administrator] (oVirt JIRA)]

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

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

Assignee: Shlomo Ben David  (was: infra)

Shlomi, can you please add all the bug status changing hooks to this project?

> Gerrit hooks for ovirt-imageio project
> --
>
> Key: OVIRT-760
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-760
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: sbonazzo
>Assignee: Shlomo Ben David
>
> Hi,can you please add gerrit hooks to ovirt-imageio project?
> 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.482.3#100017)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-766) Code Review - Error invalid author

[eyal edri [Administrator] (oVirt JIRA)]

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

eyal edri [Administrator] updated OVIRT-766:

Resolution: Fixed
Status: Done  (was: Blocked)

> Code Review - Error invalid author
> --
>
> Key: OVIRT-766
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-766
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: sbonazzo
>Assignee: infra
>
> While editing a commit message or a file from gerrit I get:
> Code Review - Error invalid author
> when I save and publish the change.
> Can you please fix it?
> -- 
> 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.482.3#100017)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

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

[jenkins]

See 

Changes:

[Gal Ben Haim] Changed the mock scripts to support the new naming convention

--
[...truncated 959 lines...]
##  rc = 1
##
##! ERROR v
##! Last 20 log entries: 
logs/mocker-fedora-23-x86_64.fc23.he_basic_suite_4.0.sh/he_basic_suite_4.0.sh.log
##!
+ env_cleanup
+ echo '#'
#
+ local res=0
+ local uuid
+ echo ' Cleaning up'
 Cleaning up
+ [[ -e 

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

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

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

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

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

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

[ovirt_4.0_he-system-tests] $ /bin/bash -xe /tmp/hudson6851193448988362491.sh
+ echo shell_scripts/system_tests.collect_logs.sh
shell_scripts/system_tests.collect_logs.sh
+ VERSION=4.0
+ SUITE_TYPE=
+ WORKSPACE=
+ OVIRT_SUITE=4.0
+ 
TESTS_LOGS=
+ rm -rf 

+ mkdir -p 

+ [[ -d 

 ]]
+ mv 

 

 

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

shopt -s nullglob


WORKSPACE="$PWD"

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

SSL Server Test: www.ovirt.org (Powered by Qualys SSL Labs)

[Yaniv Kaul]

Someone tweeted about our incomplete certificate chain - see
https://www.ssllabs.com/ssltest/analyze.html?d=www.ovirt.org
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-766) Code Review - Error invalid author

[sbonazzo (oVirt JIRA)]

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

sbonazzo commented on OVIRT-766:


[~eedri] yes it was solved, thanks.

> Code Review - Error invalid author
> --
>
> Key: OVIRT-766
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-766
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: sbonazzo
>Assignee: infra
>
> While editing a commit message or a file from gerrit I get:
> Code Review - Error invalid author
> when I save and publish the change.
> Can you please fix it?
> -- 
> 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.482.3#100017)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-760) Gerrit hooks for ovirt-imageio project

[sbonazzo (oVirt JIRA)]

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

sbonazzo commented on OVIRT-760:


> Can you please specify which hooks do you want enabled?

those updating bugzilla status

> Gerrit hooks for ovirt-imageio project
> --
>
> Key: OVIRT-760
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-760
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: sbonazzo
>Assignee: infra
>
> Hi,can you please add gerrit hooks to ovirt-imageio project?
> 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.482.3#100017)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra