June 2017 - Infra - oVirt List Archives

oVirt infra daily report - unstable production jobs - 364
by jenkins＠jenkins.phx.ovirt.org 26 Jun '17

26 Jun '17

------=_Part_816_1564398414.1498431603063 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/364//artifact/exported-a… Cheers, Jenkins ------=_Part_816_1564398414.1498431603063 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 - 25/06/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/ovirt_4.1_hc-system-tests/">ovirt_4.1_hc-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_master_hc-system-tests/">ovirt_master_hc-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> ------=_Part_816_1564398414.1498431603063--

1 0

[oVirt Jenkins] standard-enqueue - Build #1969 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 25 Jun '17

25 Jun '17

------=_Part_808_1848448626.1498415651160 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/standard-enqueue/1969/ Build Name: 1969 vdsm (master) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/78547 - title: place dhclientmon.sh under static - project: vdsm - branch: master - author: Dan Kenigsberg <danken(a)redhat.com> ------=_Part_808_1848448626.1498415651160--

1 0

[JIRA] (OVIRT-1415) Add more FC26 slaves
by ngoldin＠redhat.com (oVirt JIRA) 25 Jun '17

25 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1415?page=com.atlassian.jira.… ] ngoldin(a)redhat.com commented on OVIRT-1415: ------------------------------------------- This also affects Lago - as currently fc26 is our only way to test compatibility with libvirt 3.x. > Add more FC26 slaves > -------------------- > > Key: OVIRT-1415 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1415 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Barak Korren > Assignee: infra > > We only have one ATM, this means that many jobs need to wait in queue for it. > Please add more. -- This message was sent by Atlassian JIRA (v1000.1085.0#100052)

1 0

[JIRA] (OVIRT-1478) Fix 'mock_runner.sh' on FC26
by Barak Korren (oVirt JIRA) 25 Jun '17

25 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1478?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1478: ----------------------------------- Assignee: Barak Korren (was: infra) > Fix 'mock_runner.sh' on FC26 > ---------------------------- > > Key: OVIRT-1478 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1478 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: Barak Korren > Priority: Highest > > All mock_runner.sh runs on FC26 are failing, we need to investigate and fix. -- This message was sent by Atlassian JIRA (v1000.1085.0#100052)

1 0

[JIRA] (OVIRT-1478) Fix 'mock_runner.sh' on FC26
by Barak Korren (oVirt JIRA) 25 Jun '17

25 Jun '17

Barak Korren created OVIRT-1478: ----------------------------------- Summary: Fix 'mock_runner.sh' on FC26 Key: OVIRT-1478 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1478 Project: oVirt - virtualization made easy Issue Type: Improvement Components: oVirt CI Reporter: Barak Korren Assignee: infra Priority: Highest All mock_runner.sh runs on FC26 are failing, we need to investigate and fix. -- This message was sent by Atlassian JIRA (v1000.1085.0#100052)

1 0

[JIRA] (OVIRT-1478) Fix 'mock_runner.sh' on FC26
by Barak Korren (oVirt JIRA) 25 Jun '17

25 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1478?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1478: -------------------------------- Epic Link: OVIRT-400 > Fix 'mock_runner.sh' on FC26 > ---------------------------- > > Key: OVIRT-1478 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1478 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Priority: Highest > > All mock_runner.sh runs on FC26 are failing, we need to investigate and fix. -- This message was sent by Atlassian JIRA (v1000.1085.0#100052)

1 0

[JIRA] (OVIRT-1475) Check why http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_64/447/ wasn't time triggered for months
by Yuval Turgeman (oVirt JIRA) 25 Jun '17

25 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1475?page=com.atlassian.jira.… ] Yuval Turgeman commented on OVIRT-1475: --------------------------------------- Yes, [~eedri] is right, I think the deletion messed up lastSuccessful, making it point to some old version. However, using the rpm would mean a bigger change, and it would take a little more time to run (extract the rpm etc). I think that the best way to fix this, is to copy the squashfs from its original place to the exported-artifacts dir with a timestamp, so instead of cp <squashfs> exported-artifacts, it would be something like cp squashfs exported-artifacts/squashfs-<builddate>, and let image-ng continue to pick up the squashfs by a build number. > Check why http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_6… wasn't time triggered for months > ---------------------------------------------------------------------------------------------------------------------------- > > Key: OVIRT-1475 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1475 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: eedri > Assignee: infra > Priority: High > > The follow job http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_6… is defined to run nightly (00 04 * * *) but for some reason didn't run for 9 months(!). > We need to investigate why it didn't run and maybe find some clues in the logs. > cc [~sbonazzo(a)redhat.com] -- This message was sent by Atlassian JIRA (v1000.1085.0#100052)

1 0

[JIRA] (OVIRT-1475) Check why http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_64/447/ wasn't time triggered for months
by eedri (oVirt JIRA) 25 Jun '17

25 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1475?page=com.atlassian.jira.… ] eedri commented on OVIRT-1475: ------------------------------ I think the problem was that image_ng suite was talking the last successful build from Jenkins, and because most of the jobs were deleted, it took an older build instead of latest. We can't verify it because the current image_ng suite takes the squashfs image, which doesn't have a datestamp, so we can't know for sure which image was tested in the suite. I believe [~yturgema(a)redhat.com] is checking an option to change that to take the RPMs instead, so we'll know exactly which image was tested. So, in regards to this ticket, we need to find out why the jobs were deleted and make sure we are taking steps to prevent it happening in the future, even if we're out of space, we should probably setup long history of builds while keeping a shorter history of artifacts if possible. > Check why http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_6… wasn't time triggered for months > ---------------------------------------------------------------------------------------------------------------------------- > > Key: OVIRT-1475 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1475 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: eedri > Assignee: infra > Priority: High > > The follow job http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_6… is defined to run nightly (00 04 * * *) but for some reason didn't run for 9 months(!). > We need to investigate why it didn't run and maybe find some clues in the logs. > cc [~sbonazzo(a)redhat.com] -- This message was sent by Atlassian JIRA (v1000.1085.0#100052)

1 0

[JIRA] (OVIRT-1475) Check why http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_64/447/ wasn't time triggered for months
by eedri (oVirt JIRA) 25 Jun '17

25 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1475?page=com.atlassian.jira.… ] eedri commented on OVIRT-1475: ------------------------------ It looks like the job was running all the time ( full logs can be found on the Jenkins server, under /var/log/jenkins), here is the log from this month [1]. [~ederevea] is it possible the jobs were deleted from Jenkins during the latest space cleanup? [1] jenkins.log-20170601.gz:INFO: ovirt-node-ng_master_build-artifacts-el7-x86_64 #425 main build action completed: SUCCESS jenkins.log-20170602.gz:INFO: ovirt-node-ng_master_build-artifacts-el7-x86_64 #426 main build action completed: SUCCESS jenkins.log-20170603.gz:INFO: ovirt-node-ng_master_build-artifacts-el7-x86_64 #427 main build action completed: SUCCESS jenkins.log-20170605.gz:INFO: ovirt-node-ng_master_build-artifacts-el7-x86_64 #429 main build action completed: SUCCESS jenkins.log-20170606.gz:INFO: ovirt-node-ng_master_build-artifacts-el7-x86_64 #430 main build action completed: SUCCESS jenkins.log-20170607.gz:INFO: ovirt-node-ng_master_build-artifacts-el7-x86_64 #431 main build action completed: SUCCESS jenkins.log-20170608.gz:INFO: ovirt-node-ng_master_build-artifacts-el7-x86_64 #432 main build action completed: SUCCESS jenkins.log-20170609.gz:INFO: ovirt-node-ng_master_build-artifacts-el7-x86_64 #433 main build action completed: SUCCESS jenkins.log-20170610.gz:INFO: ovirt-node-ng_master_build-artifacts-el7-x86_64 #434 main build action completed: SUCCESS jenkins.log-20170612.gz:INFO: ovirt-node-ng_master_build-artifacts-el7-x86_64 #436 main build action completed: SUCCESS jenkins.log-20170613.gz:INFO: ovirt-node-ng_master_build-artifacts-el7-x86_64 #437 main build action completed: SUCCESS jenkins.log-20170614.gz:INFO: ovirt-node-ng_master_build-artifacts-el7-x86_64 #438 main build action completed: SUCCESS jenkins.log-20170615.gz:INFO: ovirt-node-ng_master_build-artifacts-el7-x86_64 #439 main build action completed: SUCCESS jenkins.log-20170616.gz:INFO: ovirt-node-ng_master_build-artifacts-el7-x86_64 #440 main build action completed: SUCCESS jenkins.log-20170617.gz:INFO: ovirt-node-ng_master_build-artifacts-el7-x86_64 #441 main build action completed: SUCCESS jenkins.log-20170619.gz:INFO: ovirt-node-ng_master_build-artifacts-el7-x86_64 #443 main build action completed: SUCCESS jenkins.log-20170620.gz:INFO: ovirt-node-ng_master_build-artifacts-el7-x86_64 #444 main build action completed: SUCCESS jenkins.log-20170621.gz:INFO: ovirt-node-ng_master_build-artifacts-el7-x86_64 #445 main build action completed: SUCCESS jenkins.log-20170623.gz:INFO: ovirt-node-ng_master_build-artifacts-el7-x86_64 #447 main build action completed: SUCCESS jenkins.log-20170624.gz:INFO: ovirt-node-ng_master_build-artifacts-el7-x86_64 #448 main build action completed: SUCCESS jenkins.log-20170624.gz:INFO: ovirt-node-ng_master_build-artifacts-el7-x86_64 #449 main build action completed: SUCCESS cc [~yturgema(a)redhat.com] > Check why http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_6… wasn't time triggered for months > ---------------------------------------------------------------------------------------------------------------------------- > > Key: OVIRT-1475 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1475 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: eedri > Assignee: infra > Priority: High > > The follow job http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_6… is defined to run nightly (00 04 * * *) but for some reason didn't run for 9 months(!). > We need to investigate why it didn't run and maybe find some clues in the logs. > cc [~sbonazzo(a)redhat.com] -- This message was sent by Atlassian JIRA (v1000.1085.0#100052)

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #7343 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 25 Jun '17

25 Jun '17

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

1 1