May 2020 - Devel - oVirt List Archives

[VDSM] Started getting virNetTLSContextCheckCertTimes:154 : The server certificate /etc/pki/vdsm/certs/vdsmcert.pem has expired
by Edward Haas 11 Jan '24

11 Jan '24

Hi, I have a VM which acts as an oVirt host with VDSM installed. I use it for testing without connecting it to Engine. Recently VDSM fails to come up and I see this error: Sep 26 17:58:18 localhost libvirtd: 2018-09-26 14:58:18.978+0000: 12176: error : virNetTLSContextCheckCertTimes:154 : The server certificate /etc/pki/vdsm/certs/vdsmcert.pem has expired Any hint on how to generate or fetch a new certificate without the help of Engine? Thanks, Edy.

3 5

Error: Adding new Host to ovirt-engine
by Ahmad Khiet 14 Aug '23

14 Aug '23

Hi, Can't add new host to ovirt engine, because the following error: 2019-06-12 12:23:09,664 p=4134 u=engine | TASK [ovirt-host-deploy-facts : Set facts] ************************************* 2019-06-12 12:23:09,684 p=4134 u=engine | ok: [10.35.1.17] => { "ansible_facts": { "ansible_python_interpreter": "/usr/bin/python2", "host_deploy_vdsm_version": "4.40.0" }, "changed": false } 2019-06-12 12:23:09,697 p=4134 u=engine | TASK [ovirt-provider-ovn-driver : Install ovs] ********************************* 2019-06-12 12:23:09,726 p=4134 u=engine | fatal: [10.35.1.17]: FAILED! => {} MSG: The conditional check 'cluster_switch == "ovs" or (ovn_central is defined and ovn_central | ipaddr and ovn_engine_cluster_version is version_compare('4.2', '>='))' failed. The error was: The ipaddr filter requires python's netaddr be installed on the ansible controller The error appears to be in '/home/engine/apps/engine/share/ovirt-engine/playbooks/roles/ovirt-provider-ovn-driver/tasks/configure.yml': line 3, column 5, but may be elsewhere in the file depending on the exact syntax problem. The offending line appears to be: - block: - name: Install ovs ^ here 2019-06-12 12:23:09,728 p=4134 u=engine | PLAY RECAP ********************************************************************* 2019-06-12 12:23:09,728 p=4134 u=engine | 10.35.1.17 : ok=3 changed=0 unreachable=0 failed=1 skipped=0 rescued=0 ignored=0 whats missing!? Thanks -- Ahmad Khiet Red Hat <https://www.redhat.com/> akhiet(a)redhat.com M: +972-54-6225629 <https://red.ht/sig>

7 10

Purging inactive maintainers from vdsm-master-maintainers
by Nir Soffer 21 Jun '21

21 Jun '21

I want to remove inactive contributors from vdsm-master-maintainers. I suggest the simple rule of 2 years of inactivity for removing from this group, based on git log. See the list below for current status: https://gerrit.ovirt.org/#/admin/groups/106,members Thoughts? Nir

6 11

Error Java SDK Issue??
by Geschwentner, Patrick 02 Apr '21

02 Apr '21

Dear Ladies and Gentlemen! I am currently working with the java-sdk and I encountered a problem. If I would like to retrieve the disk details, I get the following error: Disk currDisk = ovirtConnection.followLink(diskAttachment.disk()); The Error is occurring in this line: [cid:image001.png@01D44537.AF127FD0] The getResponst looks quiet ok. (I inspected: [cid:image002.png@01D44537.AF127FD0] and it looks ok). Error: wrong number of arguments The code is quiet similar to what you published on github (https://github.com/oVirt/ovirt-engine-sdk-java/blob/master/sdk/src/test/jav… ). Can you confirm the defect? Best regards Patrick

6 11

Add Evgheni Dereveanchin to ovirt quay owners group
by Nir Soffer 01 Jun '20

01 Jun '20

I suggest to add Evgheni to the owners group: https://quay.io/organization/ovirt/teams/owners So he managed groups and repos. Nir

2 1

Re: Problem with mixing all the changes
by Nir Soffer 28 May '20

28 May '20

On Wed, May 13, 2020 at 12:19 PM FMGarcia <francisco.garcia(a)wbsgo.com> wrote: Hi Fran, I'm moving the discussion to devel mailing list where it belongs. > In https://gerrit.ovirt.org/#/c/107082/ we have "several problems" to decide this patch: > > At the base (current version in github), the synergy ('download_disk_snapshot.py' and 'upload_disk_snapshot.py') does not working: > > 'Download_disk_snapshot.py' only download volumes of a disk. > 'Upload_disk_snapshot.py' requires: virtual machine configuration ('.ovf'), a only disk to upload in path './disks/xxxx', and manual action to attach disk to the vm. > > Then, I think that if you want a synergy with both scripts, we should change 'download_disk_snapshot.py' before that 'upload_disk_snapshot.py'. If not, you should edit 'upload_disk_snapshot.py' to add a variable 'vm_id'(as variable sd_name in this script) to attach the uploaded disk. I agree. It would be nice if we can do: $ mkdir -p backups/vm-id $ download_disk_snapshots.py --backup-dir backups/vm-id ... $ upload_disk_snapshots.py --backup-dir backups/vm-id ... download_disk_snapshots.py will download vm ovf and all disks. upload_disk_snaphsots.py would take the output of download_disk_snapshots.py and create a new vm. > I suppose that the best thing is to discard the gerrit, and to propose first what you want with 'download_disk_snapshot.py' and 'upload_disk_snapshot.py' and then act accordingly (several patch). Do you agree? This is a bigger change that can take more time. I think we better fix the issues in the current scripts - the first one is the missing attach disk that you fix in your patch. Since you posted this fix with a lot of other unrelated fixes (some wrong or unneeded), we cannot merge it. This is another reason to post minimal patches that do one fix. > I'm only truly interested in opened bug with block domain and volumes of > 1GB: https://bugzilla.redhat.com/show_bug.cgi?id=1707707. I make these changes to help a little since you would help me by solving the bug. I don't code in Python, I code in Java, using Java-sdk and the bug is a major limitation in my software, so I want resolve this bug (1 year old). =( I hope you understand. :) Sure, I understand. If you don't time to work on this, some other developer can take over this patch. The bug should be fixed by: https://gerrit.ovirt.org/c/108991/ It would be nice if you can test this. I started a build here: https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/5867/ When the build is ready, you will be able to install engine from this build by adidng a yum repo with the baseurl: https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/5867/artifa… Note that this requires CentOS 8.1. If you want to test on CentOS 7, you need to wait until the fix will be backported to 4.3, or since you like Java, maybe port it yourself? Note also that we have a much more advanced backup and restore options: https://github.com/oVirt/ovirt-engine-sdk/blob/master/sdk/examples/backup_v… Here is example run I did yesterday: I started with full backup of a running vm: $ ./backup_vm.py full --engine-url https://engine3/ --username admin@internal --password-file /home/nsoffer/.config/ovirt/engine3/password --cafile /home/nsoffer/Downloads/certs/engine3.pem --backup-dir /home/nsoffer/tmp/backups/test-nfs b5732b5c-37ee-4c66-b77e-bda5d37a10fe [ 0.0 ] Starting full backup for VM b5732b5c-37ee-4c66-b77e-bda5d37a10fe [ 1.5 ] Waiting until backup f73541c6-88d1-4dac-a551-da922cdb3f55 is ready [ 4.6 ] Created checkpoint '4754dc34-da4b-4e62-84ea-164c413b003c' (to use in --from-checkpoint-uuid for the next incremental backup) [ 4.6 ] Creating image transfer for disk 566e6aa6-575b-4f83-88c9-e5e5b54d9649 [ 5.9 ] Waiting until transfer 98e5aabc-fedb-4d2c-81c5-eed1a8b07790 will be ready [ 5.9 ] Image transfer 98e5aabc-fedb-4d2c-81c5-eed1a8b07790 is ready [ 5.9 ] Transfer url: https://host4:54322/images/13a0a396-5070-4b0f-a5cd-e2506c5abf0f Formatting '/home/nsoffer/tmp/backups/test-nfs/566e6aa6-575b-4f83-88c9-e5e5b54d9649.202005132336.full.qcow2', fmt=qcow2 size=6442450944 cluster_size=65536 lazy_refcounts=off refcount_bits=16 [ 100.00% ] 6.00 GiB, 18.34 seconds, 334.95 MiB/s [ 24.3 ] Finalizing transfer 98e5aabc-fedb-4d2c-81c5-eed1a8b07790 [ 24.5 ] Full backup completed successfully This downloads all vms disks to ~/tmp/backups/test-nfs/, creating 566e6aa6-575b-4f83-88c9-e5e5b54d9649.202005132336.full.qcow2 This file includes entire disk content at the time the backup was stated. This includes data from all snapshots. Then I run incremental backup of the same vm, recoding the data changes since the full backup: $ ./backup_vm.py incremental --engine-url https://engine3/ --username admin@internal --password-file /home/nsoffer/.config/ovirt/engine3/password --cafile /home/nsoffer/Downloads/certs/engine3.pem --backup-dir /home/nsoffer/tmp/backups/test-nfs --from-checkpoint-uuid 4754dc34-da4b-4e62-84ea-164c413b003c b5732b5c-37ee-4c66-b77e-bda5d37a10fe [ 0.0 ] Starting incremental backup for VM b5732b5c-37ee-4c66-b77e-bda5d37a10fe [ 1.3 ] Waiting until backup 01a88749-06eb-431a-81f2-b03db24b878e is ready [ 2.3 ] Created checkpoint '6f80d3c5-5b81-42ae-9700-2ccab37ad93b' (to use in --from-checkpoint-uuid for the next incremental backup) [ 2.3 ] Creating image transfer for disk 566e6aa6-575b-4f83-88c9-e5e5b54d9649 [ 3.4 ] Waiting until transfer 16c90052-9411-46f6-8dc6-b2f260206708 will be ready [ 3.4 ] Image transfer 16c90052-9411-46f6-8dc6-b2f260206708 is ready [ 3.4 ] Transfer url: https://host4:54322/images/b9a44902-46f1-43b3-a9ad-9d72735c53ad Formatting '/home/nsoffer/tmp/backups/test-nfs/566e6aa6-575b-4f83-88c9-e5e5b54d9649.202005132347.incremental.qcow2', fmt=qcow2 size=6442450944 cluster_size=65536 lazy_refcounts=off refcount_bits=16 [ 100.00% ] 6.00 GiB, 0.63 seconds, 9.52 GiB/s [ 4.0 ] Finalizing transfer 16c90052-9411-46f6-8dc6-b2f260206708 [ 4.1 ] Incremental backup completed successfully This backup is tiny since the only thing changed was new directory created on the vm, and some system logs modified since the full backup. Then I rebased the incremental backup on top of the full backup: cd home/nsoffer/tmp/backups/test-nfs qemu-img rebase -u -b 566e6aa6-575b-4f83-88c9-e5e5b54d9649.202005132336.full.qcow2 -F qcow2 566e6aa6-575b-4f83-88c9-e5e5b54d9649.202005132347.incremental.qcow2 This images are now a valid qcow2 chain that can be uploaded using upload_disk.py: $ python3 upload_disk.py --engine-url https://engine3/ --username admin@internal --password /home/nsoffer/.config/ovirt/engine3/password --cafile /home/nsoffer/Downloads/certs/engine3.pem --disk-format qcow2 --disk-sparse --sd-name iscsi2-1 /home/nsoffer/tmp/backups/test-nfs/566e6aa6-575b-4f83-88c9-e5e5b54d9649.202005132347.incremental.qcow2 Checking image... Image format: qcow2 Disk format: cow Disk content type: data Disk provisioned size: 6442450944 Disk initial size: 2755264512 Disk name: 566e6aa6-575b-4f83-88c9-e5e5b54d9649.202005132347.incremental.qcow2 Connecting... Creating disk... Disk id: a9785777-8aac-4515-a47a-2f5126e3af73 Creating image transfer... Transfer ID: 6e0384b6-730b-4416-a954-bf45e627d5cf Transfer host: host4 Uploading image... [ 100.00% ] 6.00 GiB, 20.50 seconds, 299.70 MiB/s Finalizing image transfer... Upload completed successfully The result is a single qcow2 disk on the domain iscs2-1. I created a new vm from this disk. This backup script is not complete yet, we don't download the VM OVF in each backup, and we don't create the VM from the OVF. These features should be added later. You may want to start testing and intergating this code instead of the snapshot based download. See https://www.ovirt.org/develop/release-management/features/storage/increment… Nir

3 5

Resolve IPv6 hostname inside vdsm-gluster
by Kaustav Majumder 28 May '20

28 May '20

Hi devel, Is it possible to resolve an IPv6 address from a hostname inside VDSM? I am aware of socket.getaddrinfo <https://docs.python.org/3.8/library/socket.html#socket.getaddrinfo>, but are there any libs inside vdsm which already does it, and I can use. What do I want to do with it? For this command inside VDSM *gluster vol info <volname> --remote-host=host1.test.example.com <http://host1.test.example.com>* Gluster is not able to resolve the ip of host1.test.example.com and fails as https://pastebin.com/Bt1AUvkU. I wanted to know if a workaround can be added in vdsm-gluster to resolve a static IPv6 host and pass the ip to the gluster command. -- Thanks, Kaustav Majumder

1 0

ovirt-engine has been tagged (ovirt-engine-4.4.1.1)
by Tal Nisan 27 May '20

27 May '20

1 0

Cant get Sysprep to insert product key in Win2016 guest on RHV 4.3
by Lynn Dixon 24 May '20

24 May '20

I am trying to create a basic Windows server 2016 template in RHV 4.3 . I've installed the OS from the Windows DVD, and installed all the RHV tools, and drivers. Then I do a sysprep on my windows VM and make a template from it. I'd like to inject the product key when the template is cloned. I thought if we define the product key in /etc/ovirt-engine/osinfo.conf.d/10-productkeys.properties. with something like this: # Windows2016x64(29, OsType.Windows, true); os.windows_2016x64.id.value = 29 os.windows_2016x64.name.value = Windows 2016 x64 os.windows_2016x64.derivedFrom.value = windows_2012R2x64 os.windows_2016x64.cpu.unsupported.value = conroe, penryn, nehalem, opteron_g1 os.windows_2016x64.sysprepPath.value = ${ENGINE_USR}/conf/sysprep/sysprep.2k16x64 os.windows_2016x64.productKey.value = MY-WIN-PRODUCT-KEY That it would insert the product key when we tick the "Cloud Init / Sysprep" box on the run-once dialog. Now, I know this is semi-working, because all the other things I define in the run-once dialog after clicking sysprep works: Admin password, hostname, etc. But NOT the product key! I have even tried hard coding the product key in the sysprep.2k16x64 file and no luck. What am I doing wrong here? *Lynn Dixon* | Red Hat Certified Architect #100-006-188 *Solutions Architect* | NA Commercial Google Voice: 423-618-1414 Cell/Text: 423-774-3188 Click here to view my Certification Portfolio <http://red.ht/1XMX2Mi>

2 1

Re: package conflicts when executing dnf update
by Nir Soffer 22 May '20

22 May '20

On Fri, May 22, 2020 at 4:39 PM Stefan Wichmann <stefan(a)wichmann.ch> wrote: > I have exactly the same problem. Fresh install of CentOS 8.1, did the install of oVirt-4.4-Release (added new host). And now I have this conflict… Which conflict? This looks like a reply, but there is no context from the original message.

2 1

Re: package conflicts when executing dnf update
by Stefan Wichmann 21 May '20

21 May '20

Hi, I have exactly the same problem. Fresh install of CentOS 8.1, did the install of oVirt-4.4-Release (added new host). And now I have this conflict… Is there any solution to this? Kind regards, Stefan

1 0

ovirt-engine has been tagged (ovirt-engine-4.3.10.4)
by Tal Nisan 21 May '20

21 May '20

1 0

oVirt 4.4.0 Release is now generally available
by Sandro Bonazzola 20 May '20

20 May '20

oVirt 4.4.0 Release is now generally available The oVirt Project is excited to announce the general availability of the oVirt 4.4.0 Release, as of May 20th, 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 Some of the features included in the oVirt 4.4.0 release require content that will be available in CentOS Linux 8.2 but cannot be tested on RHEL 8.2 yet due to some incompatibility in the openvswitch package that is shipped in CentOS Virt SIG, which requires rebuilding openvswitch on top of CentOS 8.2. The cluster switch type OVS is not implemented for CentOS 8 hosts. Please note that oVirt 4.4 only supports clusters and datacenters with compatibility version 4.2 and above. If clusters or datacenters 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, 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 users mailing list thread on this at https://lists.ovirt.org/archives/list/users@ovirt.org/thread/NDSVUZSESOXEFJ… ) Installation instructions For the engine: either use the oVirt appliance or install CentOS Linux 8 minimal by following these steps: - Install the CentOS Linux 8 image 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.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…, selecting the minimal installation. - dnf install https://resources.ovirt.org/pub/yum-repo/ovirt-release44.rpm - dnf update (reboot if needed) - Attach the host to the engine and let it be deployed. Update instructionsUpdate from oVirt 4.4 Release Candidate On the engine side and on CentOS hosts, you’ll need to switch from ovirt44-pre to ovirt44 repositories. In order to do so, you need to: 1. dnf remove ovirt-release44-pre 2. rm -f /etc/yum.repos.d/ovirt-4.4-pre-dependencies.repo 3. rm -f /etc/yum.repos.d/ovirt-4.4-pre.repo 4. dnf install https://resources.ovirt.org/pub/yum-repo/ovirt-release44.rpm 5. dnf update On the engine side you’ll need to run engine-setup only if you were not already on the latest release candidate. On oVirt Node, you’ll need to upgrade with: 1. Move node to maintenance 2. dnf install https://resources.ovirt.org/pub/ovirt-4.4/rpm/el8/noarch/ovirt-node-ng-imag… 3. Reboot 4. Activate the host Update from oVirt 4.3 oVirt 4.4 is available only for CentOS 8. In-place upgrades from previous installations, based on CentOS 7, are not possible. For the engine, use backup, and restore that into a new engine. Nodes will need to be reinstalled. A 4.4 engine can still manage existing 4.3 hosts, but you can’t add new ones. For a standalone engine, please refer to upgrade procedure at https://ovirt.org/documentation/upgrade_guide/#Upgrading_from_4-3 If needed, run ovirt-engine-rename (see engine rename tool documentation at https://www.ovirt.org/documentation/admin-guide/chap-Utilities.html ) When upgrading hosts: You need to upgrade one host at a time. 1. Turn host to maintenance. Virtual machines on that host should migrate automatically to a different host. 2. Remove it from the engine 3. Re-install it with el8 or oVirt Node as per installation instructions 4. Re-add the host to the engine Please note that you may see some issues live migrating VMs from el7 to el8. If you hit such a case, please turn off the vm on el7 host and get it started on the new el8 host in order to be able to move the next el7 host to maintenance. What’s new in oVirt 4.4.0 Release? - 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 API/SDK v3 support deprecated in past versions. - 4K block disk support only for file-based storage. iSCSI/FC storage do not support 4K disks yet. - You can export a VM to a data domain. - You can edit floating disks. - Ansible Runner (ansible-runner) is integrated within the engine, enabling more detailed monitoring of playbooks executed from the engine. - Adding and reinstalling hosts is now completely based on Ansible, replacing ovirt-host-deploy, which is not used anymore. - 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/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.*

2 1

oVirt and Fedora
by Sandro Bonazzola 20 May '20

20 May '20

If you have followed the oVirt project for a few releases you already know oVirt has struggled to keep the pace with the fast innovation cycles Fedora Project is following. Back in September 2019 CentOS project launched CentOS Stream as a rolling preview of future RHEL kernels and features, providing an upstream development platform for ecosystem developers that sits between Fedora and RHEL. Since then the oVirt project tried to keep the software working on Fedora, CenOS Stream, and RHEL/CentOS but it became quickly evident the project lacked resources to keep the project running on three platforms. Further, our user surveys show that oVirt users strongly prefer using oVirt on CentOS and RHEL. With the upcoming end of life of Fedora 30 the oVirt project has decided to stop trying to keep the pace with this amazing platform, focusing on stabilizing the software codebase on RHEL / CentOS Linux. By focusing our resources and community efforts on RHEL/CentOS Linux and Centos Stream, we can provide better support for those platforms and use more time for moving oVirt forward. -- 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.*

4 11

Re: [oVirt Jenkins] ovirt-system-tests_he-basic-suite-4.3 - Build # 448 - Failure!
by Yedidyah Bar David 20 May '20

20 May '20

On Wed, May 20, 2020 at 7:06 AM <jenkins(a)jenkins.phx.ovirt.org> wrote: > > Project: https://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-4.3/ > Build: https://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-4.3/448/ Checked this, and failed to find exact root cause. It failed in 012_local_maintenance_sdk.local_maintenance, to put the host to maintenance, because, https://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-4.3/448/art… 2020-05-20 00:03:57,239-04 ERROR [org.ovirt.engine.api.restapi.resource.AbstractBackendResource] (default task-6) [] Operation Failed: [Cannot switch the Host(s) to Maintenance mode. There are no available hosts capable of running the engine VM.] Before that, engine.log: 2020-05-19 23:52:22,933-04 WARN [org.ovirt.engine.core.vdsbroker.irsbroker.IrsProxy] (EE-ManagedThreadFactory-engine-Thread-89) [] vds 'lago-he-basic-suite-4-3-host-0' reported domain '9624d30d-4a7a-4061-80c8-149a1e770275:nfs' as in problem, attempting to move the vds to status NonOperational then it started migrating the engine vm to host-1. Relevant lines about the migration can also be seen in HA logs on both hosts. Couldn't find anywhere why it had storage problems and moved to nonoperational. Nir, can you please have a look? Thanks. It's likely a local issue (high load or whatever), but can't be certain. Best regards, -- Didi

1 0

OST CI basic suite failure
by Artem Hrechanychenko 19 May '20

19 May '20

Hi, I'm getting failure on ci check for my patch for network suite changes https://gerrit.ovirt.org/#/c/108317/ CI failures https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/9350/ <https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/9350/…> My patch does not change the basic-suite master and local run passed locally. Does anybody know or get something similar ?

5 7

ovirt-engine has been tagged (ovirt-engine-4.4.1)
by Tal Nisan 19 May '20

19 May '20

1 0

ssl error during host install
by Vojtech Juranek 19 May '20

19 May '20

Hi, I'm getting following SSL error when adding new host: engine: [...] 2020-05-18 18:28:35,530-04 WARN [org.ovirt.vdsm.jsonrpc.client.utils.retry.Retryable] (EE-ManagedThreadFactory-engine-Thread-42) [762c711c] Retry failed 2020-05-18 18:28:39,033-04 WARN [org.ovirt.vdsm.jsonrpc.client.utils.retry.Retryable] (EE-ManagedThreadFactory-engine-Thread-43) [762c711c] Retry failed 2020-05-18 18:28:39,033-04 ERROR [org.ovirt.engine.core.bll.hostdeploy.InstallVdsInternalCommand] (EE-ManagedThreadFactory-engine-Thread-3) [762c711c] Host installation failed for host 'ab082e77-315c-4cfe-8188-11fbee94c2b8', 'fc30-glance': Network error during communication with the host host (vdsm log): 2020-05-18 18:26:36,963-0400 ERROR (Reactor thread) [vds.dispatcher] uncaptured python exception, closing channel <yajsonrpc.betterAsyncore.Dispatcher connected ('::ffff:192.168.122.246', 52428, 0, 0) at 0x7f9f8c7e8d30> (<class 'ssl.SSLError'>:[X509] no certificate or crl found (_ssl.c:4053) [/usr/lib64/python3.7/asyncore.py|readwrite|110] [/usr/lib64/python3.7/asyncore.py|handle_write_event|441] [/usr/lib/python3.7/site-packages/yajsonrpc/betterAsyncore.py|handle_write|75] [/usr/lib/python3.7/site-packages/yajsonrpc/betterAsyncore.py|_delegate_call|173] [/usr/lib/python3.7/site-packages/vdsm/sslutils.py|handle_write|190] [/usr/lib/python3.7/site-packages/vdsm/sslutils.py|_handle_io|194] [/usr/lib/python3.7/site-packages/vdsm/sslutils.py|_set_up_socket|154]) (betterAsyncore:184) Any idea what's wrong and/or how to fix it? Both engine and host are on FC30, host is installed from standard ovirt-release44-pre repo and engine is dev build of latest engine master with glance API v2 patches [1]. Thanks Vojta [1] https://gerrit.ovirt.org/#/q/topic:"Image+Service+API+v2"

3 9

[Feedback needed] oVirt 4.4.0 Test week
by Sandro Bonazzola 18 May '20

18 May '20

Hi, oVirt team is planning to release oVirt 4.4.0 Ga in the next couple of weeks. oVirt 4.4.0 release candidate was released yesterday and we'd like to gather as much feedback as possible. Please join us testing this release candidate next week, starting Sunday May 10th 2020 till Friday May 15th 2020! We are going to coordinate the testing effort with a public Trello board at https://trello.com/b/5ZNJgPC3/ovirt-440-test-day You'll find instructions on how to use the board there. For joining the board you can use this link: https://trello.com/invite/b/5ZNJgPC3/f1b1826ee4902f348c44607765a15099/ovirt… If you have not an environment dedicated to testing, remember you can set up a few VMs and test the deployment with nested virtualization using your production environment creating a virtual test environment. In this case please be careful avoiding touching the production environment from the testing one. The oVirt team will monitor the Trello board, the #ovirt IRC channel on irc.oftc.net server and the users(a)ovirt.org mailing list to assist with the testing and debugging issues. Basic instructions for setting up a minimal system are available in release candidate announce at: https://lists.ovirt.org/archives/list/announce@ovirt.org/message/3QORBKVKTA… Release notes for this release candidate are available here: https://ovirt.org/release/4.4.0/ 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.*

1 1

are we storing the back-end fqdn (like the one used in gluster) in engine?
by Prajith Kesava Prasad 18 May '20

18 May '20

Hi all, I hope this email finds you well. I just wanted to check, does anyone know if there is a way to get the back-end hostname from the ovirt-engine?, (this scenario is most likely to occur when an external logical network is attached). I did see a way to get the network interface, with respect to each host. like Even though RHV-engine, contains logical network-attached to it, and its details (like ipv4). There is no primary key present that could help us identify that a network is gluster related or not. so we cannot actually get the details, because we won't know if a network is gluster network or something else. I just wanted to see, if there is any other way to get the details of the backend hostname? Thanks in advance, Prajith.

3 3

4.4 beta - systemd & pids - daemon fails
by lejeczek 15 May '20

15 May '20

hi devel, Some inconsistencies in systemd's daemon configs &/|| binaries? Starting Open vSwitch Database Unit... ovs|00002|daemon_unix|EMER|/var/run/openvswitch/ovsdb-server.pid.tmp: create failed (Permission denied) Starting ovsdb-server ovsdb-server: /var/run/openvswitch/ovsdb-server.pid.tmp: create failed (Permission denied) [FAILED] Any quick fix would mind to suggest? many thanks, L.

4 7

oVirt 4.4.0 GA GO / NO GO
by Sandro Bonazzola 15 May '20

15 May '20

Hi, we just released oVirt 4.4.0 RC2 fixing most of the issues reported during the test week. As of today, we have no open blocker bugs <https://bugzilla.redhat.com/buglist.cgi?quicksearch=target_milestone%3Aovir…> and no proposed blocker bugs <https://bugzilla.redhat.com/buglist.cgi?quicksearch=target_milestone%3Aovir…> . If nobody raises any flag against releasing GA, I think we can promote this release to GA next week on May 20th (note: oVirt Node and oVirt Engine Appliance will need to be rebuilt from official release repo so they'll differ only by ovirt-release44 rpm included in the build) Deadline for raising a NO GO flag is May 19th , 18:00 CEST -- 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

Re: [ovirt-users] POWER9 Support: VDSM requiring LVM2 package that's missing
by Amit Bawer 15 May '20

15 May '20

+devel <devel(a)ovirt.org> On Fri, May 15, 2020 at 2:29 AM Amit Bawer <abawer(a)redhat.com> wrote: > yes it correlates to the bug mentioned, > currently the rpm for vdsm-4.30.46 is available at 4.3 pre-release repo > https://resources.ovirt.org/pub/ovirt-4.3-pre/rpm/el7/ppc64le/ > repodata is one level up > > On Fri, May 15, 2020 at 2:26 AM Vinícius Ferrão <ferrao(a)versatushpc.com.br> > wrote: > >> Hi Amit, I think I found the answer: It’s not available yet. >> >> https://bugzilla.redhat.com/show_bug.cgi?id=1829348 >> >> It's this bug right? >> >> Thanks, >> >> On 14 May 2020, at 20:14, Vinícius Ferrão <ferrao(a)versatushpc.com.br> >> wrote: >> >> Hi Amit, thanks for confirming. >> >> Do you know in which repository VDSM 4.30.36 is available? >> >> It’s not available on any of both: >> rhel-7-for-power-9-rpms/ppc64le >> Red Hat Enterprise Linux 7 for POWER9 (RPMs) >> 9,156 >> rhel-7-server-rhv-4-mgmt-agent-for-power-9-rpms/ppc64le Red Hat >> Virtualization 4 Management Agents (for RHEL 7 Server for IBM POWER9 814 >> >> >> Thank you! >> >> >> On 14 May 2020, at 20:09, Amit Bawer <abawer(a)redhat.com> wrote: >> >> >> On Fri, May 15, 2020 at 12:19 AM Vinícius Ferrão via Users < >> users(a)ovirt.org> wrote: >> >>> Hello, >>> >>> I would like to know if this is a bug or not, if yes I will submit to >>> Red Hat. >>> >> Fixed on vdsm-4.30.46 >> >>> >>> I’m trying to add a ppc64le (POWER9) machine to the hosts pool, but >>> there’s missing dependencies on VDSM: >>> >>> --> Processing Dependency: lvm2 >= 7:2.02.186-7.el7_8.1 for package: >>> vdsm-4.30.44-1.el7ev.ppc64le >>> --> Finished Dependency Resolution >>> Error: Package: vdsm-4.30.44-1.el7ev.ppc64le >>> (rhel-7-server-rhv-4-mgmt-agent-for-power-9-rpms) >>> Requires: lvm2 >= 7:2.02.186-7.el7_8.1 >>> Available: 7:lvm2-2.02.171-8.el7.ppc64le >>> (rhel-7-for-power-9-rpms) >>> lvm2 = 7:2.02.171-8.el7 >>> Available: 7:lvm2-2.02.177-4.el7.ppc64le >>> (rhel-7-for-power-9-rpms) >>> lvm2 = 7:2.02.177-4.el7 >>> Available: 7:lvm2-2.02.180-8.el7.ppc64le >>> (rhel-7-for-power-9-rpms) >>> lvm2 = 7:2.02.180-8.el7 >>> Available: 7:lvm2-2.02.180-10.el7_6.1.ppc64le >>> (rhel-7-for-power-9-rpms) >>> lvm2 = 7:2.02.180-10.el7_6.1 >>> Available: 7:lvm2-2.02.180-10.el7_6.2.ppc64le >>> (rhel-7-for-power-9-rpms) >>> lvm2 = 7:2.02.180-10.el7_6.2 >>> Available: 7:lvm2-2.02.180-10.el7_6.3.ppc64le >>> (rhel-7-for-power-9-rpms) >>> lvm2 = 7:2.02.180-10.el7_6.3 >>> Available: 7:lvm2-2.02.180-10.el7_6.7.ppc64le >>> (rhel-7-for-power-9-rpms) >>> lvm2 = 7:2.02.180-10.el7_6.7 >>> Available: 7:lvm2-2.02.180-10.el7_6.8.ppc64le >>> (rhel-7-for-power-9-rpms) >>> lvm2 = 7:2.02.180-10.el7_6.8 >>> Installing: 7:lvm2-2.02.180-10.el7_6.9.ppc64le >>> (rhel-7-for-power-9-rpms) >>> lvm2 = 7:2.02.180-10.el7_6.9 >>> >>> >>> Thanks, >>> >>> _______________________________________________ >>> Users mailing list -- users(a)ovirt.org >>> To unsubscribe send an email to users-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/users@ovirt.org/message/I3YDM2VN7K2GH… >>> >> >> >>

1 0

ovirt-engine has been tagged (ovirt-engine-4.4.0.3)
by Tal Nisan 14 May '20

14 May '20

1 0

sanlock 3.8.1 is available for testing
by Nir Soffer 14 May '20

14 May '20

I pushed sanlock 3.8.1 to Fedora updates-testing. If you have a Fedora 30 setup please upgrade sanlock: sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-87665d32ca and provide feedback here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-87665d32ca The update is also available for other versions: f31: https://bodhi.fedoraproject.org/updates/FEDORA-2020-455253f67d f32: https://bodhi.fedoraproject.org/updates/FEDORA-2020-99d4242726 f33: already in stable Cheers, Nir

1 2

OST
by Michal Skrivanek 14 May '20

14 May '20

Hi, I’m getting " Failed to download metadata for repo \'ovirt-master-advanced-virtualization-testing\’” when using ovirt-release-master.rpm since today. Any idea? Also, in CI the backup/restore test seem to be failing for few days now. Any idea anyone? It doesn’t fail in my local runs so could be just a dependency problem too… Thanks, michal

4 15

ovirt-engine has been tagged (ovirt-engine-4.4.0.2)
by Tal Nisan 13 May '20

13 May '20

1 0

ovirt-engine has been tagged (ovirt-engine-4.3.10.3)
by Tal Nisan 13 May '20

13 May '20

1 0

ovirt-engine has been tagged (ovirt-engine-4.4.0.1)
by Tal Nisan 13 May '20

13 May '20

1 0

ovirt-engine has been tagged (ovirt-engine-4.3.10.2)
by Tal Nisan 13 May '20

13 May '20

1 0

testing uses of Injector.get with mockito
by Fedor Gavrilov 13 May '20

13 May '20

We have quite a few occasions when Injector.get(SomeClass.class) is used inside command. Given that mockito can't mock static methods and power mock is not used, I wonder what one should do when these usages have to be mocked in unit tests. Funny enough, workarounds for this usage in my specific case include mocking constructor (unsupported by mockito) and mocking superclass method (unsupported by mockito). Also, why not to @Inject these instances in the first place? Thanks, Fedor

1 0

openvswitch on Centos 8 will not re/build
by lejeczek 12 May '20

12 May '20

hi guys, Centos 8 comes with gcc-8 which openvswitch does not like (from rpm source: openvswitch-2.11.1-5.el8.src.rpm) and it fails to build. Would that be correct? ... checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /usr/bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking whether make supports nested variables... yes checking how to create a pax tar archive... gnutar checking whether make supports the include directive... yes (GNU style) checking for x86_64-redhat-linux-gnu-gcc... no checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... configure: error: in `/yum.rpm/rpmbuilds/os.generic/build/openvswitch-2.11.1': configure: error: cannot run C compiled programs. If you meant to cross compile, use `--host'. See `config.log' for more details regards, L.

2 1

ovirt_vm module and supported operating systems
by Sandro Bonazzola 12 May '20

12 May '20

Hi, I see that in https://docs.ansible.com/ansible/latest/modules/ovirt_vm_module.html operating system is missing rhel8. Is this intended? I think that because of this, the hosted engine on 4.4.0 is still deployed with RHEL7 specs. https://github.com/oVirt/ovirt-ansible-hosted-engine-setup/blob/master/task… Can we move on to RHEL 8? -- 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>*

2 1

libvirtd fails on: operation failed: pool 'default' already exists with uuid dd48b6ad-9a00-46eb-a3a4-c122d8a294a5
by Dana Elfassy 08 May '20

08 May '20

Hi everyone, libvirtd fails with this error when I activate VirtualMachineManager from the journal: May 08 16:10:05 delfassy libvirtd[26476]: libvirt version: 5.6.0, package: 10.el8 (CBS <cbs(a)centos.org>, 2020-02-27-01:09:46, ) May 08 16:10:05 delfassy libvirtd[26476]: hostname: delfassy May 08 16:10:05 delfassy libvirtd[26476]: operation failed: pool 'default' already exists with uuid dd48b6ad-9a00-46eb-a3a4-c122d8a294a5 May 08 16:10:19 delfassy sudo[26639]: delfassy : TTY=pts/5 ; PWD=/home/delfassy/ovirt-engine-master ; USER=root ; COMMAND=/bin/journalctl May 08 16:10:19 delfassy sudo[26639]: pam_systemd(sudo:session): Cannot create session: Already running in a session or user slice May 08 16:10:19 delfassy sudo[26639]: pam_unix(sudo:session): session opened for user root by (uid=0) Among steps that I have tried were destroying the default pool and recreating it, removing all libvirt packages and virtual-machine-manager, erasing /etc/libvirt, and reinstalling them, all result with this error Has anyone encountered this error/ has an idea how to fix it? Thanks, Dana

1 1

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

Vdsm CI is missing glusterfs repo
by Amit Bawer 04 May '20

04 May '20

Example from https://jenkins.ovirt.org/job/vdsm_standard-check-patch/20818/consoleText [2020-05-04T06:40:08.041Z] Failed to download metadata for repo 'glusterfs' [2020-05-04T06:40:08.041Z] Error: Failed to download metadata for repo 'glusterfs' Suggesting: https://gerrit.ovirt.org/#/c/108782/ Thanks.

1 0

Can't install vdsm and vdsm-client from master repository
by Shani Leviim 03 May '20

03 May '20

Hi all, I'm trying to install vdsm and vdsm-client from the master repository on an fc31 host, but I'm getting an error which packages don't exists: # dnf install vdsm vdsm-client Last metadata expiration check: 0:35:20 ago on Sun 03 May 2020 10:50:57 AM IDT. No match for argument: vdsm No match for argument: vdsm-client Error: Unable to find a match: vdsm vdsm-client I've noticed while installing the master rpm, the source repository is *commandline* instead of ovirt-release-master or something like that. # sudo yum install -y http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm Last metadata expiration check: 2:38:37 ago on Sun 03 May 2020 08:11:06 AM IDT. ovirt-release-master.rpm 27 kB/s | 11 kB 00:00 Dependencies resolved. ============================================================================================================================================================================================== Package Architecture Version Repository Size ============================================================================================================================================================================================== Installing: ovirt-release-master noarch 4.4.0-0.3.master.20200502011334.gitb4c7d97.el8 *@commandline* 11 k Does anyone encounter this issue? Same happened to me with ovirt-release43.rpm Thanks ahead *Regards,* *Shani Leviim*

3 2

oVirt 4.4.0 Beta release refresh is now available for testing
by Sandro Bonazzola 03 May '20

03 May '20

oVirt 4.4.0 Beta release refresh is now available for testing The oVirt Project is excited to announce the availability of the beta release of oVirt 4.4.0 refresh (beta 4) for testing, as of April 17th, 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 Beta release. The oVirt Project makes no guarantees as to its suitability or usefulness. This pre-release must not to be used in production. In particular, please note that upgrades from 4.3 and future upgrades from this beta to the final 4.4 release from this version are not supported. Some of the features included in oVirt 4.4.0 Beta 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. Known Issues - ovirt-imageio development is still in progress. In this beta you can’t upload images to data domains using the engine web application. You can still copy iso images into the deprecated ISO domain for installing VMs or upload and download to/from data domains is fully functional via the REST API and SDK. For uploading and downloading via the SDK, please see: - https://github.com/oVirt/ovirt-engine-sdk/blob/master/sdk/examples/upload_d… - https://github.com/oVirt/ovirt-engine-sdk/blob/master/sdk/examples/download… Both scripts are standalone command line tool, try --help for more info. 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 Beta? - 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/>* <https://www.redhat.com/en/summit?sc_cid=7013a000002D2QxAAK>* *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

4 3

CloudSpin case study
by Sandro Bonazzola 03 May '20

03 May '20

Hi, on oVirt website we highlight CloudSpin case study[1] but the web site for that company can't be resolved anymore. Looks like the company closed. Any objections in removing the case from the oVirt website? [1] https://ovirt.org/community/user-stories/cloudspin-case-study.html -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/>* <https://www.redhat.com/en/summit?sc_cid=7013a000002D2QxAAK>* *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>*

2 1