June 2019 - Infra - oVirt List Archives

what is a telecommunications job
by kumarfield28＠gmail.com 23 Sep '19

23 Sep '19

These days, you will often come across telecommunication field technician jobs on the internet and newspapers. This must have gotten you curious regarding telecom engineer jobs. You might be wondering whether it would be the right career option for you and what kind of telecom services you will need to provide if this is the field you opt for. If that is the case, this is where your search culminates since we will provide you with the required details regarding telecom engineer jobs and services among other things. https://www.fieldengineer.com/blogs/telecom-engineer-job-description/

3 2

[oVirt CI] standard-enqueue - Build #17451 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 24 Jul '19

24 Jul '19

Build: http://jenkins.ovirt.org/job/standard-enqueue/17451/ Build Name: #17451 Build Description: Gerrit: 95261 - ovirt-vmconsole (4.1, 4.2, master) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/95261 - title: build: Fix build broken on Fedora - project: ovirt-vmconsole - branch: master - author: Tomasz Baranski <tbaransk(a)redhat.com>

2 1

[oVirt Jenkins] ovirt-release_master_build-artifacts-fcraw-x86_64 - Build # 149 - Failure!
by jenkins＠jenkins.phx.ovirt.org 03 Jul '19

03 Jul '19

Project: http://jenkins.ovirt.org/job/ovirt-release_master_build-artifacts-fcraw-x86… Build: http://jenkins.ovirt.org/job/ovirt-release_master_build-artifacts-fcraw-x86… Build Number: 149 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #149 [Eyal Edri] add cthao(a)redhat.com [Sandro Bonazzola] fc29: add gluster-6 fedora 29 repo ----------------- Failed Tests: ----------------- No tests ran.

1 15

Storage test case needs to be fixed: 002_bootstrap.resize_and_refresh_storage_domain
by Dafna Ron 02 Jul '19

02 Jul '19

Hi Tal, I am seeing random failures for test 002_bootstrap.resize_and_refresh_storage_domain It looks like this is a timing issue since by the time we print out the error we actually see the resize succeeded. see example below: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/14185/testRep… Can you please assign someone from the storage team to fix this test? Thanks, Dafna

4 14

[CQ]: 101190,12 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 01 Jul '19

01 Jul '19

Change 101190,12 (ovirt-engine) 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/101190/12 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/14773/

2 1

oVirt infra daily report - unstable production jobs - 872
by jenkins＠jenkins.phx.ovirt.org 01 Jul '19

01 Jul '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/872//artifact/exported-a… Cheers, Jenkins

1 0

[CQ]: 101184,4 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 01 Jul '19

01 Jul '19

Change 101184,4 (vdsm) 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/101184/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/14793/

1 0

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

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

1 0

[CQ]: 99792,4 (ioprocess) failed "ovirt-master" system tests
by oVirt Jenkins 29 Jun '19

29 Jun '19

Change 99792,4 (ioprocess) 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/99792/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/14780/

1 0

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

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

1 0

[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

[CQ]: 101274, 2 (otopi) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 27 Jun '19

27 Jun '19

A system test invoked by the "ovirt-master" change queue including change 101274,2 (otopi) failed. However, this change seems not to be the root cause for this failure. Change 101155,3 (otopi) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 101155,3 (otopi) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/101274/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/101155/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/14757/

1 0

[CQ]: 101274, 2 (otopi) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 27 Jun '19

27 Jun '19

A system test invoked by the "ovirt-master" change queue including change 101274,2 (otopi) failed. However, this change seems not to be the root cause for this failure. Change 101155,3 (otopi) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 101155,3 (otopi) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/101274/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/101155/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/14756/

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 (#2). 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, 6 insertions(+), 0 deletions(-) git pull ssh://gerrit-staging.phx.ovirt.org:29418/stage-stdci1 refs/changes/54/254/2 -- 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: 2 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

[CQ]: 101068,3 (vdsm) failed "ovirt-4.3" system tests
by oVirt Jenkins 27 Jun '19

27 Jun '19

Change 101068,3 (vdsm) 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://gerrit.ovirt.org/#/c/101068/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/1366/

1 0

[CQ]: 101274, 2 (otopi) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 27 Jun '19

27 Jun '19

A system test invoked by the "ovirt-master" change queue including change 101274,2 (otopi) failed. However, this change seems not to be the root cause for this failure. Change 101155,3 (otopi) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 101155,3 (otopi) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/101274/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/101155/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/14752/

1 0

[CQ]: 100994, 3 (otopi) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 27 Jun '19

27 Jun '19

A system test invoked by the "ovirt-master" change queue including change 100994,3 (otopi) failed. However, this change seems not to be the root cause for this failure. Change 101155,3 (otopi) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 101155,3 (otopi) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/100994/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/101155/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/14751/

1 0

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

27 Jun '19

sbonazzo created OVIRT-2746: ------------------------------- Summary: 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: infra "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

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

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

1 0

[CQ]: 101175, 2 (ovirt-provider-ovn) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 26 Jun '19

26 Jun '19

A system test invoked by the "ovirt-4.2" change queue including change 101175,2 (ovirt-provider-ovn) failed. However, this change seems not to be the root cause for this failure. Change 100733,12 (ovirt-provider-ovn) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 100733,12 (ovirt-provider-ovn) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/101175/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/100733/12 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/4573/

1 0

[CQ]: 101176, 3 (ovirt-provider-ovn) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 26 Jun '19

26 Jun '19

A system test invoked by the "ovirt-4.2" change queue including change 101176,3 (ovirt-provider-ovn) failed. However, this change seems not to be the root cause for this failure. Change 100733,12 (ovirt-provider-ovn) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 100733,12 (ovirt-provider-ovn) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/101176/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/100733/12 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/4572/

1 0

[CQ]: 101200, 2 (ovirt-provider-ovn) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 26 Jun '19

26 Jun '19

A system test invoked by the "ovirt-4.2" change queue including change 101200,2 (ovirt-provider-ovn) failed. However, this change seems not to be the root cause for this failure. Change 100733,12 (ovirt-provider-ovn) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 100733,12 (ovirt-provider-ovn) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/101200/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/100733/12 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/4571/

1 0

[CQ]: 101089,1 (vdsm) failed "ovirt-4.3" system tests
by oVirt Jenkins 26 Jun '19

26 Jun '19

Change 101089,1 (vdsm) 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://gerrit.ovirt.org/#/c/101089/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/1357/

1 0

[CQ]: 101139, 1 (ovirt-log-collector) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 26 Jun '19

26 Jun '19

A system test invoked by the "ovirt-4.3" change queue including change 101139,1 (ovirt-log-collector) failed. However, this change seems not to be the root cause for this failure. Change 101138,1 (ovirt-log-collector) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 101138,1 (ovirt-log-collector) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/101139/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/101138/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/1355/

1 0

[JIRA] (OVIRT-2745) move carla.osci.io to new IP
by Evgheni Dereveanchin (oVirt JIRA) 26 Jun '19

26 Jun '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2745?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-2745: ------------------------------------------- Assignee: Marc Dequènes (Duck) (was: infra) > move carla.osci.io to new IP > ---------------------------- > > Key: OVIRT-2745 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2745 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Evgheni Dereveanchin > Assignee: Marc Dequènes (Duck) > > We were assigned a new guest range in PHX so carla.osci.io needs to be moved. > Current IP: 209.132.185.11 > New IP: 38.145.51.11 > We also need to power cycle this VM to apply platform upgrades so it can be done along with the IP change. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100105)

1 0

[JIRA] (OVIRT-2745) move carla.osci.io to new IP
by Evgheni Dereveanchin (oVirt JIRA) 26 Jun '19

26 Jun '19

Evgheni Dereveanchin created OVIRT-2745: ------------------------------------------- Summary: move carla.osci.io to new IP Key: OVIRT-2745 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2745 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Evgheni Dereveanchin Assignee: infra We were assigned a new guest range in PHX so carla.osci.io needs to be moved. Current IP: 209.132.185.11 New IP: 38.145.51.11 We also need to power cycle this VM to apply platform upgrades so it can be done along with the IP change. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100105)

1 0

Build failed in Jenkins: system-sync_mirrors-fedora-updates-fc29-x86_64 #686
by jenkins＠jenkins.phx.ovirt.org 26 Jun '19

26 Jun '19

1 1

[CQ]: 101155,3 (otopi) failed "ovirt-master" system tests
by oVirt Jenkins 26 Jun '19

26 Jun '19

Change 101155,3 (otopi) 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/101155/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/14731/

3 3

[JIRA] (OVIRT-2742) ovirt-appliance build failure on missing module urllib.request
by sbonazzo (oVirt JIRA) 26 Jun '19

26 Jun '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2742?page=com.atlassian.jira.… ] sbonazzo updated OVIRT-2742: ---------------------------- Assignee: sbonazzo (was: infra) Resolution: Won't Do Status: Done (was: To Do) looks like the issue is that imagefactory moved to python3 and broke support on python 2, closing this ticket, we need to handle this on development side > ovirt-appliance build failure on missing module urllib.request > -------------------------------------------------------------- > > Key: OVIRT-2742 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2742 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: sbonazzo > > *16:16:26* Traceback (most recent call last):*16:16:26* File > "scripts/create_ova.py", line 4, in <module>*16:16:26* from > imagefactory_plugins.ovfcommon.ovfcommon import > RHEVOVFPackage*16:16:26* File > "/home/jenkins/workspace/ovirt-appliance_master_build-artifacts-el7-x86_64/ovirt-appliance/engine-appliance/imagefactory/imagefactory_plugins/ovfcommon/ovfcommon.py", > line 29, in <module>*16:16:26* from imgfac.PersistentImageManager > import PersistentImageManager*16:16:26* File > "/home/jenkins/workspace/ovirt-appliance_master_build-artifacts-el7-x86_64/ovirt-appliance/engine-appliance/imagefactory/imgfac/PersistentImageManager.py", > line 17, in <module>*16:16:26* from .ApplicationConfiguration > import ApplicationConfiguration*16:16:26* File > "/home/jenkins/workspace/ovirt-appliance_master_build-artifacts-el7-x86_64/ovirt-appliance/engine-appliance/imagefactory/imgfac/ApplicationConfiguration.py", > line 24, in <module>*16:16:26* import urllib.request*16:16:26* > ImportError: No module named request > Seen in > https://jenkins.ovirt.org/job/ovirt-appliance_master_build-artifacts-el7-x8… > https://jenkins.ovirt.org/job/ovirt-appliance_4.3_build-artifacts-el7-x86_6… > https://jenkins.ovirt.org/job/ovirt-appliance_4.2_build-artifacts-el7-x86_6… > -- > Sandro Bonazzola > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://www.redhat.com/> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100105)

1 0

[CQ]: 101138,1 (ovirt-log-collector) failed "ovirt-4.3" system tests
by oVirt Jenkins 26 Jun '19

26 Jun '19

Change 101138,1 (ovirt-log-collector) 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://gerrit.ovirt.org/#/c/101138/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/1349/

1 0

[CQ]: 101135,2 (ovirt-iso-uploader) failed "ovirt-4.3" system tests
by oVirt Jenkins 26 Jun '19

26 Jun '19

Change 101135,2 (ovirt-iso-uploader) 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://gerrit.ovirt.org/#/c/101135/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/1343/

1 0

[CQ]: 100734, 10 (ovirt-provider-ovn) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 26 Jun '19

26 Jun '19

A system test invoked by the "ovirt-4.3" change queue including change 100734,10 (ovirt-provider-ovn) failed. However, this change seems not to be the root cause for this failure. Change 100347,18 (ovirt-provider-ovn) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 100347,18 (ovirt-provider-ovn) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/100734/10 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/100347/18 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/1337/

1 0

[CQ]: 170e6b6 (ovirt-engine-sdk-go) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 26 Jun '19

26 Jun '19

A system test invoked by the "ovirt-4.3" change queue including change 170e6b6 (ovirt-engine-sdk-go) failed. However, this change seems not to be the root cause for this failure. Change e09c696 (ovirt-engine-sdk-go) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change e09c696 (ovirt-engine-sdk-go) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://github.com/oVirt/ovirt-engine-sdk-go/commit/170e6b6e906e7c23cf5858d… For further details about the change that seems to be the root cause behind the testing failures see: https://github.com/oVirt/ovirt-engine-sdk-go/commit/e09c69642cf137807bb075d… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/1331/

1 0

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

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

1 0

[CQ]: e09c696 (ovirt-engine-sdk-go) failed "ovirt-4.3" system tests
by oVirt Jenkins 25 Jun '19

25 Jun '19

Change e09c696 (ovirt-engine-sdk-go) 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-engine-sdk-go/commit/e09c69642cf137807bb075d… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/1325/

1 0

[CQ]: 98030, 8 (ovirt-provider-ovn) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 25 Jun '19

25 Jun '19

A system test invoked by the "ovirt-4.2" change queue including change 98030,8 (ovirt-provider-ovn) failed. However, this change seems not to be the root cause for this failure. Change 100733,12 (ovirt-provider-ovn) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 100733,12 (ovirt-provider-ovn) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/98030/8 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/100733/12 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/4565/

1 0

[CQ]: 100659, 6 (ovirt-provider-ovn) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 25 Jun '19

25 Jun '19

A system test invoked by the "ovirt-4.3" change queue including change 100659,6 (ovirt-provider-ovn) failed. However, this change seems not to be the root cause for this failure. Change 100347,18 (ovirt-provider-ovn) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 100347,18 (ovirt-provider-ovn) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/100659/6 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/100347/18 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/1319/

1 0

[CQ]: 100957, 4 (ovirt-provider-ovn) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 25 Jun '19

25 Jun '19

A system test invoked by the "ovirt-4.2" change queue including change 100957,4 (ovirt-provider-ovn) failed. However, this change seems not to be the root cause for this failure. Change 100733,12 (ovirt-provider-ovn) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 100733,12 (ovirt-provider-ovn) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/100957/4 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/100733/12 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/4563/

1 0

Fwd: [CentOS-devel] The future of the community build services
by Sandro Bonazzola 25 Jun '19

25 Jun '19

FYI ---------- Forwarded message --------- Da: Thomas Oulevey <thomas.oulevey(a)cern.ch> Date: lun 24 giu 2019 alle ore 17:21 Subject: [CentOS-devel] The future of the community build services To: <centos-devel(a)centos.org> Hi Folks, It's time to have a look to the SIGs and the community needs for the next version of the community build service(cbs). We would like to request feedback and know if the different communities plan on using modular builds, and what would be their timeline to be able to produce C8 artifacts (rpms, imagefactory builds, etc...). As you know Koji is now used to build CentOS 8 [1], and is based on the mbbox [2] distribution. It makes sense for cbs.centos.org to follow this trend and be based on the same templates. At the same time we needed to evaluate how and where we can deploy the new Openshift based templates, and associated builders for different arches. It's understood that the transition between both systems should be smooth and do not impact your C6/C7 builds and release cycle. We will plan accordingly. Please let us know, if you have comments and/or new ideas. -- Thomas Oulevey [1]: https://blog.centos.org/2019/06/centos-8-status-17-june-2019/ [2]: https://github.com/puiterwijk/mbbox _______________________________________________ CentOS-devel mailing list CentOS-devel(a)centos.org https://lists.centos.org/mailman/listinfo/centos-devel -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/>

1 0

[CQ]: 100597, 22 (ovirt-provider-ovn) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 25 Jun '19

25 Jun '19

A system test invoked by the "ovirt-4.2" change queue including change 100597,22 (ovirt-provider-ovn) failed. However, this change seems not to be the root cause for this failure. Change 100733,12 (ovirt-provider-ovn) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 100733,12 (ovirt-provider-ovn) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/100597/22 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/100733/12 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/4560/

1 0

[JIRA] (OVIRT-2742) ovirt-appliance build failure on missing module urllib.request
by Anton Marchukov (oVirt JIRA) 25 Jun '19

25 Jun '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2742?page=com.atlassian.jira.… ] Anton Marchukov commented on OVIRT-2742: ---------------------------------------- [~sbonazzo(a)redhat.com] it looks to be controllable from STDCI project files indeed. Were you able to fix it or still need help? > ovirt-appliance build failure on missing module urllib.request > -------------------------------------------------------------- > > Key: OVIRT-2742 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2742 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > *16:16:26* Traceback (most recent call last):*16:16:26* File > "scripts/create_ova.py", line 4, in <module>*16:16:26* from > imagefactory_plugins.ovfcommon.ovfcommon import > RHEVOVFPackage*16:16:26* File > "/home/jenkins/workspace/ovirt-appliance_master_build-artifacts-el7-x86_64/ovirt-appliance/engine-appliance/imagefactory/imagefactory_plugins/ovfcommon/ovfcommon.py", > line 29, in <module>*16:16:26* from imgfac.PersistentImageManager > import PersistentImageManager*16:16:26* File > "/home/jenkins/workspace/ovirt-appliance_master_build-artifacts-el7-x86_64/ovirt-appliance/engine-appliance/imagefactory/imgfac/PersistentImageManager.py", > line 17, in <module>*16:16:26* from .ApplicationConfiguration > import ApplicationConfiguration*16:16:26* File > "/home/jenkins/workspace/ovirt-appliance_master_build-artifacts-el7-x86_64/ovirt-appliance/engine-appliance/imagefactory/imgfac/ApplicationConfiguration.py", > line 24, in <module>*16:16:26* import urllib.request*16:16:26* > ImportError: No module named request > Seen in > https://jenkins.ovirt.org/job/ovirt-appliance_master_build-artifacts-el7-x8… > https://jenkins.ovirt.org/job/ovirt-appliance_4.3_build-artifacts-el7-x86_6… > https://jenkins.ovirt.org/job/ovirt-appliance_4.2_build-artifacts-el7-x86_6… > -- > Sandro Bonazzola > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://www.redhat.com/> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100105)

1 0