- Users - oVirt List Archives

[ANN] oVirt 4.4.6 Third Release Candidate is now available for testing
by Lev Veyde 08 Apr '21

08 Apr '21

oVirt 4.4.6 Third Release Candidate is now available for testing The oVirt Project is pleased to announce the availability of oVirt 4.4.6 Third Release Candidate for testing, as of April 8th, 2021. This update is the sixth 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.6 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.6 (redeploy in case of already being on 4.4.6). 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.6 Node and Appliance on CentOS Linux. Additional Resources: * Read more about the oVirt 4.4.6 release highlights: http://www.ovirt.org/release/4.4.6/ * 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.6/ [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

Q: Sparsify/fstrim don't reduce actual disk image size
by Andrei Verovski 08 Apr '21

08 Apr '21

Hi ! I have VM (under oVirt) with single disk thin provision (~600 GB) running NextCloud on Debian 9. Right now VM HD is almost empty. Unfortunately, it occupies 584 GB (virtual size = 600 GB) All partition (except swap and boot) are EXT4 with discard option. in oVirt “enable discard = on”. # fstrim -av runs successfully: /var: 477.6 GiB (512851144704 bytes) trimmed on /dev/mapper/vg--system-lv4--data /boot: 853.8 MiB (895229952 bytes) trimmed on /dev/mapper/vg--system-lv2--boot /: 88.4 GiB (94888611840 bytes) trimmed on /dev/mapper/vg--system-lv3—sys When fstrim runs again, it trims zero. I even run “Sparsify” in oVirt. Unfortunately, actual size is still 584 GB. Here is /etc/fstab /dev/mapper/vg--system-lv3--sys / ext4 discard,noatime,nodiratime,errors=remount-ro 0 1 /dev/mapper/vg--system-lv2--boot /boot ext2 defaults 0 2 /dev/mapper/vg--system-lv4--data /var ext4 discard,noatime,nodiratime 0 2 /dev/mapper/vg--system-lv1--swap none swap sw 0 0 When disk was partitioned/formatted, swap and boot were created first and positioned at the beginning. What is wrong here? Is it possible to fix all this ? Thanks in advance. Andrei

2 3

cannot export - "r.original_template is undefined"
by Diggy Mc 08 Apr '21

08 Apr '21

I cannot export a VM to a data domain. I receive the error: Export VM Failed r.original_template is undefined The VM originated as an OVA provided by a third party. After importing the OVA and customizing the VM, I wanted to export it for backup purposes, but cannot. I am running oVirt 4.4.4. You can download the OVA directly from ERPNext.org if that helps troubleshooting. Download the "Production Image" from here: https://erpnext.org/get-started Any help is appreciated and let me know if additional information is needed.

2 3

oVirt longevity after CentOS 8, RHV changes
by David White 08 Apr '21

08 Apr '21

I'm replying to Thomas's thread below, but am creating a new subject so as not to hijack the original thread. I'm sure that this topic has come up before. I first joined this list last fall, when I began planning and testing with oVirt, but as of the past few weeks, I'm paying closer attention to the mailing list now that I'm actually using oVirt and am getting ready to deploy to a production environment. I'll also try to jump in and help other people as time permits and as my experience grow. I echo Thomas's concerns here. While I'm thankful for Red Hat's gesture to allow people to use up to 16 Red Hat installs at no charge, I'm concerned about the longevity of oVirt, now that Red Hat is no longer going to support RHV going forward. What is the benefit to Red Hat / IBM of supporting this platform now that it is no longer being commercialized as a Red Hat product? What is to prevent Red Hat from pulling the plug on this project, similar to what happened to CentOS 8? As a user of oVirt (4.5, installed on Red Hat 8.3), how can I and others help to contribute to the project to ensure its longevity? Or should I really just go find an alternative in the future? (I had been planning to use oVirt for a while, and did some testing last fall, so the announcement of RHV's (commercial) demise was poor timing for me, because I don't have time to switch gears and change my plans to use something else, like Proxmox or something. From what I've seen, this is a great product, and I guess I can understand Red Hat's decision to pull the plug on the commercial project, now that OpenShift supports full VMs. But my understanding is that OpenShift is a lot more complicated and requires more resources. I really don't need a full kubernetes environment. I just need a stable virtualization platform. Sent with ProtonMail Secure Email. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Thursday, April 1, 2021 5:44 PM, Thomas Hoberg <thomas(a)hoberg.net> wrote: > I personally consider the fact that you gave up on 4.3/CentOS7 before CentOS 8 could have even been remotely reliable to run "a free open-source virtualization solution for your entire enterprise", a rather violent break of trust. > > I understand Redhat's motivation with Python 2/3 etc., but users just don't. Please just try for a minute to view this from a user's perspective. > > With CentOS 7 supported until 2024, we naturally expect the added value on top via oVirt to persist just as long. > > And with CentOS 8 support lasting until the end of this year, oVirt 4.4 can't be considered "Petrus" or a rock to build on. > > Most of us run oVirt simply because we are most interested in the VMs it runs (tenants paying rent). > > We're not interested in keeping oVirt itself stable and from failing after any update to the house of cards. > > And yes, by now I am sorry to have chosen oVirt at all, finding that 4.3 was abandonend before 4.4 or the CentOS 8 below was even stable and long before the base OS ran out of support. > > To the users out there oVirt is a platform, a tool, not a means to itself.

6 9

New Management VLAN for hyperconverged cluster
by David White 08 Apr '21

08 Apr '21

I'm working on setting up my environment prior to production, and have run into an issue. I got most things configured, but due to a limitation on one of my switches, I decided to change the management vlan that the hosts communicate on. Over the course of changing that vlan, I wound up resetting my router to default settings. I have the router operational again, and I also have 1 of my switches operational. Now, I'm trying to bring the oVirt cluster back online.This is oVirt 4.5 running on RHEL 8.3. The old vlan is 1, and the new vlan is 10. Currently, hosts 2 & 3 are accessible over the new vlan, and can ping each other. I'm able to ssh to both hosts, and when I run "gluster peer status", I see that they are connected to each other. However, host 1 is not accessible from anything. I can't ping it, and it cannot get out. As part of my troubleshooting, I've done the following: From the host console, I ran `nmcli connection delete` to delete the old vlan (VLAN 1). I moved the /etc/sysconfig/network-scripts/interface.1 file to interface.10, and edited the file accordingly to make sure the vlan and device settings are set to 10 instead of 1, and I rebooted the host. The engine seems to be running, but I don't understand why. From each of the hosts that are working (host 2 and host 3), I ran "hosted-engine --check-liveliness" and both hosts indicate that the engine is NOT running. Yet the engine loads in a web browser, and I'm able to log into /ovirt-engine/webadmin/. The engine thinks that all 3 hosts is nonresponsive. See screenshot below: [Screenshot from 2021-04-07 17-33-48.png] What I'm really looking for help with is to get the first host back online. Once it is healthy and gluster is healthy, I feel confident I can get the engine operational again. What else should I look for on this host? Sent with ProtonMail Secure Email.

1 1

How to restore Storage Domain from disaster recovery
by miguel.garcia＠toshibagcs.com 07 Apr '21

07 Apr '21

My engine drop dead so had to create a new one and I'm trying to recover virtual drives from previous engine. I'm using next instructions to import storage domain https://www.ovirt.org/develop/release-management/features/storage/importsto… but in order to do it well need to unattach storage domain from previous engine which that is not possible right now since the engine has died. Anyway discarting requirements I got the following warning message: This operation might be unrecoverable and destructive! Storage Domain(s) are already attached to a Data Center. Aproving this operation might cause data corruption if both Data Centers are Active. Do you have an idea how to deactivate a Storage domain without ovirt-engine? Is there any chance to export virtual drives as backups without engine? Thanks in advance.

2 1

oVirt 4.4.4 not dislaying Sign-on Screen
by louisb＠ameritech.net 07 Apr '21

07 Apr '21

I recently installed oVirt 4.4.4, everything appeared to run successfully, however, I’m unable to get the sign-on screen to display on my RHEL 8.3 machine. I did do an install using the remote database installation. I encountered no issue with the install, I can see the “engine” and “ovirt_engine_history” in PostgreSQL 13.3. The tables and table spaces have all been created as designed by the installation process. When I enter the URL that was displayed once the installation completed I get the following information displayed on the screen: Internal Error I’ve tried using the port 443 and port 80 URL and get the same results. The URL are as follows: http://WorkstationName:80/ovirt-engine https://WorkstationName:443/ovirt-engine For three days I’ve been trying to locate logs that will help me located and resolve the problem, but so far I’ve had no luck. Can anyone tell where I should start looking to resolve my issue? I’ve checked several system logs and logs for Apache with luck. What should I be looking for within the logs? What logs should I be looking at? I don’t believe my issue is with the back-end database, I thinks its something with Apache not being able to find the web pages to display. How can I start to investigate my problem an develop a solution? My Linux/RHEL 8.3 OS has all of the latest patches and fixes applied. Thanks

3 10

Experience on using HCI with geo-replication for DR
by wodel youchi 07 Apr '21

07 Apr '21

Hi, Does anyone use ovirt HCI with geo-replication for DR? if yes, could you share your experience? We recently did a setup of 2 HCI platforms, and we configured geo-replication between them. The two platforms were configured with encryption and VDO. When testing the DR, we had some surprises : - Sometimes VMs are not imported - Sometimes some VMs are imported others not - Sometimes VMs are imported without their disks - Sometimes deleted items from the source are imported!!! - And sometimes the imported VMs are corrupted. Regards. <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

2 1

Re: Restored engine backup: The provided authorization grant for the auth code has expired.
by Nicolás 07 Apr '21

07 Apr '21

Hi Shani, El 6/4/21 a las 15:15, Shani Leviim escribió: > Hi, > Did you try to refresh the page and try again? Yes, several times. Also different browsers with no difference. > Can you share a screenshot? Sure. Adding the screenshot in this e-mail. This happens after authenticating like admin (internal) on either the administration panel or the VM portal. Thanks. > > *Regards, > * > *Shani Leviim > * > > > On Tue, Apr 6, 2021 at 4:20 PM Nicolás <nicolas(a)devels.es > <mailto:nicolas@devels.es>> wrote: > > bump... > > El 26/3/21 a las 8:21, Nicolás escribió: > > Please, any help with this? > > > > El 24/3/21 a las 10:05, Nicolás escribió: > >> Hi, > >> > >> I'm restoring a full ovirt engine backup, having used the > --scope=all > >> option, for oVirt 4.3. > >> > >> I restored the backup on a fresh CentOS7 machine. The process went > >> well, but when trying to log into the restored authentication > system > >> I get the following message which won't allow me to log in: > >> > >> The provided authorization grant for the auth code has expired. > >> > >> What does that mean and how can it be fixed? > >> > >> Thanks. > >> > >> Nicolás > >> _______________________________________________ > >> Users mailing list -- users(a)ovirt.org <mailto:users@ovirt.org> > >> To unsubscribe send an email to users-leave(a)ovirt.org > <mailto:users-leave@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/PADF5SSC6XUYC… > > _______________________________________________ > > Users mailing list -- users(a)ovirt.org <mailto:users@ovirt.org> > > To unsubscribe send an email to users-leave(a)ovirt.org > <mailto:users-leave@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/5VYLMSCUGDDBW… > _______________________________________________ > Users mailing list -- users(a)ovirt.org <mailto:users@ovirt.org> > To unsubscribe send an email to users-leave(a)ovirt.org > <mailto:users-leave@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/N6Q4EEC3KKK7P… >

1 0

Engine Upgrade to 4.4.5 Version Number Question
by Nur Imam Febrianto 06 Apr '21

06 Apr '21

I’m currently trying to upgrade our cluster from 4.4.4 to 4.4.5. All using oVirt Node. All host are successfully upgraded to 4.4.5 (I can see the image layer was changed from 4.4.4 to 4.4.5, cockpit also shows same version), but in Engine VM, already run engine-upgrade-check, upgrading ovirt-setup, running engine-setup successfully, reboot the engine but whenever I open the engine web page, it still showing Version 4.4.4.5-1.el8. Is this version correct ? Because my second Cluster that use their own hosted engine shows different version (4.4.5.11-1.el8). Anybody having a same issues like me ? Thanks before. Regards, Nur Imam Febrianto

1 0

Re: Upgrading DWH from 4.4.4 to 4.4.5
by Yedidyah Bar David 06 Apr '21

06 Apr '21

On Thu, Mar 18, 2021 at 6:47 PM Nur Imam Febrianto <nur_imam(a)outlook.com> wrote: > > Hi, > > > > I’m currently trying to upgrade my oVirt Cluster into 4.4.5. Hosted engine upgrade work successfully. But whenever I tried upgrading DWH on separate machine it keep giving me this error : Failed to execute stage 'Misc configuration': 'OVESETUP_SYSTEM/selinuxBooleans' > > > > In engine-setup log : > > > > 2021-03-18 23:34:10,976+0700 DEBUG otopi.context context._executeMethod:145 method exception > > Traceback (most recent call last): > > File "/usr/lib/python3.6/site-packages/otopi/context.py", line 132, in _executeMethod > > method['method']() > > File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine-common/apache/selinux.py", line 40, in _misc > > osetupcons.SystemEnv.SELINUX_BOOLEANS > > KeyError: 'OVESETUP_SYSTEM/selinuxBooleans' > > 2021-03-18 23:34:10,977+0700 ERROR otopi.context context._executeMethod:154 Failed to execute stage 'Misc configuration': 'OVESETUP_SYSTEM/selinuxBooleans' > > > > Using CentOS 8.3 as separate DWH machine. Anybody maybe can help me ? > > Thanks before. Sorry, this is looks like a bug, caused by [1]. Would you like to report it on bugzilla? I think a workaround is to run engine-setup like this: # engine-setup --otopi-environment=OVESETUP_SYSTEM/selinuxBooleans=multi-str:\ The shell will prompt with '> '. Just press Enter. Martin - seems like I was wrong when commenting on [1] that it seems harmless... Marcin: we should probably add separate-dwh to ovirt-system-tests or something like that. [1] https://gerrit.ovirt.org/c/ovirt-engine/+/113263 Sorry and best regards, -- Didi

2 2

4.4 -> 4.3
by KSNull Zero 06 Apr '21

06 Apr '21

Hi, What is the most simpliest way to backward migrate VMs from oVirt 4.4 to oVirt 4.3 ? Is it possible to use export domain or there are some other ways ? Thank you.

3 4

EMC Unity300 with iSCSI
by Dan Yasny 06 Apr '21

06 Apr '21

Hi all, I've got a brand new Unity300 that I'm trying to hook up to a 4.3 setup with iSCSI. The way I have it organized is simple: - each hypervisor has two NICs set to 192.168.10.x and 192.168.20.x - the SAN has 4 ports on each controller (A and B), amounting to 8 portal IPs I can log into. The problem with the EMC is that at any time, only either A or B addresses would be active, so I can only login to 4 out of the 8 addresses, while the engine, in order to add all the possible target IQNs needs to log into all 8 of them. I've been trying to find a solution for a while now, EMC generally suggest I use powerpath (not an option here obviously). Did anyone set up one of these EMC boxes with oVirt before? Thanks

1 0

Accidentally changed VM Assigned Bridge for Hosted-Engine
by phunyguy＠neverserio.us 06 Apr '21

06 Apr '21

Hello, exactly as the title suggests, I did something stupid, and I am not sure how to fix this. I also cannot be certain that this was the exact cause of the problem, as I was troubleshooting another issue with a different VM refusing to start. What I did by accident, was selected the hosted-engine VM, rather than the VM I was attempting to troubleshoot, and changed the assigned network of the VM adapter to something else, and of course, lost connectivity to the engine VM. This caused HA to kick in and restart the engine, however, like the other VM, it is now refusing to start. Can anyone give me any pointers? agent/broker/vdsm.log are not showing anything useful that I can see. Thanks in advance. -phunyguy

2 1

Problem-VDSM command failed:Received fatal alert certificate_expire
by fmendoza＠red.com.sv 06 Apr '21

06 Apr '21

Recently Ovirt sent certificate expiration messages. And it does not let me manage the server VMs, I have looked for information about this and I can not find something that is clear. The version of Ovirt that I own is 3.6.3.4-1.el7.cents. I have at least 4 operational VMs of vital importance. Thanks for the support

2 1

Problems after upgrade from 4.4.3 to 4.4.4
by tferic＠swissonline.ch 06 Apr '21

06 Apr '21

Hi I have problems after upgrading my 2-node cluster from 4.4.3 to 4.4.4. Initially, I performed the upgrade of the oVirt hosts using the oVirt GUI (I wasn't planning any changes). It appears that the upgrade broke the system. On host1, the ovirt-engine was configured to run on the oVirt host itself (not self-hosted engine). After the upgrade, the oVirt GUI didn't load in the Browser anymore. I tried to fix the issue by migrating to self-hosted engine, which did not work, so I ran engine restore and engine-setup in order to get back to the initial state. I am now able to login to the oVirt GUI again, but I am having the following problems: host1 is in status "Unassigned", and it has the SPM role. It cannot be set to maintenance mode, nor re-installed from GUI, but I am able to reboot the host from oVirt. All Storage Domains are inactive. (all NFS) In the /var/log/messages log, I can see the following message appearing frequently: "vdsm[5935]: ERROR ssl handshake: socket error, address: ::ffff:192.168.100.61" The cluster is down and no VM's can be run. I don't know how to fix either of the issues. Does anyone have an idea? I am appending a tar file containing log files to this email. http://gofile.me/5fp92/d7iGEqh3H <http://gofile.me/5fp92/d7iGEqh3H> Many thanks Toni

2 7

No option to remove OpenStack Glance storage domain.
by Gary Taylor 05 Apr '21

05 Apr '21

Hi, I was playing around a few months ago and added an ovirt-image-repository storage domain. There wasn't a real purpose for doing it, just trying to learn and play around. I tried to remove it earlier but couldn't figure out how because the Remove button is greyed out. I got busy and forgot about it. I am trying to clean it up now but the Remove button is still greyed out for that domain. How do I get rid of it now? It isn't being used. It's unattached. I'm the admin. https://imgur.com/KBKUu16.png oVirt Open Virtualization Manager Software Version:4.4.4.7-1.el8 Thank-you, Gary

2 2

Hosted-Engine vs Standalone Engine
by Ian Easter 05 Apr '21

05 Apr '21

Hello Folks, I have had to install a Hosted-Engine a few times in my environment. There have been some hardware issues and power issues that left the HE unrecoverable. In this situation, would the Standalone Engine install be more viable and less prone to become inoperable due to the previous issues? My assumption would be to have a head baremetal server run the Engine to control and maintain my blades. *Thank you,* *Ian*

3 2

Error while updating volume meta data: [Errno 17] File exists", ), code = 208
by adrianquintero＠gmail.com 05 Apr '21

05 Apr '21

Hi, I am encountering the following error every hour in the ovirt-engine.log file and I can also see the same in the oVirt engine UI --------------------------------------- 2021-04-05 01:49:20,072-04 ERROR [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-76) [7dd3eb3d] Command 'SetVolumeDescriptionVDSCommand( SetVolumeDescriptionVDSCommandParameters:{storagePoolId='dfe84316-bbdb-11ea-beb6-00163e1ab088', ignoreFailoverLimit='false', storageDomainId='9ed31575-9cc4-4b05-a5d9-23d21d6e915e', imageGroupId='2af73aad-5079-4583-824c-a93b20b93835', imageId='ad5a523c-fdc1-49dd-900b-73f801564f1d'})' execution failed: IRSGenericException: IRSErrorException: Failed to SetVolumeDescriptionVDS, error = Error while updating volume meta data: ("(u'/rhev/data-center/mnt/glusterSD192.168.0.4:_data1/9ed31575-9cc4-4b05-a5d9-23d21d6e915e/images/2af73aad-5079-4583-824c-a93b20b93835/ad5a523c-fdc1-49dd-900b-73f801564f1d',)[Errno 17] File exists",), code = 208 2021-04-05 02:49:14,333-04 ERROR [org.ovirt.engine.core.bll.gluster.GlusterGeoRepSyncJob] (DefaultQuartzScheduler3) [2bf694b9] VDS error Command execution failed: rc=2 out='geo-replication command failed\n' err='' 2021-04-05 02:49:20,332-04 ERROR [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-5) [6b6dd1af] Command 'SetVolumeDescriptionVDSCommand( SetVolumeDescriptionVDSCommandParameters:{storagePoolId='dfe84316-bbdb-11ea-beb6-00163e1ab088', ignoreFailoverLimit='false', storageDomainId='9ed31575-9cc4-4b05-a5d9-23d21d6e915e', imageGroupId='2af73aad-5079-4583-824c-a93b20b93835', imageId='ad5a523c-fdc1-49dd-900b-73f801564f1d'})' execution failed: IRSGenericException: IRSErrorException: Failed to SetVolumeDescriptionVDS, error = Error while updating volume meta data: ("(u'/rhev/data-center/mnt/glusterSD/192.168.0.4:_data1/9ed31575-9cc4-4b05-a5d9-23d21d6e915e/images/2af73aad-5079-4583-824c-a93b20b93835/ad5a523c-fdc1-49dd-900b-73f801564f1d',)[Errno 17] File exists",), code = 208 --------------------------------------- I looked up the mentioned error codes but not sure if these are the correct ones: https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.3/ht… --------------------------------------- 17 > VDS_MAINTENANCE_FAILED > Error > Failed to switch Host ${VdsName} to Maintenance mode. 208 > PROVIDER_UPDATE_FAILED > Error > Failed to update provider ${ProviderName}. (User: ${UserName}) --------------------------------------- From the Engine UI's event tab I can see: --------------------------------------- Failed to update VMs/Templates OVF data for Storage Domain data1 in Data Center Default. Failed to update OVF disks 2af73aad-5079-4583-824c-a93b20b93835, OVF data isn't updated on those OVF stores (Data Center Default, Storage Domain data1). VDSM command SetVolumeDescriptionVDS failed: Error while updating volume meta data: ("(u'/rhev/data-center/mnt/glusterSD/192.168.0.4:_data1/9ed31575-9cc4-4b05-a5d9-23d21d6e915e/images/2af73aad-5079-4583-824c-a93b20b93835/ad5a523c-fdc1-49dd-900b-73f801564f1d',)[Errno 17] File exists",) --------------------------------------- I know the error belongs to the "data1" storage domain and this is a 12 node Distributed Replicate volume (Replicat 3) HCI. If I try to update the OVF using the UI I get the following log entries in the engine --------------------------------------- 2021-04-05 03:20:03,101-04 WARN [org.ovirt.engine.core.dal.job.ExecutionMessageDirector] (default task-1183) [6761980f-dcf6-400e-bfd8-fd2c70e7569a] The message key 'UpdateOvfStoreForStorageDomain' is missing from 'bundles/ExecutionMessages' 2021-04-05 03:20:03,178-04 INFO [org.ovirt.engine.core.bll.storage.domain.UpdateOvfStoreForStorageDomainCommand] (default task-1183) [6761980f-dcf6-400e-bfd8-fd2c70e7569a] Lock Acquired to object 'EngineLock:{exclusiveLocks='[9ed31575-9cc4-4b05-a5d9-23d21d6e915e=STORAGE]', sharedLocks=''}' 2021-04-05 03:20:03,204-04 INFO [org.ovirt.engine.core.bll.storage.domain.UpdateOvfStoreForStorageDomainCommand] (default task-1183) [6761980f-dcf6-400e-bfd8-fd2c70e7569a] Running command: UpdateOvfStoreForStorageDomainCommand internal: false. Entities affected : ID: 9ed31575-9cc4-4b05-a5d9-23d21d6e915e Type: StorageAction group MANIPULATE_STORAGE_DOMAIN with role type ADMIN 2021-04-05 03:20:03,505-04 ERROR [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-62) [13f4ac4f] Failed in 'SetVolumeDescriptionVDS' method 2021-04-05 03:20:03,512-04 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-62) [13f4ac4f] EVENT_ID: IRS_BROKER_COMMAND_FAILURE(10,803), VDSM command SetVolumeDescriptionVDS failed: Error while updating volume meta data: ("(u'/rhev/data-center/mnt/glusterSD/192.168.0.4:_data1/9ed31575-9cc4-4b05-a5d9-23d21d6e915e/images/2af73aad-5079-4583-824c-a93b20b93835/ad5a523c-fdc1-49dd-900b-73f801564f1d',)[Errno 17] File exists",) 2021-04-05 03:20:03,513-04 ERROR [org.ovirt.engine.core.vdsbroker.irsbroker.SetVolumeDescriptionVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-62) [13f4ac4f] Command 'SetVolumeDescriptionVDSCommand( SetVolumeDescriptionVDSCommandParameters:{storagePoolId='dfe84316-bbdb-11ea-beb6-00163e1ab088', ignoreFailoverLimit='false', storageDomainId='9ed31575-9cc4-4b05-a5d9-23d21d6e915e', imageGroupId='2af73aad-5079-4583-824c-a93b20b93835', imageId='ad5a523c-fdc1-49dd-900b-73f801564f1d'})' execution failed: IRSGenericException: IRSErrorException: Failed to SetVolumeDescriptionVDS, error = Error while updating volume meta data: ("(u'/rhev/data-center/mnt/glusterSD/192.168.0.4:_data1/9ed31575-9cc4-4b05-a5d9-23d21d6e915e/images/2af73aad-5079-4583-824c-a93b20b93835/ad5a523c-fdc1-49dd-900b-73f801564f1d',)[Errno 17] File exists",), code = 208 2021-04-05 03:20:03,538-04 WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-62) [13f4ac4f] EVENT_ID: UPDATE_FOR_OVF_STORES_FAILED(1,016), Failed to update OVF disks 2af73aad-5079-4583-824c-a93b20b93835, OVF data isn't updated on those OVF stores (Data Center Default, Storage Domain data1). 2021-04-05 03:20:03,513-04 WARN [org.ovirt.engine.core.bll.storage.ovfstore.ProcessOvfUpdateForStorageDomainCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-62) [13f4ac4f] failed to update domain '9ed31575-9cc4-4b05-a5d9-23d21d6e915e' ovf store disk '2af73aad-5079-4583-824c-a93b20b93835' 2021-04-05 03:20:03,558-04 WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-62) [13f4ac4f] EVENT_ID: UPDATE_OVF_FOR_STORAGE_DOMAIN_FAILED(190), Failed to update VMs/Templates OVF data for Storage Domain data1 in Data Center Default. --------------------------------------- Any ideas on how to overcome this issue? Thanks, Adrian

1 0

Upgrade to release for oVirt 4.4.5 failing
by Gary Pedretty 05 Apr '21

05 Apr '21

Upgraded hosted-engine installation to latest version 4.4.5 today and engine will not come online. It starts and I can ssh and connect via cockpit, but it never passes liveliness check according to command line vm-status and Web portal for engine never loads. All processes appear to be working and nothing jumps out to me in the logs but ha agent keeps rebooting it on different hosts with the same result. 8 host in the cluster all are also updated to the latest updates across the board. This is Centos Stream 8 Ideas? Gary _______________________________ Gary Pedretty IT Manager Ravn Alaska Office: 907-266-8451 Mobile: 907-388-2247 Email: gary.pedretty(a)ravnalaska.com "We call Alaska......Home!" Ravn Alaska CONFIDENTIALITY NOTICE: The information in this email may be confidential and/or privileged. This email is intended to be reviewed by only the individual or organization named above. If you are not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any review, dissemination, forwarding or copying of the email and its attachments, if any, or the information contained herein is prohibited. If you have received this email in error, please immediately notify the sender by return email and delete this email from your system. Thank you.

4 3

Standard operating procedure for a node failure on HCI required
by Thomas Hoberg 04 Apr '21

04 Apr '21

oVirt may have started as a vSphere 'look-alike', but it graduated to a Nutanix 'clone', at least in terms of marketing. IMHO that means the 3-node hyperconverged default oVirt setup (2 replicas and 1 arbiter) deserves special love in terms of documenting failure scenarios. 3-node HCI is supposed to defend you against long-term effects of any single point of failure. There is no protection against the loss of dynamic state/session data, but state-free services should recover or resume: that's what it's all about. Sadly, what I find missing in the oVirt and Gluster documentation is an SOP (standard operating procedure) that one should follow in case of a late-night/early-morning on-call wakeup when one of those three HCI nodes should have failed... dramatically or via a 'brown out' e.g. where only the storage part was actually lost. My impression is that the oVirt and Gluster teams are barely talking, but in HCI that's fatal. And I sure can't find those recovery procedures, not even in the commercial RH documents. So please, either add them or show me where I missed them.

2 2

oVirt cannot start VM after reboot with cluster chipset set to i440fx
by Joris Dobbelsteen 03 Apr '21

03 Apr '21

Hi I’m running a oVirt 4.4.4 installation (with a single node and single cluster). After a recent reboot, I’m trying to start the VMs, which fails with: VM udc1 is down with error. Exit message: XML error: The device at PCI address 0000:00:02.0 cannot be plugged into the PCI controller with index='0'. It requires a controller that accepts a pcie-root-port.. Dmesg shows: Mar 15 17:07:48 ovirt1 journal[2245]: internal error: a PCI slot is needed to connect a PCI controller model='pcie-root-port', but none is available, and it cannot be automatically added The issue seems with the “custom chipset/firmware” set to i440fx rather than Q35 for the cluster. The VM is configured to cluster default. The rationale for running i440 is that Debian doesn’t actually support Q35 with cloud-init, leading to an uninitialized VM. Since I’m running mainly Debian/Ubuntu VMs it’s needed to have i440 set instead. The error is also visible in oVirt Manager, when checking out the “Vm Devices” for the failed VM (all of them). The workaround for starting the VM seems to be to do: Edit -> System -> Advanced Parameters -> Custom Chipset/Firmware Type -> Change to Q35 and back to cluster default (being i440). This resets the list to remove the need for a pcie-root-port. I gives the impressions that there is an initialization error of the ovirt engine, where the Q35 devices are loaded in incorrectly or maybe not fetched as the right cluster default. I’ve not tested what happens if the configured for i440fx is applied at VM level, rather than cluster level. Does anyone know how to resolve this for future versions? Or what can be done to make this work after a reboot? Best regards, Joris

1 0

VMConsole: Certificate invalid: name is not a listed principal
by Stefan Seifried 02 Apr '21

02 Apr '21

Hi, I recently tried out the vm console feature on an ovirt eval environment running 4.4.4.7-1.el8: 1.) pasted the pub-key of my local user into the web interface (User->Options) 2.) connected via ssh like so ssh -p 2222 sevm -l ovirt-vmconsole 3.) got the list of all the vm's :) 4.) choose a vm with a virtio serial console enabled 5.) Certificate invalid :( --- Please, enter the id of the Serial Console you want to connect to. To disconnect from a Serial Console, enter the sequence: <Enter><~><.> SELECT> 24 Certificate invalid: name is not a listed principal Host key verification failed. Connection to sevm closed. --- I guess somethings wrong in "/etc/pki/ovirt-vmconsole". Is there any additional information I can get out from the logs or the console proxy (e.g. the "name" which is not a listed principal)? To be honest I never really worked with SSH certificates, so I fear I will do something stupid if I try to fix this head on. So any advice or help on this issue is appreciated. Thanks, Stefan

1 0

Re: Power failure makes cluster and hosted engine unusable
by Thomas Hoberg 01 Apr '21

01 Apr '21

I am glad you got it done! I find that oVirt resembles more an adventure game (with all its huge emotional rewards, once you prevail), than a streamlined machine, that just works every time you push a button. Those are boring, sure, but really what I am looking for when the mission is to run infrastructure.

1 0

Re: Power failure makes cluster and hosted engine unusable
by Roman Bednar 01 Apr '21

01 Apr '21

Hi Seann, On Mon, Mar 29, 2021 at 8:31 PM Seann G. Clark via Users <users(a)ovirt.org> wrote: > All, > > > > After a power failure, and generator failure I lost my cluster, and the > Hosted engine refused to restart after power was restored. I would expect, > once storage comes up that the hosted engine comes back online without too > much of a fight. In practice because the SPM went down as well, there is no > (clearly documented) way to clear any of the stale locks, and no way to > recover both the hosted engine and the cluster. > Could you provide more details/logs on storage not coming up? Also more information about the current locks would be great, is there any procedure you tried that did not work for cleaning those up? I have spent the last 12 hours trying to get a functional hosted-engine > back online, on a new node and each attempt hits a new error, from the > installer not understanding that 16384mb of dedicated VM memory out of > 192GB free on the host is indeed bigger than 4096MB, to ansible dying on > an error like this “Error while executing action: Cannot add Storage > Connection. Storage connection already exists.” > > The memory error referenced above shows up as: > > [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": > "Available memory ( {'failed': False, 'changed': False, 'ansible_facts': > {u'max_mem': u'180746'}}MB ) is less then the minimal requirement (4096MB). > Be aware that 512MB is reserved for the host and cannot be allocated to the > engine VM."} > > That is what I typically get when I try the steps outlined in the KB > “CHAPTER 7. RECOVERING A SELF-HOSTED ENGINE FROM AN EXISTING BACKUP” from > the RH Customer portal. I have tried this numerous ways, and the cluster > still remains in a bad state, with the hosted engine being 100% inoperable. > This could be a bug in the ansible role, did that happen during "hosted-engine --deploy" or other part of the recovery guide? Provide logs here as well please, its seems like a completely separate issue though. > > What I do have are the two host that are part of the cluster and can host > the engine, and backups of the original hosted engine, both disk and > engine-backup generated. I am not sure what I can do next, to recover this > cluster, any suggestions would be apricated. > > > > Regards, > > Seann > > > > > _______________________________________________ > 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/JLDIFTKYDPQ6Y… >

3 3