- Devel - oVirt List Archives

CI OST UI fails: Fixture "save_page_source" called directly
by Yedidyah Bar David 08 May '20

08 May '20

Hi all, See e.g.: https://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-test… https://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-test… Fixture "save_page_source" called directly. Fixtures are not meant to be called directly, but are created automatically when test functions request them as parameters. See https://docs.pytest.org/en/latest/fixture.html for more information about fixtures, and https://docs.pytest.org/en/latest/deprecations.html#calling-fixtures-direct… about how to update your code. Known issue? Thanks, -- Didi

3 2

uplaod_disk/download_disk possible breakage - you need now ovirt-imgaeio-client
by Nir Soffer 07 May '20

07 May '20

We merged imageio patch changing the package structure. Unfortunately this change is not backward compatible and breaks older versions of upload_disk.py, download_disk.py, and backup_vm.py from ovirt-engine-sdk. If you try to upload or download disks using the SDK and upload fail with: $ ./upload_disk.py -h Traceback (most recent call last): File "./upload_disk.py", line 44, in <module> from ovirt_imageio import ui ImportError: cannot import name 'ui' from 'ovirt_imageio' (/usr/lib64/python3.7/site-packages/ovirt_imageio/__init__.py) You need to install ovirt-imageio-package: sudo dnf install ovirt-imageio-client and use this patch: https://gerrit.ovirt.org/c/108840/ If you cannot find ovirt-imageio-client, you are need to install ovirt-release-master.rpm: sudo dnf install https://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm Nir

1 0

Yahoo & DMARC - @list admins
by lejeczek 07 May '20

07 May '20

hi everyone Maintainers/Admins - could you guys please fix DMARC so those Yahoo Mail users, such as me, would get their own emails. Yahoo(maybe other well know providers) changed theirs policies some longer time ago and as of today (probably for longer time only that nobody minded, or... it's just me on Yahoo's mail??) own emails go to a black hole. Number of mailing lists, including Redhat's ones, got this fixed some time ago. many thanks, L.

3 2

oVirt 4.4.0 First Release Candidate is now available for testing!
by Sandro Bonazzola 07 May '20

07 May '20

The oVirt Project is excited to announce the availability of the first Release Candidate of oVirt 4.4.0 for testing, as of May 6th, 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 on top of oVirt 4.3. Important notes before you try it Please note this is a pre-release build. The oVirt Project makes no guarantees as to its suitability or usefulness. This pre-release must not to be used in production. Some of the features included in oVirt 4.4.0 Release Candidate require content that will be available in CentOS Linux 8.2 but can’t be tested on RHEL 8.2 beta yet due to some incompatibility in openvswitch package shipped in CentOS Virt SIG which requires to rebuild openvswitch on top of CentOS 8.2. Installation instructions For the engine: either use appliance or: - Install CentOS Linux 8 minimal from http://centos.mirror.garr.it/centos/8.1.1911/isos/x86_64/CentOS-8.1.1911-x8… - dnf install https://resources.ovirt.org/pub/yum-repo/ovirt-release44-pre.rpm - dnf update (reboot if needed) - dnf module enable -y javapackages-tools pki-deps postgresql:12 - dnf install ovirt-engine - engine-setup For the nodes: Either use oVirt Node ISO or: - Install CentOS Linux 8 from http://centos.mirror.garr.it/centos/8.1.1911/isos/x86_64/CentOS-8.1.1911-x8… ; select minimal installation - dnf install https://resources.ovirt.org/pub/yum-repo/ovirt-release44-pre.rpm - dnf update (reboot if needed) - Attach the host to engine and let it be deployed. What’s new in oVirt 4.4.0 Release Candidate? - Hypervisors based on CentOS Linux 8 (rebuilt from award winning RHEL8), for both oVirt Node and standalone CentOS Linux hosts - Easier network management and configuration flexibility with NetworkManager - VMs based on a more modern Q35 chipset with legacy seabios and UEFI firmware - Support for direct passthrough of local host disks to VMs - Live migration improvements for High Performance guests. - New Windows Guest tools installer based on WiX framework now moved to VirtioWin project - Dropped support for cluster level prior to 4.2 - Dropped SDK3 support - 4K disks support only for file based storage. iSCSI/FC storage do not support 4k disks yet. - Exporting a VM to a data domain - Editing of floating disks - Integrating ansible-runner into engine, which allows a more detailed monitoring of playbooks executed from engine - Adding/reinstalling hosts are now completely based on Ansible - The OpenStack Neutron Agent cannot be configured by oVirt anymore, it should be configured by TripleO instead This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 8.1 * CentOS Linux (or similar) 8.1 This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 8.1 * CentOS Linux (or similar) 8.1 * oVirt Node 4.4 based on CentOS Linux 8.1 (available for x86_64 only) See the release notes [1] for installation instructions and a list of new features and bugs fixed. If you manage more than one oVirt instance, OKD or RDO we also recommend to try ManageIQ <http://manageiq.org/>. In such a case, please be sure to take the qc2 image and not the ova image. Notes: - oVirt Appliance is already available for CentOS Linux 8 - oVirt Node NG is already available for CentOS Linux 8 Additional Resources: * Read more about the oVirt 4.4.0 release highlights: http://www.ovirt.org/release/4.4.0/ * 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.4.0/ [2] http://resources.ovirt.org/pub/ovirt-4.4-pre/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/> [image: |Our code is open_] <https://www.redhat.com/en/our-code-is-open> *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

1 0

Contribution opportunity: oVirt website links maintenance
by Sandro Bonazzola 06 May '20

06 May '20

Hi, oVirt website accumulated a good amount of broken links over the years. You can see them listed in this etherpad: https://review.rdoproject.org/etherpad/p/SLEq1-6FwW9aw7344eRr You can help fixing the links by edit text files written in markdown language, it's pretty easy to understand and can be done even by somebody without any development skill. This is a good chance to contribute back to oVirt project, looking forward to review your patches at https://github.com/oVirt/ovirt-site ! Thanks! -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/> [image: |Our code is open_] <https://www.redhat.com/en/our-code-is-open> *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours. <https://mojo.redhat.com/docs/DOC-1199578>*

1 0

ovirt-engine has been tagged (ovirt-engine-4.4.0)
by Tal Nisan 06 May '20

06 May '20

1 0

ovirt-engine has been tagged (ovirt-engine-4.3.10.1)
by Tal Nisan 06 May '20

06 May '20

1 0

Re: [CQ]: 108508, 5 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by Yedidyah Bar David 04 May '20

04 May '20

On Mon, May 4, 2020 at 12:54 PM oVirt Jenkins <jenkins(a)ovirt.org> wrote: > > A system test invoked by the "ovirt-master" change queue including change > 108508,5 (ovirt-engine) failed. However, this change seems not to be the root > cause for this failure. Change 107284,12 (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 107284,12 (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/108508/5 > > For further details about the change that seems to be the root cause behind the > testing failures see: > https://gerrit.ovirt.org/#/c/107284/12 > > For failed test results see: > https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/23516/ 12:40:26 Problem 1: package ovirt-engine-4.4.0-0.8.master.20200504085451.git4f394541974.el8.noarch requires apache-commons-jxpath, but none of the providers can be installed 12:40:26 - cannot install the best candidate for the job 12:40:26 - package apache-commons-jxpath-1.3-29.module_el8.0.0+30+832da3a1.noarch is excluded 12:40:26 Problem 2: package ovirt-engine-extension-aaa-ldap-setup-1.4.1-0.279.202003021945.el8.noarch requires ovirt-engine-extension-aaa-ldap = 1.4.1-0.279.202003021945.el8, but none of the providers can be installed 12:40:26 - package ovirt-engine-extension-aaa-ldap-1.4.1-0.279.202003021945.el8.noarch requires slf4j-jdk14, but none of the providers can be installed 12:40:26 - conflicting requests 12:40:26 - package slf4j-jdk14-1.7.25-4.module_el8.1.0+233+b2be703e.noarch is excluded 12:40:26 - package slf4j-jdk14-1.7.25-4.module_el8.0.0+30+832da3a1.noarch is excluded Known issue? > _______________________________________________ > Infra mailing list -- infra(a)ovirt.org > To unsubscribe send an email to infra-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/7EGCWUPY5I4MR… -- Didi

3 2

4.4 Beta for c8 Stream - ?
by lejeczek 04 May '20

04 May '20

hi everyone. A novice here. I'd like to ask if 4.4 is tested against c8steam and will work? And in case of NO answer I'll say that it would be great if possible, to have 4.4 fully tested and working on c8s. many thanks, L.

2 3

Re: [CQ]: 108705, 9 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by Yedidyah Bar David 04 May '20

04 May '20

On Sun, May 3, 2020 at 12:57 PM oVirt Jenkins <jenkins(a)ovirt.org> wrote: > > A system test invoked by the "ovirt-master" change queue including change > 108705,9 (ovirt-engine) failed. However, this change seems not to be the root > cause for this failure. Change 107284,12 (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 107284,12 (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/108705/9 > > For further details about the change that seems to be the root cause behind the > testing failures see: > https://gerrit.ovirt.org/#/c/107284/12 > > For failed test results see: > https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/23505/ The engine did manage to run ssh-copy-id to both host-0 and host-1, but then failed, a few seconds later, while running ansible: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/23505/artifa… 2020-05-03 05:54:49,779-04 ERROR [org.ovirt.engine.core.common.utils.ansible.AnsibleExecutor] (EE-ManagedThreadFactory-engine-Thread-1) [13ea1de1] Error executing playbook: Failed to add host to inventory: SSH timeout waiting for response from 'lago-basic-suite-master-host-0' A few other lines along this one, as well as similar ones for host-1, do not give (me) more information. lago did manage to collect logs from both hosts, a few seconds later. vdsm logs are empty, messages does not give me a clue. What is the timeout on trying to ssh (with ansible)? engine.log shows only 1-2 seconds from start to timeout. Perhaps we should make it a bit longer? Best regards, -- Didi

3 4