August 2018 - Infra - Ovirt List Archives

[ OST Failure Report ] [ oVirt master (ovirt-engine) ] [ 6-08-2018 ] [ TEST NAME ]

by Dafna Ron

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/... <https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8975/artif...>(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>*

6 years, 3 months

3
5
0 / 0

[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)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2411?page=com.atlassian.jir... ] 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)

6 years, 3 months

1
0
0 / 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)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2411?page=com.atlassian.jir... ] 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)

6 years, 3 months

1
0
0 / 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)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2411?page=com.atlassian.jir... ] 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)

6 years, 3 months

1
0
0 / 0

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

by oVirt Jenkins

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/

6 years, 3 months

2
1
0 / 0

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

by oVirt Jenkins

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/

6 years, 3 months

2
1
0 / 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)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2411?page=com.atlassian.jir... ] 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... > 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)

6 years, 3 months

1
0
0 / 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)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2411?page=com.atlassian.jir... ] 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... > 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)

6 years, 3 months

1
0
0 / 0

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

by oVirt Jenkins

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/

6 years, 3 months

2
1
0 / 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)

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)

6 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Infra August 2018