- Devel - oVirt List Archives

[OST] Network suites fail CI builds
by Nir Soffer 17 Nov '20

17 Nov '20

I had many failures in recent OST patches, so I posted this change: https://gerrit.ovirt.org/c/112174/ This patch does not change anything, but it modifies the lago vm configuration so it triggers 8 jobs. 2 network test suites failed: https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-system-tests_sta… Can someone look at the network suite failures? If these suites are not stable, we should not included them in the CI for OST patches, or mark them as expected failures so they do not fail the build. I triggered another build since I see lot of random failures in other suites. Nir

4 6

expect OST failures on el8 for the next couple of hours
by Marcin Sobczyk 16 Nov '20

16 Nov '20

Hi all, while working on cleanup procedures for ost-images I accidentally removed the RPMs from the templates server. Not my day... I'm rebuilding them right now and will republish them ASAP, but you if you try running el8-based basic/networking suites you will probably end up with a failure. Hopefully when the cleanup patch is ready I will never have to do this manually again and will avoid mistakes like this in the future. Very sorry for the inconvenience. Regards, Marcin

1 0

bz 1875386 openssl conf files point at qemu-ca-certificate: status
by Yedidyah Bar David 15 Nov '20

15 Nov '20

Hi all, I now finished verifying my patches, currently pushed to github [1]. Verified clean engine-setup and engine-setup upgrade from current master. Didn't verify adding hosts nor encrypted migration between them, but I think it should work. With the top patch there, also verified pki-enroll-pkcs12.sh, which verifies also pki-enroll-request.sh, with both default and --ca-file=qemu-ca. Now: Currently, that's 16 patches. The entire stack diff ('git diff' from master) is 580 lines, whereas with the current split ('git log '--format=%h %s' -u' from master) it's 1045 lines (~ twice), but perhaps easier to follow, and shows my thought/refinement process, although probably many comments you might have on earlier patches I already addressed in later ones. I also do not think we must have all 16 patches add all the extra load on CI, so didn't yet push to gerrit. So I wonder if just to squash them to a single one, or something in between, both for review and for eventual merging. We definitely need all of them merged at once, or if we want to prevent breakage and still merge splitted, quite a lot more work (which I don't have time for). Comments are welcome. [1] https://github.com/didib/ovirt-engine/commits/qemu-ca-fixes Best regards, -- Didi

2 2

Re: [oVirt Jenkins] ovirt-system-tests_he-basic-suite-master - Build # 1818 - Failure!
by Yedidyah Bar David 15 Nov '20

15 Nov '20

On Sat, Nov 14, 2020 at 5:29 AM <jenkins(a)jenkins.phx.ovirt.org> wrote: > > Project: https://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-master/ > Build: https://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-master/1818/ https://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-master/1818… Error Message 'module' object has no attribute 'guest_os_image_name' Stacktrace Traceback (most recent call last): File "/usr/lib64/python2.7/unittest/case.py", line 369, in run testMethod() File "/usr/lib/python2.7/site-packages/nose/loader.py", line 418, in loadTestsFromName addr.filename, addr.module) File "/usr/lib/python2.7/site-packages/nose/importer.py", line 47, in importFromPath return self.importFromDir(dir_path, fqname) File "/usr/lib/python2.7/site-packages/nose/importer.py", line 94, in importFromDir mod = load_module(part_fqname, fh, filename, desc) File "/home/jenkins/agent/workspace/ovirt-system-tests_he-basic-suite-master/ovirt-system-tests/he-basic-suite-master/test-scenarios/002_bootstrap.py", line 88, in <module> GUEST_IMAGE_NAME = versioning.guest_os_image_name() AttributeError: 'module' object has no attribute 'guest_os_image_name' Seems to be caused by: https://gerrit.ovirt.org/112196 Can you please have a look? Thanks. Best regards, -- Didi

1 0

ovirt-engine has been tagged (ovirt-engine-4.4.3.12)
by Tal Nisan 13 Nov '20

13 Nov '20

2 1

Travis builds
by Vojtech Juranek 11 Nov '20

11 Nov '20

Hi, recently, I noticed Travis builds waits in the queue for a very long time. Looking around I found out Travis probably reduced resources for OSS projects. Also I found out all projects should migrate from travis-ci.org to travis- ci.com by end of December 2020 [1] (see Q. When will the migration from travis-ci.org to travis-ci.com be completed?). Recently they announce new pricing model [2] when OSS projects will get some initial credit and after that either has to pay or ask the support for another credit (see section "Building on a public repositories only" in [2]). Maybe time to migrate away from travis-ci to something else, e.g. GH Actions? Thoughts? Vojta [1] https://docs.travis-ci.com/user/migrate/open-source-repository-migration [2] https://blog.travis-ci.com/2020-11-02-travis-ci-new-billing

3 4

ovirt-engine has been tagged (ovirt-engine-4.4.4)
by Tal Nisan 11 Nov '20

11 Nov '20

1 0

[ANN] oVirt 4.4.3 is now generally available
by Sandro Bonazzola 10 Nov '20

10 Nov '20

oVirt 4.4.3 is now generally available The oVirt project is excited to announce the general availability of oVirt 4.4.3 , as of November 10th, 2020. This release unleashes an altogether more powerful and flexible open source virtualization solution that encompasses hundreds of individual changes and a wide range of enhancements across the engine, storage, network, user interface, and analytics, as compared to oVirt 4.3. Important notes before you install / upgrade Please note that oVirt 4.4 only supports clusters and data centers with compatibility version 4.2 and above. If clusters or data centers are running with an older compatibility version, you need to upgrade them to at least 4.2 (4.3 is recommended). Please note that in RHEL 8 / CentOS 8 several devices that worked on EL7 are no longer supported. For example, the megaraid_sas driver is removed. If you use Enterprise Linux 8 hosts you can try to provide the necessary drivers for the deprecated hardware using the DUD method (See the users’ mailing list thread on this at https://lists.ovirt.org/archives/list/users@ovirt.org/thread/NDSVUZSESOXEFJ… ) Documentation - If you want to try oVirt as quickly as possible, follow the instructions on the Download <https://ovirt.org/download/> page. - For complete installation, administration, and usage instructions, see the oVirt Documentation <https://ovirt.org/documentation/>. - For upgrading from a previous version, see the oVirt Upgrade Guide <https://ovirt.org/documentation/upgrade_guide/>. - For a general overview of oVirt, see About oVirt <https://ovirt.org/community/about.html>. What’s new in oVirt 4.4.3 Release? This update is the third in a series of stabilization updates to the 4.4 series. This release is available now on x86_64 architecture for: - Red Hat Enterprise Linux 8.2 / 8.3 - CentOS Linux (or similar) 8.2 - CentOS Stream (tech preview) This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: - Red Hat Enterprise Linux 8.2 / 8.3 - CentOS Linux (or similar) 8.2 - CentOS Stream (tech preview) Please note that this release introduces cluster compatibility level 4.5 which is supported only with Red Hat Enterprise Linux 8.3 or equivalent. oVirt Node and Appliance have been updated, including: - oVirt 4.4.3: https://www.ovirt.org/release/4.4.3/ - Ansible 2.9.15: https://github.com/ansible/ansible/blob/stable-2.9/changelogs/CHANGELOG-v2.… - Glusterfs 7.8: https://docs.gluster.org/en/latest/release-notes/7.8/ See the release notes [1] for installation instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is already available for CentOS Linux 8 - oVirt Node NG will be available soon for CentOS Linux 8 Additional resources: - Read more about the oVirt 4.4.3 release highlights: https://www.ovirt.org/release/4.4.3/ - 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] https://www.ovirt.org/release/4.4.3/ <https://www.ovirt.org/release/4.4.3/> [2] https://resources.ovirt.org/pub/ovirt-4.4/iso/ -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/> *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

1 0

Change compatibility level for data center/cluster during upgrade - what exactly are we changing?
by Patrick Chiang 10 Nov '20

10 Nov '20

Hi all, From the upgrade procedure, when we completed most upgrade tasks, we have to change the compatibility level in cluster and data center, and then restart all guest VM afterwards.It seems no down time expected with these 2 changes from the procedure. I wonder what exactly we are changing (a setting in the database/file??) and most important of all, whether there will be a few seconds down time when we made those changes to "data center"? Because I worried if a data center change could lead to storage domain's down time and eventually force hypervisors, guest VM restart before expected time. (My hosts/guest VM directly use HP 3par's storage as boot disks/data disks...) Hope anyone can share any experience on this. Thank you, Patrick Chiang

2 1

[OST] Network suites fails, 6+ days runtime?
by Nir Soffer 09 Nov '20

09 Nov '20

I have a trivial patch: https://gerrit.ovirt.org/c/112068 This should not have any effect on the network tests, but I ran the tests twice, and the network suite fails in both runs: - https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-system-tests_sta… - https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-system-tests_sta… The first run waited in the queue, 1 day 12 hours then ran for 11 hours. The second run waited in the queue for 2 days 21 hours and then ran for 19 hours. This is a total of 135 hours waiting for test results! Looks like we don't have the resources to test OST patches. The current way testing 8 suites for every patch is not workable. Can someone look at the network suite failure? Should we remove it from the test matrix? Nir

3 4