November 2018 - Infra - Ovirt List Archives

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

by Dafna Ron (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2542?page=com.atlassian.jir... ] Dafna Ron commented on OVIRT-2542: ---------------------------------- https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10977/ > 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: infra > 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

[CQ]: 95190,2 (ovirt-engine) failed "ovirt-master" system tests

by oVirt Jenkins

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

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)

Dafna Ron created OVIRT-2568: -------------------------------- Summary: 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 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

[JIRA] (OVIRT-2567) jenkins password in secrets file has expired/ not matched any longer.

by Ehud Yonasi (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2567?page=com.atlassian.jir... ] Ehud Yonasi reassigned OVIRT-2567: ---------------------------------- Assignee: Ehud Yonasi (was: infra) > jenkins password in secrets file has expired/ not matched any longer. > --------------------------------------------------------------------- > > Key: OVIRT-2567 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2567 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Ehud Yonasi > Assignee: Ehud Yonasi > > jenkins password on secrets yaml is no longer working. > I am working on creating a jenkins job to update or create new secrets file. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

6 years, 4 months

1
0
0 / 0

[JIRA] (OVIRT-2567) jenkins password in secrets file has expired/ not matched any longer.

by Ehud Yonasi (oVirt JIRA)

Ehud Yonasi created OVIRT-2567: ---------------------------------- Summary: jenkins password in secrets file has expired/ not matched any longer. Key: OVIRT-2567 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2567 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Ehud Yonasi Assignee: infra jenkins password on secrets yaml is no longer working. I am working on creating a jenkins job to update or create new secrets file. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

6 years, 4 months

1
0
0 / 0

[oVirt CI] standard-enqueue - Build #17248 - FAILURE!

by jenkins＠jenkins.phx.ovirt.org

Build: http://jenkins.ovirt.org/job/standard-enqueue/17248/ Build Name: #17248 Build Description: Gerrit: 95175 - ovirt-vmconsole (4.1, 4.2, master) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/95175 - title: build: Fixes for python2/3 builds - project: ovirt-vmconsole - branch: master - author: Tomasz Baranski <tbaransk(a)redhat.com>

6 years, 4 months

1
0
0 / 0

[JIRA] (OVIRT-2566) make network suite blocking

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2566?page=com.atlassian.jir... ] Barak Korren edited comment on OVIRT-2566 at 11/5/18 7:55 AM: -------------------------------------------------------------- {quote} To save time I prefer the network suite to run in parallel to the basic suite. {quote} Its not a matter of preference - there is no other option. [~gbenhaim(a)redhat.com] WDYT? will this prolong our CQ iterations? Also how are we with capacity? Do we have enough? would this be a good candidate to run in a container? cc: [~ederevea] was (Author: bkorren(a)redhat.com): {quote} To save time I prefer the network suite to run in parallel to the basic suite. {quote} Its not a matter of preference - there is not other option. [~gbenhaim(a)redhat.com] WDYT? will this prolong our CQ iterations? Also how are we with capacity? Do we have enough? would this be a good candidate to run in a container? cc: [~ederevea] > make network suite blocking > --------------------------- > > Key: OVIRT-2566 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2566 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: OST > Reporter: danken > Assignee: infra > Priority: High > > The network suite is executing nightly for almost a year. It has a caring team that tends to it, and it does not have false positives. > Currently, it currently fails for a week on the 4.2 branch, but it is due to a production code bug. > https://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-te... > I would like to see this suite escalated to the importance of the basic suite, making it a gating condition for marking a collection of packages as "tested". > [~gbenhaim(a)redhat.com], what should be done to make this happen? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

6 years, 4 months

1
0
0 / 0

[JIRA] (OVIRT-2566) make network suite blocking

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2566?page=com.atlassian.jir... ] Barak Korren edited comment on OVIRT-2566 at 11/5/18 7:55 AM: -------------------------------------------------------------- {quote} To save time I prefer the network suite to run in parallel to the basic suite. {quote} Its not a matter of preference - there is not other option. [~gbenhaim(a)redhat.com] WDYT? will this prolong our CQ iterations? Also how are we with capacity? Do we have enough? would this be a good candidate to run in a container? cc: [~ederevea] was (Author: bkorren(a)redhat.com): {{quote}} To save time I prefer the network suite to run in parallel to the basic suite. {{quote}} Its not a matter of preference - there is not other option. [~gbenhaim(a)redhat.com] WDYT? will this prolong our CQ iterations? Also how are we with capacity? Do we have enough? would this be a good candidate to run in a container? cc: [~ederevea] > make network suite blocking > --------------------------- > > Key: OVIRT-2566 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2566 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: OST > Reporter: danken > Assignee: infra > Priority: High > > The network suite is executing nightly for almost a year. It has a caring team that tends to it, and it does not have false positives. > Currently, it currently fails for a week on the 4.2 branch, but it is due to a production code bug. > https://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-te... > I would like to see this suite escalated to the importance of the basic suite, making it a gating condition for marking a collection of packages as "tested". > [~gbenhaim(a)redhat.com], what should be done to make this happen? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

6 years, 4 months

1
0
0 / 0

[JIRA] (OVIRT-2566) make network suite blocking

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2566?page=com.atlassian.jir... ] Barak Korren commented on OVIRT-2566: ------------------------------------- {{quote}} To save time I prefer the network suite to run in parallel to the basic suite. {{quote}} Its not a matter of preference - there is not other option. [~gbenhaim(a)redhat.com] WDYT? will this prolong our CQ iterations? Also how are we with capacity? Do we have enough? would this be a good candidate to run in a container? cc: [~ederevea] > make network suite blocking > --------------------------- > > Key: OVIRT-2566 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2566 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: OST > Reporter: danken > Assignee: infra > Priority: High > > The network suite is executing nightly for almost a year. It has a caring team that tends to it, and it does not have false positives. > Currently, it currently fails for a week on the 4.2 branch, but it is due to a production code bug. > https://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-te... > I would like to see this suite escalated to the importance of the basic suite, making it a gating condition for marking a collection of packages as "tested". > [~gbenhaim(a)redhat.com], what should be done to make this happen? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

6 years, 4 months

1
0
0 / 0

[JIRA] (OVIRT-2566) make network suite blocking

by danken (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2566?page=com.atlassian.jir... ] danken commented on OVIRT-2566: ------------------------------- https://jenkins.ovirt.org/job/ovirt-system-tests_network-suite-4.2/buildT... shows that it runs for 44-48 minutes. https://jenkins.ovirt.org/job/ovirt-system-tests_network-suite-master/bui... runs slightly quicker (41-45 minutes) To save time I prefer the network suite to run in parallel to the basic suite. > make network suite blocking > --------------------------- > > Key: OVIRT-2566 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2566 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: OST > Reporter: danken > Assignee: infra > Priority: High > > The network suite is executing nightly for almost a year. It has a caring team that tends to it, and it does not have false positives. > Currently, it currently fails for a week on the 4.2 branch, but it is due to a production code bug. > https://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-te... > I would like to see this suite escalated to the importance of the basic suite, making it a gating condition for marking a collection of packages as "tested". > [~gbenhaim(a)redhat.com], what should be done to make this happen? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

6 years, 4 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Infra November 2018