February 2018 - Infra - Ovirt List Archives

[JIRA] (OVIRT-1877) Update docs to indicated adding 'jenkins:' prefix to build URLs

by eyal edri (oVirt JIRA)

This is a multi-part message in MIME format... ------------=_1517918909-19670-172 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1877?page=com.atlassian.jir... ] eyal edri commented on OVIRT-1877: ---------------------------------- [~gbenhaim(a)redhat.com] [~sbonazolla(a)redhat.com] [~amarchuk] FYI. > Update docs to indicated adding 'jenkins:' prefix to build URLs > --------------------------------------------------------------- > > Key: OVIRT-1877 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1877 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Documentation > Reporter: Barak Korren > Assignee: infra > > Our infra includes multipile places where users can input text that is used as configuration for repoman. Users are typically expected to place URLs of build jobs there to make repoman acquire built artifacts (For e.g. testing). > So far documentation specified that the plain URL to the build job can be used. This turns out to only be true for builds made on jenkins.ovirt.org. For URLs pointing at other jenkins servers, the '{{jenkins:}}' prefix needs to be added. > Documentation should be updated to teach users to add the '{{jenkins:}}' prefix. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079) ------------=_1517918909-19670-172 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1877?page=com.atlassian.jir... ]</pre> <h3>eyal edri commented on OVIRT-1877:</h3> <p>[~gbenhaim(a)redhat.com] [~sbonazolla(a)redhat.com] [~amarchuk] FYI.</p> <blockquote><h3>Update docs to indicated adding ‘jenkins:’ prefix to build URLs</h3> <pre> Key: OVIRT-1877 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1877 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Documentation Reporter: Barak Korren Assignee: infra</pre> <p>Our infra includes multipile places where users can input text that is used as configuration for repoman. Users are typically expected to place URLs of build jobs there to make repoman acquire built artifacts (For e.g. testing). So far documentation specified that the plain URL to the build job can be used. This turns out to only be true for builds made on jenkins.ovirt.org. For URLs pointing at other jenkins servers, the ‘{{jenkins:}}’ prefix needs to be added. Documentation should be updated to teach users to add the ‘{{jenkins:}}’ prefix.</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BS..." 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> ------------=_1517918909-19670-172--

6 years, 10 months

1
0
0 / 0

[CQ]: 87140, 3 (ovirt-engine) failed "ovirt-4.2" system tests, but isn't the failure root cause

by oVirt Jenkins

A system test invoked by the "ovirt-4.2" change queue including change 87140,3 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 87027,2 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 87027,2 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/87140/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/87027/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/521/

6 years, 10 months

3
2
0 / 0

[CQ]: 87072, 1 (ovirt-guest-agent) failed "ovirt-4.2" system tests, but isn't the failure root cause

by oVirt Jenkins

A system test invoked by the "ovirt-4.2" change queue including change 87072,1 (ovirt-guest-agent) failed. However, this change seems not to be the root cause for this failure. Change 83813,1 (ovirt-guest-agent) 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 83813,1 (ovirt-guest-agent) 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/87072/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/83813/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/528/

6 years, 10 months

1
0
0 / 0

[CQ]: 83288, 1 (ovirt-engine-extension-logger-log4j) failed "ovirt-4.2" system tests

by oVirt Jenkins

Change 83288,1 (ovirt-engine-extension-logger-log4j) 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/83288/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/527/

6 years, 10 months

1
0
0 / 0

[JIRA] (OVIRT-1877) Update docs to indicated adding 'jenkins:' prefix to build URLs

by eyal edri (oVirt JIRA)

This is a multi-part message in MIME format... ------------=_1517911412-28556-136 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1877?page=com.atlassian.jir... ] eyal edri commented on OVIRT-1877: ---------------------------------- Adding potential locations to update: * OST docs * Manual job * repoman docs * Official oVirt releases > Update docs to indicated adding 'jenkins:' prefix to build URLs > --------------------------------------------------------------- > > Key: OVIRT-1877 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1877 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Documentation > Reporter: Barak Korren > Assignee: infra > > Our infra includes multipile places where users can input text that is used as configuration for repoman. Users are typically expected to place URLs of build jobs there to make repoman acquire built artifacts (For e.g. testing). > So far documentation specified that the plain URL to the build job can be used. This turns out to only be true for builds made on jenkins.ovirt.org. For URLs pointing at other jenkins servers, the '{{jenkins:}}' prefix needs to be added. > Documentation should be updated to teach users to add the '{{jenkins:}}' prefix. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079) ------------=_1517911412-28556-136 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1877?page=com.atlassian.jir... ]</pre> <h3>eyal edri commented on OVIRT-1877:</h3> <p>Adding potential locations to update:</p> <ul><li><p>OST docs</p></li> <li><p>Manual job</p></li> <li><p>repoman docs</p></li> <li><p>Official oVirt releases</p></li></ul> <blockquote><h3>Update docs to indicated adding ‘jenkins:’ prefix to build URLs</h3> <pre> Key: OVIRT-1877 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1877 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Documentation Reporter: Barak Korren Assignee: infra</pre> <p>Our infra includes multipile places where users can input text that is used as configuration for repoman. Users are typically expected to place URLs of build jobs there to make repoman acquire built artifacts (For e.g. testing). So far documentation specified that the plain URL to the build job can be used. This turns out to only be true for builds made on jenkins.ovirt.org. For URLs pointing at other jenkins servers, the ‘{{jenkins:}}’ prefix needs to be added. Documentation should be updated to teach users to add the ‘{{jenkins:}}’ prefix.</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BS..." 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> ------------=_1517911412-28556-136--

6 years, 10 months

1
0
0 / 0

[JIRA] (OVIRT-1877) Update docs to indicated adding 'jenkins:' prefix to build URLs

by Barak Korren (oVirt JIRA)

This is a multi-part message in MIME format... ------------=_1517911157-10812-203 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Barak Korren created OVIRT-1877: ----------------------------------- Summary: Update docs to indicated adding 'jenkins:' prefix to build URLs Key: OVIRT-1877 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1877 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Documentation Reporter: Barak Korren Assignee: infra Our infra includes multipile places where users can input text that is used as configuration for repoman. Users are typically expected to place URLs of build jobs there to make repoman acquire built artifacts (For e.g. testing). So far documentation specified that the plain URL to the build job can be used. This turns out to only be true for builds made on jenkins.ovirt.org. For URLs pointing at other jenkins servers, the '{{jenkins:}}' prefix needs to be added. Documentation should be updated to teach users to add the '{{jenkins:}}' prefix. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079) ------------=_1517911157-10812-203 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <h3>Barak Korren created OVIRT-1877:</h3> <pre> Summary: Update docs to indicated adding 'jenkins:' prefix to build URLs Key: OVIRT-1877 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1877 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Documentation Reporter: Barak Korren Assignee: infra</pre> <p>Our infra includes multipile places where users can input text that is used as configuration for repoman. Users are typically expected to place URLs of build jobs there to make repoman acquire built artifacts (For e.g. testing).</p> <p>So far documentation specified that the plain URL to the build job can be used. This turns out to only be true for builds made on jenkins.ovirt.org. For URLs pointing at other jenkins servers, the ‘{{jenkins:}}’ prefix needs to be added.</p> <p>Documentation should be updated to teach users to add the ‘{{jenkins:}}’ prefix.</p> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BS..." 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> ------------=_1517911157-10812-203--

6 years, 10 months

1
0
0 / 0

[JIRA] (OVIRT-1877) Update docs to indicated adding 'jenkins:' prefix to build URLs

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1877?page=com.atlassian.jir... ] Barak Korren updated OVIRT-1877: -------------------------------- Epic Link: OVIRT-400 > Update docs to indicated adding 'jenkins:' prefix to build URLs > --------------------------------------------------------------- > > Key: OVIRT-1877 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1877 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Documentation > Reporter: Barak Korren > Assignee: infra > > Our infra includes multipile places where users can input text that is used as configuration for repoman. Users are typically expected to place URLs of build jobs there to make repoman acquire built artifacts (For e.g. testing). > So far documentation specified that the plain URL to the build job can be used. This turns out to only be true for builds made on jenkins.ovirt.org. For URLs pointing at other jenkins servers, the '{{jenkins:}}' prefix needs to be added. > Documentation should be updated to teach users to add the '{{jenkins:}}' prefix. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)

6 years, 10 months

1
0
0 / 0

[CQ]: 87186, 1 (ovirt-engine-extension-logger-log4j) failed "ovirt-4.2" system tests, but isn't the failure root cause

by oVirt Jenkins

A system test invoked by the "ovirt-4.2" change queue including change 87186,1 (ovirt-engine-extension-logger-log4j) failed. However, this change seems not to be the root cause for this failure. Change 83288,1 (ovirt-engine-extension- logger-log4j) 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 83288,1 (ovirt-engine- extension-logger-log4j) 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/87186/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/83288/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/525/

6 years, 10 months

1
0
0 / 0

[CQ]: 83288, 1 (ovirt-engine-extension-logger-log4j) failed "ovirt-4.2" system tests

by oVirt Jenkins

Change 83288,1 (ovirt-engine-extension-logger-log4j) 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/83288/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/523/

6 years, 10 months

1
0
0 / 0

Re: [oVirt Jenkins] ovirt-system-tests_hc-basic-suite-master - Build # 183 - Failure!

by Eyal Edri

On Feb 6, 2018 10:37, "Simone Tiraboschi" <stirabos(a)redhat.com> wrote: On Tue, Feb 6, 2018 at 9:15 AM, Sandro Bonazzola <sbonazzo(a)redhat.com> wrote: > I see: > > *04:29:42* Error: Ansible(>= 2.2) is not installed.*04:29:42* Some of the features might not work if not installed. > > > Followed by: > > *04:29:53* Running test scenario 002_bootstrap.py*04:29:53* + env_run_test /home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-master/ovirt-system-tests/hc-basic-suite-master/test-scenarios/002_bootstrap.py*04:29:53* + local res=0*04:29:53* + cd /home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-master/ovirt-system-tests/deployment-hc-basic-suite-master*04:29:53* + lago ovirt runtest /home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-master/ovirt-system-tests/hc-basic-suite-master/test-scenarios/002_bootstrap.py*04:29:53* @ Run test: 002_bootstrap.py: *04:29:53* nose.config: INFO: Ignoring files matching ['^\\.', '^_', '^setup\\.py$']*04:29:53* # wait_engine: *04:42:13* * Collect artifacts: *04:42:30* - [Thread-4] lago-hc-basic-suite-master-engine: ERROR (in 0:00:16)*04:42:30* Error while running thread*04:42:30* Traceback (most recent call last):*04:42:30* File "/usr/lib/python2.7/site-packages/lago/utils.py", line 58, in _ret_via_queue*04:42:30* queue.put({'return': func()})*04:42:30* File "/usr/lib/python2.7/site-packages/lago/prefix.py", line 1504, in _collect_artifacts*04:42:30* vm.collect_artifacts(path, ignore_nopath)*04:42:30* File "/usr/lib/python2.7/site-packages/lago/plugins/vm.py", line 635, in collect_artifacts*04:42:30* ignore_nopath=ignore_nopath*04:42:30* File "/usr/lib/python2.7/site-packages/lago/plugins/vm.py", line 381, in extract_paths*04:42:30* return self.provider.extract_paths(paths, *args, **kwargs)*04:42:30* File "/usr/lib/python2.7/site-packages/lago/plugins/vm.py", line 251, in extract_paths*04:42:30* format(self.vm.name())*04:42:30* ExtractPathError: Unable to extract paths from lago-hc-basic-suite-master-engine: unreachable with SSH > > > lago is not able to extract logs from the engine because the engine vm is down. > > The deploy failed with: > > > 2018-02-05 22:29:38,221-0500 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils.run:190 ansible-playbook stderr: > 2018-02-05 22:29:38,222-0500 DEBUG otopi.context context._executeMethod:143 method exception > Traceback (most recent call last): > File "/usr/lib/python2.7/site-packages/otopi/context.py", line 133, in _executeMethod > method['method']() > File "/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/gr-he-ansiblesetup/core/target_vm.py", line 193, in _closeup > r = ah.run() > File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_setup/ansible_utils.py", line 194, in run > raise RuntimeError(_('Failed executing ansible-playbook')) > RuntimeError: Failed executing ansible-playbook > > Didi, Simone, can you please have a look? > > The issue is here: Feb 5 22:21:39 lago-hc-basic-suite-master-host0 libvirtd: 2018-02-06 03:21:39.367+0000: 16907: error : x86ModelFromCPU:1061 : internal error: Unknown CPU model Haswell-noTSXIBRS We are incorrectly handling the CPU model name for AMD and IBRS enabled families. We have an open bug here: https://bugzilla.redhat.com/show_bug.cgi?id=1541328 We fixed a similar issue for basic suite, it might fail on slave with outdated lago-ost-plugin. Gal, can you please have a look to see if it's the same issue we fixed already? > Ansible logs are at: > > http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-master/183... > > > > > > > > > > > > 2018-02-06 4:43 GMT+01:00 <jenkins(a)jenkins.phx.ovirt.org>: > >> Project: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-sui >> te-master/ >> Build: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-sui >> te-master/183/ >> Build Number: 183 >> Build Status: Failure >> Triggered By: Started by timer >> >> ------------------------------------- >> Changes Since Last Success: >> ------------------------------------- >> Changes for Build #183 >> [Sandro Bonazzola] hc-basic-suite-4.1: add centos-qemu-ev-release-el7 >> >> [Sandro Bonazzola] ovirt-engine: dropped fcraw on master >> >> [Barak Korren] Add a timeout to pipline STDCI jobs >> >> [Sandro Bonazzola] ovirt-guest-agent: drop el6 on >= 4.2 >> >> >> >> >> ----------------- >> Failed Tests: >> ----------------- >> No tests ran. >> _______________________________________________ >> Infra mailing list >> Infra(a)ovirt.org >> http://lists.ovirt.org/mailman/listinfo/infra >> >> > > > -- > > SANDRO BONAZZOLA > > ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D > > Red Hat EMEA <https://www.redhat.com/> > <https://red.ht/sig> > TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> > > _______________________________________________ Infra mailing list Infra(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/infra

6 years, 10 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Infra February 2018