June 2021 - Infra - Ovirt List Archives

[oVirt Jenkins] ovirt-release_4.3_build-artifacts-el7-x86_64 - Build # 1019 - Failure!

by jenkins＠jenkins.phx.ovirt.org

Project: https://jenkins.ovirt.org/job/ovirt-release_4.3_build-artifacts-el7-x86_64/ Build: https://jenkins.ovirt.org/job/ovirt-release_4.3_build-artifacts-el7-x86_6... Build Number: 1019 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #1019 [Sandro Bonazzola] Revert "automation: install centos-release if missing" ----------------- Failed Tests: ----------------- No tests ran.

2 years, 9 months

1
1
0 / 0

[oVirt Jenkins] ovirt-system-tests_basic-suite-master_nightly - Build # 1261 - Failure!

by jenkins＠jenkins.phx.ovirt.org

Project: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-master_nightly/ Build: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-master_night... Build Number: 1261 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #1261 [Yedidyah Bar David] ansible: fix engine fqdn detection ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: basic-suite-master.test-scenarios.test_100_basic_ui_sanity.test_clusters[firefox] Error Message: selenium.common.exceptions.TimeoutException: Message: Clusters menu is not displayed Stack Trace: ovirt_driver = <ost_utils.selenium.navigation.driver.Driver object at 0x7f04b05565c0> def test_clusters(ovirt_driver): webadmin_menu = WebAdminLeftMenu(ovirt_driver) > cluster_list_view = webadmin_menu.open_cluster_list_view() basic-suite-master/test-scenarios/test_100_basic_ui_sanity.py:301: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ ost_utils/ost_utils/selenium/page_objects/WebAdminLeftMenu.py:69: in open_cluster_list_view self._open_compute_menu('Clusters', 'MenuView_clustersAnchor') ost_utils/ost_utils/selenium/page_objects/WebAdminLeftMenu.py:95: in _open_compute_menu self._open_menu('compute', menu_name, menu_id) ost_utils/ost_utils/selenium/page_objects/WebAdminLeftMenu.py:105: in _open_menu self.ovirt_driver.id_wait_and_click(menu_name + ' menu', menu_id) ost_utils/ost_utils/selenium/navigation/driver.py:231: in id_wait_and_click self.xpath_wait_and_click(message, '//*[@id="' + element_id + '"]', wait_long) ost_utils/ost_utils/selenium/navigation/driver.py:301: in xpath_wait_and_click wait_until(message + ' is not displayed', self.is_xpath_displayed, xpath) ost_utils/ost_utils/selenium/navigation/driver.py:306: in wait_until self._wait_until(message, assertions.SHORT_TIMEOUT, condition_method, *args) ost_utils/ost_utils/selenium/navigation/driver.py:312: in _wait_until WebDriverWait(self.driver, timeout).until(ConditionClass(condition_method, *args), message) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = <selenium.webdriver.support.wait.WebDriverWait (session="13b19ca4-f917-435c-858a-2bcf94b812e9")> method = <ost_utils.selenium.navigation.driver.ConditionClass object at 0x7f04b0684550> message = 'Clusters menu is not displayed' def until(self, method, message=''): """Calls the method provided with the driver as an argument until the \ return value is not False.""" screen = None stacktrace = None end_time = time.time() + self._timeout while True: try: value = method(self._driver) if value: return value except self._ignored_exceptions as exc: screen = getattr(exc, 'screen', None) stacktrace = getattr(exc, 'stacktrace', None) time.sleep(self._poll) if time.time() > end_time: break > raise TimeoutException(message, screen, stacktrace) E selenium.common.exceptions.TimeoutException: Message: Clusters menu is not displayed .tox/deps/lib/python3.6/site-packages/selenium/webdriver/support/wait.py:80: TimeoutException

2 years, 9 months

1
1
0 / 0

[oVirt Jenkins] ovirt-release_4.2_build-artifacts-el7-x86_64 - Build # 1450 - Failure!

by jenkins＠jenkins.phx.ovirt.org

Project: https://jenkins.ovirt.org/job/ovirt-release_4.2_build-artifacts-el7-x86_64/ Build: https://jenkins.ovirt.org/job/ovirt-release_4.2_build-artifacts-el7-x86_6... Build Number: 1450 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #1450 [Sandro Bonazzola] automation: add v2 configuration ----------------- Failed Tests: ----------------- No tests ran.

2 years, 9 months

1
1
0 / 0

oVirt infra daily report - unstable production jobs - 1597

by jenkins＠jenkins.phx.ovirt.org

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - https://jenkins.ovirt.org/job/system_jenkins-report/1597//artifact/export... Cheers, Jenkins

2 years, 9 months

1
0
0 / 0

[CQ]: 115412, 1 (ovirt-node-ng-image) 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 115412,1 (ovirt-node-ng-image) failed. However, this change seems not to be the root cause for this failure. Change 114808,1 (ovirt-node-ng-image) 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 114808,1 (ovirt-node-ng-image) 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/ovirt-node-ng-image/+/#/c/115412/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/c/ovirt-node-ng-image/+/#/c/114808/1 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/30439/

2 years, 9 months

1
0
0 / 0

[CQ]: 115400,2 (jenkins) failed "dummy-master" system tests

by oVirt Jenkins

Change 115400,2 (jenkins) is probably the reason behind recent system test failures in the "dummy-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/jenkins/+/#/c/115400/2 For failed test results see: https://jenkins.ovirt.org/job/dummy-master_change-queue-tester/627/

2 years, 10 months

1
0
0 / 0

[oVirt Jenkins] deploy-to-gated-dummy-master - Build #556 - FAILURE!

by jenkins＠jenkins.phx.ovirt.org

Build: https://jenkins.ovirt.org/job/deploy-to-gated-dummy-master/556/ Build Name: #556 Build Status: FAILURE Gerrit change: null - title: null - project: null - branch: null - author: null <null>

2 years, 10 months

1
0
0 / 0

[JIRA] (OVIRT-3101) Add "ci system-test" command

by Shani Leviim (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-3101?page=com.atlassian.jir... ] Shani Leviim commented on OVIRT-3101: ------------------------------------- +1 for adding the suite name. BTW, you can run manually OST with your own parameters (engine artifacts and OST patch set). *Regards,* *Shani Leviim* On Thu, Jun 24, 2021 at 3:08 PM Nir Soffer <nsoffer(a)redhat.com> wrote: > On Thu, Jun 24, 2021 at 2:11 PM Yedidyah Bar David <didi(a)redhat.com> > wrote: > > > > On Thu, Jun 24, 2021 at 1:51 PM Marcin Sobczyk <msobczyk(a)redhat.com> > wrote: > > > > > > > > > > > > On 6/23/21 5:44 PM, Nir Soffer wrote: > > > > Similar to "ci build", "ci test", "ci merge" add a new command that > > > > triggers OST run. > > > > > > > > Running OST is tied now in vdsm (and engine?) to Code-Review: +2. > > > > This causes trouble and does not allow non-maintainers to use the > convenient OST > > > > infrastructure. > > > > > > > > Expected flow: > > > > > > > > 1. User add a comment with "ci system-test" > > > "ci system-test" is sooo long, I vote for "ci ost". > > > > +1. > > > > Perhaps we can add an optional suite name? E.g. 'ci ost > ansible-suite-master' > > +1 > _______________________________________________ > Devel mailing list -- devel(a)ovirt.org > To unsubscribe send an email to devel-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/devel@ovirt.org/message/SKS3XFCIC6S... > > Add "ci system-test" command > ---------------------------- > > Key: OVIRT-3101 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3101 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > Similar to "ci build", "ci test", "ci merge" add a new command that > triggers OST run. > Running OST is tied now in vdsm (and engine?) to Code-Review: +2. > This causes trouble and does not allow non-maintainers to use the convenient OST > infrastructure. > Expected flow: > 1. User add a comment with "ci system-test" > 2. OST flow building and running OST triggered -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100166)

2 years, 10 months

1
0
0 / 0

[JIRA] (OVIRT-3101) Add "ci system-test" command

by Nir Soffer (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-3101?page=com.atlassian.jir... ] Nir Soffer commented on OVIRT-3101: ----------------------------------- On Thu, Jun 24, 2021 at 1:49 PM Marcin Sobczyk <msobczyk(a)redhat.com> wrote: > > > > On 6/23/21 5:44 PM, Nir Soffer wrote: > > Similar to "ci build", "ci test", "ci merge" add a new command that > > triggers OST run. > > > > Running OST is tied now in vdsm (and engine?) to Code-Review: +2. > > This causes trouble and does not allow non-maintainers to use the convenient OST > > infrastructure. > > > > Expected flow: > > > > 1. User add a comment with "ci system-test" > "ci system-test" is sooo long, I vote for "ci ost". Works for me, but "system-test" is more consistent with other ci commands: https://ovirt-infra-docs.readthedocs.io/en/latest/CI/Using_STDCI_with_Ger... > Add "ci system-test" command > ---------------------------- > > Key: OVIRT-3101 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3101 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > Similar to "ci build", "ci test", "ci merge" add a new command that > triggers OST run. > Running OST is tied now in vdsm (and engine?) to Code-Review: +2. > This causes trouble and does not allow non-maintainers to use the convenient OST > infrastructure. > Expected flow: > 1. User add a comment with "ci system-test" > 2. OST flow building and running OST triggered -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100166)

2 years, 10 months

1
0
0 / 0

[JIRA] (OVIRT-3101) Add "ci system-test" command

by Nir Soffer (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-3101?page=com.atlassian.jir... ] Nir Soffer commented on OVIRT-3101: ----------------------------------- On Thu, Jun 24, 2021 at 2:11 PM Yedidyah Bar David <didi(a)redhat.com> wrote: > > On Thu, Jun 24, 2021 at 1:51 PM Marcin Sobczyk <msobczyk(a)redhat.com> wrote: > > > > > > > > On 6/23/21 5:44 PM, Nir Soffer wrote: > > > Similar to "ci build", "ci test", "ci merge" add a new command that > > > triggers OST run. > > > > > > Running OST is tied now in vdsm (and engine?) to Code-Review: +2. > > > This causes trouble and does not allow non-maintainers to use the convenient OST > > > infrastructure. > > > > > > Expected flow: > > > > > > 1. User add a comment with "ci system-test" > > "ci system-test" is sooo long, I vote for "ci ost". > > +1. > > Perhaps we can add an optional suite name? E.g. 'ci ost ansible-suite-master' +1 > Add "ci system-test" command > ---------------------------- > > Key: OVIRT-3101 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3101 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > Similar to "ci build", "ci test", "ci merge" add a new command that > triggers OST run. > Running OST is tied now in vdsm (and engine?) to Code-Review: +2. > This causes trouble and does not allow non-maintainers to use the convenient OST > infrastructure. > Expected flow: > 1. User add a comment with "ci system-test" > 2. OST flow building and running OST triggered -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100166)

2 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Infra June 2021