- Infra - oVirt List Archives

[oVirt Jenkins] ovirt-appliance_ovirt-4.1-snapshot_build-artifacts-el7-x86_64 - Build # 364 - Failure!
by jenkins＠jenkins.phx.ovirt.org 06 Dec '17

06 Dec '17

------=_Part_278_1610545235.1512485606319 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.1-snapshot_build-artif… Build: http://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.1-snapshot_build-artif… Build Number: 364 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #364 [Daniel Belenky] Added germano(a)redhat.com to whitelist [Gal Ben Haim] kubevirt-ansible: Adding github pipeline [Martin Sivak] Cleanup the job for ovirt-optimizer [Yuval Turgeman] automation: view install log in console ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_278_1610545235.1512485606319--

1 1

[JIRA] (OVIRT-1795) add /tmp engine logs to be collected in ost
by Dafna Ron (oVirt JIRA) 06 Dec '17

06 Dec '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1795?page=com.atlassian.jira.… ] Dafna Ron reassigned OVIRT-1795: -------------------------------- Assignee: Dafna Ron (was: infra) > add /tmp engine logs to be collected in ost > ------------------------------------------- > > Key: OVIRT-1795 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1795 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: Dafna Ron > > when engine fails to be deployed and there is nothing written in the engine log it would make debugging easier if we also collect the tmp logs created by engine, -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100074)

1 0

[JIRA] (OVIRT-1795) add /tmp engine logs to be collected in ost
by Dafna Ron (oVirt JIRA) 06 Dec '17

06 Dec '17

Dafna Ron created OVIRT-1795: -------------------------------- Summary: add /tmp engine logs to be collected in ost Key: OVIRT-1795 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1795 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Dafna Ron Assignee: infra when engine fails to be deployed and there is nothing written in the engine log it would make debugging easier if we also collect the tmp logs created by engine, -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100074)

1 0

Default assignee for bugzilla component
by Sahina Bose 06 Dec '17

06 Dec '17

Hi! Could you change the default assignee on Product: cockpit-ovirt Component:gdeploy to godas(a)redhat.com? thanks sahina

3 3

[JIRA] (OVIRT-1788) new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium
by Daniel Belenky (oVirt JIRA) 06 Dec '17

06 Dec '17

This is a multi-part message in MIME format... ------------=_1512572024-12025-143 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1788?page=com.atlassian.jira.… ] Daniel Belenky commented on OVIRT-1788: --------------------------------------- [~gshereme(a)redhat.com] I'll be happy to assist with that > new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium > ------------------------------------------------------------------------------ > > Key: OVIRT-1788 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1788 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: OST > Reporter: Greg Sheremeta > Assignee: infra > > I'm writing a suite that does headless UI testing. One goal is to open headless firefox and actually open the UI, perform a login, make sure things look good, make sure there are no ui.log errors, etc. I'll also eventually add chromium, which can run headless now too. > The suite requires several firefox versions to be installed on the test machine, along with chromium. There are also some binary components required, geckodriver and chromedriver. These are not packaged. > Ideally the browsers can be installed to /opt/firefox55, /opt/firefox56, /opt/chromium62, etc. on the machine running the suite. So I think it makes sense to maintain a custom rpm with all of this. > Where can this rpm live? What is a reliable way to do this? (I know we want to avoid copr.) -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100074) ------------=_1512572024-12025-143 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1788?page=com.atlassian.jira.… ]</pre> <h3>Daniel Belenky commented on OVIRT-1788:</h3> <p>[~gshereme(a)redhat.com] I'll be happy to assist with that</p> <blockquote><h3>new ui_sanity scenario for basic_suite — need multiple firefoxes and chromium</h3> <pre> Key: OVIRT-1788 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1788 Project: oVirt - virtualization made easy Issue Type: Improvement Components: OST Reporter: Greg Sheremeta Assignee: infra</pre> <p>I'm writing a suite that does headless UI testing. One goal is to open headless firefox and actually open the UI, perform a login, make sure things look good, make sure there are no ui.log errors, etc. I'll also eventually add chromium, which can run headless now too. The suite requires several firefox versions to be installed on the test machine, along with chromium. There are also some binary components required, geckodriver and chromedriver. These are not packaged. Ideally the browsers can be installed to /opt/firefox55, /opt/firefox56, /opt/chromium62, etc. on the machine running the suite. So I think it makes sense to maintain a custom rpm with all of this. Where can this rpm live? What is a reliable way to do this? (I know we want to avoid copr.)</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100074)</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> ------------=_1512572024-12025-143--

1 0

[CQ]: 85136,3 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 06 Dec '17

06 Dec '17

Change 85136,3 (ovirt-engine) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/85136/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4313/

1 0

[JIRA] (OVIRT-1788) new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium
by Greg Sheremeta (oVirt JIRA) 06 Dec '17

06 Dec '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1788?page=com.atlassian.jira.… ] Greg Sheremeta commented on OVIRT-1788: --------------------------------------- Ok -- I'll need your assistance setting it up. I have no idea how to pull them, start them, or cache them :) > new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium > ------------------------------------------------------------------------------ > > Key: OVIRT-1788 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1788 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: OST > Reporter: Greg Sheremeta > Assignee: infra > > I'm writing a suite that does headless UI testing. One goal is to open headless firefox and actually open the UI, perform a login, make sure things look good, make sure there are no ui.log errors, etc. I'll also eventually add chromium, which can run headless now too. > The suite requires several firefox versions to be installed on the test machine, along with chromium. There are also some binary components required, geckodriver and chromedriver. These are not packaged. > Ideally the browsers can be installed to /opt/firefox55, /opt/firefox56, /opt/chromium62, etc. on the machine running the suite. So I think it makes sense to maintain a custom rpm with all of this. > Where can this rpm live? What is a reliable way to do this? (I know we want to avoid copr.) -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100074)

1 0

[JIRA] (OVIRT-1788) new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium
by Barak Korren (oVirt JIRA) 06 Dec '17

06 Dec '17

This is a multi-part message in MIME format... ------------=_1512568585-25653-223 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1788?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1788: ------------------------------------- [~gshereme(a)redhat.com] awesome! so we don`t need to make our own, just use theirs and make sure they are cached properly between runs... > new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium > ------------------------------------------------------------------------------ > > Key: OVIRT-1788 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1788 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: OST > Reporter: Greg Sheremeta > Assignee: infra > > I'm writing a suite that does headless UI testing. One goal is to open headless firefox and actually open the UI, perform a login, make sure things look good, make sure there are no ui.log errors, etc. I'll also eventually add chromium, which can run headless now too. > The suite requires several firefox versions to be installed on the test machine, along with chromium. There are also some binary components required, geckodriver and chromedriver. These are not packaged. > Ideally the browsers can be installed to /opt/firefox55, /opt/firefox56, /opt/chromium62, etc. on the machine running the suite. So I think it makes sense to maintain a custom rpm with all of this. > Where can this rpm live? What is a reliable way to do this? (I know we want to avoid copr.) -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100074) ------------=_1512568585-25653-223 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1788?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren commented on OVIRT-1788:</h3> <p>[~gshereme(a)redhat.com] awesome! so we don`t need to make our own, just use theirs and make sure they are cached properly between runs…</p> <blockquote><h3>new ui_sanity scenario for basic_suite — need multiple firefoxes and chromium</h3> <pre> Key: OVIRT-1788 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1788 Project: oVirt - virtualization made easy Issue Type: Improvement Components: OST Reporter: Greg Sheremeta Assignee: infra</pre> <p>I'm writing a suite that does headless UI testing. One goal is to open headless firefox and actually open the UI, perform a login, make sure things look good, make sure there are no ui.log errors, etc. I'll also eventually add chromium, which can run headless now too. The suite requires several firefox versions to be installed on the test machine, along with chromium. There are also some binary components required, geckodriver and chromedriver. These are not packaged. Ideally the browsers can be installed to /opt/firefox55, /opt/firefox56, /opt/chromium62, etc. on the machine running the suite. So I think it makes sense to maintain a custom rpm with all of this. Where can this rpm live? What is a reliable way to do this? (I know we want to avoid copr.)</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100074)</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> ------------=_1512568585-25653-223--

1 0

[JIRA] (OVIRT-1793) PHX repo mirror inconsistent
by Evgheni Dereveanchin (oVirt JIRA) 06 Dec '17

06 Dec '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1793?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-1793: ------------------------------------------- Assignee: Daniel Belenky (was: infra) > PHX repo mirror inconsistent > ---------------------------- > > Key: OVIRT-1793 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1793 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Evgheni Dereveanchin > Assignee: Daniel Belenky > > The [infra-docs_master_check-merged-el7-x86_64|http://jenkins.ovirt.org/job/infr…] job failed due to a missing RPM on the mirror that is present in the index: > 12:13:44 http://mirrors.phx.ovirt.org/repos/yum/epel-el7/base/f/fontawesome-fonts-4.…: [Errno 14] HTTP Error 404 - Not Found > We may need to fix this mirror or disable it for this job if this package is filtered out to conserve disk space. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100074)

1 0

[JIRA] (OVIRT-1788) new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium
by Greg Sheremeta (oVirt JIRA) 06 Dec '17

06 Dec '17

This is a multi-part message in MIME format... ------------=_1512558689-17283-163 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1788?page=com.atlassian.jira.… ] Greg Sheremeta commented on OVIRT-1788: --------------------------------------- They provide containers already: https://github.com/SeleniumHQ/docker-selenium Can we use those somehow? > new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium > ------------------------------------------------------------------------------ > > Key: OVIRT-1788 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1788 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: OST > Reporter: Greg Sheremeta > Assignee: infra > > I'm writing a suite that does headless UI testing. One goal is to open headless firefox and actually open the UI, perform a login, make sure things look good, make sure there are no ui.log errors, etc. I'll also eventually add chromium, which can run headless now too. > The suite requires several firefox versions to be installed on the test machine, along with chromium. There are also some binary components required, geckodriver and chromedriver. These are not packaged. > Ideally the browsers can be installed to /opt/firefox55, /opt/firefox56, /opt/chromium62, etc. on the machine running the suite. So I think it makes sense to maintain a custom rpm with all of this. > Where can this rpm live? What is a reliable way to do this? (I know we want to avoid copr.) -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100074) ------------=_1512558689-17283-163 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1788?page=com.atlassian.jira.… ]</pre> <h3>Greg Sheremeta commented on OVIRT-1788:</h3> <p>They provide containers already: <a href="https://github.com/SeleniumHQ/docker-selenium">https://github.com/SeleniumHQ/docker-selenium</a></p> <p>Can we use those somehow?</p> <blockquote><h3>new ui_sanity scenario for basic_suite — need multiple firefoxes and chromium</h3> <pre> Key: OVIRT-1788 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1788 Project: oVirt - virtualization made easy Issue Type: Improvement Components: OST Reporter: Greg Sheremeta Assignee: infra</pre> <p>I'm writing a suite that does headless UI testing. One goal is to open headless firefox and actually open the UI, perform a login, make sure things look good, make sure there are no ui.log errors, etc. I'll also eventually add chromium, which can run headless now too. The suite requires several firefox versions to be installed on the test machine, along with chromium. There are also some binary components required, geckodriver and chromedriver. These are not packaged. Ideally the browsers can be installed to /opt/firefox55, /opt/firefox56, /opt/chromium62, etc. on the machine running the suite. So I think it makes sense to maintain a custom rpm with all of this. Where can this rpm live? What is a reliable way to do this? (I know we want to avoid copr.)</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100074)</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> ------------=_1512558689-17283-163--

1 0