- Infra - oVirt List Archives

[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

[JIRA] (OVIRT-1477) Make 4.1 nightly publisher synce from 'tested' instaed of collecting packages on it own
by Barak Korren (oVirt JIRA) 24 Jun '17

24 Jun '17

Barak Korren created OVIRT-1477: ----------------------------------- Summary: Make 4.1 nightly publisher synce from 'tested' instaed of collecting packages on it own Key: OVIRT-1477 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1477 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Repositories Mgmt Reporter: Barak Korren Assignee: infra The 4.1 nightly publisher jobs are still using the old scheme of collecting packages directly from build-artifacts jobs instead of from 'tested'. We should move them to collect from 'tested' like the 'master' niightly publisher jobs. As part of this work we should re-factor the YAML for the publisher jobs to make all of them use the same YAML job template instead of hard-coded job definitions. -- This message was sent by Atlassian JIRA (v1000.1085.0#100052)

1 0

[JIRA] (OVIRT-1477) Make 4.1 nightly publisher synce from 'tested' instaed of collecting packages on it own
by Barak Korren (oVirt JIRA) 24 Jun '17

24 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1477?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1477: -------------------------------- Epic Link: OVIRT-400 > Make 4.1 nightly publisher synce from 'tested' instaed of collecting packages on it own > --------------------------------------------------------------------------------------- > > Key: OVIRT-1477 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1477 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Repositories Mgmt > Reporter: Barak Korren > Assignee: infra > > The 4.1 nightly publisher jobs are still using the old scheme of collecting packages directly from build-artifacts jobs instead of from 'tested'. We should move them to collect from 'tested' like the 'master' niightly publisher jobs. > As part of this work we should re-factor the YAML for the publisher jobs to make all of them use the same YAML job template instead of hard-coded job definitions. -- This message was sent by Atlassian JIRA (v1000.1085.0#100052)

1 0

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

24 Jun '17

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

1 1

[oVirt Jenkins] ovirt-node-ng_ovirt-4.1-pre_build-artifacts-el7-x86_64 - Build # 260 - Failure!
by jenkins＠jenkins.phx.ovirt.org 24 Jun '17

24 Jun '17

------=_Part_765_626085193.1498276809535 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.1-pre_build-artifacts-el… Build: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.1-pre_build-artifacts-el… Build Number: 260 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #260 ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_765_626085193.1498276809535--

1 1

[oVirt Jenkins] ovirt-node-ng_ovirt-4.1_build-artifacts-el7-x86_64 - Build # 167 - Failure!
by jenkins＠jenkins.phx.ovirt.org 24 Jun '17

24 Jun '17

------=_Part_761_1311727970.1498276808226 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.1_build-artifacts-el7-x8… Build: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.1_build-artifacts-el7-x8… Build Number: 167 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #167 ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_761_1311727970.1498276808226--

1 1

[oVirt Jenkins] ovirt-node-ng_ovirt-4.1-snapshot_build-artifacts-el7-x86_64 - Build # 169 - Failure!
by jenkins＠jenkins.phx.ovirt.org 24 Jun '17

24 Jun '17

------=_Part_763_1469445831.1498276808654 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.1-snapshot_build-artifac… Build: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.1-snapshot_build-artifac… Build Number: 169 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #169 ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_763_1469445831.1498276808654--

1 1