- Infra - oVirt List Archives

[JIRA] (OVIRT-2413) Set up CNV Jenkins to run STDCI
by Daniel Belenky (oVirt JIRA) 08 Aug '18

08 Aug '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2413?page=com.atlassian.jira.… ] Daniel Belenky updated OVIRT-2413: ---------------------------------- Description: Add here all tasks that needs to be done in order to run STDCI on CNV Jenkins > Set up CNV Jenkins to run STDCI > ------------------------------- > > Key: OVIRT-2413 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2413 > Project: oVirt - virtualization made easy > Issue Type: Epic > Reporter: Daniel Belenky > Assignee: infra > > Add here all tasks that needs to be done in order to run STDCI on CNV Jenkins -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2413) Set up CNV Jenkins to run STDCI
by Daniel Belenky (oVirt JIRA) 08 Aug '18

08 Aug '18

Daniel Belenky created OVIRT-2413: ------------------------------------- Summary: Set up CNV Jenkins to run STDCI Key: OVIRT-2413 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2413 Project: oVirt - virtualization made easy Issue Type: Epic Reporter: Daniel Belenky Assignee: infra -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[CQ]: 93556,2 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 08 Aug '18

08 Aug '18

Change 93556,2 (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/93556/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/9000/

2 1

[JIRA] (OVIRT-2412) docker.errors.APIError: 400 Client Error: Bad Request
by Dafna Ron (oVirt JIRA) 08 Aug '18

08 Aug '18

Dafna Ron created OVIRT-2412: -------------------------------- Summary: docker.errors.APIError: 400 Client Error: Bad Request Key: OVIRT-2412 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2412 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Dafna Ron Assignee: infra we have a failure in master ovirt-engine CQ which seems to be related to container cleanup: https://pastebin.com/h1KCGT7p can you please have a look? http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/9000/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[ OST Failure Report ] [ oVirt master (ovirt-engine) ] [ 6-08-2018 ] [ TEST NAME ]
by Dafna Ron 08 Aug '18

08 Aug '18

Hi, We have a failure in CQ on ovirt-master for test 001_upgrade_engine.test_initialize_engine on upgrade suite. *Link and headline of suspected patches: https://gerrit.ovirt.org/#/c/93466/ <https://gerrit.ovirt.org/#/c/93466/> - core: clean stale image_transfer on upgradeLink to Job:https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8975 <https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8975>Link to all logs:https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8975/ar… <https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8975/artifac…>(Relevant) error snippet from the log: <error>* [ INFO ] Stage: Misc configuration [ INFO ] Upgrading CA [ INFO ] Backing up database localhost:ovirt_engine_history to '/var/lib/ovirt-engine-dwh/backups/dwh-20180806074534.L73Aa6.dump'. [ INFO ] Creating/refreshing DWH database schema [ INFO ] Configuring WebSocket Proxy [ INFO ] Backing up database localhost:engine to '/var/lib/ovirt-engine/backups/engine-20180806074537.V9dDgr.dump'. [ INFO ] Creating/refreshing Engine database schema [ ERROR ] schema.sh: FATAL: Cannot execute sql command: --file=/usr/share/ovirt-engine/dbscripts/upgrade/04_03_0270_add_foreign_key_to_image_transfers.sql [ ERROR ] Failed to execute stage 'Misc configuration': Engine schema refresh failed [WARNING] Rollback of DWH database postponed to Stage "Clean up" [ INFO ] Rolling back database schema [ INFO ] Clearing Engine database engine [ INFO ] Restoring Engine database engine [ INFO ] Restoring file '/var/lib/ovirt-engine/backups/engine-20180806074537.V9dDgr.dump' to database localhost:engine. [ ERROR ] Errors while restoring engine database, please check the log file for details [ INFO ] Stage: Clean up Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20180806074515-jb06pl.log [ INFO ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20180806074550-setup.conf' [WARNING] Rollback of DWH database started This might be a long process, but it should be safe to start the engine service before it finishes, if needed. [ INFO ] Clearing DWH database ovirt_engine_history [ INFO ] Restoring DWH database ovirt_engine_history [ INFO ] Restoring file '/var/lib/ovirt-engine-dwh/backups/dwh-20180806074534.L73Aa6.dump' to database localhost:ovirt_engine_history. [ ERROR ] Errors while restoring ovirt_engine_history database, please check the log file for details [ INFO ] Stage: Pre-termination *</error>*

3 5

[JIRA] (OVIRT-2411) ovirt-4.2 vdsm project failing on packaging on suite upgrade-from-prevrelease in test 002_bootstrap.add_hosts
by Piotr Kliczewski (oVirt JIRA) 08 Aug '18

08 Aug '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2411?page=com.atlassian.jira.… ] Piotr Kliczewski commented on OVIRT-2411: ----------------------------------------- This could be related to check-merge job [1] failure. I checked the logs and found that functional tests were unable to connect to vdsm: 2018-08-07 19:34:39,578::ssh.py::get_ssh_client::367::lago.ssh::DEBUG::Socket error connecting to vdsm_functional_tests_host-el7: timed out 2018-08-07 19:34:39,579::ssh.py::get_ssh_client::381::lago.ssh::DEBUG::Still got 99 tries for vdsm_functional_tests_host-el7 2018-08-07 19:34:43,587::ssh.py::get_ssh_client::367::lago.ssh::DEBUG::Socket error connecting to vdsm_functional_tests_host-el7: [Errno None] Unable to connect to port 22 on 192.168.200.2 I checked that vdsm log and found setupNetwork failure: Aug 7 15:20:50 vdsm_functional_tests_host-el7 vdsm[31471]: ERROR u'1.2.3.4/' does not appear to be an IPv4 or IPv6 interface#012Traceback (most recent call last):#012 File "/usr/lib/python2.7/site-packages/vdsm/API.py", line 1529, in setupNetworks#012 supervdsm.getProxy().setupNetworks(networks, bondings, options)#012 File "/usr/lib/python2.7/site-packages/vdsm/common/supervdsm.py", line 55, in __call__#012 return callMethod()#012 File "/usr/lib/python2.7/site-packages/vdsm/common/supervdsm.py", line 53, in <lambda>#012 **kwargs)#012 File "<string>", line 2, in setupNetworks#012 File "/usr/lib64/python2.7/multiprocessing/managers.py", line 773, in _callmethod#012 raise convert_to_error(kind, result)#012ConfigNetworkError: (22, "u'1.2.3.4/' does not appear to be an IPv4 or IPv6 interface") Aug 7 15:20:50 vdsm_functional_tests_host-el7 vdsm[31471]: ERROR gateway or netmask were given without ip address#012Traceback (most recent call last):#012 File "/usr/lib/python2.7/site-packages/vdsm/API.py", line 1529, in setupNetworks#012 supervdsm.getProxy().setupNetworks(networks, bondings, options)#012 File "/usr/lib/python2.7/site-packages/vdsm/common/supervdsm.py", line 55, in __call__#012 return callMethod()#012 File "/usr/lib/python2.7/site-packages/vdsm/common/supervdsm.py", line 53, in <lambda>#012 **kwargs)#012 File "<string>", line 2, in setupNetworks#012 File "/usr/lib64/python2.7/multiprocessing/managers.py", line 773, in _callmethod#012 raise convert_to_error(kind, result)#012ConfigNetworkError: (22, 'gateway or netmask were given without ip address') Aug 7 15:20:50 vdsm_functional_tests_host-el7 vdsm[31471]: ERROR gateway or netmask were given without ip address#012Traceback (most recent call last):#012 File "/usr/lib/python2.7/site-packages/vdsm/API.py", line 1529, in setupNetworks#012 supervdsm.getProxy().setupNetworks(networks, bondings, options)#012 File "/usr/lib/python2.7/site-packages/vdsm/common/supervdsm.py", line 55, in __call__#012 return callMethod()#012 File "/usr/lib/python2.7/site-packages/vdsm/common/supervdsm.py", line 53, in <lambda>#012 **kwargs)#012 File "<string>", line 2, in setupNetworks#012 File "/usr/lib64/python2.7/multiprocessing/managers.py", line 773, in _callmethod#012 raise convert_to_error(kind, result)#012ConfigNetworkError: (22, 'gateway or netmask were given without ip address') Aug 7 15:20:51 vdsm_functional_tests_host-el7 vdsm[31471]: ERROR u'1.2.3.256/255.255.0.0' does not appear to be an IPv4 or IPv6 interface#012Traceback (most recent call last):#012 File "/usr/lib/python2.7/site-packages/vdsm/API.py", line 1529, in setupNetworks#012 supervdsm.getProxy().setupNetworks(networks, bondings, options)#012 File "/usr/lib/python2.7/site-packages/vdsm/common/supervdsm.py", line 55, in __call__#012 return callMethod()#012 File "/usr/lib/python2.7/site-packages/vdsm/common/supervdsm.py", line 53, in <lambda>#012 **kwargs)#012 File "<string>", line 2, in setupNetworks#012 File "/usr/lib64/python2.7/multiprocessing/managers.py", line 773, in _callmethod#012 raise convert_to_error(kind, result)#012ConfigNetworkError: (22, "u'1.2.3.256/255.255.0.0' does not appear to be an IPv4 or IPv6 interface") [~danken(a)redhat.com] [~edwardh] have you seen it before? [1] https://jenkins.ovirt.org/job/vdsm_4.2_check-merged-el7-x86_64/225/ > ovirt-4.2 vdsm project failing on packaging on suite upgrade-from-prevrelease in test 002_bootstrap.add_hosts > ------------------------------------------------------------------------------------------------------------- > > Key: OVIRT-2411 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2411 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Priority: High > Labels: ost_failures, ost_packages > > https://pastebin.com/Ry4UHhtM > I am not sure if we need dsm-jsonrpc as our reposync has dsm-jsonrpc-java. > will re-run reposync tool and also look into the package and where its coming from -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2411) ovirt-4.2 vdsm project failing on packaging on suite upgrade-from-prevrelease in test 002_bootstrap.add_hosts
by Eyal Edri (oVirt JIRA) 08 Aug '18

08 Aug '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2411?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2411: ---------------------------------- we need both, cc [~pkliczew(a)redhat.com] and [~fromani(a)redhat.com] > ovirt-4.2 vdsm project failing on packaging on suite upgrade-from-prevrelease in test 002_bootstrap.add_hosts > ------------------------------------------------------------------------------------------------------------- > > Key: OVIRT-2411 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2411 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Priority: High > Labels: ost_failures, ost_packages > > https://pastebin.com/Ry4UHhtM > I am not sure if we need dsm-jsonrpc as our reposync has dsm-jsonrpc-java. > will re-run reposync tool and also look into the package and where its coming from -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2411) ovirt-4.2 vdsm project failing on packaging on suite upgrade-from-prevrelease in test 002_bootstrap.add_hosts
by Dafna Ron (oVirt JIRA) 08 Aug '18

08 Aug '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2411?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2411: ---------------------------------- [~danken(a)redhat.com] [~sbonazzo(a)redhat.com] which of these packages are actually needed? https://pastebin.com/AEVtv8gv do we need vdsm-jsonrpc or just vdsm-jsonrpc-java? if we do need vdsm-jsonrpc then we have a lower version in tested. > ovirt-4.2 vdsm project failing on packaging on suite upgrade-from-prevrelease in test 002_bootstrap.add_hosts > ------------------------------------------------------------------------------------------------------------- > > Key: OVIRT-2411 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2411 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Priority: High > Labels: ost_failures, ost_packages > > https://pastebin.com/Ry4UHhtM > I am not sure if we need dsm-jsonrpc as our reposync has dsm-jsonrpc-java. > will re-run reposync tool and also look into the package and where its coming from -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[CQ]: 93478, 2 (vdsm) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 08 Aug '18

08 Aug '18

A system test invoked by the "ovirt-4.2" change queue including change 93478,2 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 93253,3 (vdsm) 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 93253,3 (vdsm) 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/93478/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/93253/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2808/

2 1

[CQ]: 93546, 3 (vdsm) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 08 Aug '18

08 Aug '18

A system test invoked by the "ovirt-4.2" change queue including change 93546,3 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 93253,3 (vdsm) 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 93253,3 (vdsm) 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/93546/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/93253/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2810/

2 1

[JIRA] (OVIRT-2411) ovirt-4.2 vdsm project failing on packaging on suite upgrade-from-prevrelease in test 002_bootstrap.add_hosts
by Dafna Ron (oVirt JIRA) 08 Aug '18

08 Aug '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2411?page=com.atlassian.jira.… ] Dafna Ron edited comment on OVIRT-2411 at 8/8/18 7:02 AM: ---------------------------------------------------------- here are the logs and full build: https://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2810/ was (Author: dron): here are the logs and full build: https://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2812/artifact/b… > ovirt-4.2 vdsm project failing on packaging on suite upgrade-from-prevrelease in test 002_bootstrap.add_hosts > ------------------------------------------------------------------------------------------------------------- > > Key: OVIRT-2411 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2411 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Priority: High > Labels: ost_failures, ost_packages > > https://pastebin.com/Ry4UHhtM > I am not sure if we need dsm-jsonrpc as our reposync has dsm-jsonrpc-java. > will re-run reposync tool and also look into the package and where its coming from -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2411) ovirt-4.2 vdsm project failing on packaging on suite upgrade-from-prevrelease in test 002_bootstrap.add_hosts
by Dafna Ron (oVirt JIRA) 08 Aug '18

08 Aug '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2411?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2411: ---------------------------------- here are the logs and full build: https://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2812/artifact/b… > ovirt-4.2 vdsm project failing on packaging on suite upgrade-from-prevrelease in test 002_bootstrap.add_hosts > ------------------------------------------------------------------------------------------------------------- > > Key: OVIRT-2411 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2411 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Priority: High > Labels: ost_failures, ost_packages > > https://pastebin.com/Ry4UHhtM > I am not sure if we need dsm-jsonrpc as our reposync has dsm-jsonrpc-java. > will re-run reposync tool and also look into the package and where its coming from -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[CQ]: 93560, 2 (ovirt-engine) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 08 Aug '18

08 Aug '18

A system test invoked by the "ovirt-4.2" change queue including change 93560,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 93501,3 (ovirt-engine) 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 93501,3 (ovirt-engine) 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/93560/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/93501/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2812/

2 1

[JIRA] (OVIRT-2411) ovirt-4.2 vdsm project failing on packaging on suite upgrade-from-prevrelease in test 002_bootstrap.add_hosts
by Dafna Ron (oVirt JIRA) 08 Aug '18

08 Aug '18

Dafna Ron created OVIRT-2411: -------------------------------- Summary: ovirt-4.2 vdsm project failing on packaging on suite upgrade-from-prevrelease in test 002_bootstrap.add_hosts Key: OVIRT-2411 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2411 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Dafna Ron Assignee: infra Priority: High https://pastebin.com/Ry4UHhtM I am not sure if we need dsm-jsonrpc as our reposync has dsm-jsonrpc-java. will re-run reposync tool and also look into the package and where its coming from -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2410) assistance with new stdci v2 job
by Barak Korren (oVirt JIRA) 08 Aug '18

08 Aug '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2410?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-2410: ----------------------------------- Assignee: Barak Korren (was: infra) > assistance with new stdci v2 job > -------------------------------- > > Key: OVIRT-2410 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2410 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Components: CI client projects > Reporter: Greg Sheremeta > Assignee: Barak Korren > > Hi, > I just added automation.yaml to ovirt-engine-ui-extensions > https://gerrit.ovirt.org/#/c/93563/ > The build was unstable -- looks like a ci issue, but maybe I've done > something wrong? My build-artifacts both passed. > https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-engine-ui-extens… > -- > GREG SHEREMETA > SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX > Red Hat NA > <https://www.redhat.com/> > gshereme(a)redhat.com IRC: gshereme > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2410) assistance with new stdci v2 job
by Barak Korren (oVirt JIRA) 08 Aug '18

08 Aug '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2410?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2410: -------------------------------- Component/s: CI client projects > assistance with new stdci v2 job > -------------------------------- > > Key: OVIRT-2410 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2410 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Components: CI client projects > Reporter: Greg Sheremeta > Assignee: infra > > Hi, > I just added automation.yaml to ovirt-engine-ui-extensions > https://gerrit.ovirt.org/#/c/93563/ > The build was unstable -- looks like a ci issue, but maybe I've done > something wrong? My build-artifacts both passed. > https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-engine-ui-extens… > -- > GREG SHEREMETA > SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX > Red Hat NA > <https://www.redhat.com/> > gshereme(a)redhat.com IRC: gshereme > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2410) assistance with new stdci v2 job
by Barak Korren (oVirt JIRA) 08 Aug '18

08 Aug '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2410?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2410: ------------------------------------- The queue name is release branches should be 'ovirt-master' and not 'master'. release-branches is a dictionary where keys are local branch names and values are (one or more) release change queue names. > assistance with new stdci v2 job > -------------------------------- > > Key: OVIRT-2410 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2410 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Greg Sheremeta > Assignee: infra > > Hi, > I just added automation.yaml to ovirt-engine-ui-extensions > https://gerrit.ovirt.org/#/c/93563/ > The build was unstable -- looks like a ci issue, but maybe I've done > something wrong? My build-artifacts both passed. > https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-engine-ui-extens… > -- > GREG SHEREMETA > SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX > Red Hat NA > <https://www.redhat.com/> > gshereme(a)redhat.com IRC: gshereme > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[oVirt Jenkins] ovirt-system-tests_he-node-ng-suite-master - Build # 263 - Failure!
by jenkins＠jenkins.phx.ovirt.org 08 Aug '18

08 Aug '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-master/263/ Build Number: 263 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #263 [Gal Ben Haim] HE: Added Local Maintenance Tests ----------------- Failed Tests: ----------------- No tests ran.

1 1

[oVirt CI] standard-enqueue - Build #15532 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 08 Aug '18

08 Aug '18

Build: http://jenkins.ovirt.org/job/standard-enqueue/15532/ Build Name: #15532 Build Description: Gerrit: 93509 - ovirt-engine (4.2.5) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/93509 - title: build: post ovirt-engine-4.2.5.z branching - project: ovirt-engine - branch: ovirt-engine-4.2.5.z - author: Sandro Bonazzola <sbonazzo(a)redhat.com>

1 2

oVirt infra daily report - unstable production jobs - 545
by jenkins＠jenkins.phx.ovirt.org 08 Aug '18

08 Aug '18

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

1 0

[JIRA] (OVIRT-2410) assistance with new stdci v2 job
by Greg Sheremeta (oVirt JIRA) 07 Aug '18

07 Aug '18

Greg Sheremeta created OVIRT-2410: ------------------------------------- Summary: assistance with new stdci v2 job Key: OVIRT-2410 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2410 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Greg Sheremeta Assignee: infra Hi, I just added automation.yaml to ovirt-engine-ui-extensions https://gerrit.ovirt.org/#/c/93563/ The build was unstable -- looks like a ci issue, but maybe I've done something wrong? My build-artifacts both passed. https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-engine-ui-extens… -- GREG SHEREMETA SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX Red Hat NA <https://www.redhat.com/> gshereme(a)redhat.com IRC: gshereme <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[CQ]: 93479, 2 (vdsm) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 07 Aug '18

07 Aug '18

A system test invoked by the "ovirt-4.2" change queue including change 93479,2 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 93253,3 (vdsm) 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 93253,3 (vdsm) 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/93479/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/93253/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2807/

1 0

[JIRA] (OVIRT-2376) regression masked by local function setting __name__
by Dafna Ron (oVirt JIRA) 07 Aug '18

07 Aug '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2376?page=com.atlassian.jira.… ] Dafna Ron updated OVIRT-2376: ----------------------------- Labels: ost_failures ost_lago (was: ost_failures ost_infra ost_lago) > regression masked by local function setting __name__ > ----------------------------------------------------- > > Key: OVIRT-2376 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2376 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Priority: High > Labels: ost_failures, ost_lago > > we had two different cases where a regression was masked by issues caused when setting __name__ as local function. > see: > Jira: https://ovirt-jira.atlassian.net/browse/OVIRT-2348 > Jira: https://ovirt-jira.atlassian.net/browse/OVIRT-2375 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2409) rebuild ovirt-srv06
by Evgheni Dereveanchin (oVirt JIRA) 07 Aug '18

07 Aug '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2409?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-2409: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > rebuild ovirt-srv06 > ------------------- > > Key: OVIRT-2409 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2409 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > > ovirt-srv06 was provisioned using the SSD without LVM so its rootfs is small and not easy to resize (see OVIRT-2397 ) Opening ticket to rebuild it with LVM using the HDD as the base disk. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2409) rebuild ovirt-srv06
by Evgheni Dereveanchin (oVirt JIRA) 07 Aug '18

07 Aug '18

Evgheni Dereveanchin created OVIRT-2409: ------------------------------------------- Summary: rebuild ovirt-srv06 Key: OVIRT-2409 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2409 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Evgheni Dereveanchin Assignee: infra ovirt-srv06 was provisioned using the SSD without LVM so its rootfs is small and not easy to resize (see OVIRT-2397 ) Opening ticket to rebuild it with LVM using the HDD as the base disk. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2367) Functional tests should support testing disaster recovery scenratios with two ovirt-engine setups to simulate failover and failback
by Gal Ben Haim (oVirt JIRA) 07 Aug '18

07 Aug '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2367?page=com.atlassian.jira.… ] Gal Ben Haim reassigned OVIRT-2367: ----------------------------------- Assignee: Gal Ben Haim (was: infra) > Functional tests should support testing disaster recovery scenratios with two ovirt-engine setups to simulate failover and failback > ----------------------------------------------------------------------------------------------------------------------------------- > > Key: OVIRT-2367 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2367 > Project: oVirt - virtualization made easy > Issue Type: Epic > Components: OST > Reporter: Maor Lipchuk > Assignee: Gal Ben Haim > Priority: High > Labels: ost > > RHV/oVirt should support functional tests for the disaster recovery feature which was introduced in oVirt/RHV 4.2 > The functional tests should support testing disaster recovery scenratios with two ovirt-engine setups to simulate failover and failback between the different setups. > Here are more resources explaining about the feature and the its usecases: > github project: > https://github.com/oVirt/ovirt-ansible-disaster-recovery/ > Documentation: > https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2/ht… > Videos demostrating the usecases for oVirt DR: > https://www.youtube.com/watch?v=_TVhU9Sf2uc > https://www.youtube.com/watch?v=uRxsZME6fGs > https://www.youtube.com/watch?v=7dStBp7Wpo0 > https://www.youtube.com/watch?v=a44PdFbeIfE > https://youtu.be/ayYrV5IBFUg > https://www.youtube.com/watch?v=rt31-XJ45So&t=8s > [~gbenhaim(a)redhat.com] -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2408) Add shared volume between stdci-containers
by Daniel Belenky (oVirt JIRA) 07 Aug '18

07 Aug '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2408?page=com.atlassian.jira.… ] Daniel Belenky reassigned OVIRT-2408: ------------------------------------- Assignee: Daniel Belenky (was: infra) > Add shared volume between stdci-containers > ------------------------------------------ > > Key: OVIRT-2408 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2408 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Daniel Belenky > Assignee: Daniel Belenky > > Sometimes we need to store large files (such as images) to be used by builds. Because those files are large, we'd prefer to store them once because our disk is limited and to avoid too many I/O calls. > Create a /shared volume under /var/lib/stdci and mount it to every stdci-container slave under the same path. Projects then can access it by mounting it to mock via *.mou -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2408) Add shared volume between stdci-containers
by Daniel Belenky (oVirt JIRA) 07 Aug '18

07 Aug '18

Daniel Belenky created OVIRT-2408: ------------------------------------- Summary: Add shared volume between stdci-containers Key: OVIRT-2408 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2408 Project: oVirt - virtualization made easy Issue Type: Improvement Reporter: Daniel Belenky Assignee: infra Sometimes we need to store large files (such as images) to be used by builds. Because those files are large, we'd prefer to store them once because our disk is limited and to avoid too many I/O calls. Create a /shared volume under /var/lib/stdci and mount it to every stdci-container slave under the same path. Projects then can access it by mounting it to mock via *.mou -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2408) Add shared volume between stdci-containers
by Daniel Belenky (oVirt JIRA) 07 Aug '18

07 Aug '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2408?page=com.atlassian.jira.… ] Daniel Belenky updated OVIRT-2408: ---------------------------------- Epic Link: OVIRT-2339 > Add shared volume between stdci-containers > ------------------------------------------ > > Key: OVIRT-2408 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2408 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Daniel Belenky > Assignee: infra > > Sometimes we need to store large files (such as images) to be used by builds. Because those files are large, we'd prefer to store them once because our disk is limited and to avoid too many I/O calls. > Create a /shared volume under /var/lib/stdci and mount it to every stdci-container slave under the same path. Projects then can access it by mounting it to mock via *.mou -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2407) permissions request
by Eyal Edri (oVirt JIRA) 07 Aug '18

07 Aug '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2407?page=com.atlassian.jira.… ] Eyal Edri reassigned OVIRT-2407: -------------------------------- Assignee: Gal Ben Haim (was: infra) > permissions request > ------------------- > > Key: OVIRT-2407 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2407 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Liora Milbaum > Assignee: Gal Ben Haim > > Please provide me additional permissions on Ovirt Jenkins. > Thanks, > Liora > -- > LIORA MILBAUM > SENIOR PRINCIPAL SOFTWARE ENGINEER > cnv release team > Red Hat <https://www.redhat.com/> > <https://www.redhat.com/> > T: +972-9-7692234 <javascript:void(0);> > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[CQ]: 93551, 1 (vdsm) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 07 Aug '18

07 Aug '18

A system test invoked by the "ovirt-4.2" change queue including change 93551,1 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 93253,3 (vdsm) 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 93253,3 (vdsm) 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/93551/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/93253/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2802/

1 0

[JIRA] (OVIRT-2407) permissions request
by Liora Milbaum (oVirt JIRA) 07 Aug '18

07 Aug '18

Liora Milbaum created OVIRT-2407: ------------------------------------ Summary: permissions request Key: OVIRT-2407 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2407 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Liora Milbaum Assignee: infra Please provide me additional permissions on Ovirt Jenkins. Thanks, Liora -- LIORA MILBAUM SENIOR PRINCIPAL SOFTWARE ENGINEER cnv release team Red Hat <https://www.redhat.com/> <https://www.redhat.com/> T: +972-9-7692234 <javascript:void(0);> <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2404) CQ 4.2 vdsm failing upgrade-from-prevrelease-suite on missing 4.1 tested repo
by Dafna Ron (oVirt JIRA) 07 Aug '18

07 Aug '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2404?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2404: ---------------------------------- patches merged. waiting for builds to pass before closing. > CQ 4.2 vdsm failing upgrade-from-prevrelease-suite on missing 4.1 tested repo > ----------------------------------------------------------------------------- > > Key: OVIRT-2404 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2404 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Priority: Highest > Labels: ost_failures, ost_infra > > https://pastebin.com/uMQMjAq5 > we are failing since 4.1 tested is missing. > https://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2774/consoleFull > patch that failed is not related to the issue but this is the one that failed: > https://gerrit.ovirt.org/#/c/93253/3 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2405) 4.2 ovirt is failing on vdsm packages
by Dafna Ron (oVirt JIRA) 07 Aug '18

07 Aug '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2405?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2405: ---------------------------------- there were two issues: 1. vdsm packages from master were build and places on 4.2 branch (Dan fixed it) 2. vdsm check-merge job was broken due to link changes in lago - this was fixed as well by vdsm maintainers. > 4.2 ovirt is failing on vdsm packages > ------------------------------------- > > Key: OVIRT-2405 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2405 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures, ost_packages > > seems we are missing deps for the package but in tested I am not seeing the package at all. > Error: Package: vdsm-4.20.36-2.gita761598.el7.x86_64 (alocalsync) > '[dron@dron ovirt-system-tests]$ repoquery --repofrompath=testrepo,http://resources.ovirt.org/repos/ovirt/tested/4.2/rpm/el7/ --repoid=testrepo --query --all |grep vdsm > Repository google-chrome is listed more than once in the configuration > Repository google-talkplugin is listed more than once in the configuration > vdsm-0:4.20.35-2.git2ac8149.el7.x86_64' > will look where its coming from and issue fix/talk to devs -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[CQ]: 93501,3 (ovirt-engine) failed "ovirt-4.2" system tests
by oVirt Jenkins 07 Aug '18

07 Aug '18

Change 93501,3 (ovirt-engine) 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/93501/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2800/

1 0

[JIRA] (OVIRT-2399) missing deps for openvswitch cause failure in lago vms deployment
by sbonazzo (oVirt JIRA) 07 Aug '18

07 Aug '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2399?page=com.atlassian.jira.… ] sbonazzo reassigned OVIRT-2399: ------------------------------- Assignee: sbonazzo (was: infra) > missing deps for openvswitch cause failure in lago vms deployment > ----------------------------------------------------------------- > > Key: OVIRT-2399 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2399 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: sbonazzo > Labels: ost_failures, ost_packages > > fixed with this patch: > https://gerrit.ovirt.org/#/c/93476/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[CQ]: 93218, 1 (vdsm) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 07 Aug '18

07 Aug '18

A system test invoked by the "ovirt-4.2" change queue including change 93218,1 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 93253,3 (vdsm) 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 93253,3 (vdsm) 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/93218/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/93253/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2798/

1 0

[JIRA] (OVIRT-2406) Nagios ran out of memory
by Evgheni Dereveanchin (oVirt JIRA) 07 Aug '18

07 Aug '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2406?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-2406: ------------------------------------------- Assignee: Marc Dequènes (Duck) (was: infra) > Nagios ran out of memory > ------------------------ > > Key: OVIRT-2406 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2406 > Project: oVirt - virtualization made easy > Issue Type: Outage > Reporter: Evgheni Dereveanchin > Assignee: Marc Dequènes (Duck) > > There was a flood of Nagios notifications this morning which looked like false positives. > While investigating I stumbled upon numerous OOM conditions in logs so memory for the VM should be increased. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2405) 4.2 ovirt is failing on vdsm packages
by Dafna Ron (oVirt JIRA) 07 Aug '18

07 Aug '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2405?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2405: ---------------------------------- I spoke to Martin and re-merged https://gerrit.ovirt.org/#/c/93218/ > 4.2 ovirt is failing on vdsm packages > ------------------------------------- > > Key: OVIRT-2405 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2405 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures, ost_packages > > seems we are missing deps for the package but in tested I am not seeing the package at all. > Error: Package: vdsm-4.20.36-2.gita761598.el7.x86_64 (alocalsync) > '[dron@dron ovirt-system-tests]$ repoquery --repofrompath=testrepo,http://resources.ovirt.org/repos/ovirt/tested/4.2/rpm/el7/ --repoid=testrepo --query --all |grep vdsm > Repository google-chrome is listed more than once in the configuration > Repository google-talkplugin is listed more than once in the configuration > vdsm-0:4.20.35-2.git2ac8149.el7.x86_64' > will look where its coming from and issue fix/talk to devs -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[CQ]: 93256, 3 (vdsm) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 07 Aug '18

07 Aug '18

A system test invoked by the "ovirt-4.2" change queue including change 93256,3 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 93253,3 (vdsm) 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 93253,3 (vdsm) 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/93256/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/93253/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2796/

1 0

[JIRA] (OVIRT-2406) Nagios ran out of memory
by Evgheni Dereveanchin (oVirt JIRA) 07 Aug '18

07 Aug '18

Evgheni Dereveanchin created OVIRT-2406: ------------------------------------------- Summary: Nagios ran out of memory Key: OVIRT-2406 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2406 Project: oVirt - virtualization made easy Issue Type: Outage Reporter: Evgheni Dereveanchin Assignee: infra There was a flood of Nagios notifications this morning which looked like false positives. While investigating I stumbled upon numerous OOM conditions in logs so memory for the VM should be increased. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2405) 4.2 ovirt is failing on vdsm packages
by Dafna Ron (oVirt JIRA) 07 Aug '18

07 Aug '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2405?page=com.atlassian.jira.… ] Dafna Ron edited comment on OVIRT-2405 at 8/7/18 6:48 AM: ---------------------------------------------------------- this is the patch that had the new vdsm. https://gerrit.ovirt.org/#/c/93298/ and it failed CQ. I will re-trigger last vdsm so we have the new package was (Author: dron): this is the patch for the new vdsm. https://gerrit.ovirt.org/#/c/93426/ the head for this patch was https://gerrit.ovirt.org/#/c/93298/ it did not pass CQ. > 4.2 ovirt is failing on vdsm packages > ------------------------------------- > > Key: OVIRT-2405 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2405 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures, ost_packages > > seems we are missing deps for the package but in tested I am not seeing the package at all. > Error: Package: vdsm-4.20.36-2.gita761598.el7.x86_64 (alocalsync) > '[dron@dron ovirt-system-tests]$ repoquery --repofrompath=testrepo,http://resources.ovirt.org/repos/ovirt/tested/4.2/rpm/el7/ --repoid=testrepo --query --all |grep vdsm > Repository google-chrome is listed more than once in the configuration > Repository google-talkplugin is listed more than once in the configuration > vdsm-0:4.20.35-2.git2ac8149.el7.x86_64' > will look where its coming from and issue fix/talk to devs -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2405) 4.2 ovirt is failing on vdsm packages
by Dafna Ron (oVirt JIRA) 07 Aug '18

07 Aug '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2405?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2405: ---------------------------------- this is the patch for the new vdsm. https://gerrit.ovirt.org/#/c/93426/ the head for this patch was https://gerrit.ovirt.org/#/c/93298/ it did not pass CQ. > 4.2 ovirt is failing on vdsm packages > ------------------------------------- > > Key: OVIRT-2405 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2405 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures, ost_packages > > seems we are missing deps for the package but in tested I am not seeing the package at all. > Error: Package: vdsm-4.20.36-2.gita761598.el7.x86_64 (alocalsync) > '[dron@dron ovirt-system-tests]$ repoquery --repofrompath=testrepo,http://resources.ovirt.org/repos/ovirt/tested/4.2/rpm/el7/ --repoid=testrepo --query --all |grep vdsm > Repository google-chrome is listed more than once in the configuration > Repository google-talkplugin is listed more than once in the configuration > vdsm-0:4.20.35-2.git2ac8149.el7.x86_64' > will look where its coming from and issue fix/talk to devs -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2405) 4.2 ovirt is failing on vdsm packages
by Dafna Ron (oVirt JIRA) 07 Aug '18

07 Aug '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2405?page=com.atlassian.jira.… ] Dafna Ron updated OVIRT-2405: ----------------------------- Labels: ost_failures ost_packages (was: ) > 4.2 ovirt is failing on vdsm packages > ------------------------------------- > > Key: OVIRT-2405 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2405 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures, ost_packages > > seems we are missing deps for the package but in tested I am not seeing the package at all. > Error: Package: vdsm-4.20.36-2.gita761598.el7.x86_64 (alocalsync) > '[dron@dron ovirt-system-tests]$ repoquery --repofrompath=testrepo,http://resources.ovirt.org/repos/ovirt/tested/4.2/rpm/el7/ --repoid=testrepo --query --all |grep vdsm > Repository google-chrome is listed more than once in the configuration > Repository google-talkplugin is listed more than once in the configuration > vdsm-0:4.20.35-2.git2ac8149.el7.x86_64' > will look where its coming from and issue fix/talk to devs -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2405) 4.2 ovirt is failing on vdsm packages
by Dafna Ron (oVirt JIRA) 07 Aug '18

07 Aug '18

Dafna Ron created OVIRT-2405: -------------------------------- Summary: 4.2 ovirt is failing on vdsm packages Key: OVIRT-2405 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2405 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Dafna Ron Assignee: infra seems we are missing deps for the package but in tested I am not seeing the package at all. Error: Package: vdsm-4.20.36-2.gita761598.el7.x86_64 (alocalsync) '[dron@dron ovirt-system-tests]$ repoquery --repofrompath=testrepo,http://resources.ovirt.org/repos/ovirt/tested/4.2/rpm/el7/ --repoid=testrepo --query --all |grep vdsm Repository google-chrome is listed more than once in the configuration Repository google-talkplugin is listed more than once in the configuration vdsm-0:4.20.35-2.git2ac8149.el7.x86_64' will look where its coming from and issue fix/talk to devs -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

oVirt infra daily report - unstable production jobs - 544
by jenkins＠jenkins.phx.ovirt.org 07 Aug '18

07 Aug '18

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

1 0

[CQ]: 93508,1 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 07 Aug '18

07 Aug '18

Change 93508,1 (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/93508/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8988/

1 0

[CQ]: 93537, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 07 Aug '18

07 Aug '18

A system test invoked by the "ovirt-master" change queue including change 93537,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 92691,13 (ovirt-engine) 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 92691,13 (ovirt-engine) 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/93537/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/92691/13 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8987/

1 0

[CQ]: 93504, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 06 Aug '18

06 Aug '18

A system test invoked by the "ovirt-master" change queue including change 93504,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 92691,13 (ovirt-engine) 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 92691,13 (ovirt-engine) 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/93504/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/92691/13 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8985/

1 0

[CQ]: 93257, 3 (vdsm) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 06 Aug '18

06 Aug '18

A system test invoked by the "ovirt-4.2" change queue including change 93257,3 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 93253,3 (vdsm) 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 93253,3 (vdsm) 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/93257/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/93253/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2793/

1 0