- Devel - oVirt List Archives

[Announcement] Introducing Standard CI build summary
by Daniel Belenky 31 May '18

31 May '18

Hi, On behalf of oVirt's CI team, I'm happy to announce the STDCI build summary - *We've used patternfly *[1] <http://www.patternfly.org/> to ensure a clean, simple and elegant view of information for your builds. The summary is available for STDCI V2 [2] projects and it is located under *build-artifacts/ci_build_summary.html* *[image: location.png]* STDCI build summary is a single web page, generated dynamically for every build on STDCI. It visualizes all CI threads that ran for that build and features a set of quick links. The main view shows a list of all threads with an indicator if that thread failed or passed. The quick links to the right of each thread lead to *log* and *artifacts* of that thread only. Note that *log* shows the output of your script only to ease debugging. [image: threads_list.png] At the top right side, you will find a set of quick links for convenience: [image: menus.png] *Test results* (available if JUnit XML files were exported during the build) leads to a summary of all JUnit test results that were collected during the build. *Test results analyzer *shows the history of test execution results in a tabular format. *Findbugs results *(available if Findbugs report was generated and exported during the build) shows trend report for Findbugs. *Full build log* shows the full log of all threads. This log is harder to understand as it includes output from CI runtime environment as well as from your scripts. *Rebuild (for GitHub PR)/Retrigger (for Gerrit patch): *Run the build again. The new build will report and vote to Gerrit/GitHub with the new result. *View PR/patch: *Links back to the PR on GitHub or patchset page in Gerrit. [image: view_in_jenkins.png] *View in Jenkins* will lead you back to the build view in Jenkins [image: view_in_blueocean.png] *View in Blue Ocean *will lead you to the build view in Jenkins Blue Ocean view STDCI Documentation https://ovirt-infra-docs.readthedocs.io/en/latest/CI/Build_and_test_standar… For any questions, don't hesitate to contact the CI team at #rhev-integ, #rhev-dev or view mail at infra(a)ovirt.org. Thanks, Daniel.

2 1

CI not responding to GitHub web hooks
by Tomáš Golembiovský 31 May '18

31 May '18

Hi, it seems CI is not responding to GitHub web hooks... is it congested or broken? Tomas -- Tomáš Golembiovský <tgolembi(a)redhat.com>

2 1

[ OST Failure Report ] [ oVirt master ] [ 2018-05-25 ] [AddHost]
by Barak Korren 30 May '18

30 May '18

Test failed: [ AddHost (in upgrade-from-release-suite) ] Link to suspected patches: https://gerrit.ovirt.org/#/c/91445/5 - Disable TLS versions < 1.2 for hosts with cluster level>=4.1 Link to Job: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7776/ Link to all logs: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7776/artifact… Error snippet from log: From nosetst log: <error> AssertionError: False != True after 1200 seconds </error> Not finding a host deploy log in /var/log/ovirt-engine for some reason. This seems to have cause consistent failure in all other engine patches that followed it. -- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted

7 24

Travis failure on ovirt-engine
by Sandro Bonazzola 30 May '18

30 May '18

Hi, now that travis is correctly using postresql 9.5, it fails on: ERROR: function uuid_generate_v1() does not exist looking at the spec file, I think we miss postgresql-contrib (or it's equivalent) within the test environment. Roman, can you help with this? -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig> <https://redhat.com/summit>

1 1

unboundid-ldapsdk-4.0.6 is now available for testing
by Sandro Bonazzola 30 May '18

30 May '18

On Fedora we had previously 4.0.5. The new releases 4.0.6 will be soon available in updates-testing repository for Fedora >= 27 and includes several bug fixes and a few enhancements. You can see release notes here: https://github.com/ pingidentity/ldapsdk/releases In oVirt this package is required by ovirt-engine-extension-aaa-ldap. If you're going to test the package, please provide karma: Fedora 28: https://bodhi.fedoraproject.org/updates/FEDORA-2018-733f231fd4 Fedora 27: https://bodhi.fedoraproject.org/updates/FEDORA-2018-18d425fcdd Thanks, -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig> <https://redhat.com/summit>

1 1

Does ovirt engine itself support high scalability
by simiam 30 May '18

30 May '18

Hi, Does ovirt engine itself support high scalability? Thanks.

2 2

UI validation testing in ovirt-system-tests
by Greg Sheremeta 29 May '18

29 May '18

Hi, I added some basic UI validation testing to ovirt-system-tests [1]. Now when ovirt-engine patches are merged, OST will verify that the webadmin UI loads and renders. It currently verifies on both Chrome and Firefox and takes screenshots (example: [2]). We decided to start with the basics -- only login and a few simple navigation verification, with no assertions. Patches are most welcome since I need to move on to other tasks. Known needs: - add an assertion that ui.log remains empty while browsing - web-ui tests - assertions that things look decent Best wishes, Greg [1] https://gerrit.ovirt.org/#/c/67166/ Use a headless browser to perform basic UI sanity tests -- verify the UI loads, we can login, the UI renders correctly, navigation works, etc. [2] https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7829/artifac… (URL expires, screenshot below) Example from the test: -- GREG SHEREMETA SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX Red Hat NA <https://www.redhat.com/> gshereme(a)redhat.com IRC: gshereme <https://red.ht/sig>

1 0

[ OST Failure Report ] [ oVirt master ] [ 2018-05-28 ] [004_basic_sanity.disk_operations]
by Barak Korren 28 May '18

28 May '18

Test failed: [ 004_basic_sanity.disk_operations <http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7811/testRepo…> ] Link to suspected patches: https://gerrit.ovirt.org/#/c/91068/4 Link to Job: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7811/ Link to all logs: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7811/artifact… Error snippet from log: <error> Note: There is another ongoing regression in engine master ATM, but this issue is causing a different suit to fail so it was luckily not masked by it. False != True after 600 seconds -------------------- >> begin captured logging << -------------------- lago.utils: ERROR: Error while running thread Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/lago/utils.py", line 58, in _ret_via_queue queue.put({'return': func()}) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 59, in wrapper return func(get_test_prefix(), *args, **kwargs) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 78, in wrapper prefix.virt_env.engine_vm().get_api(api_ver=4), *args, **kwargs File "/home/jenkins/workspace/ovirt-master_change-queue-tester/ovirt-system-tests/basic-suite-master/test-scenarios/004_basic_sanity.py", line 528, in cold_storage_migration lambda: api.follow_link( File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 271, in assert_true_within_long assert_equals_within_long(func, True, allowed_exceptions) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 258, in assert_equals_within_long func, value, LONG_TIMEOUT, allowed_exceptions=allowed_exceptions File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 237, in assert_equals_within '%s != %s after %s seconds' % (res, value, timeout) AssertionError: False != True after 600 seconds --------------------- >> end captured logging << --------------------- </error> -- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted

2 2

Does ovirt engine itself support high scalability
by simiam 28 May '18

28 May '18

Hi, Does ovirt engine itself support high scalability? Thanks.

1 0

CVE-2018-3639 - Important - oVirt - Speculative Store Bypass
by Sandro Bonazzola 25 May '18

25 May '18

As you may have already heard, an industry-wide issue was found in the way many modern microprocessor designs have implemented speculative execution of Load & Store instructions. This issue is well described by CVE-2018-3639 announce available at https://access.redhat.com/security/cve/cve-2018-3639. oVirt team has released right now an update of ovirt-engine to version 4.2.3.7 which add support for SSBD CPUs in order to mitigate the security issue. If you are running oVirt on Red Hat Enterprise Linux, please apply updates described in https://access.redhat.com/security/cve/cve-2018-3639. If you are running oVirt on CentOS Linux please apply updated described by: CESA-2018:1629 Important CentOS 7 kernel Security Update <https://lists.centos.org/pipermail/centos-announce/2018-May/022843.html> CESA-2018:1632 Important CentOS 7 libvirt Security Update <https://lists.centos.org/pipermail/centos-announce/2018-May/022840.html> CESA-2018:1649 Important CentOS 7 java-1.8.0-openjdk Security Update <https://lists.centos.org/pipermail/centos-announce/2018-May/022839.html> CESA-2018:1648 Important CentOS 7 java-1.7.0-openjdk Security Update <https://lists.centos.org/pipermail/centos-announce/2018-May/022838.html> An update for qemu-kvm-ev has been also tagged for release and announced with CESA-2018:1655 Important: qemu-kvm-ev security update <https://lists.centos.org/pipermail/centos-virt/2018-May/005804.html> but due to some issues in CentOS release process for Virt SIG content, it is not yet available on mirrors. We are working with CentOS community to get the packages signed and published as soon as possible. In the meanwhile you can still get the update package by enabling the test repository https://buildlogs.centos.org/centos/7/virt/x86_64/kvm-common/ on your systems or manually installing the package from the repository. If you're running oVirt on a different Linux distribution, please check with your vendor for available updates. Please note that to fully mitigate this vulnerability, system administrators must apply both hardware “microcode” updates and software patches that enable new functionality. At this time, microprocessor microcode will be delivered by the individual manufacturers. The oVirt team recommends end users and systems administrator to apply any available updates as soon as practical. Thanks, -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig> <https://redhat.com/summit>

1 1