- Infra - oVirt List Archives

[JIRA] (OVIRT-1919) missing documentation on ci re-merge please in github
by eyal edri (oVirt JIRA) 07 Mar '18

07 Mar '18

This is a multi-part message in MIME format... ------------=_1520412194-21289-127 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1919?page=com.atlassian.jira.… ] eyal edri commented on OVIRT-1919: ---------------------------------- Until we have that RFE implemented, we need to document this process, even if its not final. > missing documentation on ci re-merge please in github > ----------------------------------------------------- > > Key: OVIRT-1919 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1919 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Dafna Ron > Assignee: infra > > we needed to re-merge a change from github and did not know how to do it. > looking at the documentation it either does not exist or not documented. > http://ovirt-infra-docs.readthedocs.io/en/latest/CI/Using_STDCI_with_GitHub… > I am assuming that we can re-merge so opening a jira for the doc. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081) ------------=_1520412194-21289-127 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1919?page=com.atlassian.jira.… ]</pre> <h3>eyal edri commented on OVIRT-1919:</h3> <p>Until we have that RFE implemented, we need to document this process, even if its not final.</p> <blockquote><h3>missing documentation on ci re-merge please in github</h3> <pre> Key: OVIRT-1919 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1919 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Dafna Ron Assignee: infra</pre> <p>we needed to re-merge a change from github and did not know how to do it. looking at the documentation it either does not exist or not documented. <a href="http://ovirt-infra-docs.readthedocs.io/en/latest/CI/Using_STDCI_with_GitHub…">http://ovirt-infra-docs.readthedocs.io/en/latest/CI/Using_STDCI_with_GitHub…</a> I am assuming that we can re-merge so opening a jira for the doc.</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1520412194-21289-127--

1 0

[JIRA] (OVIRT-1919) missing documentation on ci re-merge please in github
by Barak Korren (oVirt JIRA) 07 Mar '18

07 Mar '18

This is a multi-part message in MIME format... ------------=_1520411242-30870-123 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1919?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1919: ------------------------------------- Please open an RFE ticket for supporting {{ci re-merge please}} in GitHub. It would be veryi simple to implement actually, all it take is a few little code changes in {{pipelines/standard-stage.groovy}} if you care to try... > missing documentation on ci re-merge please in github > ----------------------------------------------------- > > Key: OVIRT-1919 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1919 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Dafna Ron > Assignee: infra > > we needed to re-merge a change from github and did not know how to do it. > looking at the documentation it either does not exist or not documented. > http://ovirt-infra-docs.readthedocs.io/en/latest/CI/Using_STDCI_with_GitHub… > I am assuming that we can re-merge so opening a jira for the doc. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081) ------------=_1520411242-30870-123 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1919?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren commented on OVIRT-1919:</h3> <p>Please open an RFE ticket for supporting {{ci re-merge please}} in GitHub. It would be veryi simple to implement actually, all it take is a few little code changes in {{pipelines/standard-stage.groovy}} if you care to try…</p> <blockquote><h3>missing documentation on ci re-merge please in github</h3> <pre> Key: OVIRT-1919 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1919 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Dafna Ron Assignee: infra</pre> <p>we needed to re-merge a change from github and did not know how to do it. looking at the documentation it either does not exist or not documented. <a href="http://ovirt-infra-docs.readthedocs.io/en/latest/CI/Using_STDCI_with_GitHub…">http://ovirt-infra-docs.readthedocs.io/en/latest/CI/Using_STDCI_with_GitHub…</a> I am assuming that we can re-merge so opening a jira for the doc.</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1520411242-30870-123--

1 0

[JIRA] (OVIRT-1919) missing documentation on ci re-merge please in github
by Barak Korren (oVirt JIRA) 07 Mar '18

07 Mar '18

This is a multi-part message in MIME format... ------------=_1520411126-14008-137 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1919?page=com.atlassian.jira.… ] Barak Korren edited comment on OVIRT-1919 at 3/7/18 8:25 AM: ------------------------------------------------------------- There is no 'ci re-merge please' command for github, however for pieplien-based jobs (v2) any stage for any project can be run manually using the [standard-manual-runner|http://jenkins.ovirt.org/job/standard-manual-runner/] job. What you need to do there is specify a Git URL for the project, a refspec to clone (the default uses the master branch which should be what you want in most cases), and the STDCI stage to run, it this case it would be 'check-merged'. was (Author: bkorren(a)redhat.com) There is no 'ci re-merge please' command for github, however for pieplien-based jobs (v2) any stage can be rerun manually using the [standard-manual-runner|http://jenkins.ovirt.org/job/standard-manual-runner/] job. What you need to do there is specify a Git URL for the project, a refspec to clone (the default uses the master branch which should be what you want in most cases), and the STDCI stage to run, it this case it would be 'check-merged'. > missing documentation on ci re-merge please in github > ----------------------------------------------------- > > Key: OVIRT-1919 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1919 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Dafna Ron > Assignee: infra > > we needed to re-merge a change from github and did not know how to do it. > looking at the documentation it either does not exist or not documented. > http://ovirt-infra-docs.readthedocs.io/en/latest/CI/Using_STDCI_with_GitHub… > I am assuming that we can re-merge so opening a jira for the doc. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081) ------------=_1520411126-14008-137 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1919?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren edited comment on OVIRT-1919 at 3/7/18 8:25 AM:</h3> <p>There is no ‘ci re-merge please’ command for github, however for pieplien-based jobs (v2) any stage for any project can be run manually using the [standard-manual-runner|<a href="http://jenkins.ovirt.org/job/standard-manual-runner/">http://jenkins.ovirt.org/job/standard-manual-runner/</a>] job.</p> <p>What you need to do there is specify a Git URL for the project, a refspec to clone (the default uses the master branch which should be what you want in most cases), and the STDCI stage to run, it this case it would be ‘check-merged’.</p> <p>was (Author: bkorren(a)redhat.com) There is no ‘ci re-merge please’ command for github, however for pieplien-based jobs (v2) any stage can be rerun manually using the [standard-manual-runner|<a href="http://jenkins.ovirt.org/job/standard-manual-runner/">http://jenkins.ovirt.org/job/standard-manual-runner/</a>] job.</p> <p>What you need to do there is specify a Git URL for the project, a refspec to clone (the default uses the master branch which should be what you want in most cases), and the STDCI stage to run, it this case it would be ‘check-merged’.</p> <blockquote><h3>missing documentation on ci re-merge please in github</h3> <pre> Key: OVIRT-1919 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1919 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Dafna Ron Assignee: infra</pre> <p>we needed to re-merge a change from github and did not know how to do it. looking at the documentation it either does not exist or not documented. <a href="http://ovirt-infra-docs.readthedocs.io/en/latest/CI/Using_STDCI_with_GitHub…">http://ovirt-infra-docs.readthedocs.io/en/latest/CI/Using_STDCI_with_GitHub…</a> I am assuming that we can re-merge so opening a jira for the doc.</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1520411126-14008-137--

1 0

[JIRA] (OVIRT-1919) missing documentation on ci re-merge please in github
by Barak Korren (oVirt JIRA) 07 Mar '18

07 Mar '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1919?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1919: ------------------------------------- There is no 'ci re-merge please' command for github, however for pieplien-based jobs (v2) any stage can be rerun manually using the [standard-manual-runner|http://jenkins.ovirt.org/job/standard-manual-runner/] job. What you need to do there is specify a Git URL for the project, a refspec to clone (the default uses the master branch which should be what you want in most cases), and the STDCI stage to run, it this case it would be 'check-merged'. > missing documentation on ci re-merge please in github > ----------------------------------------------------- > > Key: OVIRT-1919 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1919 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Dafna Ron > Assignee: infra > > we needed to re-merge a change from github and did not know how to do it. > looking at the documentation it either does not exist or not documented. > http://ovirt-infra-docs.readthedocs.io/en/latest/CI/Using_STDCI_with_GitHub… > I am assuming that we can re-merge so opening a jira for the doc. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081)

1 0

[JIRA] (OVIRT-1920) Modify ci_env_client.py to be case and signs insensitive
by Daniel Belenky (oVirt JIRA) 07 Mar '18

07 Mar '18

This is a multi-part message in MIME format... ------------=_1520407593-14384-146 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1920?page=com.atlassian.jira.… ] Daniel Belenky updated OVIRT-1920: ---------------------------------- Issue Type: Task (was: Bug) > Modify ci_env_client.py to be case and signs insensitive > -------------------------------------------------------- > > Key: OVIRT-1920 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1920 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Standard CI (Pipelines), STDCI DSL > Reporter: Daniel Belenky > Assignee: infra > > In OVIRT-1892 we make stdci config be case and signs insensitive. It means that when we will write a runner (or modify mock_runner) to use the new config, ci_env_client will have to deal with a normalized structure (without cases nor signs as dots and dashes). -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081) ------------=_1520407593-14384-146 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1920?page=com.atlassian.jira.… ]</pre> <h3>Daniel Belenky updated OVIRT-1920:</h3> <pre>Issue Type: Task (was: Bug)</pre> <blockquote><h3>Modify ci_env_client.py to be case and signs insensitive</h3> <pre> Key: OVIRT-1920 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1920 Project: oVirt - virtualization made easy Issue Type: Task Components: Standard CI (Pipelines), STDCI DSL Reporter: Daniel Belenky Assignee: infra</pre> <p>In OVIRT-1892 we make stdci config be case and signs insensitive. It means that when we will write a runner (or modify mock_runner) to use the new config, ci_env_client will have to deal with a normalized structure (without cases nor signs as dots and dashes).</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1520407593-14384-146--

1 0

[JIRA] (OVIRT-1920) Modify ci_env_client.py to be case and signs insensitive
by Daniel Belenky (oVirt JIRA) 07 Mar '18

07 Mar '18

Daniel Belenky created OVIRT-1920: ------------------------------------- Summary: Modify ci_env_client.py to be case and signs insensitive Key: OVIRT-1920 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1920 Project: oVirt - virtualization made easy Issue Type: Bug Components: Standard CI (Pipelines), STDCI DSL Reporter: Daniel Belenky Assignee: infra In OVIRT-1892 we make stdci config be case and signs insensitive. It means that when we will write a runner (or modify mock_runner) to use the new config, ci_env_client will have to deal with a normalized structure (without cases nor signs as dots and dashes). -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081)

1 0

[JIRA] (OVIRT-1920) Modify ci_env_client.py to be case and signs insensitive
by Daniel Belenky (oVirt JIRA) 07 Mar '18

07 Mar '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1920?page=com.atlassian.jira.… ] Daniel Belenky updated OVIRT-1920: ---------------------------------- Epic Link: OVIRT-400 > Modify ci_env_client.py to be case and signs insensitive > -------------------------------------------------------- > > Key: OVIRT-1920 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1920 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Standard CI (Pipelines), STDCI DSL > Reporter: Daniel Belenky > Assignee: infra > > In OVIRT-1892 we make stdci config be case and signs insensitive. It means that when we will write a runner (or modify mock_runner) to use the new config, ci_env_client will have to deal with a normalized structure (without cases nor signs as dots and dashes). -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081)

1 0

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-master - Build # 211 - Failure!
by jenkins＠jenkins.phx.ovirt.org 07 Mar '18

07 Mar '18

------=_Part_171_710260247.1520307928418 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Project: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-mas= ter/=20 Build: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-maste= r/211/ Build Number: 211 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #211 [Yaniv Kaul] Set custom emulated machine (rhel-7.4) for VM2 ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 002_bootstrap.add_hosts Error Message: The response content type 'text/html; charset=3Diso-8859-1' isn't the expec= ted XML -------------------- >> begin captured logging << -------------------- ovirtlago.testlib: ERROR: * Unhandled exception in <function _host_is_u= p_4 at 0x45ff230> Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 219, i= n assert_equals_within res =3D func() File "/home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-master/ov= irt-system-tests/hc-basic-suite-master/test-scenarios/002_bootstrap.py", li= ne 254, in _host_is_up_4 host_obj =3D host_service.get() File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 363= 46, in get return self._internal_get(headers, query, wait) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 211,= in _internal_get 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 208,= in callback self._check_fault(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 130,= in _check_fault body =3D self._internal_read_body(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 316,= in _internal_read_body self._connection.check_xml_content_type(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/__init__.py", line 849= , in check_xml_content_type response.headers File "/usr/lib64/python2.7/site-packages/ovirtsdk4/__init__.py", line 889= , in _check_content_type raise Error(msg) Error: The response content type 'text/html; charset=3Diso-8859-1' isn't th= e expected XML --------------------- >> end captured logging << --------------------- Stack Trace: 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 runTes= t self.test(*self.arg) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 129, i= n wrapped_test test() File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 59, in= wrapper return func(get_test_prefix(), *args, **kwargs) File "/home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-master/ov= irt-system-tests/hc-basic-suite-master/test-scenarios/002_bootstrap.py", li= ne 229, in add_hosts add_hosts_4(prefix) File "/home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-master/ov= irt-system-tests/hc-basic-suite-master/test-scenarios/002_bootstrap.py", li= ne 273, in add_hosts_4 testlib.assert_true_within(_host_is_up_4, timeout=3D15*60) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 263, i= n assert_true_within assert_equals_within(func, True, timeout, allowed_exceptions) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 219, i= n assert_equals_within res =3D func() File "/home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-master/ov= irt-system-tests/hc-basic-suite-master/test-scenarios/002_bootstrap.py", li= ne 254, in _host_is_up_4 host_obj =3D host_service.get() File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 363= 46, in get return self._internal_get(headers, query, wait) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 211,= in _internal_get 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 208,= in callback self._check_fault(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 130,= in _check_fault body =3D self._internal_read_body(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 316,= in _internal_read_body self._connection.check_xml_content_type(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/__init__.py", line 849= , in check_xml_content_type response.headers File "/usr/lib64/python2.7/site-packages/ovirtsdk4/__init__.py", line 889= , in _check_content_type raise Error(msg) 'The response content type \'text/html; charset=3Diso-8859-1\' isn\'t the e= xpected XML\n-------------------- >> begin captured logging << ------------= --------\novirtlago.testlib: ERROR: * Unhandled exception in <function = _host_is_up_4 at 0x45ff230>\nTraceback (most recent call last):\n File "/u= sr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 219, in assert_e= quals_within\n res =3D func()\n File "/home/jenkins/workspace/ovirt-sys= tem-tests_hc-basic-suite-master/ovirt-system-tests/hc-basic-suite-master/te= st-scenarios/002_bootstrap.py", line 254, in _host_is_up_4\n host_obj = =3D host_service.get()\n File "/usr/lib64/python2.7/site-packages/ovirtsdk= 4/services.py", line 36346, in get\n return self._internal_get(headers, = query, wait)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.= py", line 211, in _internal_get\n return future.wait() if wait else futu= re\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line = 55, in wait\n return self._code(response)\n File "/usr/lib64/python2.7/= site-packages/ovirtsdk4/service.py", line 208, in callback\n self._check= _fault(response)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/serv= ice.py", line 130, in _check_fault\n body =3D self._internal_read_body(r= esponse)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py",= line 316, in _internal_read_body\n self._connection.check_xml_content_t= ype(response)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/__init_= _.py", line 849, in check_xml_content_type\n response.headers\n File "/= usr/lib64/python2.7/site-packages/ovirtsdk4/__init__.py", line 889, in _che= ck_content_type\n raise Error(msg)\nError: The response content type \'t= ext/html; charset=3Diso-8859-1\' isn\'t the expected XML\n-----------------= ---- >> end captured logging << ---------------------' ------=_Part_171_710260247.1520307928418--

1 1

planned Jenkins restart
by Evgheni Dereveanchin 07 Mar '18

07 Mar '18

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

1 1

[JIRA] (OVIRT-1919) missing documentation on ci re-merge please in github
by Dafna Ron (oVirt JIRA) 06 Mar '18

06 Mar '18

This is a multi-part message in MIME format... ------------=_1520353920-12885-275 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Dafna Ron created OVIRT-1919: -------------------------------- Summary: missing documentation on ci re-merge please in github Key: OVIRT-1919 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1919 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Dafna Ron Assignee: infra we needed to re-merge a change from github and did not know how to do it. looking at the documentation it either does not exist or not documented. http://ovirt-infra-docs.readthedocs.io/en/latest/CI/Using_STDCI_with_GitHub… I am assuming that we can re-merge so opening a jira for the doc. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081) ------------=_1520353920-12885-275 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <h3>Dafna Ron created OVIRT-1919:</h3> <pre> Summary: missing documentation on ci re-merge please in github Key: OVIRT-1919 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1919 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Dafna Ron Assignee: infra</pre> <p>we needed to re-merge a change from github and did not know how to do it. looking at the documentation it either does not exist or not documented. <a href="http://ovirt-infra-docs.readthedocs.io/en/latest/CI/Using_STDCI_with_GitHub…">http://ovirt-infra-docs.readthedocs.io/en/latest/CI/Using_STDCI_with_GitHub…</a></p> <p>I am assuming that we can re-merge so opening a jira for the doc.</p> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1520353920-12885-275--

1 0

Fwd: Still Failing: oVirt/ovirt-engine#4888 (master - 1cc377f)
by Sandro Bonazzola 06 Mar '18

06 Mar '18

Hi, not sure who's monitoring Travis failures and maintaining Travis jobs, but looks like we have an error in the test suite It's currently failing on: ------------------------------------------------------- T E S T S ------------------------------------------------------- Running org.ovirt.engine.core.dal.job.ExecutionMessageDirectorTest Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.234 sec Running org.ovirt.engine.core.dal.dbbroker.DbConnectionUtilTest Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.936 sec <<< FAILURE! org.ovirt.engine.core.dal.dbbroker.DbConnectionUtilTest Time elapsed: 936 sec <<< FAILURE! java.lang.AssertionError: Unable to init tests Looks pretty much similar to what happens in jenkins for fcraw builds, tracked here: https://bugzilla.redhat.com/show_bug.cgi?id=1550033 ---------- Forwarded message ---------- From: Travis CI <builds(a)travis-ci.org> Date: 2018-03-06 7:53 GMT+01:00 Subject: Still Failing: oVirt/ovirt-engine#4888 (master - 1cc377f) To: sbonazzo(a)redhat.com *oVirt / ovirt-engine <https://travis-ci.org/oVirt/ovirt-engine?utm_source=email&utm_medium=notifi…>* (master <https://github.com/oVirt/ovirt-engine/tree/master>) Build #4888 is still failing. <https://travis-ci.org/oVirt/ovirt-engine/builds/349675802?utm_source=email&…> 4 minutes and 38 seconds *Yedidyah Bar David* 1cc377f <https://github.com/oVirt/ovirt-engine/commit/1cc377fa30286733aeb68aa75a5bc8…> Changeset → <https://github.com/oVirt/ovirt-engine/compare/6c9465241694...1cc377fa3028> packaging: setup: postgres95: Refuse to upgrade if new data dir is not empty Change-Id: I9f69ceb2b8ea773d1bb883c3e81734a3c4c8af3c Bug-Url: https://bugzilla.redhat.com/1546771 Signed-off-by: Yedidyah Bar David <didi(a)redhat.com> *Want to know about upcoming build environment updates?* Would you like to stay up-to-date with the upcoming Travis CI build environment updates? We set up a mailing list for you! Sign up here <http://eepurl.com/9OCsP>. Documentation <https://docs.travis-ci.com> about Travis CI Need help? Mail support <support(a)travis-ci.com>! Choose who receives these build notification emails in your configuration file <https://docs.travis-ci.com/user/notifications>. *Would you like to test your private code?* Travis CI for Private Projects <https://travis-ci.com?utm_source=build_email_footer&utm_campaign=travis-ci.…> could be your new best friend! -- 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>

3 4

[JIRA] (OVIRT-1918) Single project tests in change-queue-tester
by Dafna Ron (oVirt JIRA) 06 Mar '18

06 Mar '18

This is a multi-part message in MIME format... ------------=_1520344092-23374-193 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1918?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-1918: ---------------------------------- we monitor and report an issue once its identified. we do not however, report every failed change which has failed because of the original root cause. I do try to go and either re-trigger or re-merge changes if they failed cq once the root cause is fixed but if an issue lasts for a day or two it would be difficult to make sure we do not miss anything. maybe we need to add a warning message after an issue is fixed which lists all changes that need to be re-triggered or re-merged? > Single project tests in change-queue-tester > ------------------------------------------- > > Key: OVIRT-1918 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1918 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > Please change change-queue-tester jobs for testing a single project at a > time (ok for multiple patches at once, but from the same project). > Right now if multiple patches are merged between a change-queue-tester > execution and the next one are done, all of them will be tested in the next > run, even if the changes are in different projects. > So, supposing project A and B are completely fine, a failure in project C > can still prevent changes in A and B to go ahead through the pipeline and > get released. > This cause major headaches at least to me, requiring me to go again over > all the HEAD of the projects not being published and run yet again "ci > re-merge please" again and again and again until I'm lucky enough to have > nobody else merging patches or having all the ttested patches pass at once. > I understand the need to reduce the amount of executions of the job since > it takes an hour to execute but right now it's stealing days of execution > for getting a patch landing on tested repo. > -- > 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> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081) ------------=_1520344092-23374-193 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1918?page=com.atlassian.jira.… ]</pre> <h3>Dafna Ron commented on OVIRT-1918:</h3> <p>we monitor and report an issue once its identified. we do not however, report every failed change which has failed because of the original root cause.</p> <p>I do try to go and either re-trigger or re-merge changes if they failed cq once the root cause is fixed but if an issue lasts for a day or two it would be difficult to make sure we do not miss anything.</p> <p>maybe we need to add a warning message after an issue is fixed which lists all changes that need to be re-triggered or re-merged?</p> <blockquote><h3>Single project tests in change-queue-tester</h3> <pre> Key: OVIRT-1918 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1918 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: sbonazzo Assignee: infra</pre> <p>Please change change-queue-tester jobs for testing a single project at a time (ok for multiple patches at once, but from the same project). Right now if multiple patches are merged between a change-queue-tester execution and the next one are done, all of them will be tested in the next run, even if the changes are in different projects. So, supposing project A and B are completely fine, a failure in project C can still prevent changes in A and B to go ahead through the pipeline and get released. This cause major headaches at least to me, requiring me to go again over all the HEAD of the projects not being published and run yet again “ci re-merge please” again and again and again until I'm lucky enough to have nobody else merging patches or having all the ttested patches pass at once. I understand the need to reduce the amount of executions of the job since it takes an hour to execute but right now it's stealing days of execution for getting a patch landing on tested repo. — SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <<a href="https://www.redhat.com/">https://www.redhat.com/</a>> <<a href="https://red.ht/sig">https://red.ht/sig</a>> TRIED. TESTED. TRUSTED. <<a href="https://redhat.com/trusted">https://redhat.com/trusted</a>></p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1520344092-23374-193--

1 0

[JIRA] (OVIRT-1861) Re: [ovirt-users] [ANN] oVirt 4.1.9 Release is now available
by eyal edri (oVirt JIRA) 06 Mar '18

06 Mar '18

This is a multi-part message in MIME format... ------------=_1520343278-10207-157 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable [ https://ovirt-jira.atlassian.net/browse/OVIRT-1861?page=3Dcom.atlass= ian.jira.plugin.system.issuetabpanels:all-tabpanel ] eyal edri reassigned OVIRT-1861: -------------------------------- Assignee: Marc Dequ=C3=A8nes (Duck) (was: infra) > Re: [ovirt-users] [ANN] oVirt 4.1.9 Release is now available > ------------------------------------------------------------ > > Key: OVIRT-1861 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1861 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: wiki (MediaWiki) > Reporter: sbonazzo > Assignee: Marc Dequ=C3=A8nes (Duck) > > 2018-01-24 13:47 GMT+01:00 Arman Khalatyan <arm2arm(a)gmail.com>: > > Thanks for the announcement. > > A little comment: could you please fix the line yum install > > <http://resources.ovirt.org/pub/yum-repo/ovirt-release41.rpm > > <http://resources.ovirt.org/pub/yum-repo/ovirt-release41.rpm%3E> > > There is an extra '<' symbol there since 4.0.x :=3D) > > > > > Thanks for the feedback, I opened > https://github.com/oVirt/ovirt-site/issues/1503 to track this. > Opening a ticket on infra as well for further investigations. > > > > On Wed, Jan 24, 2018 at 12:00 PM, Lev Veyde <lveyde(a)redhat.com> wrote: > > > >> The oVirt Project is pleased to announce the availability of the oVirt > >> 4.1.9 release, as of January 24th, 2017 > >> > >> This update is the ninth in a series of stabilization updates to the 4= .1 > >> series. > >> > >> Please note that no further updates will be issued for the 4.1 series. > >> We encourage users to upgrade to 4.2 series to receive new features and > >> updates. > >> > >> This release is available now for: > >> * Red Hat Enterprise Linux 7.4 or later > >> * CentOS Linux (or similar) 7.4 or later > >> > >> This release supports Hypervisor Hosts running: > >> * Red Hat Enterprise Linux 7.4 or later > >> * CentOS Linux (or similar) 7.4 or later > >> * oVirt Node 4.1 > >> > >> See the release notes [1] for installation / upgrade instructions and > >> a list of new features and bugs fixed. > >> > >> Notes: > >> - oVirt Appliance is already available > >> - oVirt Live is already available [2] > >> - oVirt Node will be available soon [2] > >> > >> Additional Resources: > >> * Read more about the oVirt 4.1.9 release highlights:http://www.ovirt.= or > >> g/release/4.1.9/ > >> * Get more oVirt Project updates on Twitter: https://twitter.com/ovirt > >> * Check out the latest project news on the oVirt blog: > >> http://www.ovirt.org/blog/ > >> > >> [1] http://www.ovirt.org/release/4.1.9/ > >> [2] http://resources.ovirt.org/pub/ovirt-4.1/iso/ > >> > >> -- > >> > >> Lev Veyde > >> > >> Software Engineer, RHCE | RHCVA | MCITP > >> > >> Red Hat Israel > >> > >> <https://www.redhat.com> > >> > >> lev(a)redhat.com | lveyde(a)redhat.com > >> <https://red.ht/sig> > >> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> > >> > >> _______________________________________________ > >> Users mailing list > >> Users(a)ovirt.org > >> http://lists.ovirt.org/mailman/listinfo/users > >> > >> > > > > _______________________________________________ > > Users mailing list > > Users(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/users > > > > > --=20 > 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> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081) ------------=_1520343278-10207-157 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1861?page=3Dcom.atlass= ian.jira.plugin.system.issuetabpanels:all-tabpanel ]</pre> <h3>eyal edri reassigned OVIRT-1861:</h3> <pre>Assignee: Marc Dequ=C3=A8nes (Duck) (was: infra)</pre> <blockquote><h3>Re: [ovirt-users] [ANN] oVirt 4.1.9 Release is now availabl= e</h3> <pre> Key: OVIRT-1861 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1861 Project: oVirt - virtualization made easy Issue Type: Bug Components: wiki (MediaWiki) Reporter: sbonazzo Assignee: Marc Dequ=C3=A8nes (Duck)</pre> <p>2018-01-24 13:47 GMT+01:00 Arman Khalatyan <arm2arm(a)gmail.com>:</p> <blockquote><p>Thanks for the announcement. A little comment: could you ple= ase fix the line yum install <<a href=3D"http://resources.ovirt.org/pub= /yum-repo/ovirt-release41.rpm">http://resources.ovirt.org/pub/yum-repo/ovir= t-release41.rpm</a> <<a href=3D"http://resources.ovirt.org/pub/yum-repo/= ovirt-release41.rpm%3E">http://resources.ovirt.org/pub/yum-repo/ovirt-relea= se41.rpm%3E</a>> There is an extra ‘<’ symbol there since= 4.0.x :=3D)</p></blockquote> <p>Thanks for the feedback, I opened <a href=3D"https://github.com/oVirt/ov= irt-site/issues/1503">https://github.com/oVirt/ovirt-site/issues/1503</a> t= o track this. Opening a ticket on infra as well for further investigations.= </p> <blockquote><pre>On Wed, Jan 24, 2018 at 12:00 PM, Lev Veyde <lveyde@red= hat.com> wrote:</pre> <blockquote><p>The oVirt Project is pleased to announce the availability of= the oVirt 4.1.9 release, as of January 24th, 2017</p> <p>This update is the ninth in a series of stabilization updates to the 4.1= series.</p> <p>Please note that no further updates will be issued for the 4.1 series. W= e encourage users to upgrade to 4.2 series to receive new features and upda= tes.</p> <p>This release is available now for:</p> <ul><li><p>Red Hat Enterprise Linux 7.4 or later</p></li> <li><p>CentOS Linux (or similar) 7.4 or later</p></li></ul> <p>This release supports Hypervisor Hosts running:</p> <ul><li><p>Red Hat Enterprise Linux 7.4 or later</p></li> <li><p>CentOS Linux (or similar) 7.4 or later</p></li> <li><p>oVirt Node 4.1</p></li></ul> <p>See the release notes [1] for installation / upgrade instructions and a = list of new features and bugs fixed.</p> <p>Notes:</p> <ul><li><p>oVirt Appliance is already available</p></li> <li><p>oVirt Live is already available [2]</p></li> <li><p>oVirt Node will be available soon [2]</p></li></ul> <p>Additional Resources:</p> <ul><li><p>Read more about the oVirt 4.1.9 release highlights:http://www.ov= irt.or</p></li></ul> <p>g/release/4.1.9/</p> <ul><li><p>Get more oVirt Project updates on Twitter: <a href=3D"https://tw= itter.com/ovirt">https://twitter.com/ovirt</a></p></li> <li><p>Check out the latest project news on the oVirt blog:</p></li></ul> <p><a href=3D"http://www.ovirt.org/blog/">http://www.ovirt.org/blog/</a></p> <p>[1] <a href=3D"http://www.ovirt.org/release/4.1.9/">http://www.ovirt.org= /release/4.1.9/</a> [2] <a href=3D"http://resources.ovirt.org/pub/ovirt-4.1= /iso/">http://resources.ovirt.org/pub/ovirt-4.1/iso/</a></p> <p>—</p> <p>Lev Veyde</p> <p>Software Engineer, RHCE | RHCVA | MCITP</p> <p>Red Hat Israel</p> <p><<a href=3D"https://www.redhat.com/">https://www.redhat.com</a>></= p> <p>lev(a)redhat.com | lveyde(a)redhat.com <<a href=3D"https://red.ht/sig">ht= tps://red.ht/sig</a>> TRIED. TESTED. TRUSTED. <<a href=3D"https://red= hat.com/trusted">https://redhat.com/trusted</a>></p> <p><em>____________________________________________</em>_ Users mailing lis= t Users(a)ovirt.org <a href=3D"http://lists.ovirt.org/mailman/listinfo/users"= >http://lists.ovirt.org/mailman/listinfo/users</a></p></blockquote> <pre>_______________________________________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users</pre></blockquote> <p>— SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA E= NG VIRTUALIZATION R&D Red Hat EMEA <<a href=3D"https://www.redhat.co= m/">https://www.redhat.com/</a>> <<a href=3D"https://red.ht/sig">http= s://red.ht/sig</a>> TRIED. TESTED. TRUSTED. <<a href=3D"https://redha= t.com/trusted">https://redhat.com/trusted</a>></p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#1000= 81)</p> <img src=3D"https://u4043402.ct.sendgrid.net/wf/open?upn=3Di5TMWGV99amJbNxJ= pSp2-2BJ33BSM3tuiUfRTk64K-2BOjFTKd1eQk0jeaIcBJlLyWiNcvGIsCfxaYIbnSSZ5n5g-2F= FAwse349mKKxFQJ8h-2FY6gV-2BKhpyUfAO2xszwz4CcILXaNX6Xc-2FlDgmflUKntctunMYkPn= xKt-2FhBJX3P0x9ZCUF0GeONEQIUn-2FF1KBf1fAXvoXpIX-2B8RiS7xJQ0Xme2ELGa6QDZ5Vyo= Bxuz09XesU0NWy6cCNRrmBL4T-2FLqxAH84C-2Fc-2FDWj1psNJ2I-2Fk5PlVlqViAxQ32lzweU= MFLPJJPy6njDZHN6xVi4gM9vW6-2FvKdgPnHmd9FeysIx-2FU64ixmR06QXyRvcZ4G-2FYkv8Uh= ucMZdoj4VG5xSdhRMV8ymgDE6NTle2RPvrHBPzdVVJ2TyE5RY1Kp2Gf4-2BSSm0w9Q6dcolBHX3= YO0UsaTzrDbfWkrd" alt=3D"" width=3D"1" height=3D"1" border=3D"0" style=3D"h= eight:1px !important;width:1px !important;border-width:0 !important;margin-= top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margi= n-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;pa= dding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1520343278-10207-157--

1 0

Packages not landed on tested repo
by Sandro Bonazzola 06 Mar '18

06 Mar '18

Hi, looks like we have some packages which never passed OST, never landed in ovirt-4.2-snapshot repo and are currently causing failure building the appliance from 4.2 snapshot repo: 03:17:20,893 INFO program:Error: Package: ovirt-engine-4.2.2.3-0.0.master.20180305171049.git0e81394.el7.centos.noarch (ovirt-4.2-snapshot) 03:17:20,893 INFO program:Requires: ovirt-ansible-roles >= 1.1.2 03:17:20,894 INFO program:Error: Package: ovirt-engine-4.2.2.3-0.0.master.20180305171049.git0e81394.el7.centos.noarch (ovirt-4.2-snapshot) 03:17:20,896 INFO program:Requires: ovirt-js-dependencies 03:17:20,897 INFO program:Error: Package: ovirt-engine-4.2.2.3-0.0.master.20180305171049.git0e81394.el7.centos.noarch (ovirt-4.2-snapshot) 03:17:20,897 INFO program:Requires: ovirt-engine-wildfly-overlay >= 11.0.1 03:17:20,899 INFO program:Error: Package: ovirt-engine-api-explorer-0.0.3-0.alpha.1.20180215git9b54c9c.el7.centos.noarch (ovirt-4.2-snapshot) 03:17:20,900 INFO program:Requires: ovirt-js-dependencies >= 1.2 I'm now trying to get the missing packages pass thorough the whole testing pipeline but be aware those packages have already been released 3 months ago so they are stable and manually tested and were passing master OST. I've no clue on why they are missing in the 4.2 testing pipeline. -- 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>

2 1

[JIRA] (OVIRT-1918) Single project tests in change-queue-tester
by Barak Korren (oVirt JIRA) 06 Mar '18

06 Mar '18

This is a multi-part message in MIME format... ------------=_1520340937-32412-262 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1918?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1918: ------------------------------------- {quote} How a pacakge maintainer will know that a package didn't land in tested? It tooks me 2 months to discover we have packages not getting in tested and I noticed just by mistake. And I'm one of those maintainers that cares a lot about packages being published. {quote} [~dron]/infra-owner is supposed to tell you. This reporting is not fully automated yet because of false positives. Specifically WRT build failures you already get a comment in Gerrit. > Single project tests in change-queue-tester > ------------------------------------------- > > Key: OVIRT-1918 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1918 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > Please change change-queue-tester jobs for testing a single project at a > time (ok for multiple patches at once, but from the same project). > Right now if multiple patches are merged between a change-queue-tester > execution and the next one are done, all of them will be tested in the next > run, even if the changes are in different projects. > So, supposing project A and B are completely fine, a failure in project C > can still prevent changes in A and B to go ahead through the pipeline and > get released. > This cause major headaches at least to me, requiring me to go again over > all the HEAD of the projects not being published and run yet again "ci > re-merge please" again and again and again until I'm lucky enough to have > nobody else merging patches or having all the ttested patches pass at once. > I understand the need to reduce the amount of executions of the job since > it takes an hour to execute but right now it's stealing days of execution > for getting a patch landing on tested repo. > -- > 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> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081) ------------=_1520340937-32412-262 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1918?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren commented on OVIRT-1918:</h3> <p>{quote} How a pacakge maintainer will know that a package didn't land in tested? It tooks me 2 months to discover we have packages not getting in tested and I noticed just by mistake. And I'm one of those maintainers that cares a lot about packages being published. {quote}</p> <p>[~dron]/infra-owner is supposed to tell you. This reporting is not fully automated yet because of false positives. Specifically WRT build failures you already get a comment in Gerrit.</p> <blockquote><h3>Single project tests in change-queue-tester</h3> <pre> Key: OVIRT-1918 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1918 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: sbonazzo Assignee: infra</pre> <p>Please change change-queue-tester jobs for testing a single project at a time (ok for multiple patches at once, but from the same project). Right now if multiple patches are merged between a change-queue-tester execution and the next one are done, all of them will be tested in the next run, even if the changes are in different projects. So, supposing project A and B are completely fine, a failure in project C can still prevent changes in A and B to go ahead through the pipeline and get released. This cause major headaches at least to me, requiring me to go again over all the HEAD of the projects not being published and run yet again “ci re-merge please” again and again and again until I'm lucky enough to have nobody else merging patches or having all the ttested patches pass at once. I understand the need to reduce the amount of executions of the job since it takes an hour to execute but right now it's stealing days of execution for getting a patch landing on tested repo. — SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <<a href="https://www.redhat.com/">https://www.redhat.com/</a>> <<a href="https://red.ht/sig">https://red.ht/sig</a>> TRIED. TESTED. TRUSTED. <<a href="https://redhat.com/trusted">https://redhat.com/trusted</a>></p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1520340937-32412-262--

1 0

[JIRA] (OVIRT-1918) Single project tests in change-queue-tester
by Barak Korren (oVirt JIRA) 06 Mar '18

06 Mar '18

This is a multi-part message in MIME format... ------------=_1520340720-12851-179 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1918?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1918: ------------------------------------- {quote} I'm not sure that the bisection really works then, since we have still packages released 2 months ago not yet landing on tested. I don't recall to have seen any job triggered automatically after a change-queue-tester failure doing bisection tests. {quote} It works. 'change-queue-tester' itself gets re-triggered by 'change-queue' with a different set of patches after failure. Only failures that were narrowed down to a single patch are reported to infra-list. You can see the state of the queue an the bisection status in a graphical display on the status page of the 'change-queue' job. If you see something that wasn't moved to tested it can be because: # the HEAD itself that was tested is really broken # some build job failed because of an infra issue (e.g s390x/fcraw issue) # OST itself was broken at the time of the test "ci re-merge please" is for handling the last 2 reasons, essentially [~dron] or the infra owner is supposed to be monitoring the CQ reports, detecting theses cases and issuing "ci re-merge please" as needed. > Single project tests in change-queue-tester > ------------------------------------------- > > Key: OVIRT-1918 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1918 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > Please change change-queue-tester jobs for testing a single project at a > time (ok for multiple patches at once, but from the same project). > Right now if multiple patches are merged between a change-queue-tester > execution and the next one are done, all of them will be tested in the next > run, even if the changes are in different projects. > So, supposing project A and B are completely fine, a failure in project C > can still prevent changes in A and B to go ahead through the pipeline and > get released. > This cause major headaches at least to me, requiring me to go again over > all the HEAD of the projects not being published and run yet again "ci > re-merge please" again and again and again until I'm lucky enough to have > nobody else merging patches or having all the ttested patches pass at once. > I understand the need to reduce the amount of executions of the job since > it takes an hour to execute but right now it's stealing days of execution > for getting a patch landing on tested repo. > -- > 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> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081) ------------=_1520340720-12851-179 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1918?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren commented on OVIRT-1918:</h3> <p>{quote} I'm not sure that the bisection really works then, since we have still packages released 2 months ago not yet landing on tested. I don't recall to have seen any job triggered automatically after a change-queue-tester failure doing bisection tests. {quote}</p> <p>It works. ‘change-queue-tester’ itself gets re-triggered by ‘change-queue’ with a different set of patches after failure. Only failures that were narrowed down to a single patch are reported to infra-list.</p> <p>You can see the state of the queue an the bisection status in a graphical display on the status page of the ‘change-queue’ job.</p> <p>If you see something that wasn't moved to tested it can be because: # the HEAD itself that was tested is really broken # some build job failed because of an infra issue (e.g s390x/fcraw issue) # OST itself was broken at the time of the test</p> <p>“ci re-merge please” is for handling the last 2 reasons, essentially [~dron] or the infra owner is supposed to be monitoring the CQ reports, detecting theses cases and issuing “ci re-merge please” as needed.</p> <blockquote><h3>Single project tests in change-queue-tester</h3> <pre> Key: OVIRT-1918 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1918 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: sbonazzo Assignee: infra</pre> <p>Please change change-queue-tester jobs for testing a single project at a time (ok for multiple patches at once, but from the same project). Right now if multiple patches are merged between a change-queue-tester execution and the next one are done, all of them will be tested in the next run, even if the changes are in different projects. So, supposing project A and B are completely fine, a failure in project C can still prevent changes in A and B to go ahead through the pipeline and get released. This cause major headaches at least to me, requiring me to go again over all the HEAD of the projects not being published and run yet again “ci re-merge please” again and again and again until I'm lucky enough to have nobody else merging patches or having all the ttested patches pass at once. I understand the need to reduce the amount of executions of the job since it takes an hour to execute but right now it's stealing days of execution for getting a patch landing on tested repo. — SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <<a href="https://www.redhat.com/">https://www.redhat.com/</a>> <<a href="https://red.ht/sig">https://red.ht/sig</a>> TRIED. TESTED. TRUSTED. <<a href="https://redhat.com/trusted">https://redhat.com/trusted</a>></p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1520340720-12851-179--

1 0

[JIRA] (OVIRT-1918) Single project tests in change-queue-tester
by sbonazzo (oVirt JIRA) 06 Mar '18

06 Mar '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1918?page=com.atlassian.jira.… ] sbonazzo commented on OVIRT-1918: --------------------------------- bq. Maybe we need to use always the official release repo as fallback to tested? I don't think so. Tested repo should not require official release repo. Official release should be eventually generated from tested repo, not the other way around. bq. In case a specific PKG failed to build and it's maintainer didn't make sure bq. to fix it and redeploy, it makes sense to get missing pkgs from latest bq. official release, as we do in OST. How a pacakge maintainer will know that a package didn't land in tested? It tooks me 2 months to discover we have packages not getting in tested and I noticed just by mistake. And I'm one of those maintainers that cares a lot about packages being published. bq. Once the maintainer of the project will build a new image and it passes, it bq. will be in tested. That's not always true. I had several packages that required me to issue "ci re-merge please" multiple times before getting to tested repo without any code change on the project itself. > Single project tests in change-queue-tester > ------------------------------------------- > > Key: OVIRT-1918 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1918 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > Please change change-queue-tester jobs for testing a single project at a > time (ok for multiple patches at once, but from the same project). > Right now if multiple patches are merged between a change-queue-tester > execution and the next one are done, all of them will be tested in the next > run, even if the changes are in different projects. > So, supposing project A and B are completely fine, a failure in project C > can still prevent changes in A and B to go ahead through the pipeline and > get released. > This cause major headaches at least to me, requiring me to go again over > all the HEAD of the projects not being published and run yet again "ci > re-merge please" again and again and again until I'm lucky enough to have > nobody else merging patches or having all the ttested patches pass at once. > I understand the need to reduce the amount of executions of the job since > it takes an hour to execute but right now it's stealing days of execution > for getting a patch landing on tested repo. > -- > 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> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081)

1 0

[JIRA] (OVIRT-1915) Add option to filter packages in OST manual
by eyal edri (oVirt JIRA) 06 Mar '18

06 Mar '18

This is a multi-part message in MIME format... ------------=_1520339293-14913-290 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1915?page=com.atlassian.jira.… ] eyal edri commented on OVIRT-1915: ---------------------------------- Here is the ticket to add this repoman filter option to the upstream job, can you or Dusan handle it? A similar code already exists in the old manual job in d/s, which doesn't work anymore. On Sun, Mar 4, 2018 at 2:39 PM, Daniel Belenky (oVirt JIRA) < -- Eyal edri MANAGER RHV DevOps EMEA VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ) > Add option to filter packages in OST manual > ------------------------------------------- > > Key: OVIRT-1915 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1915 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: Daniel Belenky > Assignee: infra > Labels: jenkins, ost > > Sometimes we want to filter packages that are being downloaded through repoman. In order to do so, we need to expose repoman's filtering API through Jenkins build parameters. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081) ------------=_1520339293-14913-290 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1915?page=com.atlassian.jira.… ]</pre> <h3>eyal edri commented on OVIRT-1915:</h3> <p>Here is the ticket to add this repoman filter option to the upstream job, can you or Dusan handle it? A similar code already exists in the old manual job in d/s, which doesn't work anymore.</p> <p>On Sun, Mar 4, 2018 at 2:39 PM, Daniel Belenky (oVirt JIRA) <</p> <p>—</p> <p>Eyal edri</p> <p>MANAGER</p> <p>RHV DevOps</p> <p>EMEA VIRTUALIZATION R&D</p> <p>Red Hat EMEA <<a href="https://www.redhat.com/">https://www.redhat.com/</a>> <<a href="https://red.ht/sig">https://red.ht/sig</a>> TRIED. TESTED. TRUSTED. <<a href="https://redhat.com/trusted">https://redhat.com/trusted</a>> phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)</p> <blockquote><h3>Add option to filter packages in OST manual</h3> <pre> Key: OVIRT-1915 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1915 Project: oVirt - virtualization made easy Issue Type: New Feature Reporter: Daniel Belenky Assignee: infra Labels: jenkins, ost</pre> <p>Sometimes we want to filter packages that are being downloaded through repoman. In order to do so, we need to expose repoman's filtering API through Jenkins build parameters.</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1520339293-14913-290--

1 0

[JIRA] (OVIRT-1915) Add option to filter packages in OST manual
by Daniel Belenky (oVirt JIRA) 06 Mar '18

06 Mar '18

This is a multi-part message in MIME format... ------------=_1520167161-24881-147 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1915?page=com.atlassian.jira.… ] Daniel Belenky updated OVIRT-1915: ---------------------------------- Labels: jenkins ost (was: ) > Add option to filter packages in OST manual > ------------------------------------------- > > Key: OVIRT-1915 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1915 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: Daniel Belenky > Assignee: infra > Labels: jenkins, ost > > Sometimes we want to filter packages that are being downloaded through repoman. In order to do so, we need to expose repoman's filtering API through Jenkins build parameters. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081) ------------=_1520167161-24881-147 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1915?page=com.atlassian.jira.… ]</pre> <h3>Daniel Belenky updated OVIRT-1915:</h3> <pre>Labels: jenkins ost (was: )</pre> <blockquote><h3>Add option to filter packages in OST manual</h3> <pre> Key: OVIRT-1915 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1915 Project: oVirt - virtualization made easy Issue Type: New Feature Reporter: Daniel Belenky Assignee: infra Labels: jenkins, ost</pre> <p>Sometimes we want to filter packages that are being downloaded through repoman. In order to do so, we need to expose repoman's filtering API through Jenkins build parameters.</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1520167161-24881-147--

2 1

[JIRA] (OVIRT-1918) Single project tests in change-queue-tester
by eyal edri (oVirt JIRA) 06 Mar '18

06 Mar '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1918?page=com.atlassian.jira.… ] eyal edri commented on OVIRT-1918: ---------------------------------- Maybe we need to use always the official release repo as fallback to tested? In case a specific PKG failed to build and it's maintainer didn't make sure to fix it and redeploy, it makes sense to get missing pkgs from latest official release, as we do in OST. Once the maintainer of the project will build a new image and it passes, it will be in tested. On Mar 6, 2018 14:02, "sbonazzo (oVirt JIRA)" <jira(a)ovirt-jira.atlassian.net> wrote: [ https://ovirt-jira.atlassian.net/browse/OVIRT-1918?page=com.atlassian.jira.… ] sbonazzo commented on OVIRT-1918: I'm not sure that the bisection really works then, since we have still packages released 2 months ago not yet landing on tested. I don't recall to have seen any job triggered automatically after a change-queue-tester failure doing bisection tests. Single project tests in change-queue-tester Key: OVIRT-1918 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1918 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: sbonazzo Assignee: infra Please change change-queue-tester jobs for testing a single project at a time (ok for multiple patches at once, but from the same project). Right now if multiple patches are merged between a change-queue-tester execution and the next one are done, all of them will be tested in the next run, even if the changes are in different projects. So, supposing project A and B are completely fine, a failure in project C can still prevent changes in A and B to go ahead through the pipeline and get released. This cause major headaches at least to me, requiring me to go again over all the HEAD of the projects not being published and run yet again “ci re-merge please” again and again and again until I'm lucky enough to have nobody else merging patches or having all the ttested patches pass at once. I understand the need to reduce the amount of executions of the job since it takes an hour to execute but right now it's stealing days of execution for getting a patch landing on t ested repo. — 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> — This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081) > Single project tests in change-queue-tester > ------------------------------------------- > > Key: OVIRT-1918 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1918 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > Please change change-queue-tester jobs for testing a single project at a > time (ok for multiple patches at once, but from the same project). > Right now if multiple patches are merged between a change-queue-tester > execution and the next one are done, all of them will be tested in the next > run, even if the changes are in different projects. > So, supposing project A and B are completely fine, a failure in project C > can still prevent changes in A and B to go ahead through the pipeline and > get released. > This cause major headaches at least to me, requiring me to go again over > all the HEAD of the projects not being published and run yet again "ci > re-merge please" again and again and again until I'm lucky enough to have > nobody else merging patches or having all the ttested patches pass at once. > I understand the need to reduce the amount of executions of the job since > it takes an hour to execute but right now it's stealing days of execution > for getting a patch landing on tested repo. > -- > 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> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081)

1 0

Re: [JIRA] (OVIRT-1918) Single project tests in change-queue-tester
by Eyal Edri 06 Mar '18

06 Mar '18

Maybe we need to use always the official release repo as fallback to tested? In case a specific PKG failed to build and it's maintainer didn't make sure to fix it and redeploy, it makes sense to get missing pkgs from latest official release, as we do in OST. Once the maintainer of the project will build a new image and it passes, it will be in tested. On Mar 6, 2018 14:02, "sbonazzo (oVirt JIRA)" <jira(a)ovirt-jira.atlassian.net> wrote: [ https://ovirt-jira.atlassian.net/browse/OVIRT-1918?page=com.atlassian.jira.… ] sbonazzo commented on OVIRT-1918: I'm not sure that the bisection really works then, since we have still packages released 2 months ago not yet landing on tested. I don't recall to have seen any job triggered automatically after a change-queue-tester failure doing bisection tests. Single project tests in change-queue-tester Key: OVIRT-1918 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1918 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: sbonazzo Assignee: infra Please change change-queue-tester jobs for testing a single project at a time (ok for multiple patches at once, but from the same project). Right now if multiple patches are merged between a change-queue-tester execution and the next one are done, all of them will be tested in the next run, even if the changes are in different projects. So, supposing project A and B are completely fine, a failure in project C can still prevent changes in A and B to go ahead through the pipeline and get released. This cause major headaches at least to me, requiring me to go again over all the HEAD of the projects not being published and run yet again “ci re-merge please” again and again and again until I'm lucky enough to have nobody else merging patches or having all the ttested patches pass at once. I understand the need to reduce the amount of executions of the job since it takes an hour to execute but right now it's stealing days of execution for getting a patch landing on t ested repo. — 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> — This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081) _______________________________________________ Infra mailing list Infra(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/infra

1 0

[JIRA] (OVIRT-1918) Single project tests in change-queue-tester
by sbonazzo (oVirt JIRA) 06 Mar '18

06 Mar '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1918?page=com.atlassian.jira.… ] sbonazzo commented on OVIRT-1918: --------------------------------- I'm not sure that the bisection really works then, since we have still packages released 2 months ago not yet landing on tested. I don't recall to have seen any job triggered automatically after a change-queue-tester failure doing bisection tests. > Single project tests in change-queue-tester > ------------------------------------------- > > Key: OVIRT-1918 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1918 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > Please change change-queue-tester jobs for testing a single project at a > time (ok for multiple patches at once, but from the same project). > Right now if multiple patches are merged between a change-queue-tester > execution and the next one are done, all of them will be tested in the next > run, even if the changes are in different projects. > So, supposing project A and B are completely fine, a failure in project C > can still prevent changes in A and B to go ahead through the pipeline and > get released. > This cause major headaches at least to me, requiring me to go again over > all the HEAD of the projects not being published and run yet again "ci > re-merge please" again and again and again until I'm lucky enough to have > nobody else merging patches or having all the ttested patches pass at once. > I understand the need to reduce the amount of executions of the job since > it takes an hour to execute but right now it's stealing days of execution > for getting a patch landing on tested repo. > -- > 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> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081)

1 0

[CQ]: 88250,4 (ovirt-engine-metrics) failed "ovirt-4.2" system tests
by oVirt Jenkins 06 Mar '18

06 Mar '18

Change 88250,4 (ovirt-engine-metrics) 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/88250/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/1041/

1 0

[JIRA] (OVIRT-1918) Single project tests in change-queue-tester
by Barak Korren (oVirt JIRA) 06 Mar '18

06 Mar '18

This is a multi-part message in MIME format... ------------=_1520333776-20649-136 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1918?page=com.atlassian.jira.… ] Barak Korren edited comment on OVIRT-1918 at 3/6/18 10:56 AM: -------------------------------------------------------------- {quote} So, supposing project A and B are completely fine, a failure in project C can still prevent changes in A and B to go ahead through the pipeline and get released. {quote} This statement is false - what will happen in this case is that a bisection search will run and isulate the change to project C, while allowing the changes for A and B to pass. This is the whole point of CQ and the difference between it and the 'experimental' system it replaced. [~sbonazzo(a)redhat.com] Unless you need further clarification, I will close this ticket as WONTFIX. was (Author: bkorren(a)redhat.com) {quote} So, supposing project A and B are completely fine, a failure in project C can still prevent changes in A and B to go ahead through the pipeline and get released. {quote} This statement is false - what will happen in this case is that a bisection search will run and isulate the change to project C, while allowing the changes for A and B to pass. This si the whole point of CQ and the difference between it and the 'experimental' system it replaced. [~sbonazzo(a)redhat.com] Unless you need further clarification, I will close this ticket as WONTFIX. > Single project tests in change-queue-tester > ------------------------------------------- > > Key: OVIRT-1918 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1918 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > Please change change-queue-tester jobs for testing a single project at a > time (ok for multiple patches at once, but from the same project). > Right now if multiple patches are merged between a change-queue-tester > execution and the next one are done, all of them will be tested in the next > run, even if the changes are in different projects. > So, supposing project A and B are completely fine, a failure in project C > can still prevent changes in A and B to go ahead through the pipeline and > get released. > This cause major headaches at least to me, requiring me to go again over > all the HEAD of the projects not being published and run yet again "ci > re-merge please" again and again and again until I'm lucky enough to have > nobody else merging patches or having all the ttested patches pass at once. > I understand the need to reduce the amount of executions of the job since > it takes an hour to execute but right now it's stealing days of execution > for getting a patch landing on tested repo. > -- > 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> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081) ------------=_1520333776-20649-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-1918?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren edited comment on OVIRT-1918 at 3/6/18 10:56 AM:</h3> <p>{quote} So, supposing project A and B are completely fine, a failure in project C can still prevent changes in A and B to go ahead through the pipeline and get released. {quote}</p> <p>This statement is false – what will happen in this case is that a bisection search will run and isulate the change to project C, while allowing the changes for A and B to pass. This is the whole point of CQ and the difference between it and the ‘experimental’ system it replaced.</p> <p>[~sbonazzo(a)redhat.com] Unless you need further clarification, I will close this ticket as WONTFIX.</p> <p>was (Author: bkorren(a)redhat.com) {quote} So, supposing project A and B are completely fine, a failure in project C can still prevent changes in A and B to go ahead through the pipeline and get released. {quote}</p> <p>This statement is false – what will happen in this case is that a bisection search will run and isulate the change to project C, while allowing the changes for A and B to pass. This si the whole point of CQ and the difference between it and the ‘experimental’ system it replaced.</p> <p>[~sbonazzo(a)redhat.com] Unless you need further clarification, I will close this ticket as WONTFIX.</p> <blockquote><h3>Single project tests in change-queue-tester</h3> <pre> Key: OVIRT-1918 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1918 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: sbonazzo Assignee: infra</pre> <p>Please change change-queue-tester jobs for testing a single project at a time (ok for multiple patches at once, but from the same project). Right now if multiple patches are merged between a change-queue-tester execution and the next one are done, all of them will be tested in the next run, even if the changes are in different projects. So, supposing project A and B are completely fine, a failure in project C can still prevent changes in A and B to go ahead through the pipeline and get released. This cause major headaches at least to me, requiring me to go again over all the HEAD of the projects not being published and run yet again “ci re-merge please” again and again and again until I'm lucky enough to have nobody else merging patches or having all the ttested patches pass at once. I understand the need to reduce the amount of executions of the job since it takes an hour to execute but right now it's stealing days of execution for getting a patch landing on tested repo. — SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <<a href="https://www.redhat.com/">https://www.redhat.com/</a>> <<a href="https://red.ht/sig">https://red.ht/sig</a>> TRIED. TESTED. TRUSTED. <<a href="https://redhat.com/trusted">https://redhat.com/trusted</a>></p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1520333776-20649-136--

1 0

[JIRA] (OVIRT-1918) Single project tests in change-queue-tester
by Barak Korren (oVirt JIRA) 06 Mar '18

06 Mar '18

This is a multi-part message in MIME format... ------------=_1520333757-27720-121 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1918?page=com.atlassian.jira.… ] Barak Korren edited comment on OVIRT-1918 at 3/6/18 10:55 AM: -------------------------------------------------------------- {quote} So, supposing project A and B are completely fine, a failure in project C can still prevent changes in A and B to go ahead through the pipeline and get released. {quote} This statement is false - what will happen in this case is that a bisection search will run and isulate the change to project C, while allowing the changes for A and B to pass. This si the whole point of CQ and the difference between it and the 'experimental' system it replaced. [~sbonazzo(a)redhat.com] Unless you need further clarification, I will close this ticket as WONTFIX. was (Author: bkorren(a)redhat.com) {quote} So, supposing project A and B are completely fine, a failure in project C can still prevent changes in A and B to go ahead through the pipeline and get released. {quote} This statement is false - what will happen in this case is that a bisection search will run and isulate the change to project C, while allowing the changes for A and B to pass. This si the whole point of CQ and the difference between it and the 'experimental' system it replaced. [~sbonazzo(a)redhat.com] Un;ess you need further clarification, I will close this ticket as WONTFIX. > Single project tests in change-queue-tester > ------------------------------------------- > > Key: OVIRT-1918 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1918 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > Please change change-queue-tester jobs for testing a single project at a > time (ok for multiple patches at once, but from the same project). > Right now if multiple patches are merged between a change-queue-tester > execution and the next one are done, all of them will be tested in the next > run, even if the changes are in different projects. > So, supposing project A and B are completely fine, a failure in project C > can still prevent changes in A and B to go ahead through the pipeline and > get released. > This cause major headaches at least to me, requiring me to go again over > all the HEAD of the projects not being published and run yet again "ci > re-merge please" again and again and again until I'm lucky enough to have > nobody else merging patches or having all the ttested patches pass at once. > I understand the need to reduce the amount of executions of the job since > it takes an hour to execute but right now it's stealing days of execution > for getting a patch landing on tested repo. > -- > 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> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081) ------------=_1520333757-27720-121 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1918?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren edited comment on OVIRT-1918 at 3/6/18 10:55 AM:</h3> <p>{quote} So, supposing project A and B are completely fine, a failure in project C can still prevent changes in A and B to go ahead through the pipeline and get released. {quote}</p> <p>This statement is false – what will happen in this case is that a bisection search will run and isulate the change to project C, while allowing the changes for A and B to pass. This si the whole point of CQ and the difference between it and the ‘experimental’ system it replaced.</p> <p>[~sbonazzo(a)redhat.com] Unless you need further clarification, I will close this ticket as WONTFIX.</p> <p>was (Author: bkorren(a)redhat.com) {quote} So, supposing project A and B are completely fine, a failure in project C can still prevent changes in A and B to go ahead through the pipeline and get released. {quote}</p> <p>This statement is false – what will happen in this case is that a bisection search will run and isulate the change to project C, while allowing the changes for A and B to pass. This si the whole point of CQ and the difference between it and the ‘experimental’ system it replaced.</p> <p>[~sbonazzo(a)redhat.com] Un;ess you need further clarification, I will close this ticket as WONTFIX.</p> <blockquote><h3>Single project tests in change-queue-tester</h3> <pre> Key: OVIRT-1918 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1918 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: sbonazzo Assignee: infra</pre> <p>Please change change-queue-tester jobs for testing a single project at a time (ok for multiple patches at once, but from the same project). Right now if multiple patches are merged between a change-queue-tester execution and the next one are done, all of them will be tested in the next run, even if the changes are in different projects. So, supposing project A and B are completely fine, a failure in project C can still prevent changes in A and B to go ahead through the pipeline and get released. This cause major headaches at least to me, requiring me to go again over all the HEAD of the projects not being published and run yet again “ci re-merge please” again and again and again until I'm lucky enough to have nobody else merging patches or having all the ttested patches pass at once. I understand the need to reduce the amount of executions of the job since it takes an hour to execute but right now it's stealing days of execution for getting a patch landing on tested repo. — SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <<a href="https://www.redhat.com/">https://www.redhat.com/</a>> <<a href="https://red.ht/sig">https://red.ht/sig</a>> TRIED. TESTED. TRUSTED. <<a href="https://redhat.com/trusted">https://redhat.com/trusted</a>></p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1520333757-27720-121--

1 0

[JIRA] (OVIRT-1918) Single project tests in change-queue-tester
by Barak Korren (oVirt JIRA) 06 Mar '18

06 Mar '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1918?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1918: ------------------------------------- {quote} So, supposing project A and B are completely fine, a failure in project C can still prevent changes in A and B to go ahead through the pipeline and get released. {quote} This statement is false - what will happen in this case is that a bisection search will run and isulate the change to project C, while allowing the changes for A and B to pass. This si the whole point of CQ and the difference between it and the 'experimental' system it replaced. [~sbonazzo(a)redhat.com] Un;ess you need further clarification, I will close this ticket as WONTFIX. > Single project tests in change-queue-tester > ------------------------------------------- > > Key: OVIRT-1918 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1918 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > Please change change-queue-tester jobs for testing a single project at a > time (ok for multiple patches at once, but from the same project). > Right now if multiple patches are merged between a change-queue-tester > execution and the next one are done, all of them will be tested in the next > run, even if the changes are in different projects. > So, supposing project A and B are completely fine, a failure in project C > can still prevent changes in A and B to go ahead through the pipeline and > get released. > This cause major headaches at least to me, requiring me to go again over > all the HEAD of the projects not being published and run yet again "ci > re-merge please" again and again and again until I'm lucky enough to have > nobody else merging patches or having all the ttested patches pass at once. > I understand the need to reduce the amount of executions of the job since > it takes an hour to execute but right now it's stealing days of execution > for getting a patch landing on tested repo. > -- > 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> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081)

1 0

[JIRA] (OVIRT-1918) Single project tests in change-queue-tester
by sbonazzo (oVirt JIRA) 06 Mar '18

06 Mar '18

sbonazzo created OVIRT-1918: ------------------------------- Summary: Single project tests in change-queue-tester Key: OVIRT-1918 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1918 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: sbonazzo Assignee: infra Please change change-queue-tester jobs for testing a single project at a time (ok for multiple patches at once, but from the same project). Right now if multiple patches are merged between a change-queue-tester execution and the next one are done, all of them will be tested in the next run, even if the changes are in different projects. So, supposing project A and B are completely fine, a failure in project C can still prevent changes in A and B to go ahead through the pipeline and get released. This cause major headaches at least to me, requiring me to go again over all the HEAD of the projects not being published and run yet again "ci re-merge please" again and again and again until I'm lucky enough to have nobody else merging patches or having all the ttested patches pass at once. I understand the need to reduce the amount of executions of the job since it takes an hour to execute but right now it's stealing days of execution for getting a patch landing on tested repo. -- 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> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081)

1 0

Build failed in Jenkins: system-sync_mirrors-epel-el6-x86_64 #1262
by jenkins＠jenkins.phx.ovirt.org 06 Mar '18

06 Mar '18

See <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/1262/displ…> ------------------------------------------ Started by timer [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/ws/> > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -fdx # timeout=10 Pruning obsolete local branches Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git > git --version # timeout=10 > git fetch --tags --progress http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* --prune > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision ea02d358e4b5ba495ce4f865f48d932427cd0bdb (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f ea02d358e4b5ba495ce4f865f48d932427cd0bdb Commit message: "Revert "Install base packeges and start services from global_setup"" > git rev-list --no-walk ea02d358e4b5ba495ce4f865f48d932427cd0bdb # timeout=10 [system-sync_mirrors-epel-el6-x86_64] $ /bin/bash -xe /tmp/jenkins562107027827444518.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror epel-el6 x86_64 jenkins/data/mirrors-reposync.conf Checking if mirror needs a resync Traceback (most recent call last): File "/usr/bin/reposync", line 343, in <module> main() File "/usr/bin/reposync", line 175, in main my.doRepoSetup() File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 681, in doRepoSetup return self._getRepos(thisrepo, True) File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 721, in _getRepos self._repos.doSetup(thisrepo) File "/usr/lib/python2.7/site-packages/yum/repos.py", line 157, in doSetup self.retrieveAllMD() File "/usr/lib/python2.7/site-packages/yum/repos.py", line 88, in retrieveAllMD dl = repo._async and repo._commonLoadRepoXML(repo) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1474, in _commonLoadRepoXML if self._latestRepoXML(local): File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1443, in _latestRepoXML oxml = self._saveOldRepoXML(local) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1300, in _saveOldRepoXML shutil.copy2(local, old_local) File "/usr/lib64/python2.7/shutil.py", line 131, in copy2 copystat(src, dst) File "/usr/lib64/python2.7/shutil.py", line 98, in copystat os.utime(dst, (st.st_atime, st.st_mtime)) OSError: [Errno 2] No such file or directory: '/home/jenkins/mirrors_cache/centos-extras-el7/repomd.xml.old.tmp' Build step 'Execute shell' marked build as failure

1 1

[JIRA] (OVIRT-1917) Off by one bug in nested config parser
by Daniel Belenky (oVirt JIRA) 06 Mar '18

06 Mar '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1917?page=com.atlassian.jira.… ] Daniel Belenky reassigned OVIRT-1917: ------------------------------------- Assignee: Daniel Belenky (was: infra) > Off by one bug in nested config parser > -------------------------------------- > > Key: OVIRT-1917 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1917 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Daniel Belenky > Assignee: Daniel Belenky > Priority: Highest > > There is an off by one bug in _cartesian_multiplication() (nested_config.py) where if given a list of vectors to try and merge with each other, the last vector, if merged, needs to be excluded from the final result since it was already merged. In other cases, if the last vector was not merged, it needs to be included in the final result. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081)

1 0

[JIRA] (OVIRT-1917) Off by one bug in nested config parser
by Daniel Belenky (oVirt JIRA) 06 Mar '18

06 Mar '18

Daniel Belenky created OVIRT-1917: ------------------------------------- Summary: Off by one bug in nested config parser Key: OVIRT-1917 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1917 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Daniel Belenky Assignee: infra Priority: Highest There is an off by one bug in _cartesian_multiplication() (nested_config.py) where if given a list of vectors to try and merge with each other, the last vector, if merged, needs to be excluded from the final result since it was already merged. In other cases, if the last vector was not merged, it needs to be included in the final result. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081)

1 0

[CQ]: 88501, 3 (ovirt-engine-metrics) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 06 Mar '18

06 Mar '18

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

1 0

[JIRA] (OVIRT-1861) Re: [ovirt-users] [ANN] oVirt 4.1.9 Release is now available
by sbonazzo (oVirt JIRA) 06 Mar '18

06 Mar '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1861?page=com.atlassian.jira.… ] sbonazzo updated OVIRT-1861: ---------------------------- Component/s: wiki (MediaWiki) > Re: [ovirt-users] [ANN] oVirt 4.1.9 Release is now available > ------------------------------------------------------------ > > Key: OVIRT-1861 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1861 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: wiki (MediaWiki) > Reporter: sbonazzo > Assignee: infra > > 2018-01-24 13:47 GMT+01:00 Arman Khalatyan <arm2arm(a)gmail.com>: > > Thanks for the announcement. > > A little comment: could you please fix the line yum install > > <http://resources.ovirt.org/pub/yum-repo/ovirt-release41.rpm > > <http://resources.ovirt.org/pub/yum-repo/ovirt-release41.rpm%3E> > > There is an extra '<' symbol there since 4.0.x :=) > > > > > Thanks for the feedback, I opened > https://github.com/oVirt/ovirt-site/issues/1503 to track this. > Opening a ticket on infra as well for further investigations. > > > > On Wed, Jan 24, 2018 at 12:00 PM, Lev Veyde <lveyde(a)redhat.com> wrote: > > > >> The oVirt Project is pleased to announce the availability of the oVirt > >> 4.1.9 release, as of January 24th, 2017 > >> > >> This update is the ninth in a series of stabilization updates to the 4.1 > >> series. > >> > >> Please note that no further updates will be issued for the 4.1 series. > >> We encourage users to upgrade to 4.2 series to receive new features and > >> updates. > >> > >> This release is available now for: > >> * Red Hat Enterprise Linux 7.4 or later > >> * CentOS Linux (or similar) 7.4 or later > >> > >> This release supports Hypervisor Hosts running: > >> * Red Hat Enterprise Linux 7.4 or later > >> * CentOS Linux (or similar) 7.4 or later > >> * oVirt Node 4.1 > >> > >> See the release notes [1] for installation / upgrade instructions and > >> a list of new features and bugs fixed. > >> > >> Notes: > >> - oVirt Appliance is already available > >> - oVirt Live is already available [2] > >> - oVirt Node will be available soon [2] > >> > >> Additional Resources: > >> * Read more about the oVirt 4.1.9 release highlights:http://www.ovirt.or > >> g/release/4.1.9/ > >> * Get more oVirt Project updates on Twitter: https://twitter.com/ovirt > >> * Check out the latest project news on the oVirt blog: > >> http://www.ovirt.org/blog/ > >> > >> [1] http://www.ovirt.org/release/4.1.9/ > >> [2] http://resources.ovirt.org/pub/ovirt-4.1/iso/ > >> > >> -- > >> > >> Lev Veyde > >> > >> Software Engineer, RHCE | RHCVA | MCITP > >> > >> Red Hat Israel > >> > >> <https://www.redhat.com> > >> > >> lev(a)redhat.com | lveyde(a)redhat.com > >> <https://red.ht/sig> > >> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> > >> > >> _______________________________________________ > >> Users mailing list > >> Users(a)ovirt.org > >> http://lists.ovirt.org/mailman/listinfo/users > >> > >> > > > > _______________________________________________ > > Users mailing list > > Users(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/users > > > > > -- > 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> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081)

1 0

[JIRA] (OVIRT-1861) Re: [ovirt-users] [ANN] oVirt 4.1.9 Release is now available
by sbonazzo (oVirt JIRA) 06 Mar '18

06 Mar '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1861?page=com.atlassian.jira.… ] sbonazzo updated OVIRT-1861: ---------------------------- Issue Type: Bug (was: By-EMAIL) > Re: [ovirt-users] [ANN] oVirt 4.1.9 Release is now available > ------------------------------------------------------------ > > Key: OVIRT-1861 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1861 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: sbonazzo > Assignee: infra > > 2018-01-24 13:47 GMT+01:00 Arman Khalatyan <arm2arm(a)gmail.com>: > > Thanks for the announcement. > > A little comment: could you please fix the line yum install > > <http://resources.ovirt.org/pub/yum-repo/ovirt-release41.rpm > > <http://resources.ovirt.org/pub/yum-repo/ovirt-release41.rpm%3E> > > There is an extra '<' symbol there since 4.0.x :=) > > > > > Thanks for the feedback, I opened > https://github.com/oVirt/ovirt-site/issues/1503 to track this. > Opening a ticket on infra as well for further investigations. > > > > On Wed, Jan 24, 2018 at 12:00 PM, Lev Veyde <lveyde(a)redhat.com> wrote: > > > >> The oVirt Project is pleased to announce the availability of the oVirt > >> 4.1.9 release, as of January 24th, 2017 > >> > >> This update is the ninth in a series of stabilization updates to the 4.1 > >> series. > >> > >> Please note that no further updates will be issued for the 4.1 series. > >> We encourage users to upgrade to 4.2 series to receive new features and > >> updates. > >> > >> This release is available now for: > >> * Red Hat Enterprise Linux 7.4 or later > >> * CentOS Linux (or similar) 7.4 or later > >> > >> This release supports Hypervisor Hosts running: > >> * Red Hat Enterprise Linux 7.4 or later > >> * CentOS Linux (or similar) 7.4 or later > >> * oVirt Node 4.1 > >> > >> See the release notes [1] for installation / upgrade instructions and > >> a list of new features and bugs fixed. > >> > >> Notes: > >> - oVirt Appliance is already available > >> - oVirt Live is already available [2] > >> - oVirt Node will be available soon [2] > >> > >> Additional Resources: > >> * Read more about the oVirt 4.1.9 release highlights:http://www.ovirt.or > >> g/release/4.1.9/ > >> * Get more oVirt Project updates on Twitter: https://twitter.com/ovirt > >> * Check out the latest project news on the oVirt blog: > >> http://www.ovirt.org/blog/ > >> > >> [1] http://www.ovirt.org/release/4.1.9/ > >> [2] http://resources.ovirt.org/pub/ovirt-4.1/iso/ > >> > >> -- > >> > >> Lev Veyde > >> > >> Software Engineer, RHCE | RHCVA | MCITP > >> > >> Red Hat Israel > >> > >> <https://www.redhat.com> > >> > >> lev(a)redhat.com | lveyde(a)redhat.com > >> <https://red.ht/sig> > >> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> > >> > >> _______________________________________________ > >> Users mailing list > >> Users(a)ovirt.org > >> http://lists.ovirt.org/mailman/listinfo/users > >> > >> > > > > _______________________________________________ > > Users mailing list > > Users(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/users > > > > > -- > 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> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081)

1 0

[JIRA] (OVIRT-1886) Add fcraw support for s390x and ppc64le
by sbonazzo (oVirt JIRA) 06 Mar '18

06 Mar '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1886?page=com.atlassian.jira.… ] sbonazzo updated OVIRT-1886: ---------------------------- Component/s: mock_runner CI Mirrors > Add fcraw support for s390x and ppc64le > --------------------------------------- > > Key: OVIRT-1886 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1886 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: CI Mirrors, mock_runner > Reporter: sbonazzo > Assignee: infra > > Hi, > pushed https://gerrit.ovirt.org/#/c/87068/ for adding support to fcraw for > s390x ad ppc64le but looks like it won't be enough, opening a ticket as > suggested by Barak. > -- > 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> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081)

1 0

[JIRA] (OVIRT-1886) Add fcraw support for s390x and ppc64le
by sbonazzo (oVirt JIRA) 06 Mar '18

06 Mar '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1886?page=com.atlassian.jira.… ] sbonazzo updated OVIRT-1886: ---------------------------- Issue Type: New Feature (was: By-EMAIL) > Add fcraw support for s390x and ppc64le > --------------------------------------- > > Key: OVIRT-1886 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1886 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: sbonazzo > Assignee: infra > > Hi, > pushed https://gerrit.ovirt.org/#/c/87068/ for adding support to fcraw for > s390x ad ppc64le but looks like it won't be enough, opening a ticket as > suggested by Barak. > -- > 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> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081)

1 0

[CQ]: 88487, 5 (ovirt-engine-metrics) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 06 Mar '18

06 Mar '18

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

1 0

[CQ]: 88480, 2 (ovirt-engine-metrics) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 06 Mar '18

06 Mar '18

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

1 0

[CQ]: 87990, 3 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 06 Mar '18

06 Mar '18

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

1 0

[CQ]: 88459, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 05 Mar '18

05 Mar '18

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

1 0

[CQ]: 88504,1 (ovirt-engine-metrics) failed "ovirt-4.2" system tests
by oVirt Jenkins 05 Mar '18

05 Mar '18

Change 88504,1 (ovirt-engine-metrics) 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/88504/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/1036/

1 0

[CQ]: 88038, 6 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 05 Mar '18

05 Mar '18

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

1 0

[CQ]: 88470, 3 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 05 Mar '18

05 Mar '18

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

1 0

hosted-engine ovirt-system-tests
by Yedidyah Bar David 05 Mar '18

05 Mar '18

Hi all, Recently I have been pushing various patches to OST in order to verify specific bugs/fixes I was working on, using them with the "manual" jenkins job but with no immediate intention to get them merged. Main reason is that it's not clear what's the best approach to get such tests merged. Do we want a new suite? How often does it run? How long does it take? Do we have enough resources? etc. Do we have plans re this? Bugs/tickets/etc.? Do we want to do something? Specifically, do we want (eventually) many more suites? This seems unmanageable. A few suites, perhaps (also) using lago snapshots? Didn't try that myself, might be useful and relevant. Some examples: https://gerrit.ovirt.org/79203 https://gerrit.ovirt.org/79215 https://gerrit.ovirt.org/84813 https://gerrit.ovirt.org/88201 https://gerrit.ovirt.org/88234 And current one - this and the next ones in the stack: https://gerrit.ovirt.org/88331 Best regards, -- Didi

3 3

[JIRA] (OVIRT-1916) ovirt site doesn't render/publish the latest blog post
by eyal edri (oVirt JIRA) 05 Mar '18

05 Mar '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1916?page=com.atlassian.jira.… ] eyal edri commented on OVIRT-1916: ---------------------------------- Can you please check? On Mon, Mar 5, 2018 at 4:25 PM, Roy Golan (oVirt JIRA) < -- Eyal edri MANAGER RHV DevOps EMEA VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ) > ovirt site doesn't render/publish the latest blog post > ------------------------------------------------------ > > Key: OVIRT-1916 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1916 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Roy Golan > Assignee: infra > > on March 4th this blog post was merged, but it is still not appearing under > Blogs. Please check what's wrongj > [1] https://github.com/oVirt/ovirt-site/pull/1529 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081)

1 0

[JIRA] (OVIRT-1916) ovirt site doesn't render/publish the latest blog post
by Roy Golan (oVirt JIRA) 05 Mar '18

05 Mar '18

Roy Golan created OVIRT-1916: -------------------------------- Summary: ovirt site doesn't render/publish the latest blog post Key: OVIRT-1916 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1916 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Roy Golan Assignee: infra on March 4th this blog post was merged, but it is still not appearing under Blogs. Please check what's wrongj [1] https://github.com/oVirt/ovirt-site/pull/1529 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081)

2 1

[CQ]: 88438, 3 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 05 Mar '18

05 Mar '18

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

1 0

[ OST Failure Report ] [ oVirt 4.2 (ovirt-engine) ] [ 05-03-2018 ] [ 006_migrations.migrate_vm ]
by Dafna Ron 05 Mar '18

05 Mar '18

Hi, We have a failure in OST on test 006_migrations.migrate_vm. >From what I can see, the migration succeeded but because there was a KeyError: 'cpuUsage' engine assume the v is down and tries to retry migration. the re-try fails with vm already exists. *Link and headline of suspected patches: *Failed change: *https://gerrit.ovirt.org/#/c/88432/2 <https://gerrit.ovirt.org/#/c/88432/2> - * *engine : Events coming too soon on refresh caps* *CQ reported this as root ca*use but I don't think its related as well: *https://gerrit.ovirt.org/#/c/88404/ <https://gerrit.ovirt.org/#/c/88404/> - * *core: Auto SD selection on template version update* *Link to Job:http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/1021/ <http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/1021/>Link to all logs:http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/1021/artifa… <http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/1021/artifact/>(Relevant) error snippet from the log: <error>* *migration starts and finishs *but fails on vm state on eyError: 'cpuUsage' *2018-03-05 05:21:33,269-0500 INFO (jsonrpc/3) [api.virt] START migrate(params={u'incomingLimit': 2, u'tunneled': u'false', u'dstqemu': u'192.0.3.2', u'autoConverge': u'false', u'src': u'lago-basic-suite-4-2-host-0', u'enableGuestEvents': False, u'dst': u'lago-basic-suite-4-2-host-1:54321', u'vmId': u'a80596a2-f57b-4878-adc3-772363e42783', u'abortOnError': u'true', u'outgoingLimit': 2, u'compressed': u'false', u'method': u'online'}) from=::ffff:192.168.200.2,42452, flow_id=123f5fd3-81a4-4ba9-9034-525674696629, vmId=a80596a2-f57b-4878-adc3-772363e42783 (api:46)2018-03-05 05:21:33,271-0500 INFO (jsonrpc/3) [api.virt] FINISH migrate return={'status': {'message': 'Migration in progress', 'code': 0}, 'progress': 0} from=::ffff:192.168.200.2,42452, flow_id=123f5fd3-81a4-4ba9-9034-525674696629, vmId=a80596a2-f57b-4878-adc3-772363e42783 (api:52)2018-03-05 05:21:33,271-0500 INFO (jsonrpc/3) [jsonrpc.JsonRpcServer] RPC call VM.migrate succeeded in 0.00 seconds (__init__:573)2018-03-05 05:21:33,473-0500 INFO (monitor/bd2f874) [IOProcessClient] Closing client ioprocess-0 (__init__:583)2018-03-05 05:21:34,936-0500 INFO (migsrc/a80596a2) [virt.vm] (vmId='a80596a2-f57b-4878-adc3-772363e42783') Creation of destination VM took: 1 seconds (migration:473)2018-03-05 05:21:34,936-0500 INFO (migsrc/a80596a2) [virt.vm] (vmId='a80596a2-f57b-4878-adc3-772363e42783') starting migration to qemu+tls://lago-basic-suite-4-2-host-1/system with miguri tcp://192.0.3.2 <http://192.0.3.2> (migration:502)2018-03-05 05:21:36,356-0500 INFO (jsonrpc/7) [api.host] START getAllVmStats() from=::ffff:192.168.200.2,42452 (api:46)2018-03-05 05:21:36,359-0500 INFO (jsonrpc/7) [api.host] FINISH getAllVmStats return={'status': {'message': 'Done', 'code': 0}, 'statsList': (suppressed)} from=::ffff:192.168.200.2,42452 (api:52)2018-03-05 05:21:36,361-0500 INFO (jsonrpc/7) [jsonrpc.JsonRpcServer] RPC call Host.getAllVmStats succeeded in 0.00 seconds (__init__:573)2018-03-05 05:21:38,861-0500 INFO (libvirt/events) [virt.vm] (vmId='a80596a2-f57b-4878-adc3-772363e42783') CPU stopped: onSuspend (vm:6063)2018-03-05 05:21:40,109-0500 WARN (periodic/0) [virt.periodic.VmDispatcher] could not run <class 'vdsm.virt.periodic.DriveWatermarkMonitor'> on ['a80596a2-f57b-4878-adc3-772363e42783'] (periodic:323)2018-03-05 05:21:40,109-0500 INFO (migsrc/a80596a2) [virt.vm] (vmId='a80596a2-f57b-4878-adc3-772363e42783') migration took 6 seconds to complete (migration:514)2018-03-05 05:21:40,110-0500 INFO (migsrc/a80596a2) [virt.vm] (vmId='a80596a2-f57b-4878-adc3-772363e42783') Changed state to Down: Migration succeeded (code=4) (vm:1677)2018-03-05 05:21:40,116-0500 INFO (migsrc/a80596a2) [virt.vm] (vmId='a80596a2-f57b-4878-adc3-772363e42783') Stopping connection (guestagent:438)2018-03-05 05:21:41,118-0500 WARN (periodic/3) [virt.periodic.VmDispatcher] could not run <class 'vdsm.virt.periodic.DriveWatermarkMonitor'> on ['a80596a2-f57b-4878-adc3-772363e42783'] (periodic:323)2018-03-05 05:21:42,063-0500 WARN (periodic/2) [virt.vmstats] Missing stat: 'balloon.current' for vm a80596a2-f57b-4878-adc3-772363e42783 (vmstats:552)2018-03-05 05:21:42,064-0500 ERROR (periodic/2) [virt.vmstats] VM metrics collection failed (vmstats:264)Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/virt/vmstats.py", line 197, in send_metrics data[prefix + '.cpu.usage'] = stat['cpuUsage']KeyError: 'cpuUsage'* *</error>*

1 0

[CQ]: 88323, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 05 Mar '18

05 Mar '18

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

1 0

[CQ]: 88432, 2 (ovirt-engine) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 05 Mar '18

05 Mar '18

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

1 0

please add leongold to ovirt-ansible-dpdk-setup github
by Irit Goihman 04 Mar '18

04 Mar '18

Please assign leongold as administrator in ovirt-ansible-dpdk-setup repo. -- IRIT GOIHMAN SOFTWARE ENGINEER EMEA VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> @redhatnews <https://twitter.com/redhatnews> Red Hat <https://www.linkedin.com/company/red-hat> Red Hat <https://www.facebook.com/RedHatInc>

2 1