June 2019 - Infra - oVirt List Archives

[Ovirt] [CQ weekly status] [28-06-2019]
by Dafna Ron 28 Jun '19

28 Jun '19

This mail is to provide the current status of CQ and allow people to review status before and after the weekend. Please refer to below colour map for further information on the meaning of the colours. *CQ-4.2*: GREEN (#1) Last failure was on 28-06 for mom due to failed test: 002_bootstrap.add_master_storage_domain. this is a known issue which has a fix which was probably not added to the upgrade suite. I re-triggered the change to see if it passes *CQ-4.3*: GREEN (#2) Last failure was on 27-06-2019 for project ovirt-web-ui due to test get_host_device which seemed to be a race. I re-triggered the patch and it passed. *CQ-Master:* GREEN (#1) Last failure was on 28-06-3019 for project ovirt-node-ng-image on build-artifacts for fc29 There is a ticket opened https://ovirt-jira.atlassian.net/browse/OVIRT-2747 Current running jobs for 4.2 [1], 4.3 [2] and master [3] can be found here: [1] http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.2_change-qu… [2] https://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.3_change-q… [3] http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-master_change… Happy week! Dafna ------------------------------------------------------------------------------------------------------------------- COLOUR MAP Green = job has been passing successfully ** green for more than 3 days may suggest we need a review of our test coverage 1. 1-3 days GREEN (#1) 2. 4-7 days GREEN (#2) 3. Over 7 days GREEN (#3) Yellow = intermittent failures for different projects but no lasting or current regressions ** intermittent would be a healthy project as we expect a number of failures during the week ** I will not report any of the solved failures or regressions. 1. Solved job failures YELLOW (#1) 2. Solved regressions YELLOW (#2) Red = job has been failing ** Active Failures. The colour will change based on the amount of time the project/s has been broken. Only active regressions would be reported. 1. 1-3 days RED (#1) 2. 4-7 days RED (#2) 3. Over 7 days RED (#3)

1 0

[CQ]: 101299,3 (mom) failed "ovirt-4.2" system tests
by oVirt Jenkins 28 Jun '19

28 Jun '19

Change 101299,3 (mom) is probably the reason behind recent system test failures in the "ovirt-4.2" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/101299/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/4577/

1 0

[CQ]: 101016, 2 (ovirt-node-ng-image) failed "ovirt-master" system tests
by oVirt Jenkins 28 Jun '19

28 Jun '19

Change 101016,2 (ovirt-node-ng-image) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/101016/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/14768/

1 0

[JIRA] (OVIRT-2747) Failed to synchronize cache for repo 'mock-copr-fc29', ignoring this repo
by Evgheni Dereveanchin (oVirt JIRA) 28 Jun '19

28 Jun '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2747?page=com.atlassian.jira.… ] Evgheni Dereveanchin commented on OVIRT-2747: --------------------------------------------- Looking at the sync job it seems to error out even though it is marked as successful: [https://jenkins.ovirt.org/job/system-sync_mirrors-mock-copr-fc29-x86_64/113…] {code}13:00:16 + reposync_out='Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64 error was 13:00:16 14: curl#35 - "TCP connection reset by peer"' 13:00:16 + [[ -n Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64 error was 13:00:16 14: curl#35 - "TCP connection reset by peer" ]]{code} Not sure if this behavior causes any kind of repo corruption. > Failed to synchronize cache for repo 'mock-copr-fc29', ignoring this repo > ------------------------------------------------------------------------- > > Key: OVIRT-2747 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2747 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Evgheni Dereveanchin > Assignee: infra > > I see this error pop out in logs: > Failed to synchronize cache for repo 'mock-copr-fc29', ignoring this repo. > Looks like a corrupted repo so it should either be fixed or removed from the configuration. > Sample job: > https://jenkins.ovirt.org/job/vdsm_standard-check-patch/7126/consoleFull -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100105)

1 0

[JIRA] (OVIRT-2747) Failed to synchronize cache for repo 'mock-copr-fc29', ignoring this repo
by Evgheni Dereveanchin (oVirt JIRA) 28 Jun '19

28 Jun '19

Evgheni Dereveanchin created OVIRT-2747: ------------------------------------------- Summary: Failed to synchronize cache for repo 'mock-copr-fc29', ignoring this repo Key: OVIRT-2747 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2747 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Evgheni Dereveanchin Assignee: infra I see this error pop out in logs: Failed to synchronize cache for repo 'mock-copr-fc29', ignoring this repo. Looks like a corrupted repo so it should either be fixed or removed from the configuration. Sample job: https://jenkins.ovirt.org/job/vdsm_standard-check-patch/7126/consoleFull -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100105)

1 0

oVirt infra daily report - unstable production jobs - 869
by jenkins＠jenkins.phx.ovirt.org 28 Jun '19

28 Jun '19

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/869//artifact/exported-a… Cheers, Jenkins

1 0

[CQ]: f30eb54 (ovirt-web-ui) failed "ovirt-4.3" system tests
by oVirt Jenkins 27 Jun '19

27 Jun '19

Change f30eb54 (ovirt-web-ui) is probably the reason behind recent system test failures in the "ovirt-4.3" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://github.com/oVirt/ovirt-web-ui/commit/f30eb543d20862dc8cb2bac4d5038e… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/1370/

1 0

Change in stage-stdci1[master]: Make the zuul 'tree' job run on the oVirt nodes
by review＠gerrit-staging.phx.ovirt.org 27 Jun '19

27 Jun '19

From Barak Korren <bkorren(a)redhat.com>: Hello Jenkins CI, Zuul CI, I'd like you to reexamine a change. Please visit https://gerrit-staging.phx.ovirt.org/254 to look at the new patch set (#4). Change subject: Make the zuul 'tree' job run on the oVirt nodes ...................................................................... Make the zuul 'tree' job run on the oVirt nodes Change-Id: Id669ab1105852f158260f719db12dad423e1f986 Signed-off-by: Barak Korren <bkorren(a)redhat.com> --- M .zuul.yaml M automation/playbooks/tree.yaml 2 files changed, 16 insertions(+), 1 deletion(-) git pull ssh://gerrit-staging.phx.ovirt.org:29418/stage-stdci1 refs/changes/54/254/4 -- To view, visit https://gerrit-staging.phx.ovirt.org/254 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-Project: stage-stdci1 Gerrit-Branch: master Gerrit-MessageType: newpatchset Gerrit-Change-Id: Id669ab1105852f158260f719db12dad423e1f986 Gerrit-Change-Number: 254 Gerrit-PatchSet: 4 Gerrit-Owner: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org> Gerrit-Reviewer: Zuul CI <zuul(a)ovirt.org>

1 0

Change in stage-stdci1[master]: Make the zuul 'tree' job run on the oVirt nodes
by review＠gerrit-staging.phx.ovirt.org 27 Jun '19

27 Jun '19

From Barak Korren <bkorren(a)redhat.com>: Hello Jenkins CI, Zuul CI, I'd like you to reexamine a change. Please visit https://gerrit-staging.phx.ovirt.org/254 to look at the new patch set (#3). Change subject: Make the zuul 'tree' job run on the oVirt nodes ...................................................................... Make the zuul 'tree' job run on the oVirt nodes Change-Id: Id669ab1105852f158260f719db12dad423e1f986 Signed-off-by: Barak Korren <bkorren(a)redhat.com> --- M .zuul.yaml 1 file changed, 14 insertions(+), 0 deletions(-) git pull ssh://gerrit-staging.phx.ovirt.org:29418/stage-stdci1 refs/changes/54/254/3 -- To view, visit https://gerrit-staging.phx.ovirt.org/254 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-Project: stage-stdci1 Gerrit-Branch: master Gerrit-MessageType: newpatchset Gerrit-Change-Id: Id669ab1105852f158260f719db12dad423e1f986 Gerrit-Change-Number: 254 Gerrit-PatchSet: 3 Gerrit-Owner: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org> Gerrit-Reviewer: Zuul CI <zuul(a)ovirt.org>

1 0

[JIRA] (OVIRT-2746) jenkins job failing to contact proxy
by Anton Marchukov (oVirt JIRA) 27 Jun '19

27 Jun '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2746?page=com.atlassian.jira.… ] Anton Marchukov reassigned OVIRT-2746: -------------------------------------- Assignee: sbonazzo (was: infra) > jenkins job failing to contact proxy > ------------------------------------ > > Key: OVIRT-2746 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2746 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: sbonazzo > > "Failed to contact proxy http://proxy01.phx.ovirt.org:3128, falling back to > non-proxied config" > seen in > https://jenkins.ovirt.org/job/ovirt-release_master_build-artifacts-fcraw-x8… > maybe the proxy is down? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100105)

1 0