- Users - oVirt List Archives

4.4.4 Image Copying / Template Create Fails - No Such File
by Alex McWhirter 08 Mar '21

08 Mar '21

I've been wrestling with this all night, digging through various bits of VDSM code trying to figure why and how this is happening. I need to make some templates, but i simply can't. VDSM <host> command HSMGetAllTasksStatusesVDS failed: value=low level Image copy failed: ("Command ['/usr/bin/qemu-img', 'convert', '-p', '-t', 'none', '-T', 'none', '-f', 'raw', '-O', 'raw', '/rhev/data-center/mnt/glusterSD/<gluster>:_Temp/45740f16-b3c9-4bb5-ba5f-3e64657fb663/images/6f87b073-c4ec-42f2-87da-d1cb6a08a150/f2dfb779-b49c-4ec9-86cd-741f3fe5b781', '/rhev/data-center/mnt/glusterSD/<gluster>:_Temp/45740f16-b3c9-4bb5-ba5f-3e64657fb663/images/84e56da6-8c26-4518-80a4-20bc395214db/039c5ada-ad6d-45c0-8393-bd4db0bbc366'] failed with rc=1 out=b'' err=bytearray(b'qemu-img: error while writing at byte 738197504: No such file or directory\\n')",) abortedcode=261 3/7/21 5:44:44 AM Following the VDSM logs, i can see the new image gets created, permissions set, etc... but as soon qemu-img starts, it fails like this. I updated all hosts and the engine, rebooted the entire stack, to no avail. So i detached the storage domain, and wiped every host and fresh installed both engine and all nodes, imported the storage domain, and still no dice. Storage domain is gluster volume, single node, created in ovirt. It happens when i make a template, copy an image, or make a new vm from a template. I can still create new vms from blank, and upload images via the web ui. Watching the gluster share, i can see the image being created, but its deleted at some point. I appears to not be being deleted by the template / copying process, as immediately after the above error, i get this one. VDSM command DeleteImageGroupVDS failed: Image does not exist in domain: 'image=4f359545-01a8-439b-832b-18c26194b066, domain=b4507449-ac40-4e35-be66-56441bb696ac' 3/7/21 5:44:44 AM I thought maybe garbage collection, but don't see any indication of that in the logs. Any ideas? I redacted host names from the log output.

3 5

Which Operating System to choose
by sinan＠turka.nl 07 Mar '21

07 Mar '21

I want to set up a small cluster consisting of 2 Hypervisor nodes (self-hosted engine) with shared storage (SAN, ISCSI). According to https://www.ovirt.org/download/ the following Operating Systems are supported with the latest oVirt version (4.4.4): - Red Hat Enterprise Linux 8.3 - CentOS Linux 8.3 - CentOS Stream (Tech Preview) My doubts are: - RHEL 8.3 is free to use up tp 16 hosts, but until when? Red Hat can decide at anytime to change their subscription program. - CentOS Linux is no more, support will stop at the end of 2021. - CentOS Stream is in Tech Preview. I don't like running production environments on "tech preview / beta" versions. I would say CentOS 7, it will receive maintenance updates up to 2024, and switch to RHEL in 2024 if the free-to-use program is still active. Unfortunately, CentOS 7 seems not to be supported. On what Operating System are you running oVirt 4.4.4 and why? Any feedback and advice is welcome. Thanks!

2 1

Cold Move VM Storage failing
by dmmailing010203＠gmail.com 07 Mar '21

07 Mar '21

Morning oVirt. I've rebuilt my oVirt environment and I'm currently on 4.4.5.8-1.el8. I have storage presented via NFS. I'm unable to move / copy VM disks when powered off. However I can Live migrate the disks when powered on. I have three storage domains presented and this is repeated across all three no matter where the storage is located. The disks are thin provisioned. I've tried deactivating and detaching the disk and it's the same NullPointerException error. 2021-03-06 15:13:17,010Z ERROR [org.ovirt.engine.core.bll.storage.disk.image.CopyDataCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-84) [af63add0-0ef3-4049-8461-b564abedba02] Command 'org.ovirt.engine.core.bll.storage.disk.image.CopyDataCommand' failed: null 2021-03-06 15:13:17,010Z ERROR [org.ovirt.engine.core.bll.storage.disk.image.CopyDataCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-84) [af63add0-0ef3-4049-8461-b564abedba02] Exception: java.lang.NullPointerException Engine log with stack trace is at https://textuploader.com/1820f Vdsm log is at https://textuploader.com/1820z I'm just checking I've not missed something obvious before raising a bug if neccessary

2 2

Gluster version upgrades
by Sketch 07 Mar '21

07 Mar '21

Is the gluster version on an oVirt host tied to the oVirt version, or would it be safe to upgrade to newer versions of gluster? I have noticed gluster is often updated to new major versions on oVirt point release upgrades. We have some compute+storage hosts on 4.3.6 which can't be upgraded easily at the moment, but we are having some gluster issues that appear to be due to bugs that I wonder if upgrading might help. Would an in-place upgrade of gluster be a bad idea without also updating oVirt?

2 1

VM ovirt-win10-01 is down with error. Exit message: Unable to get volume size for domain 5cee5082-074e-4a8b-a750-0e8fb0aff63c volume 05063eec-ca54-42c6-92d6-0a6775545eba.
by wangyu13476969128＠126.com 06 Mar '21

06 Mar '21

The version of ovirt-manager is 4.3.6.7。 I have two ovirt-nodes. After I restart one ovirt-node, all the Linux virtual machines on the ovirt-node can startup. But all the Windows virtual machines on the ovirt-node can't startup。 The title show the error: VM ovirt-win10-01 is down with error. Exit message: Unable to get volume size for domain 5cee5082-074e-4a8b-a750-0e8fb0aff63c volume 05063eec-ca54-42c6-92d6-0a6775545eba. How can I solve this problem ?

1 0

Removed FC LUN causes multipath to spam syslog
by Juhani Rautiainen 06 Mar '21

06 Mar '21

Hi! We are running ovirt 4.3.10 and we are migrating from 3PAR to Dell SC. I've managed to transfer disks from one LUN away and removed it (put it in maintenanced, detached it and removed it). Now multipath seems to spam the logs for missing disks. How can I stop this? Mar 5 09:58:58 ovirt01 multipathd: 360002ac00000000000000272000057b9: sdr - tur checker reports path is down Mar 5 09:58:59 ovirt01 multipathd: 360002ac00000000000000272000057b9: sdh - tur checker reports path is down And so on. Any idea how I can quiet this? And why didn't oVirt do this automatically? Thanks, Juhani

3 7

Re: EL7 Host support in 4.4.x
by Nir Soffer 04 Mar '21

04 Mar '21

On Thu, Mar 4, 2021 at 6:06 PM Vrgotic, Marko <M.Vrgotic(a)activevideo.com> wrote: > Hi oVirt, > > > > After reviewing the https://access.redhat.com/articles/973163 > > I wonder is it possible to have a Host running EL7, in oVirt 4.4 to > support ability to still run OSs like Win 2008R2, or is it a hard NO? > Theoretically vdsm can run on EL7 if you install python3, but without libvirt and qemu versions required in 4.4 it will not be very useful. If you need EL7, use ovirt 4.3. Nir

2 1

Create update and security plan
by Gilson Schmidt 04 Mar '21

04 Mar '21

Hi We have a large hypervisors park, and now we are starting to adopt oVirt. And I need an update and security plan for oVirt Nodes. I need to know: - What is the update cycle for oVirt? - How large companies treat the security of oVirt Node. What is the frequency of updates; Is an additional service enabled / installed on oVirt Node? Is SSH enabled maintained? What is the sysadmin access format? Currently on other hypervisors (Xen) using Vault, or we disable SSH on ESXi. How do large companies configure oVirt to comply with the needs passed on by the Security Team? Tks very much.

2 1

Difference between edit cluster and upgrade?
by Gianluca Cecchi 04 Mar '21

04 Mar '21

Hello, supposing I upgrade my env from 4.3 to 4.4. Then I can update my clusters' compatibility from 4.3 to 4.5. I can do it in two ways: 1) select cluster line, "edit" button and change "Compatibility Version" from 4.3 to 4.5 2) select cluster line, "upgrade" button correct? What is the difference? Thanks, Gianluca

1 0

[ANN] oVirt 4.4.5 Eighth Release Candidate is now available for testing
by Lev Veyde 04 Mar '21

04 Mar '21

oVirt 4.4.5 Eighth Release Candidate is now available for testing The oVirt Project is pleased to announce the availability of oVirt 4.4.5 Eighth Release Candidate for testing, as of March 4th, 2021. This update is the fifth in a series of stabilization updates to the 4.4 series. How to prevent hosts entering emergency mode after upgrade from oVirt 4.4.1 Note: Upgrading from 4.4.2 GA or later should not require re-doing these steps, if already performed while upgrading from 4.4.1 to 4.4.2 GA. These are only required to be done once. Due to Bug 1837864 <https://bugzilla.redhat.com/show_bug.cgi?id=1837864> - Host enter emergency mode after upgrading to latest build If you have your root file system on a multipath device on your hosts you should be aware that after upgrading from 4.4.1 to 4.4.5 you may get your host entering emergency mode. In order to prevent this be sure to upgrade oVirt Engine first, then on your hosts: 1. Remove the current lvm filter while still on 4.4.1, or in emergency mode (if rebooted). 2. Reboot. 3. Upgrade to 4.4.5 (redeploy in case of already being on 4.4.5). 4. Run vdsm-tool config-lvm-filter to confirm there is a new filter in place. 5. Only if not using oVirt Node: - run "dracut --force --add multipath” to rebuild initramfs with the correct filter configuration 6. Reboot. 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>. 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 be used in production. Installation instructions For installation instructions and additional information please refer to: https://ovirt.org/documentation/ This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 8.3 or newer * CentOS Linux (or similar) 8.3 or newer This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 8.3 or newer * CentOS Linux (or similar) 8.3 or newer * oVirt Node 4.4 based on CentOS Linux 8.3 (available for x86_64 only) 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 is already available for CentOS Linux 8 - We found a few issues while testing on CentOS Stream so we are still basing oVirt 4.4.5 Node and Appliance on CentOS Linux. Additional Resources: * Read more about the oVirt 4.4.5 release highlights: http://www.ovirt.org/release/4.4.5/ * 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.5/ [2] http://resources.ovirt.org/pub/ovirt-4.4-pre/iso/ -- Lev Veyde Senior Software Engineer, RHCE | RHCVA | MCITP Red Hat Israel <https://www.redhat.com> lev(a)redhat.com | lveyde(a)redhat.com <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

1 0