- Infra - oVirt List Archives

[oVirt Jenkins] ovirt-system-tests_basic-suite-4.3_el7-nightly - Build # 589 - Failure!
by jenkins＠jenkins.phx.ovirt.org 25 Jun '21

25 Jun '21

Project: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-4.3_el7-nightl… Build: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-4.3_el7-nightl… Build Number: 589 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #589 [parthdhanjal] Updating max click version ----------------- Failed Tests: ----------------- No tests ran.

1 5

[oVirt Jenkins] ovirt-release_4.3_build-artifacts-el7-x86_64 - Build # 1019 - Failure!
by jenkins＠jenkins.phx.ovirt.org 25 Jun '21

25 Jun '21

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_64/… 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.

1 1

[oVirt Jenkins] ovirt-system-tests_basic-suite-master_nightly - Build # 1261 - Failure!
by jenkins＠jenkins.phx.ovirt.org 25 Jun '21

25 Jun '21

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_nightly… 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

1 1

[oVirt Jenkins] ovirt-release_4.2_build-artifacts-el7-x86_64 - Build # 1450 - Failure!
by jenkins＠jenkins.phx.ovirt.org 25 Jun '21

25 Jun '21

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_64/… 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.

1 1

oVirt infra daily report - unstable production jobs - 1597
by jenkins＠jenkins.phx.ovirt.org 25 Jun '21

25 Jun '21

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/exported… Cheers, Jenkins

1 0

[CQ]: 115412, 1 (ovirt-node-ng-image) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 24 Jun '21

24 Jun '21

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/

1 0

[CQ]: 115400,2 (jenkins) failed "dummy-master" system tests
by oVirt Jenkins 24 Jun '21

24 Jun '21

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/

1 0

[oVirt Jenkins] deploy-to-gated-dummy-master - Build #556 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 24 Jun '21

24 Jun '21

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>

1 0

[JIRA] (OVIRT-3101) Add "ci system-test" command
by Shani Leviim (oVirt JIRA) 24 Jun '21

24 Jun '21

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

1 0

[JIRA] (OVIRT-3101) Add "ci system-test" command
by Nir Soffer (oVirt JIRA) 24 Jun '21

24 Jun '21

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

1 0

[JIRA] (OVIRT-3101) Add "ci system-test" command
by Nir Soffer (oVirt JIRA) 24 Jun '21

24 Jun '21

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

1 0

[JIRA] (OVIRT-3101) Add "ci system-test" command
by Yedidyah Bar David (oVirt JIRA) 24 Jun '21

24 Jun '21

[ https://ovirt-jira.atlassian.net/browse/OVIRT-3101?page=com.atlassian.jira.… ] Yedidyah Bar David commented on OVIRT-3101: ------------------------------------------- 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' Best regards, -- Didi > 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)

1 0

[JIRA] (OVIRT-3101) Add "ci system-test" command
by Marcin Sobczyk (oVirt JIRA) 24 Jun '21

24 Jun '21

[ https://ovirt-jira.atlassian.net/browse/OVIRT-3101?page=com.atlassian.jira.… ] Marcin Sobczyk commented on OVIRT-3101: --------------------------------------- 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". Regards, Marcin > 2. OST flow building and running OST triggered > _______________________________________________ > 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/2FCJZLFJJ2SB3… > 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)

1 0

[CQ]: 115356, 3 (ovirt-system-tests) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 24 Jun '21

24 Jun '21

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

1 0

[oVirt Jenkins] cleanup-gated-dummy-master - Build #551 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 24 Jun '21

24 Jun '21

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

1 0

oVirt infra daily report - unstable production jobs - 1596
by jenkins＠jenkins.phx.ovirt.org 24 Jun '21

24 Jun '21

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/1596//artifact/exported… Cheers, Jenkins

1 0

[JIRA] (OVIRT-3101) Add "ci system-test" command
by Nir Soffer (oVirt JIRA) 23 Jun '21

23 Jun '21

Nir Soffer created OVIRT-3101: --------------------------------- Summary: 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)

1 0

[JIRA] (OVIRT-3100) Add OST flag to all oVirt projects
by Nir Soffer (oVirt JIRA) 23 Jun '21

23 Jun '21

Nir Soffer created OVIRT-3100: --------------------------------- Summary: Add OST flag to all oVirt projects Key: OVIRT-3100 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3100 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Nir Soffer Assignee: infra Similar to Continuous-Integration flag, OST needs its own flag. OST will set this flag when OST build started from gerrit was started. We want to make this field mandatory for merging patches, like Continuous-Integration. Like Continuous-Integration maintainers should be able to override the value after OST completed, or set the value before OST started. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100166)

1 0

[CQ]: 115368, 1 (ovirt-system-tests) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 23 Jun '21

23 Jun '21

A system test invoked by the "ovirt-master" change queue including change 115368,1 (ovirt-system-tests) failed. However, this change seems not to be the root cause for this failure. Change 113144,5 (ovirt-system-tests) 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 113144,5 (ovirt-system-tests) 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-system-tests/+/#/c/115368/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-system-tests/+/#/c/113144/5 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/30387/

1 0

[CQ]: 115337, 3 (ovirt-system-tests) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 23 Jun '21

23 Jun '21

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

1 0

[oVirt Jenkins] ovirt-system-tests_basic-suite-4.3_nightly - Build # 593 - Failure!
by jenkins＠jenkins.phx.ovirt.org 23 Jun '21

23 Jun '21

Project: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-4.3_nightly/ Build: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-4.3_nightly/59… Build Number: 593 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #593 [parthdhanjal] Updating max click version ----------------- Failed Tests: ----------------- No tests ran.

1 2

[CQ]: 115333, 3 (ovirt-system-tests) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 23 Jun '21

23 Jun '21

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

1 0

[oVirt Jenkins] ovirt-system-tests_basic-suite-4.3_el7-nightly - Build # 587 - Failure!
by jenkins＠jenkins.phx.ovirt.org 23 Jun '21

23 Jun '21

Project: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-4.3_el7-nightl… Build: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-4.3_el7-nightl… Build Number: 587 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #587 [parthdhanjal] Updating max click version ----------------- Failed Tests: ----------------- No tests ran.

1 1

planned Jenkins restart
by Evgheni Dereveanchin 23 Jun '21

23 Jun '21

Hi everyone, I'll be performing a planned Jenkins restart within the next hour. No new CI jobs will be scheduled during this maintenance period. I will inform you once it is back online. -- Regards, Evgheni Dereveanchin

1 1

oVirt infra daily report - unstable production jobs - 1595
by jenkins＠jenkins.phx.ovirt.org 23 Jun '21

23 Jun '21

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/1595//artifact/exported… Cheers, Jenkins

1 0

[JIRA] (OVIRT-3099) Re: oVirt CI mirror for centos stream advancedvirt-common repo
by Nir Soffer (oVirt JIRA) 22 Jun '21

22 Jun '21

Nir Soffer created OVIRT-3099: --------------------------------- Summary: Re: oVirt CI mirror for centos stream advancedvirt-common repo Key: OVIRT-3099 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3099 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Nir Soffer Assignee: infra On Fri, Jun 11, 2021 at 12:41 PM Sandro Bonazzola <sbonazzo(a)redhat.com> wrote: > > > Il giorno ven 4 giu 2021 alle ore 19:44 Nir Soffer <nsoffer(a)redhat.com> > ha scritto: > >> I updated vdsm libvirt requirement to 7.0.0-14. The package exists in >> centos >> stream and rhel so the change is correct, but the install check fails in >> the CI. >> >> I found that adding the repo to check-patch.repos works: >> https://gerrit.ovirt.org/c/vdsm/+/115039/4/automation/check-patch.repos >> >> But depending on mirror.centos.org does not feel like the right way. I >> think >> keeping a local mirror is the right way. >> > > Please note that despite we are pointing to centos mirrors, CI is running > under proxy, so we are caching on our datacenter the rpms we consume anyway. > That said, we can mirror advanced virtualization repos as well and the > local mirror will be automatically picked up. > > I see we are already mirroring the test repo for CentOS Linux: > ./data/mirrors-reposync.conf: > 70 : [ovirt-master-centos-advanced-virtualization-el8] > 72 : baseurl= > https://buildlogs.centos.org/centos/8/virt/x86_64/advanced-virtualization/ > > For CentOS Stream we'll need an addition there. Please open a ticket on > infra-support(a)ovirt.org about it. > Trying > > > >> It looks like the stdci docs[1] are not maintained for a while, >> listing mirrors for >> fedora 30 and centos 7. >> > > I would suggest to open a ticket for this as well > > > >> >> Looking in the mirrors jobs[2] we have advanced-virtualization for >> centos[3] but >> it holds old versions (6.x). >> >> Can we add a local mirror for this repo? >> >> [1] >> https://ovirt-infra-docs.readthedocs.io/en/latest/CI/List_of_mirrors/index.… >> [2] https://jenkins.ovirt.org/search/?q=system-sync_mirrors >> [3] >> https://buildlogs.centos.org/centos/8/virt/x86_64/advanced-virtualization/P… >> >> Nir >> >> > > -- > > Sandro Bonazzola > > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > > Red Hat EMEA <https://www.redhat.com/> > > sbonazzo(a)redhat.com > <https://www.redhat.com/> > > *Red Hat respects your work life balance. Therefore there is no need to > answer this email out of your office hours. > <https://mojo.redhat.com/docs/DOC-1199578>* > > > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100166)

1 0

[CQ]: 115326,1 (ovirt-imageio) failed "ovirt-master" system tests
by oVirt Jenkins 22 Jun '21

22 Jun '21

Change 115326,1 (ovirt-imageio) 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/ovirt-imageio/+/#/c/115326/1 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/30364/

1 0

[JIRA] (OVIRT-3098) Gerrit hook adds unrelated patches to bugs
by Yedidyah Bar David (oVirt JIRA) 22 Jun '21

22 Jun '21

[ https://ovirt-jira.atlassian.net/browse/OVIRT-3098?page=com.atlassian.jira.… ] Yedidyah Bar David commented on OVIRT-3098: ------------------------------------------- On Mon, Jun 21, 2021 at 9:58 PM Eyal Shenitzky <eshenitz(a)redhat.com> wrote: > > > +Dusan Fodor > > On Mon, 21 Jun 2021 at 13:32, Nir Soffer <nsoffer(a)redhat.com> wrote: >> >> Gerrit hook is wrongly looking for https://bugzilla.redhat.com/ URLs >> in the commit message, and adding the patch to the bug. >> >> Example patch: >> https://gerrit.ovirt.org/c/vdsm/+/115339 >> >> I had to clean up the bug after the broken hook (see screenshot). >> >> The hook should really look only in the single URL in (one or more) >> Bug-Url headers: >> >> Bug-Url: https://bugzilla.redhat.com/ >> >> I reported this years ago (I think for Related-To:), and I remember we had >> a patch fixing this issue, but for some reason it was lost. >> >> Nir See also: https://ovirt-jira.atlassian.net/browse/OVIRT-3075 Best regards, -- Didi > Gerrit hook adds unrelated patches to bugs > ------------------------------------------ > > Key: OVIRT-3098 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3098 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > Attachments: Screenshot from 2021-06-21 13-16-19.png > > > Gerrit hook is wrongly looking for https://bugzilla.redhat.com/ URLs > in the commit message, and adding the patch to the bug. > Example patch: > https://gerrit.ovirt.org/c/vdsm/+/115339 > I had to clean up the bug after the broken hook (see screenshot). > The hook should really look only in the single URL in (one or more) > Bug-Url headers: > Bug-Url: https://bugzilla.redhat.com/ > I reported this years ago (I think for Related-To:), and I remember we had > a patch fixing this issue, but for some reason it was lost. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100166)

1 0

[CQ]: 115354, 5 (ovirt-system-tests) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 22 Jun '21

22 Jun '21

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

1 0

[oVirt Jenkins] ovirt-system-tests_basic-suite-master_nightly - Build # 1246 - Failure!
by jenkins＠jenkins.phx.ovirt.org 22 Jun '21

22 Jun '21

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_nightly… Build Number: 1246 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #1246 [Shani Leviim] engine_utils: verify job status by correlation id ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: basic-suite-master.test-scenarios.test_007_sd_reattach.test_deactivate_storage_domain Error Message: AssertionError: set() != {<JobStatus.FINISHED: 'finished'>} after 180 seconds Stack Trace: engine_api = <ovirtsdk4.Connection object at 0x7f522564b5c0> @order_by(_TEST_LIST) def test_deactivate_storage_domain(engine_api): # TODO: uncomment once VnicSetup checks are fixed. # TODO: this also seems to leave running tasks behind which break the deactivation. # TODO: it should be tested in multiple runs or properly waited for. # VnicSetup.vnic_setup().init(engine_api.system_service(), # VM2_NAME, DC_NAME, CLUSTER_NAME) engine = engine_api.system_service() dc = test_utils.data_center_service(engine_api.system_service(), DC_NAME) correlation_id = 'deactivate_storage_domain' def _deactivate_with_running_ovf_update_task(): try: test_utils.get_attached_storage_domain( dc, SD_SECOND_NFS_NAME, service=True).deactivate( query={'correlation_id': correlation_id}) return True except ovirtsdk4.Error as err: # The storage domain's deactivation may fail if it has running tasks. # In case of updating ovf_store disks task (UploadStream), # ignore. Otherwise, raise the exception. if not (('UploadStream' in err.args[0]) or ('OVF' in err.args[0])): raise return False assertions.assert_true_within_short( _deactivate_with_running_ovf_update_task) # Wait for the storage deactivation to be finished. assertions.assert_equals_within_short( lambda: > engine_utils.get_jobs_statuses(engine, correlation_id), {ovirtsdk4.types.JobStatus.FINISHED} ) basic-suite-master/test-scenarios/test_007_sd_reattach.py:85: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ ost_utils/ost_utils/assertions.py:74: in assert_equals_within_short error_message=error_message _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ func = <function test_deactivate_storage_domain.<locals>.<lambda> at 0x7f522576e0d0> value = {<JobStatus.FINISHED: 'finished'>}, timeout = 180 allowed_exceptions = [], initial_wait = 0 error_message = "set() != {<JobStatus.FINISHED: 'finished'>} after 180 seconds" def assert_equals_within( func, value, timeout, allowed_exceptions=None, initial_wait=10, error_message=None ): allowed_exceptions = allowed_exceptions or [] res = '<no-result-obtained>' with _EggTimer(timeout) as timer: while not timer.elapsed(): try: res = func() if res == value: return except Exception as exc: if _instance_of_any(exc, allowed_exceptions): time.sleep(3) continue LOGGER.exception("Unhandled exception in %s", func) raise if initial_wait == 0: time.sleep(3) else: time.sleep(initial_wait) initial_wait = 0 try: if error_message is None: error_message = '%s != %s after %s seconds' % (res, value, timeout) > raise AssertionError(error_message) E AssertionError: set() != {<JobStatus.FINISHED: 'finished'>} after 180 seconds ost_utils/ost_utils/assertions.py:59: AssertionError

1 9

[CQ]: 115064, 3 (ovirt-system-tests) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 22 Jun '21

22 Jun '21

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

1 0

[oVirt Jenkins] ovirt-system-tests_basic-suite-4.3_nightly - Build # 588 - Failure!
by jenkins＠jenkins.phx.ovirt.org 22 Jun '21

22 Jun '21

Project: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-4.3_nightly/ Build: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-4.3_nightly/58… Build Number: 588 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #588 [parthdhanjal] Updating max click version ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 004_basic_sanity.run_vms Error Message: Fault reason is "Operation Failed". Fault detail is "[Network error during communication with the Host.]". HTTP response code is 400. Stack Trace: Traceback (most recent call last): 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 "/home/jenkins/agent/workspace/ovirt-system-tests_basic-suite-4.3_nightly/ovirt-system-tests/basic-suite-4.3/test-scenarios/004_basic_sanity.py", line 694, in run_vms vm0_service.start(use_cloud_init=True, vm=vm_params) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 32520, in start return self._internal_action(action, 'start', None, headers, query, wait) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 299, in _internal_action return future.wait() if wait else future File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 55, in wait return self._code(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 296, in callback self._check_fault(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 134, in _check_fault self._raise_error(response, body.fault) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 118, in _raise_error raise error Error: Fault reason is "Operation Failed". Fault detail is "[Network error during communication with the Host.]". HTTP response code is 400.

1 2

oVirt infra daily report - unstable production jobs - 1594
by jenkins＠jenkins.phx.ovirt.org 22 Jun '21

22 Jun '21

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/1594//artifact/exported… Cheers, Jenkins

1 0

[CQ]: 114741, 5 (ovirt-system-tests) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 21 Jun '21

21 Jun '21

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

1 0

[CQ]: 115341, 2 (ovirt-system-tests) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 21 Jun '21

21 Jun '21

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

1 0

[CQ]: 115336, 4 (ovirt-system-tests) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 21 Jun '21

21 Jun '21

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

1 0

[CQ]: 115343, 1 (ovirt-system-tests) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 21 Jun '21

21 Jun '21

A system test invoked by the "ovirt-master" change queue including change 115343,1 (ovirt-system-tests) failed. However, this change seems not to be the root cause for this failure. Change 113144,5 (ovirt-system-tests) 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 113144,5 (ovirt-system-tests) 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-system-tests/+/#/c/115343/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-system-tests/+/#/c/113144/5 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/30332/

1 0

[JIRA] (OVIRT-3098) Gerrit hook adds unrelated patches to bugs
by Eyal Shenitzky (oVirt JIRA) 21 Jun '21

21 Jun '21

[ https://ovirt-jira.atlassian.net/browse/OVIRT-3098?page=com.atlassian.jira.… ] Eyal Shenitzky commented on OVIRT-3098: --------------------------------------- +Dusan Fodor <dfodor(a)redhat.com> On Mon, 21 Jun 2021 at 13:32, Nir Soffer <nsoffer(a)redhat.com> wrote: > Gerrit hook is wrongly looking for https://bugzilla.redhat.com/ URLs > in the commit message, and adding the patch to the bug. > > Example patch: > https://gerrit.ovirt.org/c/vdsm/+/115339 > > I had to clean up the bug after the broken hook (see screenshot). > > The hook should really look only in the single URL in (one or more) > Bug-Url headers: > > Bug-Url: https://bugzilla.redhat.com/ > > I reported this years ago (I think for Related-To:), and I remember we had > a patch fixing this issue, but for some reason it was lost. > > Nir > -- Regards, Eyal Shenitzky > Gerrit hook adds unrelated patches to bugs > ------------------------------------------ > > Key: OVIRT-3098 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3098 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > Attachments: Screenshot from 2021-06-21 13-16-19.png > > > Gerrit hook is wrongly looking for https://bugzilla.redhat.com/ URLs > in the commit message, and adding the patch to the bug. > Example patch: > https://gerrit.ovirt.org/c/vdsm/+/115339 > I had to clean up the bug after the broken hook (see screenshot). > The hook should really look only in the single URL in (one or more) > Bug-Url headers: > Bug-Url: https://bugzilla.redhat.com/ > I reported this years ago (I think for Related-To:), and I remember we had > a patch fixing this issue, but for some reason it was lost. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100166)

1 0

[JIRA] (OVIRT-3098) Gerrit hook adds unrelated patches to bugs
by Nir Soffer (oVirt JIRA) 21 Jun '21

21 Jun '21

Nir Soffer created OVIRT-3098: --------------------------------- Summary: Gerrit hook adds unrelated patches to bugs Key: OVIRT-3098 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3098 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Nir Soffer Assignee: infra Gerrit hook is wrongly looking for https://bugzilla.redhat.com/ URLs in the commit message, and adding the patch to the bug. Example patch: https://gerrit.ovirt.org/c/vdsm/+/115339 I had to clean up the bug after the broken hook (see screenshot). The hook should really look only in the single URL in (one or more) Bug-Url headers: Bug-Url: https://bugzilla.redhat.com/ I reported this years ago (I think for Related-To:), and I remember we had a patch fixing this issue, but for some reason it was lost. Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100166)

1 0

[JIRA] (OVIRT-3073) Re: Change in ovirt-engine[master]: packaging: setup: Move engine-specific pg conf to common
by Evgheni Dereveanchin (oVirt JIRA) 21 Jun '21

21 Jun '21

[ https://ovirt-jira.atlassian.net/browse/OVIRT-3073?page=com.atlassian.jira.… ] Evgheni Dereveanchin closed OVIRT-3073. --------------------------------------- Resolution: Fixed AFAIR this was fixed by setting `alternatives --set python /usr/bin/python3` to our instance build scripts > Re: Change in ovirt-engine[master]: packaging: setup: Move engine-specific pg conf to common > -------------------------------------------------------------------------------------------- > > Key: OVIRT-3073 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3073 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Yedidyah Bar David > Assignee: Evgheni Dereveanchin > > On Mon, Dec 14, 2020 at 12:21 PM Code Review <gerrit(a)ovirt.org> wrote: > > > > From Jenkins CI <jenkins(a)ovirt.org>: > > > > Jenkins CI has posted comments on this change. ( https://gerrit.ovirt.org/c/ovirt-engine/+/112414 ) > > > > Change subject: packaging: setup: Move engine-specific pg conf to common > > ...................................................................... > > > > > > Patch Set 4: Continuous-Integration-1 > > > > Build Failed > > > > https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/9236/ : FAILURE > 12:21:32 + usrc=/home/jenkins/workspace/ovirt-engine_standard-check-patch/jenkins/stdci_tools/usrc.py > 12:21:32 + [[ -x > /home/jenkins/workspace/ovirt-engine_standard-check-patch/jenkins/stdci_tools/usrc.py > ]] > 12:21:32 + /home/jenkins/workspace/ovirt-engine_standard-check-patch/jenkins/stdci_tools/usrc.py > --log -d get > 12:21:32 /usr/bin/env: ‘python’: No such file or directory > Any idea? > This is a result of manual 'ci test'. Automatic check-patch on the > same patch did succeed. > Thanks, > > > > > > -- > > To view, visit https://gerrit.ovirt.org/c/ovirt-engine/+/112414 > > To unsubscribe, or for help writing mail filters, visit https://gerrit.ovirt.org/settings > > > > Gerrit-Project: ovirt-engine > > Gerrit-Branch: master > > Gerrit-Change-Id: I8af2e259389fef59251a69c6443e3e440b93a843 > > Gerrit-Change-Number: 112414 > > Gerrit-PatchSet: 4 > > Gerrit-Owner: Yedidyah Bar David <didi(a)redhat.com> > > Gerrit-Reviewer: Asaf Rachmani <arachman(a)redhat.com> > > Gerrit-Reviewer: Evgeny Slutsky <eslutsky(a)redhat.com> > > Gerrit-Reviewer: Gal Zaidman <gzaidman(a)redhat.com> > > Gerrit-Reviewer: Jenkins CI <jenkins(a)ovirt.org> > > Gerrit-Reviewer: Lev Veyde <lveyde(a)redhat.com> > > Gerrit-Reviewer: Sandro Bonazzola <sbonazzo(a)redhat.com> > > Gerrit-Reviewer: Yedidyah Bar David <didi(a)redhat.com> > > Gerrit-Reviewer: gerrit-hooks <automation(a)ovirt.org> > > Gerrit-Comment-Date: Mon, 14 Dec 2020 10:21:34 +0000 > > Gerrit-HasComments: No > > Gerrit-Has-Labels: Yes > > Gerrit-MessageType: comment > > > -- > Didi -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100166)

1 0

[JIRA] (OVIRT-3073) Re: Change in ovirt-engine[master]: packaging: setup: Move engine-specific pg conf to common
by Evgheni Dereveanchin (oVirt JIRA) 21 Jun '21

21 Jun '21

[ https://ovirt-jira.atlassian.net/browse/OVIRT-3073?page=com.atlassian.jira.… ] Evgheni Dereveanchin updated OVIRT-3073: ---------------------------------------- Issue Type: Bug (was: By-EMAIL) > Re: Change in ovirt-engine[master]: packaging: setup: Move engine-specific pg conf to common > -------------------------------------------------------------------------------------------- > > Key: OVIRT-3073 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3073 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Yedidyah Bar David > Assignee: Evgheni Dereveanchin > > On Mon, Dec 14, 2020 at 12:21 PM Code Review <gerrit(a)ovirt.org> wrote: > > > > From Jenkins CI <jenkins(a)ovirt.org>: > > > > Jenkins CI has posted comments on this change. ( https://gerrit.ovirt.org/c/ovirt-engine/+/112414 ) > > > > Change subject: packaging: setup: Move engine-specific pg conf to common > > ...................................................................... > > > > > > Patch Set 4: Continuous-Integration-1 > > > > Build Failed > > > > https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/9236/ : FAILURE > 12:21:32 + usrc=/home/jenkins/workspace/ovirt-engine_standard-check-patch/jenkins/stdci_tools/usrc.py > 12:21:32 + [[ -x > /home/jenkins/workspace/ovirt-engine_standard-check-patch/jenkins/stdci_tools/usrc.py > ]] > 12:21:32 + /home/jenkins/workspace/ovirt-engine_standard-check-patch/jenkins/stdci_tools/usrc.py > --log -d get > 12:21:32 /usr/bin/env: ‘python’: No such file or directory > Any idea? > This is a result of manual 'ci test'. Automatic check-patch on the > same patch did succeed. > Thanks, > > > > > > -- > > To view, visit https://gerrit.ovirt.org/c/ovirt-engine/+/112414 > > To unsubscribe, or for help writing mail filters, visit https://gerrit.ovirt.org/settings > > > > Gerrit-Project: ovirt-engine > > Gerrit-Branch: master > > Gerrit-Change-Id: I8af2e259389fef59251a69c6443e3e440b93a843 > > Gerrit-Change-Number: 112414 > > Gerrit-PatchSet: 4 > > Gerrit-Owner: Yedidyah Bar David <didi(a)redhat.com> > > Gerrit-Reviewer: Asaf Rachmani <arachman(a)redhat.com> > > Gerrit-Reviewer: Evgeny Slutsky <eslutsky(a)redhat.com> > > Gerrit-Reviewer: Gal Zaidman <gzaidman(a)redhat.com> > > Gerrit-Reviewer: Jenkins CI <jenkins(a)ovirt.org> > > Gerrit-Reviewer: Lev Veyde <lveyde(a)redhat.com> > > Gerrit-Reviewer: Sandro Bonazzola <sbonazzo(a)redhat.com> > > Gerrit-Reviewer: Yedidyah Bar David <didi(a)redhat.com> > > Gerrit-Reviewer: gerrit-hooks <automation(a)ovirt.org> > > Gerrit-Comment-Date: Mon, 14 Dec 2020 10:21:34 +0000 > > Gerrit-HasComments: No > > Gerrit-Has-Labels: Yes > > Gerrit-MessageType: comment > > > -- > Didi -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100166)

1 0

[JIRA] (OVIRT-3073) Re: Change in ovirt-engine[master]: packaging: setup: Move engine-specific pg conf to common
by Evgheni Dereveanchin (oVirt JIRA) 21 Jun '21

21 Jun '21

[ https://ovirt-jira.atlassian.net/browse/OVIRT-3073?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-3073: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: Unassigned) > Re: Change in ovirt-engine[master]: packaging: setup: Move engine-specific pg conf to common > -------------------------------------------------------------------------------------------- > > Key: OVIRT-3073 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3073 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Yedidyah Bar David > Assignee: Evgheni Dereveanchin > > On Mon, Dec 14, 2020 at 12:21 PM Code Review <gerrit(a)ovirt.org> wrote: > > > > From Jenkins CI <jenkins(a)ovirt.org>: > > > > Jenkins CI has posted comments on this change. ( https://gerrit.ovirt.org/c/ovirt-engine/+/112414 ) > > > > Change subject: packaging: setup: Move engine-specific pg conf to common > > ...................................................................... > > > > > > Patch Set 4: Continuous-Integration-1 > > > > Build Failed > > > > https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/9236/ : FAILURE > 12:21:32 + usrc=/home/jenkins/workspace/ovirt-engine_standard-check-patch/jenkins/stdci_tools/usrc.py > 12:21:32 + [[ -x > /home/jenkins/workspace/ovirt-engine_standard-check-patch/jenkins/stdci_tools/usrc.py > ]] > 12:21:32 + /home/jenkins/workspace/ovirt-engine_standard-check-patch/jenkins/stdci_tools/usrc.py > --log -d get > 12:21:32 /usr/bin/env: ‘python’: No such file or directory > Any idea? > This is a result of manual 'ci test'. Automatic check-patch on the > same patch did succeed. > Thanks, > > > > > > -- > > To view, visit https://gerrit.ovirt.org/c/ovirt-engine/+/112414 > > To unsubscribe, or for help writing mail filters, visit https://gerrit.ovirt.org/settings > > > > Gerrit-Project: ovirt-engine > > Gerrit-Branch: master > > Gerrit-Change-Id: I8af2e259389fef59251a69c6443e3e440b93a843 > > Gerrit-Change-Number: 112414 > > Gerrit-PatchSet: 4 > > Gerrit-Owner: Yedidyah Bar David <didi(a)redhat.com> > > Gerrit-Reviewer: Asaf Rachmani <arachman(a)redhat.com> > > Gerrit-Reviewer: Evgeny Slutsky <eslutsky(a)redhat.com> > > Gerrit-Reviewer: Gal Zaidman <gzaidman(a)redhat.com> > > Gerrit-Reviewer: Jenkins CI <jenkins(a)ovirt.org> > > Gerrit-Reviewer: Lev Veyde <lveyde(a)redhat.com> > > Gerrit-Reviewer: Sandro Bonazzola <sbonazzo(a)redhat.com> > > Gerrit-Reviewer: Yedidyah Bar David <didi(a)redhat.com> > > Gerrit-Reviewer: gerrit-hooks <automation(a)ovirt.org> > > Gerrit-Comment-Date: Mon, 14 Dec 2020 10:21:34 +0000 > > Gerrit-HasComments: No > > Gerrit-Has-Labels: Yes > > Gerrit-MessageType: comment > > > -- > Didi -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100166)

1 0

Terraform and DNS
by Marc Dequènes (Duck) 21 Jun '21

21 Jun '21

Quack, Since you were thinking about using Terraform I was currous if NS updates were supported and they are: https://registry.terraform.io/providers/hashicorp/dns/latest/docs This means you can create a subzone of ovirt.org and delegate the full subzone or specific RRs. Then if you wish certain entries accessible from ovirt.org directly we can simply add CNAMEs. This is an alternative to using freipa's DNS management. The doc does not do into fulld etails but it's "basic DNS management" which probably means not all RR types are supported. I guess one question is how do you wish the main zone to be managed. I like to be able to manage the zone file by myself with comments and use subzones for automation but freeipa or DNS providers can do it all for you and provide an API too (with the same RR types limitation though, so it depends what kind of data you wish to put into it). I guess that's why RH decided to use IPA.REDHAT.COM instead of REDHAT.COM, freeipa can manage its own DNS entries (SRV…) for the provided services but you can still manage your main zone the way you want (for specific or historical reasons). I guess the domain to use for freeipa is also something to consider. \_o<

1 0

[oVirt Jenkins] ovirt-system-tests_basic-suite-4.3_el7-nightly - Build # 581 - Failure!
by jenkins＠jenkins.phx.ovirt.org 21 Jun '21

21 Jun '21

Project: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-4.3_el7-nightl… Build: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-4.3_el7-nightl… Build Number: 581 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #581 [parthdhanjal] Updating max click version ----------------- Failed Tests: ----------------- No tests ran.

1 1

[oVirt Jenkins] ovirt-release_4.3_build-artifacts-el7-x86_64 - Build # 1015 - Failure!
by jenkins＠jenkins.phx.ovirt.org 21 Jun '21

21 Jun '21

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_64/… Build Number: 1015 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #1015 [Sandro Bonazzola] Revert "automation: install centos-release if missing" ----------------- Failed Tests: ----------------- No tests ran.

1 1

oVirt infra daily report - unstable production jobs - 1593
by jenkins＠jenkins.phx.ovirt.org 21 Jun '21

21 Jun '21

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/1593//artifact/exported… Cheers, Jenkins

1 0

[oVirt Jenkins] ovirt-system-tests_basic-suite-4.3_el7-nightly - Build # 578 - Failure!
by jenkins＠jenkins.phx.ovirt.org 20 Jun '21

20 Jun '21

Project: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-4.3_el7-nightl… Build: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-4.3_el7-nightl… Build Number: 578 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #578 [parthdhanjal] Updating max click version ----------------- Failed Tests: ----------------- No tests ran.

1 1

[oVirt Jenkins] ovirt-system-tests_basic-suite-4.3_nightly - Build # 583 - Failure!
by jenkins＠jenkins.phx.ovirt.org 20 Jun '21

20 Jun '21

Project: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-4.3_nightly/ Build: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-4.3_nightly/58… Build Number: 583 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #583 [parthdhanjal] Updating max click version ----------------- Failed Tests: ----------------- No tests ran.

1 1

[oVirt Jenkins] cleanup-gated-ovirt-4.3 - Build #548 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 20 Jun '21

20 Jun '21

Build: https://jenkins.ovirt.org/job/cleanup-gated-ovirt-4.3/548/ Build Name: #548 Build Status: FAILURE Gerrit change: null - title: null - project: null - branch: null - author: null <null>

1 0

oVirt infra daily report - unstable production jobs - 1592
by jenkins＠jenkins.phx.ovirt.org 20 Jun '21

20 Jun '21

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/1592//artifact/exported… Cheers, Jenkins

1 0