November 2018 - Infra - Ovirt List Archives

[oVirt Jenkins] ovirt-system-tests_he-node-ng-suite-master - Build # 530 - Failure!

by jenkins＠jenkins.phx.ovirt.org

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/530/ Build Number: 530 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #530 [Martin Perina] Fix notifier check in master and 4.2 [Evgheni Dereveanchin] Define Fedora 29 mirrors ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 012_local_maintenance_sdk.local_maintenance Error Message: 143 -------------------- >> begin captured logging << -------------------- root: INFO: * Waiting For System Stability... root: INFO: * Performing Deactivation... root: INFO: * Performing Activation... root: INFO: * Waiting For System Stability... cli: DEBUG: signal 15 was caught --------------------- >> end captured logging << --------------------- Stack Trace: File "/usr/lib64/python2.7/unittest/case.py", line 369, in run testMethod() File "/usr/lib/python2.7/site-packages/nose/case.py", line 197, in runTest self.test(*self.arg) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 142, in wrapped_test test() File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 60, in wrapper return func(get_test_prefix(), *args, **kwargs) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 79, in wrapper prefix.virt_env.engine_vm().get_api(api_ver=4), *args, **kwargs File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 60, in wrapper return func(get_test_prefix(), *args, **kwargs) File "/home/jenkins/workspace/ovirt-system-tests_he-node-ng-suite-master/ovirt-system-tests/he-node-ng-suite-master/test-scenarios/012_local_maintenance_sdk.py", line 79, in local_maintenance time.sleep(wait_value) File "/usr/lib/python2.7/site-packages/lago/cmd.py", line 922, in exit_handler sys.exit(128 + signum) '143\n-------------------- >> begin captured logging << --------------------\nroot: INFO: * Waiting For System Stability...\nroot: INFO: * Performing Deactivation...\nroot: INFO: * Performing Activation...\nroot: INFO: * Waiting For System Stability...\ncli: DEBUG: signal 15 was caught\n--------------------- >> end captured logging << ---------------------'

6 years, 4 months

1
5
0 / 0

[JIRA] (OVIRT-2570) jenkins_standard-on-merge failing with authentication errors

by Evgheni Dereveanchin (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2570?page=com.atlassian.jir... ] Evgheni Dereveanchin updated OVIRT-2570: ---------------------------------------- Resolution: Duplicate Status: Done (was: To Do) Thanks for the info, closing this as duplicate. > jenkins_standard-on-merge failing with authentication errors > ------------------------------------------------------------ > > Key: OVIRT-2570 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2570 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Evgheni Dereveanchin > Assignee: infra > Priority: High > > The last couple of jobs failed so job configs are not being changed: > https://jenkins.ovirt.org/job/jenkins_standard-on-merge/ > This is likely related to revocation of old access tokens in OVIRT-2557 as the error is: > jenkins.JenkinsException: Error in request. Possibly authentication failed [401]: Unauthorized > [~bkorren(a)redhat.com] where are jenkins access credentials stored for this job so that we can create a new token and update the job accordingly? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

6 years, 4 months

1
0
0 / 0

[JIRA] (OVIRT-2570) jenkins_standard-on-merge failing with authentication errors

by Ehud Yonasi (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2570?page=com.atlassian.jir... ] Ehud Yonasi commented on OVIRT-2570: ------------------------------------ [~ederevea] I am working now on creating a job to pull the secrets file, and afterwards to update it on jenkins. https://ovirt-jira.atlassian.net/browse/OVIRT-2567 > jenkins_standard-on-merge failing with authentication errors > ------------------------------------------------------------ > > Key: OVIRT-2570 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2570 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Evgheni Dereveanchin > Assignee: infra > Priority: High > > The last couple of jobs failed so job configs are not being changed: > https://jenkins.ovirt.org/job/jenkins_standard-on-merge/ > This is likely related to revocation of old access tokens in OVIRT-2557 as the error is: > jenkins.JenkinsException: Error in request. Possibly authentication failed [401]: Unauthorized > [~bkorren(a)redhat.com] where are jenkins access credentials stored for this job so that we can create a new token and update the job accordingly? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

6 years, 4 months

1
0
0 / 0

[JIRA] (OVIRT-2542) several failures on host not being available - possible networking issue

by Evgheni Dereveanchin (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2542?page=com.atlassian.jir... ] Evgheni Dereveanchin reassigned OVIRT-2542: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > several failures on host not being available - possible networking issue > ------------------------------------------------------------------------- > > Key: OVIRT-2542 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2542 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: Evgheni Dereveanchin > Labels: ost_failures > > I have noticed that there are several issues that had failed recently with host not available. > the changes are not directly related to the issue and I cannot see anything in engine to suggest that there is a problem. > it could either be a network issue, a network test suite issue or infra related issue. > I am opening this Jira so we can follow all the failures and see if we can find a common denominator -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

6 years, 4 months

1
0
0 / 0

[JIRA] (OVIRT-2570) jenkins_standard-on-merge failing with authentication errors

by Evgheni Dereveanchin (oVirt JIRA)

Evgheni Dereveanchin created OVIRT-2570: ------------------------------------------- Summary: jenkins_standard-on-merge failing with authentication errors Key: OVIRT-2570 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2570 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Evgheni Dereveanchin Assignee: infra Priority: High The last couple of jobs failed so job configs are not being changed: https://jenkins.ovirt.org/job/jenkins_standard-on-merge/ This is likely related to revocation of old access tokens in OVIRT-2557 as the error is: jenkins.JenkinsException: Error in request. Possibly authentication failed [401]: Unauthorized [~bkorren(a)redhat.com] where are jenkins access credentials stored for this job so that we can create a new token and update the job accordingly? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

6 years, 4 months

1
0
0 / 0

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

by oVirt Jenkins

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

6 years, 4 months

1
0
0 / 0

[CQ]: 95059,4 (ovirt-engine) failed "ovirt-4.2" system tests

by oVirt Jenkins

Change 95059,4 (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/95059/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3448/

6 years, 4 months

2
1
0 / 0

[JIRA] (OVIRT-2568) ovirt-master failed on ovirt-engine for upgrade suite

by Dafna Ron (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2568?page=com.atlassian.jir... ] Dafna Ron commented on OVIRT-2568: ---------------------------------- revert patch: https://gerrit.ovirt.org/95270 waiting for the revert to pass before closing. > ovirt-master failed on ovirt-engine for upgrade suite > ----------------------------------------------------- > > Key: OVIRT-2568 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2568 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Priority: Highest > Labels: ost_code_regression, ost_failures > > Link and headline of suspected patches: > https://gerrit.ovirt.org/#/c/95190/ - engine: Remove Cluster Levels 3.6 and 4.0 > Link to Job: > https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10975 > Link to all logs: > https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10975/arti... > (Relevant) error snippet from the log: > {noformat} > 2018-11-04 06:26:54,619-05 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-1) [1d8362d9] EVENT_ID: USER_VDC_LOGIN(30), User admin@internal-authz connecting from '192.168.201.1' using session 'v2y73+8hVB7ccwgjlAQOAK539eW6UsAysQQHbbiSy+mGDSTjOyZ38bpl9XLrGXSLJAqKyeXSdqfrbAqB4qWZUA==' logged in. > 2018-11-04 06:26:54,873-05 WARN [org.ovirt.engine.core.bll.storage.pool.AddEmptyStoragePoolCommand] (default task-1) [4b627395-5dd6-4211-a63e-d78f3728ec6f] Validation of action 'AddEmptyStoragePool' failed for user admin@internal-authz. Reasons: VAR__TYPE__STORAGE__POOL,VAR__ACTION__CREATE,ACTION_TYPE_FAILED_GIVEN_VERSION_NOT_SUPPORTED > 2018-11-04 06:26:54,877-05 ERROR [org.ovirt.engine.api.restapi.resource.AbstractBackendResource] (default task-1) [] Operation Failed: [Cannot create Data Center. Selected Compatibility Version is not supported. > {noformat} -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

6 years, 4 months

1
0
0 / 0

[ OST Failure Report ] [ oVirt Master (ovirt-engine) ] [ 05-11-2018 ] [ 002_bootstrap.add_dc ]

by Dafna Ron

Hi, We failed to add a DC due to computability level in the upgrade suite. The upgrade suite is upgrading 4.2 to master. Eli, can you please check if any fix is needed for upgrade? Link and headline of suspected patches: https://gerrit.ovirt.org/#/c/95190/ - engine: Remove Cluster Levels 3.6 and 4.0 Link to Job: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10975 Link to all logs: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10975/arti... (Relevant) error snippet from the log: <error> 2018-11-04 06:26:54,619-05 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-1) [1d8362d9] EVENT_ID: USER_VDC_LOGIN(30), User admin@internal-authz connecting from '192.168.201.1' using session 'v2y73+8hVB7ccwgjlAQOAK539eW6UsAysQQHbbiSy+mGDSTjOyZ38bpl9XLrGXSLJAqKyeXSdqfrbAqB4qWZUA==' logged in. 2018-11-04 06:26:54,873-05 WARN [org.ovirt.engine.core.bll.storage.pool.AddEmptyStoragePoolCommand] (default task-1) [4b627395-5dd6-4211-a63e-d78f3728ec6f] Validation of action 'AddEmptyStoragePool' failed for user admin@internal-authz. Reasons: VAR__TYPE__STORAGE__POOL,VAR__ACTION__CREATE,ACTION_TYPE_FAILED_GIVEN_VERSION_NOT_SUPPORTED 2018-11-04 06:26:54,877-05 ERROR [org.ovirt.engine.api.restapi.resource.AbstractBackendResource] (default task-1) [] Operation Failed: [Cannot create Data Center. Selected Compatibility Version is not supported. </error>

6 years, 4 months

2
2
0 / 0

[oVirt Jenkins] ovirt-appliance_master_build-artifacts-fc28-x86_64 - Build # 114 - Failure!

by jenkins＠jenkins.phx.ovirt.org

Project: http://jenkins.ovirt.org/job/ovirt-appliance_master_build-artifacts-fc28-... Build: http://jenkins.ovirt.org/job/ovirt-appliance_master_build-artifacts-fc28-... Build Number: 114 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #114 [Evgheni Dereveanchin] Define Fedora 29 mirrors [Yuval Turgeman] automation: remove build-artifacts* from stdci-v2 ----------------- Failed Tests: ----------------- No tests ran.

6 years, 4 months

1
1
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Infra November 2018