- Infra - oVirt List Archives

[oVirt Jenkins] test-repo_ovirt_experimental_4.1 - Build #137 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 05 Jan '17

05 Jan '17

------=_Part_114_1200791132.1483624417005 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.1/137/, Build Number: 137, Build Status: FAILURE ------=_Part_114_1200791132.1483624417005--

1 1

[oVirt Jenkins] test-repo_ovirt_experimental_4.1 - Build #132 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 05 Jan '17

05 Jan '17

------=_Part_108_650058888.1483612637724 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.1/132/, Build Number: 132, Build Status: FAILURE ------=_Part_108_650058888.1483612637724--

1 1

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #4587 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 05 Jan '17

05 Jan '17

------=_Part_104_490884013.1483591907507 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/4587/, Build Number: 4587, Build Status: FAILURE ------=_Part_104_490884013.1483591907507--

1 1

[JIRA] (OVIRT-1007) repo closure job should find also optional pkg
by eyal edri [Administrator] (oVirt JIRA) 05 Jan '17

05 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1007?page=com.atlassian.jira.… ] eyal edri [Administrator] commented on OVIRT-1007: -------------------------------------------------- The job should: 1. monitoring experimental reops ( right now it checks only snapshot ) 2. detect any missing rpms that are also optional ( maybe compare to stable version? ) > repo closure job should find also optional pkg > ---------------------------------------------- > > Key: OVIRT-1007 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1007 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: eyal edri [Administrator] > Assignee: infra > Priority: Highest > > http://jenkins.ovirt.org/job/repos_4.1_check-closure_el7_merged/38/console -- This message was sent by Atlassian JIRA (v1000.656.2#100024)

1 0

[JIRA] (OVIRT-1007) repo closure job should find also optional pkg
by eyal edri [Administrator] (oVirt JIRA) 05 Jan '17

05 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1007?page=com.atlassian.jira.… ] eyal edri [Administrator] updated OVIRT-1007: --------------------------------------------- Summary: repo closure job should find also optional pkg (was: repo closure jobs failed to find missing pkg on experimental 4.1) > repo closure job should find also optional pkg > ---------------------------------------------- > > Key: OVIRT-1007 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1007 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: eyal edri [Administrator] > Assignee: infra > Priority: Highest > > http://jenkins.ovirt.org/job/repos_4.1_check-closure_el7_merged/38/console -- This message was sent by Atlassian JIRA (v1000.656.2#100024)

1 0

[JIRA] (OVIRT-1007) repo closure jobs failed to find missing pkg on experimental 4.1
by eyal edri [Administrator] (oVirt JIRA) 05 Jan '17

05 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1007?page=com.atlassian.jira.… ] eyal edri [Administrator] updated OVIRT-1007: --------------------------------------------- Epic Link: OVIRT-400 > repo closure jobs failed to find missing pkg on experimental 4.1 > ---------------------------------------------------------------- > > Key: OVIRT-1007 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1007 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: eyal edri [Administrator] > Assignee: infra > Priority: Highest > > http://jenkins.ovirt.org/job/repos_4.1_check-closure_el7_merged/38/console -- This message was sent by Atlassian JIRA (v1000.656.2#100024)

1 0

[JIRA] (OVIRT-1007) repo closure jobs failed to find missing pkg on experimental 4.1
by eyal edri [Administrator] (oVirt JIRA) 05 Jan '17

05 Jan '17

eyal edri [Administrator] created OVIRT-1007: ------------------------------------------------ Summary: repo closure jobs failed to find missing pkg on experimental 4.1 Key: OVIRT-1007 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1007 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: eyal edri [Administrator] Assignee: infra Priority: Highest http://jenkins.ovirt.org/job/repos_4.1_check-closure_el7_merged/38/console -- This message was sent by Atlassian JIRA (v1000.656.2#100024)

1 0

Build failed in Jenkins: ovirt_3.6_he-system-tests #790
by jenkins＠jenkins.phx.ovirt.org 05 Jan '17

05 Jan '17

See <http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/790/changes> Changes: [Yaniv Kaul] Fixes and changes to storage tests [Dan Kenigsberg] vdsm: exclude f23 from 4.1 branch [Yaniv Bronhaim] Update Jenkins slaves for vdsm to f24 and f25 and remove excludes [Eyal Edri] update vdsm jobs to use 4.1 jobs [ngoldin] Add fc25 lago jobs [Juan Hernandez] Build and check API model from branch 4.1 ------------------------------------------ [...truncated 608 lines...] + local ID=3 + lvcreate -L20G -n lun3_bdev vg1_storage + targetcli /backstores/block create name=lun3_bdev dev=/dev/vg1_storage/lun3_bdev + targetcli /iscsi/iqn.2014-07.org.ovirt:storage/tpg1/luns/ create /backstores/block/lun3_bdev + for I in '$(seq $NUM_LUNS)' + create_lun 4 + local ID=4 + lvcreate -L20G -n lun4_bdev vg1_storage + targetcli /backstores/block create name=lun4_bdev dev=/dev/vg1_storage/lun4_bdev + targetcli /iscsi/iqn.2014-07.org.ovirt:storage/tpg1/luns/ create /backstores/block/lun4_bdev + targetcli /iscsi/iqn.2014-07.org.ovirt:storage/tpg1 set auth userid=username password=password + targetcli /iscsi/iqn.2014-07.org.ovirt:storage/tpg1 set attribute demo_mode_write_protect=0 generate_node_acls=1 cache_dynamic_acls=1 default_cmdsn_depth=64 + targetcli saveconfig + systemctl enable target Created symlink from /etc/systemd/system/multi-user.target.wants/target.service to /usr/lib/systemd/system/target.service. + systemctl start target + sed -i 's/#node.session.auth.authmethod = CHAP/node.session.auth.authmethod = CHAP/g' /etc/iscsi/iscsid.conf + sed -i 's/#node.session.auth.username = username/node.session.auth.username = username/g' /etc/iscsi/iscsid.conf + sed -i 's/#node.session.auth.password = password/node.session.auth.password = password/g' /etc/iscsi/iscsid.conf + iscsiadm -m discovery -t sendtargets -p 127.0.0.1 + iscsiadm -m node -L all + rescan-scsi-bus.sh which: no multipath in (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin) + lsscsi -i + grep 36 + awk '{print $NF}' + sort + iscsiadm -m node -U all + iscsiadm -m node -o delete + systemctl stop iscsi.service + systemctl disable iscsi.service Removed symlink /etc/systemd/system/sysinit.target.wants/iscsi.service. + install_deps_389ds + yum install -y --downloaddir=/dev/shm 389-ds-base + setup_389ds + DOMAIN=lago.local + PASSWORD=12345678 ++ sed s/_/-/g ++ hostname + HOSTNAME=lago-he-basic-suite-3-6-storage.lago.local ++ /sbin/ip -4 -o addr show dev eth0 ++ awk '{split($4,a,"."); print a[1] "." a[2] "." a[3] "." a[4]}' ++ awk -F/ '{print $1}' + ADDR=192.168.200.2 + cat + sed -i s/@HOSTNAME@/lago-he-basic-suite-3-6-storage.lago.local/g answer_file.inf + sed -i s/@PASSWORD@/12345678/g answer_file.inf + sed -i s/@DOMAIN@/lago.local/g answer_file.inf + cat + /usr/sbin/setup-ds.pl --silent --file=answer_file.inf Warning: using root as the server user id. You are strongly encouraged to use a non-root user. * [Thread-2] Deploy VM lago-he-basic-suite-3-6-storage: ERROR (in 0:02:27) Error while running thread Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/lago/utils.py", line 55, in _ret_via_queue queue.put({'return': func()}) File "/usr/lib/python2.7/site-packages/lago/prefix.py", line 1242, in _deploy_host host.name(), RuntimeError: <http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ws/ovirt-system-test…> failed with status 1 on lago-he-basic-suite-3-6-storage * [Thread-4] Deploy VM lago-he-basic-suite-3-6-host0: ERROR (in 0:08:50) * [Thread-5] Deploy VM lago-he-basic-suite-3-6-host1: ERROR (in 0:08:51) # Deploy environment: ERROR (in 0:08:51) @ Deploy oVirt environment: ERROR (in 0:08:51) Error occured, aborting Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/ovirtlago/cmd.py", line 281, in do_run self.cli_plugins[args.ovirtverb].do_run(args) File "/usr/lib/python2.7/site-packages/lago/plugins/cli.py", line 184, in do_run self._do_run(**vars(args)) File "/usr/lib/python2.7/site-packages/lago/utils.py", line 489, in wrapper return func(*args, **kwargs) File "/usr/lib/python2.7/site-packages/lago/utils.py", line 500, in wrapper return func(*args, prefix=prefix, **kwargs) File "/usr/lib/python2.7/site-packages/ovirtlago/cmd.py", line 187, in do_deploy prefix.deploy() File "/usr/lib/python2.7/site-packages/lago/log_utils.py", line 621, in wrapper return func(*args, **kwargs) File "/usr/lib/python2.7/site-packages/ovirtlago/reposetup.py", line 68, in wrapper return func(*args, **kwargs) File "/usr/lib/python2.7/site-packages/ovirtlago/__init__.py", line 198, in deploy return super(OvirtPrefix, self).deploy() File "/usr/lib/python2.7/site-packages/lago/log_utils.py", line 621, in wrapper return func(*args, **kwargs) File "/usr/lib/python2.7/site-packages/lago/prefix.py", line 1249, in deploy self._deploy_host, self.virt_env.get_vms().values() File "/usr/lib/python2.7/site-packages/lago/utils.py", line 97, in invoke_in_parallel vt.join_all() File "/usr/lib/python2.7/site-packages/lago/utils.py", line 55, in _ret_via_queue queue.put({'return': func()}) File "/usr/lib/python2.7/site-packages/lago/prefix.py", line 1242, in _deploy_host host.name(), RuntimeError: <http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ws/ovirt-system-test…> failed with status 1 on lago-he-basic-suite-3-6-storage + res=1 + exit 1 + cleanup + rm -rf exported-artifacts + mkdir -p exported-artifacts + [[ -d deployment-he-basic-suite-3.6/current/logs ]] + mv deployment-he-basic-suite-3.6/current/logs exported-artifacts/lago_logs + find deployment-he-basic-suite-3.6 -iname 'nose*.xml' -exec mv '{}' exported-artifacts/ ';' + [[ -d test_logs ]] + [[ -e failure_msg.txt ]] + mv failure_msg.txt exported-artifacts/ + ./run_suite.sh --cleanup he-basic-suite-3.6 + CLI=lago + DO_CLEANUP=false + RECOMMENDED_RAM_IN_MB=8196 + EXTRA_SOURCES=() ++ getopt -o ho:e:n:b:cs:r: --long help,output:,engine:,node:,boot-iso:,cleanup --long extra-rpm-source,reposync-config: -n run_suite.sh -- --cleanup he-basic-suite-3.6 + options=' --cleanup -- '\''he-basic-suite-3.6'\''' + [[ 0 != \0 ]] + eval set -- ' --cleanup -- '\''he-basic-suite-3.6'\''' ++ set -- --cleanup -- he-basic-suite-3.6 + true + case $1 in + DO_CLEANUP=true + shift + true + case $1 in + shift + break + [[ -z he-basic-suite-3.6 ]] ++ realpath he-basic-suite-3.6 + export SUITE=<http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ws/ovirt-system-test…> + SUITE=<http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ws/ovirt-system-test…> + '[' -z '' ']' + export PREFIX=<http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ws/ovirt-system-test…> + PREFIX=<http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ws/ovirt-system-test…> + true + env_cleanup + echo '#########################' ######################### + local res=0 + local uuid + echo '======== Cleaning up' ======== Cleaning up + [[ -e <http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ws/ovirt-system-test…> ]] + echo '----------- Cleaning with lago' ----------- Cleaning with lago + lago --workdir <http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ws/ovirt-system-test…> destroy --yes --all-prefixes + echo '----------- Cleaning with lago done' ----------- Cleaning with lago done + [[ 0 != \0 ]] + echo '======== Cleanup done' ======== Cleanup done + exit 0 + exit Took 607 seconds =================================== logout Finish: shell @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @@ Tue Dec 27 13:49:16 UTC 2016 automation/he_basic_suite_3.6.sh chroot finished @@ took 617 seconds @@ rc = 1 @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ ========== Scrubbing chroot mock \ --configdir="<http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ws/ovirt-system-tests"> \ --root="mocker-epel-7-x86_64.el7" \ --resultdir="logs/mocker-epel-7-x86_64.el7.scrub" \ --scrub=chroot WARNING: Could not find required logging config file: <http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ws/ovirt-system-test….> Using default... INFO: mock.py version 1.2.21 starting (python version = 3.5.1)... Start: init plugins INFO: selinux enabled Finish: init plugins Start: run Start: scrub ['chroot'] INFO: scrubbing chroot for mocker-epel-7-x86_64.el7 Finish: scrub ['chroot'] Finish: run Scrub chroot took 5 seconds ============================ ########################################################## ## Tue Dec 27 13:49:21 UTC 2016 Finished env: el7:epel-7-x86_64 ## took 622 seconds ## rc = 1 ########################################################## ##! ERROR vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv ##! Last 20 log entries: logs/mocker-epel-7-x86_64.el7.he_basic_suite_3.6.sh/he_basic_suite_3.6.sh.log ##! + env_cleanup + echo '#########################' ######################### + local res=0 + local uuid + echo '======== Cleaning up' ======== Cleaning up + [[ -e <http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ws/ovirt-system-test…> ]] + echo '----------- Cleaning with lago' ----------- Cleaning with lago + lago --workdir <http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ws/ovirt-system-test…> destroy --yes --all-prefixes + echo '----------- Cleaning with lago done' ----------- Cleaning with lago done + [[ 0 != \0 ]] + echo '======== Cleanup done' ======== Cleanup done + exit 0 + exit Took 607 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/hudson6318118267408142511.sh + echo shell_scripts/system_tests.collect_logs.sh shell_scripts/system_tests.collect_logs.sh + VERSION=3.6 + SUITE_TYPE= + WORKSPACE=<http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ws/> + OVIRT_SUITE=3.6 + TESTS_LOGS=<http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ws/ovirt-system-test…> + rm -rf <http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/790/artifact/exporte…> + mkdir -p <http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/790/artifact/exporte…> + [[ -d <http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ws/ovirt-system-test…> ]] + mv <http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ws/ovirt-system-test…> <http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ws/ovirt-system-test…> <http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/790/artifact/exporte…> POST BUILD TASK : SUCCESS END OF POST BUILD TASK : 0 Recording test results ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error? Archiving artifacts

1 11

oVirt infra daily report - unstable production jobs - 190
by jenkins＠jenkins.phx.ovirt.org 05 Jan '17

05 Jan '17

------=_Part_100_493996725.1483570862350 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit 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/190//artifact/exported-a… Cheers, Jenkins ------=_Part_100_493996725.1483570862350 Content-Type: text/html; charset=us-ascii; name=upstream_report.html Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=upstream_report.html Content-ID: <upstream_report.html> <!DOCTYPE html><head><style type="text/css"> table.gridtable { border-collapse: collapse; table-layout:fixed; width:1600px; font-family: monospace; font-size:13px; } .head { font-size:20px; font-family: arial; } .sub { font-size:18px; background-color:#e5e5e5; font-family: arial; } pre { font-family: monospace; display: inline; white-space: pre-wrap; white-space: -moz-pre-wrap !important; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word; } </style> </head> <body> <table class="gridtable" border=2> <tr><th colspan=2 class=head> RHEVM CI Jenkins Daily Report - 04/01/2017 </th></tr><tr><th colspan=2 class=sub> <font color="blue"><a href="http://jenkins.ovirt.org/">00 Unstable Critical</a></font> </th></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/deploy-to-ovirt_experimental_3.6/">deploy-to-ovirt_experimental_3.6</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-master-experimental_build-…">ovirt-node-ng_ovirt-master-experimental_build-artifacts-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/">ovirt_3.6_he-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_3.6_image-ng-system-tests/">ovirt_3.6_image-ng-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_4.1_system-tests/">ovirt_4.1_system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/repos_4.0_check-closure_fc23_merged/">repos_4.0_check-closure_fc23_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/repos_4.1_check-closure_fc24_merged/">repos_4.1_check-closure_fc24_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/repos_master_check-closure_el7_merged/">repos_master_check-closure_el7_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/repos_master_check-closure_fc24_merged/">repos_master_check-closure_fc24_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/system-backup_jenkins_old_ovirt_org/">system-backup_jenkins_old_ovirt_org</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> ------=_Part_100_493996725.1483570862350--

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_4.1 - Build #124 - SUCCESS!
by jenkins＠jenkins.phx.ovirt.org 04 Jan '17

04 Jan '17

------=_Part_97_1734815977.1483543294377 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.1/124/, Build Number: 124, Build Status: SUCCESS ------=_Part_97_1734815977.1483543294377--

1 0

[JIRA] (OVIRT-1005) Fix race condition caused by experimental cleanup script
by Barak Korren (oVirt JIRA) 04 Jan '17

04 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1005?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1005: ----------------------------------- Assignee: Barak Korren (was: infra) > Fix race condition caused by experimental cleanup script > -------------------------------------------------------- > > Key: OVIRT-1005 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1005 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Barak Korren > Assignee: Barak Korren > Priority: Highest > > The experimental repo has a cleanup script that is ran every hour via cron. The script is meant to delete old and unused package builds. > The content of the script is as follows: > {code} > find \ > /srv/resources/repos/ovirt/experimental/*/* \ > -maxdepth 0 \ > -type d \ > -not -name 'latest.*' \ > -and \ > -mtime +1 \ > -exec rm -rf {} \; > {code} > The problem here is that 'latest' is not filtered out to not be deleted by this script. It is OK to delete it in most cases because then it gets recreated by the 'deploy-to-experimental' job, but there might be a case where 'test-repo_ovirt-experimental_*' can run before this happens, this may cause it to get an empty or partial 'latest' repo. > To remedy this, the script needs to be changed to be the following: > {code} > find \ > /srv/resources/repos/ovirt/experimental/*/* \ > -maxdepth 0 \ > -type d \ > -not -name 'latest.*' \ > -and \ > -not -name 'latest' \ > -and \ > -mtime +1 \ > -exec rm -rf {} \; > {code} > The script itself on the resources server was already changed in-palce, this ticket is so we this change is also "backed up" to the 'infra-puppet' repo. -- This message was sent by Atlassian JIRA (v1000.656.2#100024)

1 0

[JIRA] (OVIRT-1005) Fix race condition caused by experimental cleanup script
by Barak Korren (oVirt JIRA) 04 Jan '17

04 Jan '17

Barak Korren created OVIRT-1005: ----------------------------------- Summary: Fix race condition caused by experimental cleanup script Key: OVIRT-1005 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1005 Project: oVirt - virtualization made easy Issue Type: Improvement Reporter: Barak Korren Assignee: infra Priority: Highest The experimental repo has a cleanup script that is ran every hour via cron. The script is meant to delete old and unused package builds. The content of the script is as follows: {code} find \ /srv/resources/repos/ovirt/experimental/*/* \ -maxdepth 0 \ -type d \ -not -name 'latest.*' \ -and \ -mtime +1 \ -exec rm -rf {} \; {code} The problem here is that 'latest' is not filtered out to not be deleted by this script. It is OK to delete it in most cases because then it gets recreated by the 'deploy-to-experimental' job, but there might be a case where 'test-repo_ovirt-experimental_*' can run before this happens, this may cause it to get an empty or partial 'latest' repo. To remedy this, the script needs to be changed to be the following: {code} find \ /srv/resources/repos/ovirt/experimental/*/* \ -maxdepth 0 \ -type d \ -not -name 'latest.*' \ -and \ -not -name 'latest' \ -and \ -mtime +1 \ -exec rm -rf {} \; {code} The script itself on the resources server was already changed in-palce, this ticket is so we this change is also "backed up" to the 'infra-puppet' repo. -- This message was sent by Atlassian JIRA (v1000.656.2#100024)

1 0

[JIRA] (OVIRT-1005) Fix race condition caused by experimental cleanup script
by Barak Korren (oVirt JIRA) 04 Jan '17

04 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1005?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1005: -------------------------------- Epic Link: OVIRT-400 > Fix race condition caused by experimental cleanup script > -------------------------------------------------------- > > Key: OVIRT-1005 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1005 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Barak Korren > Assignee: infra > Priority: Highest > > The experimental repo has a cleanup script that is ran every hour via cron. The script is meant to delete old and unused package builds. > The content of the script is as follows: > {code} > find \ > /srv/resources/repos/ovirt/experimental/*/* \ > -maxdepth 0 \ > -type d \ > -not -name 'latest.*' \ > -and \ > -mtime +1 \ > -exec rm -rf {} \; > {code} > The problem here is that 'latest' is not filtered out to not be deleted by this script. It is OK to delete it in most cases because then it gets recreated by the 'deploy-to-experimental' job, but there might be a case where 'test-repo_ovirt-experimental_*' can run before this happens, this may cause it to get an empty or partial 'latest' repo. > To remedy this, the script needs to be changed to be the following: > {code} > find \ > /srv/resources/repos/ovirt/experimental/*/* \ > -maxdepth 0 \ > -type d \ > -not -name 'latest.*' \ > -and \ > -not -name 'latest' \ > -and \ > -mtime +1 \ > -exec rm -rf {} \; > {code} > The script itself on the resources server was already changed in-palce, this ticket is so we this change is also "backed up" to the 'infra-puppet' repo. -- This message was sent by Atlassian JIRA (v1000.656.2#100024)

1 0

engine CI failing upgrade tasks due to missing dependencies
by Allon Mureinik 04 Jan '17

04 Jan '17

Hi infra, Upgrade tasks in engine CI seem to be failing due to missing dependencies. E.g. [1]: Error downloading packages: vdsm-jsonrpc-java-1.3.5-1.20170103113616.gitfbe3dec.el7.centos.noarch: [Errno 256] No more mirrors to try. ovirt-engine-dwh-setup-4.1.0-0.0.master.20170103090346.el7.centos.noarch: [Errno 256] No more mirrors to try. ovirt-engine-dwh-4.1.0-0.0.master.20170103090346.el7.centos.noarch: [Errno 256] No more mirrors to try. ovirt-engine-cli-3.6.9.3-0.1.20170103.git61c5da9.el7.centos.noarch: [Errno 256] No more mirrors to try. ovirt-imageio-proxy-1.0.0-0.201701021040.git022783e.el7.centos.noarch: [Errno 256] No more mirrors to try. ovirt-engine-sdk-python-3.6.9.2-0.1.20170103.gite99bbd1.el7.centos.noarch: [Errno 256] No more mirrors to try. ovirt-imageio-proxy-setup-1.0.0-0.201701021040.git022783e.el7.centos.noarch: [Errno 256] No more mirrors to try. ovirt-engine-extension-aaa-jdbc-1.1.3-0.0.master.20170103103520.gitd0ff686.el7.noarch: [Errno 256] No more mirrors to try. ovirt-vmconsole-proxy-1.0.4-0.0.master.20170103150743.git51ed572.el7.centos.noarch: [Errno 256] No more mirrors to try. ovirt-vmconsole-1.0.4-0.0.master.20170103150743.git51ed572.el7.centos.noarch: [Errno 256] No more mirrors to try. ovirt-iso-uploader-4.1.0-0.0.master.20170103091034.git14502bd.el7.centos.noarch: [Errno 256] No more mirrors to try. ovirt-setup-lib-1.1.0-1.20170103120007.git402fec4.el7.centos.noarch: [Errno 256] No more mirrors to try. ovirt-host-deploy-1.6.0-0.0.master.20170103133827.git7eea7f1.el7.centos.noarch: [Errno 256] No more mirrors to try. ovirt-host-deploy-java-1.6.0-0.0.master.20170103133827.git7eea7f1.el7.centos.noarch: [Errno 256] No more mirrors to try. ovirt-engine-wildfly-overlay-10.0.0-1.el7.noarch: [Errno 256] No more mirrors to try. ovirt-engine-dashboard-1.1.0-0.4.20170103gitfad882b.el7.centos.noarch: [Errno 256] No more mirrors to try. ovirt-imageio-common-1.0.0-0.201701021040.git022783e.el7.centos.noarch: [Errno 256] No more mirrors to try. [1] http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-4.1_el7_creat…

2 2

how does findbugs work?
by Michal Skrivanek 04 Jan '17

04 Jan '17

Hi, I was trying to see why the recent NPE[1] was not found by findbugs. Typically identifying potential NPE is the most easy thing…but it was not reported. So I triggered the build again on the wrong patch [2] and it doesn’t show anything useful[3] Does it work at all? There seem to be no artifacts to review that Thanks, michal [1] https://gerrit.ovirt.org/#/c/68731 [2] https://gerrit.ovirt.org/#/c/68400/5 [3] http://jenkins.ovirt.org/job/ovirt-engine_master_find-bugs_created/11732/

2 3

[JIRA] (OVIRT-1004) Please collect libvirt/qemu logs in OST
by Pavel Zhukov (oVirt JIRA) 04 Jan '17

04 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1004?page=com.atlassian.jira.… ] Pavel Zhukov reassigned OVIRT-1004: ----------------------------------- Assignee: Nadav Goldin (was: infra) > Please collect libvirt/qemu logs in OST > --------------------------------------- > > Key: OVIRT-1004 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1004 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Pavel Zhukov > Assignee: Nadav Goldin > > For some problems we need qemu logs to investigate the issue. They're > missed now: > http://jenkins.ovirt.org/job/ovirt_4.1_system-tests/28/artifact/exported-ar… > Please collect logs and publish them in artifactts. > -- > Pavel Zhukov > Software Engineer > RHEV Devops > IRC: landgraf -- This message was sent by Atlassian JIRA (v1000.656.2#100024)

1 0

[JIRA] (OVIRT-1003) Ensure PHX proxy does not cache resources.ovirt.org
by Barak Korren (oVirt JIRA) 04 Jan '17

04 Jan '17

Barak Korren created OVIRT-1003: ----------------------------------- Summary: Ensure PHX proxy does not cache resources.ovirt.org Key: OVIRT-1003 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1003 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Repositories Mgmt Reporter: Barak Korren Assignee: infra Priority: High Out proxy is currently caching packages from resources.ovirt.org when jobs ask for then, since resources.ovirt.org is now in PHX, this is redundant and places unnecessary load on the proxy. We need to configure the proxy to issue an HTTP permanent redirect (301) to all requests for file from resource.ovirt.org. -- This message was sent by Atlassian JIRA (v1000.656.2#100024)

1 0

[JIRA] (OVIRT-1003) Ensure PHX proxy does not cache resources.ovirt.org
by Barak Korren (oVirt JIRA) 04 Jan '17

04 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1003?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1003: -------------------------------- Epic Link: OVIRT-403 > Ensure PHX proxy does not cache resources.ovirt.org > ---------------------------------------------------- > > Key: OVIRT-1003 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1003 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Repositories Mgmt > Reporter: Barak Korren > Assignee: infra > Priority: High > > Out proxy is currently caching packages from resources.ovirt.org when jobs ask for then, since resources.ovirt.org is now in PHX, this is redundant and places unnecessary load on the proxy. > We need to configure the proxy to issue an HTTP permanent redirect (301) to all requests for file from resource.ovirt.org. -- This message was sent by Atlassian JIRA (v1000.656.2#100024)

1 0

oVirt infra daily report - unstable production jobs - 189
by jenkins＠jenkins.phx.ovirt.org 04 Jan '17

04 Jan '17

------=_Part_91_1455951705.1483484462352 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit 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/189//artifact/exported-a… Cheers, Jenkins ------=_Part_91_1455951705.1483484462352 Content-Type: text/html; charset=us-ascii; name=upstream_report.html Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=upstream_report.html Content-ID: <upstream_report.html> <!DOCTYPE html><head><style type="text/css"> table.gridtable { border-collapse: collapse; table-layout:fixed; width:1600px; font-family: monospace; font-size:13px; } .head { font-size:20px; font-family: arial; } .sub { font-size:18px; background-color:#e5e5e5; font-family: arial; } pre { font-family: monospace; display: inline; white-space: pre-wrap; white-space: -moz-pre-wrap !important; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word; } </style> </head> <body> <table class="gridtable" border=2> <tr><th colspan=2 class=head> RHEVM CI Jenkins Daily Report - 03/01/2017 </th></tr><tr><th colspan=2 class=sub> <font color="blue"><a href="http://jenkins.ovirt.org/">00 Unstable Critical</a></font> </th></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/deploy-to-ovirt_experimental_3.6/">deploy-to-ovirt_experimental_3.6</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-master-experimental_build-…">ovirt-node-ng_ovirt-master-experimental_build-artifacts-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/">ovirt_3.6_he-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_3.6_image-ng-system-tests/">ovirt_3.6_image-ng-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/repos_4.0_check-closure_fc23_merged/">repos_4.0_check-closure_fc23_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/repos_4.1_check-closure_fc24_merged/">repos_4.1_check-closure_fc24_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/repos_master_check-closure_el7_merged/">repos_master_check-closure_el7_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/repos_master_check-closure_fc24_merged/">repos_master_check-closure_fc24_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/system-backup_jenkins_old_ovirt_org/">system-backup_jenkins_old_ovirt_org</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> ------=_Part_91_1455951705.1483484462352--

1 0

[JIRA] (OVIRT-1000) Java SDK 4.1 branch don't execute jenkins jobs
by Gil Shinar (oVirt JIRA) 03 Jan '17

03 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1000?page=com.atlassian.jira.… ] Gil Shinar commented on OVIRT-1000: ----------------------------------- Just a bit mess but should work. We prefer to leave each project with its name but as long as there are different names, it's OK by me. > Java SDK 4.1 branch don't execute jenkins jobs > ---------------------------------------------- > > Key: OVIRT-1000 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1000 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins > Reporter: Ondra Machacek > Assignee: infra > > Jenkins job are not still executed from sdk_4.1 branch of the Java SDK project, > you can see an example here: https://gerrit.ovirt.org/#/c/69455/1 > I've created a patch[1] which I think should fix build-artifacts job, not sure about check-patch job. > [1] https://gerrit.ovirt.org/#/c/69459/ -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-1000) Java SDK 4.1 branch don't execute jenkins jobs
by Juan Hernández (oVirt JIRA) 03 Jan '17

03 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1000?page=com.atlassian.jira.… ] Juan Hernández commented on OVIRT-1000: --------------------------------------- Not sure what you mean by "where they should be built"? Do you mean for what versions of oVirt they should be built? In that case this is my suggestion: Git repository - RPM name - Where to build ovirt-engine-sdk - python-ovirt-engine-sdk4 - 4.y ovirt-engine-sdk-java - java-ovirt-engine-sdk4 - 4.y ovirt-engine-sdk-v3 - ovirt-engine-sdk-python - 3.y and 4.y ovirt-engine-sdk-java-v3 - ovirt-engine-sdk-java - 3.y and 4.y Would that help? I mean, doing this isn't useful for me, I am suggesting it because I thought it would solve the issues that you experience in the CI environment. Maybe we should setup a meeting so that you can explain me better what are those issues. > Java SDK 4.1 branch don't execute jenkins jobs > ---------------------------------------------- > > Key: OVIRT-1000 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1000 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins > Reporter: Ondra Machacek > Assignee: infra > > Jenkins job are not still executed from sdk_4.1 branch of the Java SDK project, > you can see an example here: https://gerrit.ovirt.org/#/c/69455/1 > I've created a patch[1] which I think should fix build-artifacts job, not sure about check-patch job. > [1] https://gerrit.ovirt.org/#/c/69459/ -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-1001) GitHub token for ovirt-engine-api-model and Travis CI
by eyal edri [Administrator] (oVirt JIRA) 03 Jan '17

03 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1001?page=com.atlassian.jira.… ] eyal edri [Administrator] updated OVIRT-1001: --------------------------------------------- Resolution: Fixed Status: Done (was: To Do) > GitHub token for ovirt-engine-api-model and Travis CI > ----------------------------------------------------- > > Key: OVIRT-1001 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1001 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Petr Horacek > Assignee: infra > > Hello, > I'd like to publish documentation made by > https://github.com/oVirt/ovirt-engine-api-model on GitHub pages (built > and deployed by Travis). I've already done that on my fork > https://github.com/phoracek/ovirt-engine-api-model but I'd like it to > be publicly available on ovirt.github.io/ovirt-engine-api-model. > What I need for that is GitHub token > (https://github.com/settings/tokens/new) that will give me > 'public_repo' scope rights (to be able to create a new branch and push > commits into it). It will be encrypted for Travis and therefore not > usable by others. Second think is to enable Travis for > ovirt-engine-api-model repository. Maybe it would be also necessary to > enable GitHub Pages on the project, but I think it will be done > automatically with branch gh-pages. > Would it be possible? Is there a better way, such as creating a new > user, give him rights for the repository and generate token for it? > Thanks, > Petr -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-1001) GitHub token for ovirt-engine-api-model and Travis CI
by Petr Horacek (oVirt JIRA) 03 Jan '17

03 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1001?page=com.atlassian.jira.… ] Petr Horacek commented on OVIRT-1001: ------------------------------------- It works, thanks again. > GitHub token for ovirt-engine-api-model and Travis CI > ----------------------------------------------------- > > Key: OVIRT-1001 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1001 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Petr Horacek > Assignee: infra > > Hello, > I'd like to publish documentation made by > https://github.com/oVirt/ovirt-engine-api-model on GitHub pages (built > and deployed by Travis). I've already done that on my fork > https://github.com/phoracek/ovirt-engine-api-model but I'd like it to > be publicly available on ovirt.github.io/ovirt-engine-api-model. > What I need for that is GitHub token > (https://github.com/settings/tokens/new) that will give me > 'public_repo' scope rights (to be able to create a new branch and push > commits into it). It will be encrypted for Travis and therefore not > usable by others. Second think is to enable Travis for > ovirt-engine-api-model repository. Maybe it would be also necessary to > enable GitHub Pages on the project, but I think it will be done > automatically with branch gh-pages. > Would it be possible? Is there a better way, such as creating a new > user, give him rights for the repository and generate token for it? > Thanks, > Petr -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-1001) GitHub token for ovirt-engine-api-model and Travis CI
by eyal edri [Administrator] (oVirt JIRA) 03 Jan '17

03 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1001?page=com.atlassian.jira.… ] eyal edri [Administrator] commented on OVIRT-1001: -------------------------------------------------- done, you should have admin rights on that repo now. > GitHub token for ovirt-engine-api-model and Travis CI > ----------------------------------------------------- > > Key: OVIRT-1001 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1001 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Petr Horacek > Assignee: infra > > Hello, > I'd like to publish documentation made by > https://github.com/oVirt/ovirt-engine-api-model on GitHub pages (built > and deployed by Travis). I've already done that on my fork > https://github.com/phoracek/ovirt-engine-api-model but I'd like it to > be publicly available on ovirt.github.io/ovirt-engine-api-model. > What I need for that is GitHub token > (https://github.com/settings/tokens/new) that will give me > 'public_repo' scope rights (to be able to create a new branch and push > commits into it). It will be encrypted for Travis and therefore not > usable by others. Second think is to enable Travis for > ovirt-engine-api-model repository. Maybe it would be also necessary to > enable GitHub Pages on the project, but I think it will be done > automatically with branch gh-pages. > Would it be possible? Is there a better way, such as creating a new > user, give him rights for the repository and generate token for it? > Thanks, > Petr -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-1001) GitHub token for ovirt-engine-api-model and Travis CI
by Petr Horacek (oVirt JIRA) 03 Jan '17

03 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1001?page=com.atlassian.jira.… ] Petr Horacek commented on OVIRT-1001: ------------------------------------- Ok, could you please set those rights to phoracek(a)redhat.com? Thanks a lot. > GitHub token for ovirt-engine-api-model and Travis CI > ----------------------------------------------------- > > Key: OVIRT-1001 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1001 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Petr Horacek > Assignee: infra > > Hello, > I'd like to publish documentation made by > https://github.com/oVirt/ovirt-engine-api-model on GitHub pages (built > and deployed by Travis). I've already done that on my fork > https://github.com/phoracek/ovirt-engine-api-model but I'd like it to > be publicly available on ovirt.github.io/ovirt-engine-api-model. > What I need for that is GitHub token > (https://github.com/settings/tokens/new) that will give me > 'public_repo' scope rights (to be able to create a new branch and push > commits into it). It will be encrypted for Travis and therefore not > usable by others. Second think is to enable Travis for > ovirt-engine-api-model repository. Maybe it would be also necessary to > enable GitHub Pages on the project, but I think it will be done > automatically with branch gh-pages. > Would it be possible? Is there a better way, such as creating a new > user, give him rights for the repository and generate token for it? > Thanks, > Petr -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-1001) GitHub token for ovirt-engine-api-model and Travis CI
by eyal edri [Administrator] (oVirt JIRA) 03 Jan '17

03 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1001?page=com.atlassian.jira.… ] eyal edri [Administrator] commented on OVIRT-1001: -------------------------------------------------- Usually the maintainer of the project does it from GitHub, So you just need to permission updated - who should be the maintainer on the GitHub project? > GitHub token for ovirt-engine-api-model and Travis CI > ----------------------------------------------------- > > Key: OVIRT-1001 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1001 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Petr Horacek > Assignee: infra > > Hello, > I'd like to publish documentation made by > https://github.com/oVirt/ovirt-engine-api-model on GitHub pages (built > and deployed by Travis). I've already done that on my fork > https://github.com/phoracek/ovirt-engine-api-model but I'd like it to > be publicly available on ovirt.github.io/ovirt-engine-api-model. > What I need for that is GitHub token > (https://github.com/settings/tokens/new) that will give me > 'public_repo' scope rights (to be able to create a new branch and push > commits into it). It will be encrypted for Travis and therefore not > usable by others. Second think is to enable Travis for > ovirt-engine-api-model repository. Maybe it would be also necessary to > enable GitHub Pages on the project, but I think it will be done > automatically with branch gh-pages. > Would it be possible? Is there a better way, such as creating a new > user, give him rights for the repository and generate token for it? > Thanks, > Petr -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-1001) GitHub token for ovirt-engine-api-model and Travis CI
by Petr Horacek (oVirt JIRA) 03 Jan '17

03 Jan '17

Petr Horacek created OVIRT-1001: ----------------------------------- Summary: GitHub token for ovirt-engine-api-model and Travis CI Key: OVIRT-1001 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1001 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Petr Horacek Assignee: infra Hello, I'd like to publish documentation made by https://github.com/oVirt/ovirt-engine-api-model on GitHub pages (built and deployed by Travis). I've already done that on my fork https://github.com/phoracek/ovirt-engine-api-model but I'd like it to be publicly available on ovirt.github.io/ovirt-engine-api-model. What I need for that is GitHub token (https://github.com/settings/tokens/new) that will give me 'public_repo' scope rights (to be able to create a new branch and push commits into it). It will be encrypted for Travis and therefore not usable by others. Second think is to enable Travis for ovirt-engine-api-model repository. Maybe it would be also necessary to enable GitHub Pages on the project, but I think it will be done automatically with branch gh-pages. Would it be possible? Is there a better way, such as creating a new user, give him rights for the repository and generate token for it? Thanks, Petr -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-1000) Java SDK 4.1 branch don't execute jenkins jobs
by eyal edri [Administrator] (oVirt JIRA) 03 Jan '17

03 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1000?page=com.atlassian.jira.… ] eyal edri [Administrator] commented on OVIRT-1000: -------------------------------------------------- So what do you suggest? can you layout the new repos/name you'd like to see for V3+V4 and where they should be built? > Java SDK 4.1 branch don't execute jenkins jobs > ---------------------------------------------- > > Key: OVIRT-1000 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1000 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins > Reporter: Ondra Machacek > Assignee: infra > > Jenkins job are not still executed from sdk_4.1 branch of the Java SDK project, > you can see an example here: https://gerrit.ovirt.org/#/c/69455/1 > I've created a patch[1] which I think should fix build-artifacts job, not sure about check-patch job. > [1] https://gerrit.ovirt.org/#/c/69459/ -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-973) add support for custom build params on build-on-demand jobs
by eyal edri [Administrator] (oVirt JIRA) 03 Jan '17

03 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-973?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-973: -------------------------------------------- Summary: add support for custom build params on build-on-demand jobs (was: nightly ovirt-engine build is missing Chrome permutation) > add support for custom build params on build-on-demand jobs > ----------------------------------------------------------- > > Key: OVIRT-973 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-973 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins > Reporter: Greg Sheremeta > Assignee: infra > > mburman [reports|https://bugzilla.redhat.com/show_bug.cgi?id=1400010] that the nightly ovirt-engine build is missing the Chrome permutation. > From the [build|http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-el7-…] > {noformat} > 21:13:24 [INFO] Compiling 1 permutation > 21:13:24 [INFO] Compiling permutation 0... > 21:16:54 [INFO] Compile of permutations succeeded > {noformat} > That should compile 2 if we want Firefox and Chrome, or 3 if we also want IE. > mburman reports this started on November 30. I'm not sure what changed. > Adding build flags will fix: > DEV_EXTRA_BUILD_FLAGS_GWT_DEFAULTS="-Dgwt.userAgent=safari,gecko1_8" -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-973) add support for custom build params on build-on-demand jobs
by eyal edri [Administrator] (oVirt JIRA) 03 Jan '17

03 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-973?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-973: ------------------------------------------------- I changed the job to add support for it, but its not trivial and not sure when we can do it, If someone needs a specific build, he'll need to run it locally for now or send a patch like suggested in this ticket > add support for custom build params on build-on-demand jobs > ----------------------------------------------------------- > > Key: OVIRT-973 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-973 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins > Reporter: Greg Sheremeta > Assignee: infra > > mburman [reports|https://bugzilla.redhat.com/show_bug.cgi?id=1400010] that the nightly ovirt-engine build is missing the Chrome permutation. > From the [build|http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-el7-…] > {noformat} > 21:13:24 [INFO] Compiling 1 permutation > 21:13:24 [INFO] Compiling permutation 0... > 21:16:54 [INFO] Compile of permutations succeeded > {noformat} > That should compile 2 if we want Firefox and Chrome, or 3 if we also want IE. > mburman reports this started on November 30. I'm not sure what changed. > Adding build flags will fix: > DEV_EXTRA_BUILD_FLAGS_GWT_DEFAULTS="-Dgwt.userAgent=safari,gecko1_8" -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-973) nightly ovirt-engine build is missing Chrome permutation
by Vojtech Szocs (oVirt JIRA) 03 Jan '17

03 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-973?page=com.atlassian.jira.p… ] Vojtech Szocs commented on OVIRT-973: ------------------------------------- bq. How much time it will add if we'll add chrome to the permutations? At least +50% GWT build time, I'd say. bq. I wouldn't want to pay a constant time penalty just because a single manual test needed it. Agreed. GWT Chrome build should be opt-in, only when needed. bq. You can easily send a patch to build-artifacts with the permutations you want and then use the 'build-on-demand' job using 'ci please build' to build rpms using the new PARAMS. Good point, but can we have a "long standing" (forever open) patch for this purpose? Just to clarify, what I meant in my previous comment was this: 1, user gets a nightly Engine build (FF-only) 2, user decides he/she needs Chrome support for that particular build 3, user re-triggers the particular build and passes some param (defined in Jenkins job config and somehow passed to build script) to trigger Chrome GWT permutation > nightly ovirt-engine build is missing Chrome permutation > -------------------------------------------------------- > > Key: OVIRT-973 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-973 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins > Reporter: Greg Sheremeta > Assignee: infra > > mburman [reports|https://bugzilla.redhat.com/show_bug.cgi?id=1400010] that the nightly ovirt-engine build is missing the Chrome permutation. > From the [build|http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-el7-…] > {noformat} > 21:13:24 [INFO] Compiling 1 permutation > 21:13:24 [INFO] Compiling permutation 0... > 21:16:54 [INFO] Compile of permutations succeeded > {noformat} > That should compile 2 if we want Firefox and Chrome, or 3 if we also want IE. > mburman reports this started on November 30. I'm not sure what changed. > Adding build flags will fix: > DEV_EXTRA_BUILD_FLAGS_GWT_DEFAULTS="-Dgwt.userAgent=safari,gecko1_8" -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-1000) Java SDK 4.1 branch don't execute jenkins jobs
by Juan Hernández (oVirt JIRA) 03 Jan '17

03 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1000?page=com.atlassian.jira.… ] Juan Hernández commented on OVIRT-1000: --------------------------------------- Having the project and the RPM named the same is a price that I would't like to pay. This has always been the case, even before the introduction of V4. The name of the Python SDK, for example was ovirt-engine-sdk, but the name of the RPM was ovirt-engine-sdk-python. For the Ruby SDK (which only has V4) the name is also different: the repo is ovirt-engine-sdk-ruby but the name of the RPM is rubygem-ovirt-engine-sdk4. We can't (or should not) force projects to adopt the names that the distribution packaging requires. > Java SDK 4.1 branch don't execute jenkins jobs > ---------------------------------------------- > > Key: OVIRT-1000 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1000 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins > Reporter: Ondra Machacek > Assignee: infra > > Jenkins job are not still executed from sdk_4.1 branch of the Java SDK project, > you can see an example here: https://gerrit.ovirt.org/#/c/69455/1 > I've created a patch[1] which I think should fix build-artifacts job, not sure about check-patch job. > [1] https://gerrit.ovirt.org/#/c/69459/ -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-1000) Java SDK 4.1 branch don't execute jenkins jobs
by eyal edri [Administrator] (oVirt JIRA) 03 Jan '17

03 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1000?page=com.atlassian.jira.… ] eyal edri [Administrator] commented on OVIRT-1000: -------------------------------------------------- I thought we would leave all current repos alone and create new projects both for v3 and v4, keeping the old repo for new version is a problem, since we have a diff between repo name and rpm names > Java SDK 4.1 branch don't execute jenkins jobs > ---------------------------------------------- > > Key: OVIRT-1000 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1000 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins > Reporter: Ondra Machacek > Assignee: infra > > Jenkins job are not still executed from sdk_4.1 branch of the Java SDK project, > you can see an example here: https://gerrit.ovirt.org/#/c/69455/1 > I've created a patch[1] which I think should fix build-artifacts job, not sure about check-patch job. > [1] https://gerrit.ovirt.org/#/c/69459/ -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-1000) Java SDK 4.1 branch don't execute jenkins jobs
by Juan Hernández (oVirt JIRA) 03 Jan '17

03 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1000?page=com.atlassian.jira.… ] Juan Hernández commented on OVIRT-1000: --------------------------------------- No objection from my side then. Let me insist that what I would like is to preserve the existing ovirt-engine-sdk and ovirt-engine-sdk-java git repositories for V4, and create new repositories for the old V3. If you agree with that, then proceed to create the new repositories and I will take ownership of the rest of required changes. I will however need your help if there is something that I don't know how to handle. > Java SDK 4.1 branch don't execute jenkins jobs > ---------------------------------------------- > > Key: OVIRT-1000 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1000 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins > Reporter: Ondra Machacek > Assignee: infra > > Jenkins job are not still executed from sdk_4.1 branch of the Java SDK project, > you can see an example here: https://gerrit.ovirt.org/#/c/69455/1 > I've created a patch[1] which I think should fix build-artifacts job, not sure about check-patch job. > [1] https://gerrit.ovirt.org/#/c/69459/ -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-1000) Java SDK 4.1 branch don't execute jenkins jobs
by eyal edri [Administrator] (oVirt JIRA) 03 Jan '17

03 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1000?page=com.atlassian.jira.… ] eyal edri [Administrator] commented on OVIRT-1000: -------------------------------------------------- There shouldn't be a problem to keep existing repos, we will just not build from them in CI, but no problem to keep the old branches in place. Yea, creating new projects and new jobs will give us flexibility to keep existing status in tact until we switch to new repos + jobs. > Java SDK 4.1 branch don't execute jenkins jobs > ---------------------------------------------- > > Key: OVIRT-1000 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1000 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins > Reporter: Ondra Machacek > Assignee: infra > > Jenkins job are not still executed from sdk_4.1 branch of the Java SDK project, > you can see an example here: https://gerrit.ovirt.org/#/c/69455/1 > I've created a patch[1] which I think should fix build-artifacts job, not sure about check-patch job. > [1] https://gerrit.ovirt.org/#/c/69459/ -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-1000) Java SDK 4.1 branch don't execute jenkins jobs
by Juan Hernández (oVirt JIRA) 03 Jan '17

03 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1000?page=com.atlassian.jira.… ] Juan Hernández commented on OVIRT-1000: --------------------------------------- I am OK with separating the repositories. My only concern is preserving the existing repositories for V4, as doing otherwise would disrupt the development in the current active branches (V4 is active, V3 isn't). [~gshinar] told me that creating new repositories for V3 won't solve the problem. My understanding is that the problem is solved if we have different repositories for both versions, no matter if the new ones are for V3 or V4. I also understand that creating new repositories for the old versions may involve more work, maybe renaming or updating more jobs. I am open to pay that price. Lets say that we create the new two git repositories: ovirt-engine-sdk-v3 - For V3 of the Python SDK. ovirt-engine-sdk-java-v3 - For V3 of the Java SDK The existing jobs will need to be updated so that they only build V4, and then new jobs will need to be created to build V3. Am I missing something? > Java SDK 4.1 branch don't execute jenkins jobs > ---------------------------------------------- > > Key: OVIRT-1000 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1000 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins > Reporter: Ondra Machacek > Assignee: infra > > Jenkins job are not still executed from sdk_4.1 branch of the Java SDK project, > you can see an example here: https://gerrit.ovirt.org/#/c/69455/1 > I've created a patch[1] which I think should fix build-artifacts job, not sure about check-patch job. > [1] https://gerrit.ovirt.org/#/c/69459/ -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[oVirt Jenkins] repos_4.1_check-closure_el7_merged - Build # 27 - Failure!
by jenkins＠jenkins.phx.ovirt.org 03 Jan '17

03 Jan '17

------=_Part_80_866150003.1483442183753 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/repos_4.1_check-closure_el7_merged/ Build: http://jenkins.ovirt.org/job/repos_4.1_check-closure_el7_merged/27/ Build Number: 27 Build Status: Failure Triggered By: Started by user Eyal Edri ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #27 [Eyal Edri] adding dashboard 4.1 to build from master [Gil Shinar] Fix some more issues with SDK [Gil Shinar] Some missing 4.1 in experimental ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_80_866150003.1483442183753--

1 1

[JIRA] (OVIRT-1000) Java SDK 4.1 branch don't execute jenkins jobs
by eyal edri [Administrator] (oVirt JIRA) 03 Jan '17

03 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1000?page=com.atlassian.jira.… ] eyal edri [Administrator] commented on OVIRT-1000: -------------------------------------------------- [~juan@redhat.com][~omachace@redhat.com] we have too many hacks right now to make SDK work on the same repos for V3 and V4. We can't continue to do it as you see it generate problems. We need to decide on a split of repos so each project will have its own repo ( it already has its own name and differnet rpm version ). otherwise we're bound to keep hitting issues with this setup. > Java SDK 4.1 branch don't execute jenkins jobs > ---------------------------------------------- > > Key: OVIRT-1000 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1000 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins > Reporter: Ondra Machacek > Assignee: infra > > Jenkins job are not still executed from sdk_4.1 branch of the Java SDK project, > you can see an example here: https://gerrit.ovirt.org/#/c/69455/1 > I've created a patch[1] which I think should fix build-artifacts job, not sure about check-patch job. > [1] https://gerrit.ovirt.org/#/c/69459/ -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-990) Re: Gerrit don't check for "Signed-Off" anymore
by eyal edri [Administrator] (oVirt JIRA) 03 Jan '17

03 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-990?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-990: -------------------------------------------- Resolution: Fixed Status: Done (was: To Do) > Re: Gerrit don't check for "Signed-Off" anymore > ----------------------------------------------- > > Key: OVIRT-990 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-990 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: eyal edri [Administrator] > Assignee: Shlomo Ben David > > On Wed, Dec 28, 2016 at 11:42 AM, Tal Nisan <tnisan(a)redhat.com> wrote: > > Last night I've push a serious of patches and forgot to sign off, up until > > not long ago there was a hook that enforces that but it seems like it's not > > working anymore and I was able to push the patches without the sign off: > > https://gerrit.ovirt.org/#/c/69219/1 > > > > > Its not a hook, its a definition per project, each project has the > defenition if to enforce signed-off commit: > 'Require Signed-off-by in commit message:' - and its on TRUE now for > ovirt-engine, so I'm not sure how its possible that a patch got in, we'll > need to check gerrit logs to see. > Opening a ticket on it. > > > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > > > -- > Eyal Edri > Associate Manager > RHV DevOps > EMEA ENG Virtualization R&D > Red Hat Israel > phone: +972-9-7692018 > irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-990) Re: Gerrit don't check for "Signed-Off" anymore
by Tal Nisan (oVirt JIRA) 03 Jan '17

03 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-990?page=com.atlassian.jira.p… ] Tal Nisan commented on OVIRT-990: --------------------------------- Tested yesterday and it seems to be working OK, can close On Tue, Jan 3, 2017 at 9:56 AM, eyal edri [Administrator] (oVirt JIRA) < > Re: Gerrit don't check for "Signed-Off" anymore > ----------------------------------------------- > > Key: OVIRT-990 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-990 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: eyal edri [Administrator] > Assignee: Shlomo Ben David > > On Wed, Dec 28, 2016 at 11:42 AM, Tal Nisan <tnisan(a)redhat.com> wrote: > > Last night I've push a serious of patches and forgot to sign off, up until > > not long ago there was a hook that enforces that but it seems like it's not > > working anymore and I was able to push the patches without the sign off: > > https://gerrit.ovirt.org/#/c/69219/1 > > > > > Its not a hook, its a definition per project, each project has the > defenition if to enforce signed-off commit: > 'Require Signed-off-by in commit message:' - and its on TRUE now for > ovirt-engine, so I'm not sure how its possible that a patch got in, we'll > need to check gerrit logs to see. > Opening a ticket on it. > > > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > > > -- > Eyal Edri > Associate Manager > RHV DevOps > EMEA ENG Virtualization R&D > Red Hat Israel > phone: +972-9-7692018 > irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-1000) Java SDK 4.1 branch don't execute jenkins jobs
by Ondra Machacek (oVirt JIRA) 03 Jan '17

03 Jan '17

Ondra Machacek created OVIRT-1000: ------------------------------------- Summary: Java SDK 4.1 branch don't execute jenkins jobs Key: OVIRT-1000 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1000 Project: oVirt - virtualization made easy Issue Type: Bug Components: Jenkins Reporter: Ondra Machacek Assignee: infra Jenkins job are not still executed from sdk_4.1 branch of the Java SDK project, you can see an example here: https://gerrit.ovirt.org/#/c/69455/1 I've created a patch[1] which I think should fix build-artifacts job, not sure about check-patch job. [1] https://gerrit.ovirt.org/#/c/69459/ -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-999) experimental 4.1 tests work even though rpms where missing from repos
by eyal edri [Administrator] (oVirt JIRA) 03 Jan '17

03 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-999?page=com.atlassian.jira.p… ] eyal edri [Administrator] reassigned OVIRT-999: ----------------------------------------------- Assignee: Daniel Belenky (was: infra) > experimental 4.1 tests work even though rpms where missing from repos > --------------------------------------------------------------------- > > Key: OVIRT-999 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-999 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: eyal edri [Administrator] > Assignee: Daniel Belenky > Priority: Highest > > We need to find out why experimetnal flow 4.1 worked although it had missing RPMs. > My guess is that repoman is using latest-snapshot to complete missing rpms, > we need to stop taking rpms from snapshot repos and only take from snapshot static -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-999) experimental 4.1 tests work even though rpms where missing from repos
by eyal edri [Administrator] (oVirt JIRA) 03 Jan '17

03 Jan '17

eyal edri [Administrator] created OVIRT-999: ----------------------------------------------- Summary: experimental 4.1 tests work even though rpms where missing from repos Key: OVIRT-999 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-999 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: eyal edri [Administrator] Assignee: infra Priority: Highest We need to find out why experimetnal flow 4.1 worked although it had missing RPMs. My guess is that repoman is using latest-snapshot to complete missing rpms, we need to stop taking rpms from snapshot repos and only take from snapshot static -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-999) experimental 4.1 tests work even though rpms where missing from repos
by eyal edri [Administrator] (oVirt JIRA) 03 Jan '17

03 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-999?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-999: -------------------------------------------- Epic Link: OVIRT-400 > experimental 4.1 tests work even though rpms where missing from repos > --------------------------------------------------------------------- > > Key: OVIRT-999 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-999 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: eyal edri [Administrator] > Assignee: infra > Priority: Highest > > We need to find out why experimetnal flow 4.1 worked although it had missing RPMs. > My guess is that repoman is using latest-snapshot to complete missing rpms, > we need to stop taking rpms from snapshot repos and only take from snapshot static -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

Re: vdsm ppc64 build fails
by Eyal Edri 03 Jan '17

03 Jan '17

Adding Danken, We currently don't have ppc64le builds for vdsm 4.1 due to this. On Sun, Dec 25, 2016 at 4:54 PM, Karanbir Singh <kbsingh(a)karan.org> wrote: > Altarch contet is released to http://mirror.centos.org/altarch > > Regards > > > On 25 December 2016 14:26:25 GMT+00:00, Eyal Edri <eedri(a)redhat.com> > wrote: >> >> Can you help with links to the alterarch so we can use them in the >> meantime? >> >> On Sun, Dec 25, 2016 at 3:50 PM, Karanbir Singh <kbsingh(a)karan.org> >> wrote: >> >>> We pushed ppc64le altarch 2 days back. I dont believe the SIG content os >>> there as yet. Just getting the arch's content lined up into cbs has proven >>> to be a challenge. >>> >>> Regards >>> >>> >>> On 25 December 2016 13:21:27 GMT+00:00, Sandro Bonazzola < >>> sbonazzo(a)redhat.com> wrote: >>>> >>>> Ppc64le is on altarch not on centos subdirectory. About the virt sig >>>> packages adding Karanbir, afaik both ppc64le and aarch64 are not yet pushed >>>> to mirrors. >>>> >>>> Il 25/Dic/2016 01:40 PM, "Eyal Edri" <eedri(a)redhat.com> ha scritto: >>>> >>>>> missing ppc64le repo on centos: >>>>> >>>>> DEBUG util.py:421: http://mirror.centos.org/cento >>>>> s/7/virt/ppc64le/ovirt-4.0/repodata/repomd.xml: [Errno 14] HTTP Error >>>>> 404 - Not Found >>>>> >>>>> If there is an alternate repo, please update it on >>>>> automation/.packages files in vdsm repo. >>>>> >>>>> -- >>>>> Eyal Edri >>>>> Associate Manager >>>>> RHV DevOps >>>>> EMEA ENG Virtualization R&D >>>>> Red Hat Israel >>>>> >>>>> phone: +972-9-7692018 <+972%209-769-2018> >>>>> irc: eedri (on #tlv #rhev-dev #rhev-integ) >>>>> >>>> >> >> >> -- >> Eyal Edri >> Associate Manager >> RHV DevOps >> EMEA ENG Virtualization R&D >> Red Hat Israel >> >> phone: +972-9-7692018 <+972%209-769-2018> >> irc: eedri (on #tlv #rhev-dev #rhev-integ) >> > -- Eyal Edri Associate Manager RHV DevOps EMEA ENG Virtualization R&D Red Hat Israel phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)

2 2

[JIRA] (OVIRT-956) trigger jobs on jenkins
by eyal edri [Administrator] (oVirt JIRA) 03 Jan '17

03 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-956?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-956: -------------------------------------------- Resolution: Fixed Status: Done (was: To Do) > trigger jobs on jenkins > ----------------------- > > Key: OVIRT-956 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-956 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Yuval Turgeman > Assignee: infra > > Hi, > Can I please get permissions to trigger jobs in jenkin ? > I need to trigger this one: > http://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.0-pre_build-artifacts-… > Thanks, > Yuval. -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-985) Fix the way repoman deploy to experimental
by eyal edri [Administrator] (oVirt JIRA) 03 Jan '17

03 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-985?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-985: -------------------------------------------- Resolution: Cannot Reproduce Status: Done (was: To Do) since we don't have link to the failing job, we'll need to wait until next time it happens. > Fix the way repoman deploy to experimental > ------------------------------------------ > > Key: OVIRT-985 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-985 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Gil Shinar > Assignee: infra > > Please consult with Eyal on that. > No idea what should be done. -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-990) Re: Gerrit don't check for "Signed-Off" anymore
by eyal edri [Administrator] (oVirt JIRA) 03 Jan '17

03 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-990?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-990: ------------------------------------------------- [~tnisan(a)redhat.com] any open issues still or we can close this? > Re: Gerrit don't check for "Signed-Off" anymore > ----------------------------------------------- > > Key: OVIRT-990 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-990 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: eyal edri [Administrator] > Assignee: Shlomo Ben David > > On Wed, Dec 28, 2016 at 11:42 AM, Tal Nisan <tnisan(a)redhat.com> wrote: > > Last night I've push a serious of patches and forgot to sign off, up until > > not long ago there was a hook that enforces that but it seems like it's not > > working anymore and I was able to push the patches without the sign off: > > https://gerrit.ovirt.org/#/c/69219/1 > > > > > Its not a hook, its a definition per project, each project has the > defenition if to enforce signed-off commit: > 'Require Signed-off-by in commit message:' - and its on TRUE now for > ovirt-engine, so I'm not sure how its possible that a patch got in, we'll > need to check gerrit logs to see. > Opening a ticket on it. > > > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > > > -- > Eyal Edri > Associate Manager > RHV DevOps > EMEA ENG Virtualization R&D > Red Hat Israel > phone: +972-9-7692018 > irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

The big "submit everything in branch" button you wanted.
by Barak Korren 03 Jan '17

03 Jan '17

Turns out that the button you wanted to submit all the related patches at the same time, exists and shows up automatically if all the patches in the series got the necessary +2s. This will only work for repos that are configured to "Rebase if Necessary". -- Barak Korren bkorren(a)redhat.com RHCE, RHCi, RHV-DevOps Team https://ifireball.wordpress.com/

1 0

[JIRA] (OVIRT-998) Re: Enable Github gh-pages for project ovirt-engine-api-model
by eyal edri [Administrator] (oVirt JIRA) 03 Jan '17

03 Jan '17

eyal edri [Administrator] created OVIRT-998: ----------------------------------------------- Summary: Re: Enable Github gh-pages for project ovirt-engine-api-model Key: OVIRT-998 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-998 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: eyal edri [Administrator] Assignee: infra Sending ticket to infra-support. Pavel - let me know if you need help, its just clicking on the gh-pages generate button on GitHub ( last time we did it for SDK ) On Mon, Jan 2, 2017 at 11:43 PM, Juan Hernández <jhernand(a)redhat.com> wrote: > Hello, > > In order to have a public and stable location for the documentation of > the API I would like to start using the Github gh-pages mechanism. I > have already created a 'gh-pages' branch in the 'ovirt-engine-api-model' > project, and merged to that branch the first version of the > documentation. The next step is to enable the use of that 'gh-pages' > branch as the source of the documentation in the settins of that > project. But that needs to be done by an administrator of the oVirt > organization. Would you be so kind to do that? > > Thanks in advance, > Juan Hernandez > _______________________________________________ > Infra mailing list > Infra(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/infra > > > -- Eyal Edri Associate Manager RHV DevOps EMEA ENG Virtualization R&D Red Hat Israel phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0