- Infra - oVirt List Archives

fixture 'default_storage_domain' not found (was: Change in ovirt-system-tests[master]: Collect host-deploy bundle from the engine)
by Yedidyah Bar David 08 Apr '18

08 Apr '18

On Thu, Apr 5, 2018 at 12:50 PM, Code Review <gerrit(a)ovirt.org> wrote: > From Jenkins CI: > > Jenkins CI has posted comments on this change. > > Change subject: Collect host-deploy bundle from the engine > ...................................................................... > > > Patch Set 14: Continuous-Integration-1 > > Build Failed > > http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-el7-x86_… : FAILURE 09:46:48 ==================================== ERRORS ==================================== 09:46:48 ERROR at setup of test_set_mac_pool_duplicate_macs_from_true_to_false_while_dup_exists 09:46:48 file /home/jenkins/workspace/ovirt-system-tests_master_check-patch-el7-x86_64/ovirt-system-tests/network-suite-master/tests/test_mac_pools.py, line 66 09:46:48 def test_set_mac_pool_duplicate_macs_from_true_to_false_while_dup_exists( 09:46:48 E fixture 'default_storage_domain' not found 09:46:48 > available fixtures: cache, capfd, capfdbinary, caplog, capsys, capsysbinary, cluster_0, doctest_namespace, host_1_in_cluster_0, monkeypatch, pytestconfig, record_property, record_xml_attribute, record_xml_property, recwarn, tmpdir, tmpdir_factory 09:46:48 > use 'pytest --fixtures [testpath]' for help on them. 09:46:48 09:46:48 /home/jenkins/workspace/ovirt-system-tests_master_check-patch-el7-x86_64/ovirt-system-tests/network-suite-master/tests/test_mac_pools.py:66 09:46:48 _____ ERROR at setup of test_assign_vnic_with_full_mac_pool_capacity_fails _____ 09:46:48 file /home/jenkins/workspace/ovirt-system-tests_master_check-patch-el7-x86_64/ovirt-system-tests/network-suite-master/tests/test_mac_pools.py, line 87 09:46:48 def test_assign_vnic_with_full_mac_pool_capacity_fails( 09:46:48 E fixture 'default_storage_domain' not found 09:46:48 > available fixtures: cache, capfd, capfdbinary, caplog, capsys, capsysbinary, cluster_0, doctest_namespace, host_1_in_cluster_0, monkeypatch, pytestconfig, record_property, record_xml_attribute, record_xml_property, recwarn, tmpdir, tmpdir_factory 09:46:48 > use 'pytest --fixtures [testpath]' for help on them. 09:46:48 09:46:48 /home/jenkins/workspace/ovirt-system-tests_master_check-patch-el7-x86_64/ovirt-system-tests/network-suite-master/tests/test_mac_pools.py:87 and a few similar ones later on. Any clue? > > http://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/77/ : FAILURE > > -- > To view, visit https://gerrit.ovirt.org/88925 > To unsubscribe, visit https://gerrit.ovirt.org/settings > > Gerrit-Project: ovirt-system-tests > Gerrit-Branch: master > Gerrit-MessageType: comment > Gerrit-Change-Id: I8af18a3eded4aea4518cb0608e65c687081bce20 > Gerrit-Change-Number: 88925 > Gerrit-PatchSet: 14 > Gerrit-Owner: Yedidyah Bar David <didi(a)redhat.com> > Gerrit-Reviewer: Daniel Belenky <dbelenky(a)redhat.com> > Gerrit-Reviewer: Jenkins CI > Gerrit-Reviewer: Sandro Bonazzola <sbonazzo(a)redhat.com> > Gerrit-Reviewer: Yedidyah Bar David <didi(a)redhat.com> > Gerrit-Comment-Date: Thu, 05 Apr 2018 09:50:03 +0000 > Gerrit-HasComments: No -- Didi

3 3

[JIRA] (OVIRT-1966) Install OpenShift and Kubernetes Jenkisn plugins
by Barak Korren (oVirt JIRA) 08 Apr '18

08 Apr '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1966?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1966: -------------------------------- Issue Type: New Feature (was: Improvement) > Install OpenShift and Kubernetes Jenkisn plugins > ------------------------------------------------ > > Key: OVIRT-1966 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1966 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Jenkins Master, OpenShift > Reporter: Barak Korren > Assignee: infra > Priority: High > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100082)

1 0

[JIRA] (OVIRT-1966) Install OpenShift and Kubernetes Jenkisn plugins
by Barak Korren (oVirt JIRA) 08 Apr '18

08 Apr '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1966?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1966: ------------------------------------- Note: i've already installed the plugins manually on the staging instance. Hopefully they will not get uninstalled by puppet.... > Install OpenShift and Kubernetes Jenkisn plugins > ------------------------------------------------ > > Key: OVIRT-1966 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1966 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins Master, OpenShift > Reporter: Barak Korren > Assignee: infra > Priority: High > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100082)

1 0

[JIRA] (OVIRT-1966) Install OpenShift and Kubernetes Jenkisn plugins
by Barak Korren (oVirt JIRA) 08 Apr '18

08 Apr '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1966?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1966: -------------------------------- Epic Link: OVIRT-403 > Install OpenShift and Kubernetes Jenkisn plugins > ------------------------------------------------ > > Key: OVIRT-1966 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1966 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins Master, OpenShift > Reporter: Barak Korren > Assignee: infra > Priority: High > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100082)

1 0

[JIRA] (OVIRT-1966) Install OpenShift and Kubernetes Jenkisn plugins
by Barak Korren (oVirt JIRA) 08 Apr '18

08 Apr '18

Barak Korren created OVIRT-1966: ----------------------------------- Summary: Install OpenShift and Kubernetes Jenkisn plugins Key: OVIRT-1966 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1966 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Jenkins Master, OpenShift Reporter: Barak Korren Assignee: infra Priority: High In order to use OpenShift from Jenkins we probably need the following plugins: # Kubernetes # OpenShift Pipeline # OpenShift Client Please install them on our Jenkins instances. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100082)

1 0

[CQ]: 53e0cb3 (ovirt-ansible-repositories) failed "ovirt-4.2" system tests
by oVirt Jenkins 08 Apr '18

08 Apr '18

Change 53e0cb3 (ovirt-ansible-repositories) 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://github.com/oVirt/ovirt-ansible-repositories/commit/53e0cb398028f0ce… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/1601/

2 1

[CQ]: 89581,3 (ovirt-provider-ovn) failed "ovirt-4.2" system tests
by oVirt Jenkins 08 Apr '18

08 Apr '18

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

3 3

[CQ]: 2e43ef0 (ovirt-ansible) failed "ovirt-master" system tests
by oVirt Jenkins 08 Apr '18

08 Apr '18

Change 2e43ef0 (ovirt-ansible) 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://github.com/oVirt/ovirt-ansible/commit/2e43ef0739d5fcc5b59388f511ac2… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/6724/

3 4

[JIRA] (OVIRT-1965) Add failure details to CQ messages
by Barak Korren (oVirt JIRA) 08 Apr '18

08 Apr '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1965?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1965: -------------------------------- Epic Link: OVIRT-400 > Add failure details to CQ messages > ---------------------------------- > > Key: OVIRT-1965 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1965 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Change Queue > Reporter: Barak Korren > Assignee: infra > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100082)

1 0

[JIRA] (OVIRT-1965) Add failure details to CQ messages
by Barak Korren (oVirt JIRA) 08 Apr '18

08 Apr '18

This is a multi-part message in MIME format... ------------=_1523193258-16742-109 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Barak Korren created OVIRT-1965: ----------------------------------- Summary: Add failure details to CQ messages Key: OVIRT-1965 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1965 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Change Queue Reporter: Barak Korren Assignee: infra In order to streamline the process for debugging CQ issues, we should have more failure details added to the messages it sends. Those details should include: # The names of the OST suits that failed # The OST tests that failed # If it was a build failure rather then an OST failure # If it was possible to detect - the particular change(s) that caused failure. #if its possible to tell - if its an infra issue or a code regression To implement this we would need at the very least a richer interface for passing information between the CQ tester and the and manager jobs - possibly some kind of a structured data file passed around. We may also need a richer interface to OST itself (to tell which test failed) and perhaps even to the build jobs (to tell why the build failed). -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100082) ------------=_1523193258-16742-109 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <h3>Barak Korren created OVIRT-1965:</h3> <pre> Summary: Add failure details to CQ messages Key: OVIRT-1965 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1965 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Change Queue Reporter: Barak Korren Assignee: infra</pre> <p>In order to streamline the process for debugging CQ issues, we should have more failure details added to the messages it sends. Those details should include:</p> <p># The names of the OST suits that failed # The OST tests that failed # If it was a build failure rather then an OST failure # If it was possible to detect – the particular change(s) that caused failure.</p> <pre>#if its possible to tell - if its an infra issue or a code regression</pre> <p>To implement this we would need at the very least a richer interface for passing information between the CQ tester and the and manager jobs – possibly some kind of a structured data file passed around. We may also need a richer interface to OST itself (to tell which test failed) and perhaps even to the build jobs (to tell why the build failed).</p> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100082)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1523193258-16742-109--

1 0