- Infra - oVirt List Archives

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

05 Dec '17

This is a multi-part message in MIME format... ------------=_1512491525-30467-260 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: --------------------------------------- Well that's where you lose me with the container. https://gerrit.ovirt.org/#/c/67166/12/basic-suite-master/test-scenarios/008… line 55 It uses python2-selenium from OST/nose, which connects to "geckodriver", which (roughly) connects to a locally-installed Firefox. The Firefox then opens an arbitrary URL. In our case, that's URL = 'https://192.168.201.4/ovirt-engine/webadmin' USERNAME = 'admin' PASSWORD = '123' > 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) ------------=_1512491525-30467-260 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>Well that's where you lose me with the container.</p> <p><a href="https://gerrit.ovirt.org/#/c/67166/12/basic-suite-master/test-scenarios/008…">https://gerrit.ovirt.org/#/c/67166/12/basic-suite-master/test-scenarios/008…</a> line 55</p> <p>It uses python2-selenium from OST/nose, which connects to “geckodriver”, which (roughly) connects to a locally-installed Firefox. The Firefox then opens an arbitrary URL. In our case, that's URL = '<a href="https://192.168.201.4/ovirt-engine/webadmin">https://192.168.201.4/ovirt-engine/webadmin</a>' USERNAME = ‘admin’ PASSWORD = ‘123’</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> ------------=_1512491525-30467-260--

1 0

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

05 Dec '17

This is a multi-part message in MIME format... ------------=_1512491211-28701-144 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] I can make the 1st one for you, making a CentOS container with firefox installed in it is easy enough, the real challenge for me would be how to make it run headless and talk to the testing framework and oVirt. What testing framework do you intend to use? How does it communicate with the browsers it uses for testing? Does it has built-in support to the situation where the browsers are running on different containers or hosts then the testing framework (Processes in different containers typically look to one another as if they are on different hosts)? > 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) ------------=_1512491211-28701-144 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] I can make the 1st one for you, making a CentOS container with firefox installed in it is easy enough, the real challenge for me would be how to make it run headless and talk to the testing framework and oVirt.</p> <p>What testing framework do you intend to use? How does it communicate with the browsers it uses for testing? Does it has built-in support to the situation where the browsers are running on different containers or hosts then the testing framework (Processes in different containers typically look to one another as if they are on different hosts)?</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> ------------=_1512491211-28701-144--

1 0

[JIRA] (OVIRT-1794) VM in PHX failed to migrate due to qemu bug
by Evgheni Dereveanchin (oVirt JIRA) 05 Dec '17

05 Dec '17

This is a multi-part message in MIME format... ------------=_1512485902-15750-115 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1794?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-1794: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > VM in PHX failed to migrate due to qemu bug > ------------------------------------------- > > Key: OVIRT-1794 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1794 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > Priority: Low > > While upgrading from 4.1.7 to 4.2-pre I experienced an issue with shift-n03 failing to migrate with error on receiving side: > 2017-12-05T14:24:53.090422Z qemu-kvm: warning: All CPU(s) up to maxcpus should be described in NUMA config > 2017-12-05T14:29:41.430448Z qemu-kvm: Unknown combination of migration flags: 0 > 2017-12-05T14:29:41.431120Z qemu-kvm: error while loading state section id 3(ram) > 2017-12-05T14:29:41.432665Z qemu-kvm: load of migration failed: Invalid argument > 2017-12-05 14:29:42.271+0000: shutting down, reason=crashed > Will shut down the VM to proceed with the upgrade but if this happens again we may need to investigate further -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100074) ------------=_1512485902-15750-115 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1794?page=com.atlassian.jira.… ]</pre> <h3>Evgheni Dereveanchin reassigned OVIRT-1794:</h3> <pre>Assignee: Evgheni Dereveanchin (was: infra)</pre> <blockquote><h3>VM in PHX failed to migrate due to qemu bug</h3> <pre> Key: OVIRT-1794 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1794 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Evgheni Dereveanchin Assignee: Evgheni Dereveanchin Priority: Low</pre> <p>While upgrading from 4.1.7 to 4.2-pre I experienced an issue with shift-n03 failing to migrate with error on receiving side: 2017-12-05T14:24:53.090422Z qemu-kvm: warning: All CPU(s) up to maxcpus should be described in NUMA config 2017-12-05T14:29:41.430448Z qemu-kvm: Unknown combination of migration flags: 0 2017-12-05T14:29:41.431120Z qemu-kvm: error while loading state section id 3(ram) 2017-12-05T14:29:41.432665Z qemu-kvm: load of migration failed: Invalid argument 2017-12-05 14:29:42.271+0000: shutting down, reason=crashed Will shut down the VM to proceed with the upgrade but if this happens again we may need to investigate further</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> ------------=_1512485902-15750-115--

1 0

[JIRA] (OVIRT-1794) VM in PHX failed to migrate due to qemu bug
by Evgheni Dereveanchin (oVirt JIRA) 05 Dec '17

05 Dec '17

This is a multi-part message in MIME format... ------------=_1512485897-25186-247 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Evgheni Dereveanchin created OVIRT-1794: ------------------------------------------- Summary: VM in PHX failed to migrate due to qemu bug Key: OVIRT-1794 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1794 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Evgheni Dereveanchin Assignee: infra Priority: Low While upgrading from 4.1.7 to 4.2-pre I experienced an issue with shift-n03 failing to migrate with error on receiving side: 2017-12-05T14:24:53.090422Z qemu-kvm: warning: All CPU(s) up to maxcpus should be described in NUMA config 2017-12-05T14:29:41.430448Z qemu-kvm: Unknown combination of migration flags: 0 2017-12-05T14:29:41.431120Z qemu-kvm: error while loading state section id 3(ram) 2017-12-05T14:29:41.432665Z qemu-kvm: load of migration failed: Invalid argument 2017-12-05 14:29:42.271+0000: shutting down, reason=crashed Will shut down the VM to proceed with the upgrade but if this happens again we may need to investigate further -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100074) ------------=_1512485897-25186-247 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <h3>Evgheni Dereveanchin created OVIRT-1794:</h3> <pre> Summary: VM in PHX failed to migrate due to qemu bug Key: OVIRT-1794 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1794 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Evgheni Dereveanchin Assignee: infra Priority: Low</pre> <p>While upgrading from 4.1.7 to 4.2-pre I experienced an issue with shift-n03 failing to migrate with error on receiving side:</p> <p>2017-12-05T14:24:53.090422Z qemu-kvm: warning: All CPU(s) up to maxcpus should be described in NUMA config 2017-12-05T14:29:41.430448Z qemu-kvm: Unknown combination of migration flags: 0 2017-12-05T14:29:41.431120Z qemu-kvm: error while loading state section id 3(ram) 2017-12-05T14:29:41.432665Z qemu-kvm: load of migration failed: Invalid argument 2017-12-05 14:29:42.271+0000: shutting down, reason=crashed</p> <p>Will shut down the VM to proceed with the upgrade but if this happens again we may need to investigate further</p> <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> ------------=_1512485897-25186-247--

1 0

[CQ]: 85091,1 (ovirt-engine-sdk) failed "ovirt-master" system tests
by oVirt Jenkins 05 Dec '17

05 Dec '17

Change 85091,1 (ovirt-engine-sdk) 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/85091/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4288/

1 0

[JIRA] (OVIRT-1793) PHX repo mirror inconsistent
by Daniel Belenky (oVirt JIRA) 05 Dec '17

05 Dec '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1793?page=com.atlassian.jira.… ] Daniel Belenky commented on OVIRT-1793: --------------------------------------- That's probably because I've performed cleanup in the mirrors server... I'm running the sync jobs now > 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: infra > > 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-1793) PHX repo mirror inconsistent
by Evgheni Dereveanchin (oVirt JIRA) 05 Dec '17

05 Dec '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1793?page=com.atlassian.jira.… ] Evgheni Dereveanchin updated OVIRT-1793: ---------------------------------------- Issue Type: Bug (was: Task) > 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: infra > > 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-1793) PHX repo mirror inconsistent
by Evgheni Dereveanchin (oVirt JIRA) 05 Dec '17

05 Dec '17

Evgheni Dereveanchin created OVIRT-1793: ------------------------------------------- Summary: PHX repo mirror inconsistent Key: OVIRT-1793 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1793 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Evgheni Dereveanchin Assignee: infra 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

[CQ]: 85067, 3 (ovirt-imageio) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 05 Dec '17

05 Dec '17

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

1 0

[CQ]: 85049,2 (ovirt-imageio) failed "ovirt-master" system tests
by oVirt Jenkins 05 Dec '17

05 Dec '17

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

1 0