April 2021 - Users - oVirt List Archives

Introduction & general question about oVirt
by Nicolas Kovacs 20 Apr '21

20 Apr '21

Hi, I'm a 53-year old Austrian living in Montpezat, a small village in South France. I'm an IT professional with a focus on Linux and free software, and I've been a Linux user since Slackware 7.1. I'm doing web & mail hosting for myself and several small structures like our local school and a handful of local companies. Up until recently these hostings have happened on "bare metal" root servers using CentOS 7. One main server is hosting most of the stuff: WordPress sites, one OwnCloud instance, Dolibarr management software, GEPI learning platform, Postfix/Dovecot mail server, Roundcube webmail, etc. This setup has become increasingly problematic to manage, since applications have more and more specific requirements, like different versions of PHP and corresponding modules. So I decided to split everything up nicely into a series of virtual machines, each one with a nicely tailored setup. I have a couple of sandbox servers, one public and one local, running Oracle Linux 7 (a RHEL clone like CentOS). I played around with it, and KVM-based virtualization already works quite nicely. While looking for documentation, I stumbled over oVirt, which I didn't even know existed until last week. Before I dive head first into it, I'd be curious to know a few general things. 1. Would it be overkill for a small structure like mine? 2. Will I be able to do HA on a series of modest KVM-capable root servers even if they are located in different datacenters across different countries? 3. One problem I couldn't resolve using a bone-headed keep-it-simple KVM setup is backup. For my bare-metal servers I've been using incremental backups using Rsnapshot for years. Here's a blog article I wrote on the subject: https://blog.microlinux.fr/rsnapshot-centos-7/ Unfortunately I can't use this approach with huge QCOW images, at least not without jumping through burning loops. Is there an easy way to perform remote incremental backups with oVirt? BTW, I took a peek at Proxmox and Ceph, but I admit I'm a die-hard RHEL-clone user. Cheers from the sunny South of France, Niki -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Site : https://www.microlinux.fr Blog : https://blog.microlinux.fr Mail : info(a)microlinux.fr Tél. : 04 66 63 10 32 Mob. : 06 51 80 12 12

4 3

Upgrading single host ovirt "clusters" to v4.5 via command line?
by Gilboa Davara 19 Apr '21

19 Apr '21

Hello all, As the title suggests I have a couple of single-host hyper converged setups, mostly used for testing. As I cannot use the GUI cluster upgrade method on a single host (it requires me to reboot the host, which will require me to shutdown the hosted engine), is there any method to upgrade the cluster / data-center via command line in maintenance=global mode? Beyond that, can I use the same method on my production setups? (multi-node, gluster based setups). Thanks, Gilboa

1 0

Re: FreeBSD 13 and virtio
by Nir Soffer 19 Apr '21

19 Apr '21

On Mon, Apr 19, 2021 at 5:11 PM Nur Imam Febrianto <nur_imam(a)outlook.com> wrote: > I’m having an issue, if I’m using q35 and using virtio disk + virtio > network adapter, the guest OS wont detect any disk. I440fx work fine. This > issue happened on FBSD 12.2 too. On FBSD 13 release note, it was said q35 > should working okay now, a lot of people using pc-q35-4.2 machine type > confirm it works now on vanilla KVM. But seems it still doesn’t work on > oVirt. > It will help if you can file a bug about this, and attach a vm xml that works outside of ovirt (e.g using virt-manger, or virsh), so we can compare to our vm xml. Nir > > > *From: *Sandro Bonazzola <sbonazzo(a)redhat.com> > *Sent: *19 April 2021 19:35 > *To: *Nur Imam Febrianto <nur_imam(a)outlook.com> > *Cc: *oVirt Users <users(a)ovirt.org> > *Subject: *Re: [ovirt-users] FreeBSD 13 and virtio > > > > Hi, can you please provide some more details on the issues you're seeing? > > > > Il giorno sab 17 apr 2021 alle ore 06:35 Nur Imam Febrianto < > nur_imam(a)outlook.com> ha scritto: > > Hi, > > > > Any body already try FBSD 13 sing q35 + virtio disk + virtio net ? > > I cant get it working, it should be fine in FBSD 13, lastly on FBSD 12 it > was the q35 spec issue with the kernel. Lot of people now it works nicely > on FBSD 13, but I cant get it working on oVirt. > > > > Thanks before. > > > > Regards, > > Nur Imam Febrianto > > > > _______________________________________________ > 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 > <https://apac01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovir…> > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > <https://apac01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovir…> > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/FCPJBK3AV4BSB… > <https://apac01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.ov…> > > > > > -- > > *Sandro Bonazzola* > > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > > Red Hat EMEA > <https://apac01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.redh…> > > sbonazzo(a)redhat.com > > > <https://apac01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.redh…> > > > *Red Hat respects your work life balance. Therefore there is no need to > answer this email out of your office hours. > <https://apac01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmojo.red…>* > > > > > _______________________________________________ > 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/ADIC2ERITKAMC… >

1 0

How to Upgrade Node with Local Storage ?
by Nur Imam Febrianto 19 Apr '21

19 Apr '21

Hi, How we can upgrade oVirt Node that using Local Storage ? Seems I cant find any good documentation about this. Planning to upgrade one 4.4.4 node with local storage to 4.4.5. Thanks before. Regards, Nur Imam Febrianto

1 0

Re: FreeBSD 13 and virtio
by Sandro Bonazzola 19 Apr '21

19 Apr '21

Hi, can you please provide some more details on the issues you're seeing? Il giorno sab 17 apr 2021 alle ore 06:35 Nur Imam Febrianto < nur_imam(a)outlook.com> ha scritto: > Hi, > > > > Any body already try FBSD 13 sing q35 + virtio disk + virtio net ? > > I cant get it working, it should be fine in FBSD 13, lastly on FBSD 12 it > was the q35 spec issue with the kernel. Lot of people now it works nicely > on FBSD 13, but I cant get it working on oVirt. > > > > Thanks before. > > > > Regards, > > Nur Imam Febrianto > > > _______________________________________________ > 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/FCPJBK3AV4BSB… > -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/> *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours. <https://mojo.redhat.com/docs/DOC-1199578>*

2 1

Why and when does oVirt make a compute host part of the HCI Gluster?
by Thomas Hoberg 19 Apr '21

19 Apr '21

My understanding is that in a HCI environment, the storage nodes should be rather static, but that the pure compute nodes, can be much more dynamic or opportunistic: actually those should/could even be switched off and restarted as part of oVirt's resource optimization. The 'pure compute' nodes fall into two major categories, a) those who can run the management engine, b) those who can't. What I don't quite understand is why both types seem to be made 'gluster peers', when they don't contribute storage bricks: shouldn't they just be able to mount Gluster volumes? The reason for my concern is that I actually want to manage these computing hosts with much more freedom. I may have them join and take on workloads, or not and I may want to shut them down. To my irritation I sometimes even see these 'missing' hosts being considered for quorum decisions or being listed e.g. when I do a 'gluster volume engine status'. I find hosts there, that definitely are not contributing bricks to 'engine' (or any other volume). Then I'm not even sure I have consistent behavior when I remove hosts from oVirt: I'd swear that quite a few remain as Gluster peers, even if they are completely invisible from the oVirt GUI (while hosted-engine --vm-status will still list them). So what's the theory here and would it be a bug if removed hosts remain gluster members?

2 3

Expand gluster volumes
by David White 19 Apr '21

19 Apr '21

Is it possible to expand an existing gluster volume? I have a hyperconverged environment, and have enough space right now, but I'm going to have to significantly over-provision my environment. The vast majority of our customers are using a small fraction of the amount of space that they are technically allocated, but we still need to make that space available to them. As a result, I'd like to plan ahead, and go ahead and have a plan to add storage later down the road. I'd like to plan to shut down each server in the cluster (individually, not at once), add storage, and then bring them back online. Once all 3 are back online with the additional storage, I'd like to expand the gluster volume to use the additional space. Is that possible? How? Sent with ProtonMail Secure Email.

3 3

After upgrade to 4.4.5: cockpit login error
by ovirt＠r5d.de 18 Apr '21

18 Apr '21

Hello, 1. Installation ovirt node iso 4.4.4 2. dnf upgrade -> 4.4.5 -> error login cockpit: Message: pr 18 13:02:53 h2 systemd[1]: cockpit-wsinstance-https-factory(a)2-7789-995.service: Succeeded. Apr 18 13:02:53 h2 cockpit-ws[7796]: cockpit-ws: Failed to open certificate file /run/cockpit/tls/e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855: No such file or directory Apr 18 13:02:55 h2 cockpit-ws[7796]: cockpit-session: open(/var/log/btmp) failed: Permission denied What is todo? Thx.

1 0

Ovirt and gluster 9 volume
by eevans＠digitaldatatechs.com 17 Apr '21

17 Apr '21

My setup is 3 Centos 7 servers hyper-converged with a 4th stand alone engine server. My issue is Ovirt is reading the cluster disk as 49GiB instead of 5.5 TB is should be. One server has a 928 GB raid 5 volume, the second has a 7,7 TB raid 10 volume and the third has a 5.5 TB raid 10 volume. How is Ovirt translating this to 49 GiB?? Here is a link to the screen shots for verification. https://1drv.ms/u/s!AvgvEzKKSZHbhLIrRBvQRLmoZOeEyw?e=rO83vw Logs look good unless I missed something. Any help is appreciated. Eric

2 2

Intel Optane DC Persistent Memory - Ovirt / RHEV
by jorgevisentini＠gmail.com 17 Apr '21

17 Apr '21

What is the usage experience of the Intel Optane DC Persistent Memory with oVirt? It's compatible? Have any document for configuration?

3 3

Remote VNC
by David White 17 Apr '21

17 Apr '21

I'm running into the issue described in this thread: https://lists.ovirt.org/archives/list/users@ovirt.org/message/KT3B6N3UZ3DS3… In short, I have ssh to the datacenter. I can ssh to a public IP address with the "-D 8080" option to forward local port 8080 act as a SOCKS proxy. I then edit my local computer's proxy settings and set the SOCKS host to 8080. So this is a system-wide change. I'm not setting the SOCKS proxy in the browser preferences. After I do all that, I'm able to use my browser to get to the engine web UI, and I'm able to login. However, the console for each VM isn't working. In the thread I linked to above, Alan says to do this: 2. SSH to the hypervisor tunneling a local port to that remote console port. 3. Click on the console link in the Engine and locally save the vv file.4. Edit the vv file; change host to localhost and port to whichever port you configured for the local side of the tunnel. Question: I'm confused why I need to tunnel a local port to the remote console port, if I'm already tunneling port 8080 to the host. Question: I don't have much experience with ssh port forwarding. If I already have the SOCKS proxy working, how, exactly, would I accomplish step #2? With the 8080 socks proxy working, I've now tried to run this command: ssh -L 5902:127.0.0.1:5901 username@ovirt-host-ip And in this case, I'm "assuming" that 5902 is going to listen on my local computer, and that I need to edit the vv file to connect to 127.0.0.1, port 5902. That's not working. Maybe I don't understand how SOCKS proxies work, but I was hoping / under the impression that all of my network traffic would go through the ssh tunnel on port 8080, and that vnc would work at that point. Sent with ProtonMail Secure Email.

1 1

FreeBSD 13 and virtio
by Nur Imam Febrianto 17 Apr '21

17 Apr '21

Hi, Any body already try FBSD 13 sing q35 + virtio disk + virtio net ? I cant get it working, it should be fine in FBSD 13, lastly on FBSD 12 it was the q35 spec issue with the kernel. Lot of people now it works nicely on FBSD 13, but I cant get it working on oVirt. Thanks before. Regards, Nur Imam Febrianto

1 0

Re: Strange Issue with imageio
by Nir Soffer 17 Apr '21

17 Apr '21

On Fri, Apr 16, 2021 at 7:22 PM Nur Imam Febrianto <nur_imam(a)outlook.com> wrote: > After upgrading to 4.4.5 from 4.4.4, I’m having a strange issue. Whenever I try to upload something (image or iso) to Storage Domain without clicking Test Connection, upload process wont start. It will shows the file area already uploaded but no upload process. When I try to open the log, seems if I don’t click test connection, it wont open any session in imageio. Upload process will going normally, if I click Test connection first and proceed to upload. Please file ovirt-engine bug, testing the connection should not be required for upload. > Any idea why this is happening ? Don’t have this issue before in 4.4.4. Rebooting the engine doesn’t help either. This is most likely a bug introduced in engine 4.4.5. Nir

2 1

Odd question: changing network MTU
by Chris Adams 16 Apr '21

16 Apr '21

I have an oVirt 4.3 cluster, running in one location. I have to move it to another location. I've got a couple of 1G links between the sites, and that's enough bandwidth for this (at least temporarily), but... I have my iSCSI networks defined with a MTU of 9000, and it turns out the site-to-site links only allow 1500 (and these links are going away after this is done, so I don't think either carrier would be interested in changing things to support larger). Because of that, the storage won't connect up. I tried going "under the hood" and setting a firewalld rule to force the MSS to a smaller value, but that didn't seem to get it. What happens if I change the MTU of an active iSCSI network in oVirt? I could just go manually change it on each node's iSCSI interfaces, but I'm not sure if oVirt might change it back. Also, I'm not sure what would happen to open iSCSI TCP connections (would they reduce gracefully). Any other suggestions/tips/etc.? I'd like to make this as transparent as possible, so was hoping to live-migrate VMs and storage. -- Chris Adams <cma(a)cmadams.net>

3 5

Strange Issue with imageio
by Nur Imam Febrianto 16 Apr '21

16 Apr '21

Hi, After upgrading to 4.4.5 from 4.4.4, I’m having a strange issue. Whenever I try to upload something (image or iso) to Storage Domain without clicking Test Connection, upload process wont start. It will shows the file area already uploaded but no upload process. When I try to open the log, seems if I don’t click test connection, it wont open any session in imageio. Upload process will going normally, if I click Test connection first and proceed to upload. Any idea why this is happening ? Don’t have this issue before in 4.4.4. Rebooting the engine doesn’t help either. Regards, Nur Imam Febrianto

1 0

Re: Expand gluster volumes
by David White 16 Apr '21

16 Apr '21

Sorry, I meant to reply-all, to Strahil's most recent message. So I'm doing so now. In addition to my comments below, this StackOverflow thread summarizes what I have in mind: https://stackoverflow.com/questions/43756405/extend-glusterfs-on-top-of-lvm Sent with ProtonMail Secure Email. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Friday, April 16, 2021 5:33 AM, David White <dmwhite823(a)protonmail.com> wrote: > I don't think I would have the capability to take on the expense of adding two more servers to my environment, on top of the 4th server I already have, right now. > > I realize the following isn't recommended, but would it be possible to, instead, intentionally degrade the gluster cluster by shutting 1 of the hosts down (put it in maintenance mode), add storage, and bring it back online? > > Perhaps that would be a better approach, rather than try to shift things around with a 4th server. > > Sent with ProtonMail Secure Email. > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ > On Thursday, April 15, 2021 7:36 PM, Strahil Nikolov hunter86_bg(a)yahoo.com wrote: > > > Gluster allows converting from replicted to distributed-replicated (so called expansion) of the volume. > > Of course you need to add the same amount of bricks as the replica count (which should be either 'replica 3' or 'replica 3 arbiter 1'). > > The Gluster documentation on the topic is quite extensive , but it's worth mentioning that you need to 'rebalance' your cluster after the expansion or you risk filling the old bricks - while having free space on the new bricks. > > That is expected ,as each file/dir's name is hashed and each subvolume (new vs old bricks) will have it's own range of hashes. When you expand the volume, some of the files/dirs on the old bricks have hashes that match to the new "triplet". > > Also , if you do not rebalance - that will have some performance impact as gluster will search the new bricks (for the files' whose hash matches the new subvolume) before searching the old bricks. > > P.S: I think that the Engine's web interface fully supports that operation, although I'm used to the cli. > > Best Regards, > > Strahil Nikolov > > В четвъртък, 15 април 2021 г., 20:05:50 ч. Гринуич+3, David White via Users users(a)ovirt.org написа: > > Is it possible to expand an existing gluster volume? > > I have a hyperconverged environment, and have enough space right now, but I'm going to have to significantly over-provision my environment. The vast majority of our customers are using a small fraction of the amount of space that they are technically allocated, but we still need to make that space available to them. > > As a result, I'd like to plan ahead, and go ahead and have a plan to add storage later down the road. > > I'd like to plan to shut down each server in the cluster (individually, not at once), add storage, and then bring them back online. Once all 3 are back online with the additional storage, I'd like to expand the gluster volume to use the additional space. Is that possible? How? > > Sent with ProtonMail Secure Email. > > 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/A7C3X2PW4D42G…

2 5

glance repo in 4.3
by Christoph Köhler 16 Apr '21

16 Apr '21

I use ovirt 4.3.10 and need to get access to a glance repo for vm images/templates. The buld-in external provider 'Public Glance repository for oVirt' (glance.ovirt.org) does not work, it seems not to be maintained. Does someone knows what to do? Greetings from Christoph

2 1

ovirt-hosted-engine-cleanup
by Marko Vrgotic 16 Apr '21

16 Apr '21

Dear oVirt, I have three HE Hosts. Upon upgrade from 4.3.5 to 4.3.10 the Hosted Engine did not start anymore on Host2, but working just fine on Host1 and Host3. I tried to Undeploy – Deploy on Host2 but I noticed that hosted-engine.conf contains only ca path and host id. It looks like either Undeploy properly or Deploy is failing due to reason I am unable to find in the logs. When checking the hosted-engine –vm-status, even though undeployed, the output was still containing Host2 in the list. Than I cleaned metadata on the Host1 and 3 for Host2 and at that point it was forgotten. After that I tried adding the Host2 back to HE pool, first installed the Host2 with fresh OS and than added it to Hosts pool with HostedEngine DEPLOY option. Result was the same. The VDSM on the Host2 was showing ERROR: “2021-04-16 06:47:30,422+0000 ERROR (periodic/3) [root] failed to retrieve Hosted Engine HA score '[Errno 2] No such file or directory'Is the Hosted Engine setup finished? (api:196)” The broker is showing the error: “MainThread::WARNING::2021-04-16 06:47:27,514::storage_broker::97::ovirt_hosted_engine_ha.broker.storage_broker.StorageBroker::(__init__) Can't connect vdsm storage: 'metadata_image_UUID can't be 'None' Atm, I am thinking of executing the /usr/sbin/ovirt-hosted-engine-cleanup but its effect is not clear to me. Is it going to cleanup any HE deploy remains from the Host its executed on, or its going to cleanup the other two Hosts, rendering my platfrom offline? I have been reading through https://www.ovirt.org/images/Hosted-Engine-4.3-deep-dive.pdf but its effect is not clear. I would have tested it already but this issue is on our production platform, so I need some experts input before taking further action. Please advise. ----- kind regards/met vriendelijke groeten Marko Vrgotic Sr. System Engineer @ System Administration ActiveVideo o: +31 (35) 6774131 m: +31 (65) 5734174 e: m.vrgotic(a)activevideo.com<mailto:m.vrgotic@activevideo.com> w: www.activevideo.com<http://www.activevideo.com> ActiveVideo Networks BV. Mediacentrum 3745 Joop van den Endeplein 1.1217 WJ Hilversum, The Netherlands. The information contained in this message may be legally privileged and confidential. It is intended to be read only by the individual or entity to whom it is addressed or by their designee. If the reader of this message is not the intended recipient, you are on notice that any distribution of this message, in any form, is strictly prohibited. If you have received this message in error, please immediately notify the sender and/or ActiveVideo Networks, LLC by telephone at +1 408.931.9200 and delete or destroy any copy of this message.

1 0

Need to change switch... ovirt kvm concerns?
by jpedrolima＠gmail.com 16 Apr '21

16 Apr '21

Hi I need to migrate the switch (equipment change and VLAN implementation) so I ask you to tell me what to do about the ovirt KVM cluster. What procedures and concerns I must have ? best regards, PL

2 4

Moving hosted engine storage
by Chris Adams 16 Apr '21

16 Apr '21

I'm moving a 4.3 cluster to new storage, and I'm down to the hosted engine. I am reading the following: https://www.ovirt.org/documentation/migrating_from_a_standalone_manager_to_… https://www.ovirt.org/develop/developer-guide/engine/migrate-to-hosted-engi… https://lists.ovirt.org/pipermail/users/2017-January/078739.html The last mentions a couple of options added to engine-backup to filter out the old hosted engine parts, but where do I use them? It looks like they only apply during restore, but from the last time I rebuilt the engine (mvoing from CentOS 6 to CentOS 7), I thought I just provided the backup file to hosted-engine --deploy and it handled the restore. Is there a way to pass those options to hosted-engine --deploy, or should I do like the example and just deploy a brand new engine, then log in and manually apply the backup (and filter options) then? Just trying to make sure I understand current (well, current for 4.3) best practice for replacing the hosted engine's storage array (iSCSI in this case, if that matters). -- Chris Adams <cma(a)cmadams.net>

1 1

Re: Upgrade from 4.3.5 to 4.3.10 HE Host issue
by Marko Vrgotic 15 Apr '21

15 Apr '21

Adding screenshot representing the state: [Graphical user interface, text Description automatically generated] ----- kind regards/met vriendelijke groeten Marko Vrgotic Sr. System Engineer @ System Administration ActiveVideo o: +31 (35) 6774131 m: +31 (65) 5734174 e: m.vrgotic(a)activevideo.com<mailto:m.vrgotic@activevideo.com> w: www.activevideo.com<http://www.activevideo.com> ActiveVideo Networks BV. Mediacentrum 3745 Joop van den Endeplein 1.1217 WJ Hilversum, The Netherlands. The information contained in this message may be legally privileged and confidential. It is intended to be read only by the individual or entity to whom it is addressed or by their designee. If the reader of this message is not the intended recipient, you are on notice that any distribution of this message, in any form, is strictly prohibited. If you have received this message in error, please immediately notify the sender and/or ActiveVideo Networks, LLC by telephone at +1 408.931.9200 and delete or destroy any copy of this message. From: Marko Vrgotic <M.Vrgotic(a)activevideo.com> Date: Thursday, 15 April 2021 at 23:00 To: users(a)ovirt.org <users(a)ovirt.org> Cc: Yedidyah Bar David <didi(a)redhat.com> Subject: Re: [ovirt-users] Re: Upgrade from 4.3.5 to 4.3.10 HE Host issue Looking further onto storage part, checking the host which I am unable to re-add to HE Host pool: [root@ovirt-sj-02 10.210.13.64:_hosted__engine]# ls -la total 8 drwxr-xr-x. 3 nobody nobody 4096 Apr 15 20:47 . drwxr-xr-x. 3 vdsm kvm 42 Apr 15 14:30 .. drwxr-xr-x. 6 nobody nobody 4096 Aug 20 2019 054c43fc-1924-4106-9f80-0f2ac62b9886 -rwxr-xr-x. 1 nobody nobody 0 Feb 18 2020 __DIRECT_IO_TEST__ [root@ovirt-sj-02 10.210.13.64:_hosted__engine]# cd 054c43fc-1924-4106-9f80-0f2ac62b9886/ [root@ovirt-sj-02 054c43fc-1924-4106-9f80-0f2ac62b9886]# ls dom_md ha_agent images master [root@ovirt-sj-02 054c43fc-1924-4106-9f80-0f2ac62b9886]# cd ha_agent/ [root@ovirt-sj-02 ha_agent]# ls hosted-engine.lockspace hosted-engine.metadata [root@ovirt-sj-02 ha_agent]# cat hosted-engine.lockspace cat: hosted-engine.lockspace: No such file or directory [root@ovirt-sj-02 ha_agent]# ls -la total 16 drwxr-xr-x. 2 nobody nobody 4096 Mar 31 10:30 . drwxr-xr-x. 6 nobody nobody 4096 Aug 20 2019 .. lrwxrwxrwx. 1 nobody nobody 132 Mar 31 10:30 hosted-engine.lockspace -> /var/run/vdsm/storage/054c43fc-1924-4106-9f80-0f2ac62b9886/e08188be-f733-4d5c-9222-a4b4e2228955/081f81c5-b2b2-46d5-9f82-9d9041ccc108 lrwxrwxrwx. 1 nobody nobody 132 Mar 31 10:30 hosted-engine.metadata -> /var/run/vdsm/storage/054c43fc-1924-4106-9f80-0f2ac62b9886/16b3e5ac-e70b-46e3-bf81-322954fe0b44/b6326e48-a7d2-4cba-af91-441db9f353c2 [root@ovirt-sj-02 ha_agent]# cat ^C [root@ovirt-sj-02 ha_agent]# cat /var/run/vdsm/storage/054c43fc-1924-4106-9f80-0f2ac62b9886/e08188be-f733-4d5c-9222-a4b4e2228955/081f81c5-b2b2-46d5-9f82-9d9041ccc108 cat: /var/run/vdsm/storage/054c43fc-1924-4106-9f80-0f2ac62b9886/e08188be-f733-4d5c-9222-a4b4e2228955/081f81c5-b2b2-46d5-9f82-9d9041ccc108: No such file or directory It looks like there is still lockspace and metalinks which point to location thatno longer exists – the links are marked with red. The broker.log is showing the following: Main Thread WARNING storage_broker ovirt_hosted_engine_ha.broker.storage_broker.Storage Broker Can't connect vdsm storage: 'metadata_image_UUID can't be 'None' I am starting to think that I need to run the lockspace reinitialization: 1. on each HE host systemctl stop ovirt-ha-agent ovirt-ha-brokersanlock client shutdown -f 1 # carefully, it could trigger the watchdog and reboot 2. on a single hosthosted-engine --reinitialize-lockspace 3. on each HE hostsystemctl start ovirt-ha-agent ovirt-ha-broker Is action 2 required to be executed only on Host with an issue or the action itself is gonna reinitialize lockspace on all HE Hosts? ----- kind regards/met vriendelijke groeten Marko Vrgotic Sr. System Engineer @ System Administration ActiveVideo o: +31 (35) 6774131 m: +31 (65) 5734174 e: m.vrgotic(a)activevideo.com<mailto:m.vrgotic@activevideo.com> w: www.activevideo.com<http://www.activevideo.com> ActiveVideo Networks BV. Mediacentrum 3745 Joop van den Endeplein 1.1217 WJ Hilversum, The Netherlands. The information contained in this message may be legally privileged and confidential. It is intended to be read only by the individual or entity to whom it is addressed or by their designee. If the reader of this message is not the intended recipient, you are on notice that any distribution of this message, in any form, is strictly prohibited. If you have received this message in error, please immediately notify the sender and/or ActiveVideo Networks, LLC by telephone at +1 408.931.9200 and delete or destroy any copy of this message. From: Marko Vrgotic <M.Vrgotic(a)activevideo.com> Date: Thursday, 15 April 2021 at 16:57 To: Yedidyah Bar David <didi(a)redhat.com> Cc: users(a)ovirt.org <users(a)ovirt.org> Subject: Re: [ovirt-users] Re: Upgrade from 4.3.5 to 4.3.10 HE Host issue Hi Didi, I compared the hosted-engine.conf on all three machines and indeed, host 1 and 3 have identical ones , except hosted. Hosted-engine.conf on host2 that I am trying to add back contains only hostid and ca path: ca_cert=/etc/pki/vdsm/libvirt-spice/ca-cert.pem host_id=2 Can someone help me how to check if there is DB or Storage corruption? Would it be dectructive or risky to try to populate the hosted-engine.conf of host 2 with missing values? Any advices? ----- kind regards/met vriendelijke groeten Marko Vrgotic Sr. System Engineer @ System Administration ActiveVideo o: +31 (35) 6774131 m: +31 (65) 5734174 e: m.vrgotic(a)activevideo.com<mailto:m.vrgotic@activevideo.com> w: www.activevideo.com<http://www.activevideo.com> ActiveVideo Networks BV. Mediacentrum 3745 Joop van den Endeplein 1.1217 WJ Hilversum, The Netherlands. The information contained in this message may be legally privileged and confidential. It is intended to be read only by the individual or entity to whom it is addressed or by their designee. If the reader of this message is not the intended recipient, you are on notice that any distribution of this message, in any form, is strictly prohibited. If you have received this message in error, please immediately notify the sender and/or ActiveVideo Networks, LLC by telephone at +1 408.931.9200 and delete or destroy any copy of this message. From: Marko Vrgotic <M.Vrgotic(a)activevideo.com> Date: Wednesday, 14 April 2021 at 16:16 To: Yedidyah Bar David <didi(a)redhat.com> Cc: users(a)ovirt.org <users(a)ovirt.org> Subject: Re: [ovirt-users] Re: Upgrade from 4.3.5 to 4.3.10 HE Host issue Hi Didi, It looks like the issue was with Hosted-engine Undeploy, being incomplete – the other HE Hosts still had the entries of the Host I was trying to remove, so any following HE Deploy on that Host was failing. I was able to get the other hosts to forget about this one, by running hosted-engine –clean-metadate –host-id=2 Now I would like to try to add the host back to HE pool, but I have a question: “Is there a time I should wait, between cleaning metadata and re-adding the host?” Kindly awaiting your reply. ----- kind regards/met vriendelijke groeten Marko Vrgotic Sr. System Engineer @ System Administration ActiveVideo o: +31 (35) 6774131 m: +31 (65) 5734174 e: m.vrgotic(a)activevideo.com<mailto:m.vrgotic@activevideo.com> w: www.activevideo.com<http://www.activevideo.com> ActiveVideo Networks BV. Mediacentrum 3745 Joop van den Endeplein 1.1217 WJ Hilversum, The Netherlands. The information contained in this message may be legally privileged and confidential. It is intended to be read only by the individual or entity to whom it is addressed or by their designee. If the reader of this message is not the intended recipient, you are on notice that any distribution of this message, in any form, is strictly prohibited. If you have received this message in error, please immediately notify the sender and/or ActiveVideo Networks, LLC by telephone at +1 408.931.9200 and delete or destroy any copy of this message. From: Yedidyah Bar David <didi(a)redhat.com> Date: Thursday, 18 March 2021 at 15:09 To: Marko Vrgotic <M.Vrgotic(a)activevideo.com> Cc: users(a)ovirt.org <users(a)ovirt.org> Subject: Re: [ovirt-users] Re: Upgrade from 4.3.5 to 4.3.10 HE Host issue ***CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender!!!*** Hi, On Mon, Mar 8, 2021 at 4:55 PM Marko Vrgotic <M.Vrgotic(a)activevideo.com> wrote: > > The broker log, these lines are pretty much repeating: > > > > MainThread::WARNING::2021-03-03 09:19:12,086::storage_broker::97::ovirt_hosted_engine_ha.broker.storage_broker.StorageBroker::(__init__) Can't connect vdsm storage: 'metadata_image_UUID can't be 'None' Please compare the content of /etc/ovirt-hosted-engine/hosted-engine.conf between all your hosts. host id should be unique per host, but otherwise they should be identical. If they are not, most likely there is some corruption somewhere - in the engine db or shared storage. You might want to skim this for a general rather-low-level overview: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt… Do you see no errors on your other hosts? In -ha logs? Please also note that 4.3 is EOL. The deploy process was completely rewritten in 4.4 (in ansible, previous was python), although should in principle behave similarly - so if your data is corrupted, upgrade to 4.4 probably won't fix it. Good luck and best regards, > > MainThread::INFO::2021-03-03 09:19:12,829::broker::47::ovirt_hosted_engine_ha.broker.broker.Broker::(run) ovirt-hosted-engine-ha broker 2.3.6 started > > MainThread::INFO::2021-03-03 09:19:12,829::monitor::40::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Searching for submonitors in /usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/broker/sub > > monitors > > MainThread::INFO::2021-03-03 09:19:12,829::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor cpu-load > > MainThread::INFO::2021-03-03 09:19:12,832::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor cpu-load-no-engine > > MainThread::INFO::2021-03-03 09:19:12,832::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor engine-health > > MainThread::INFO::2021-03-03 09:19:12,832::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor mem-free > > MainThread::INFO::2021-03-03 09:19:12,833::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor mgmt-bridge > > MainThread::INFO::2021-03-03 09:19:12,833::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor network > > MainThread::INFO::2021-03-03 09:19:12,833::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor storage-domain > > MainThread::INFO::2021-03-03 09:19:12,833::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor cpu-load > > MainThread::INFO::2021-03-03 09:19:12,834::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor cpu-load-no-engine > > MainThread::INFO::2021-03-03 09:19:12,835::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor engine-health > > MainThread::INFO::2021-03-03 09:19:12,835::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor mem-free > > MainThread::INFO::2021-03-03 09:19:12,835::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor mgmt-bridge > > MainThread::INFO::2021-03-03 09:19:12,835::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor network > > MainThread::INFO::2021-03-03 09:19:12,836::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor storage-domain > > MainThread::INFO::2021-03-03 09:19:12,836::monitor::50::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Finished loading submonitors > > MainThread::WARNING::2021-03-03 09:19:12,836::storage_broker::97::ovirt_hosted_engine_ha.broker.storage_broker.StorageBroker::(__init__) Can't connect vdsm storage: 'metadata_image_UUID can't be 'None' > > MainThread::INFO::2021-03-03 09:19:13,574::broker::47::ovirt_hosted_engine_ha.broker.broker.Broker::(run) ovirt-hosted-engine-ha broker 2.3.6 started > > MainThread::INFO::2021-03-03 09:19:13,575::monitor::40::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Searching for submonitors in /usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/broker/submonitors > > MainThread::INFO::2021-03-03 09:19:13,575::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor cpu-load > > MainThread::INFO::2021-03-03 09:19:13,577::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor cpu-load-no-engine > > MainThread::INFO::2021-03-03 09:19:13,578::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor engine-health > > > > > > > > ----- > > kind regards/met vriendelijke groeten > > > > Marko Vrgotic > Sr. System Engineer @ System Administration > > > ActiveVideo > > o: +31 (35) 6774131 > > m: +31 (65) 5734174 > > e: m.vrgotic(a)activevideo.com > w: https://nam10.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.active… > > > > ActiveVideo Networks BV. Mediacentrum 3745 Joop van den Endeplein 1.1217 WJ Hilversum, The Netherlands. The information contained in this message may be legally privileged and confidential. It is intended to be read only by the individual or entity to whom it is addressed or by their designee. If the reader of this message is not the intended recipient, you are on notice that any distribution of this message, in any form, is strictly prohibited. If you have received this message in error, please immediately notify the sender and/or ActiveVideo Networks, LLC by telephone at +1 408.931.9200 and delete or destroy any copy of this message. > > > > > > > > From: Marko Vrgotic <M.Vrgotic(a)activevideo.com> > Date: Monday, 8 March 2021 at 15:34 > To: Yedidyah Bar David <didi(a)redhat.com> > Cc: users(a)ovirt.org <users(a)ovirt.org> > Subject: Re: [ovirt-users] Re: Upgrade from 4.3.5 to 4.3.10 HE Host issue > > Hi Didi, > > > > Please find the attached logs from Host and Engine. > > > > Host ovirt-sj-02 HE Undeploy 2021-03-08 14:15:52 till 2021-03-08 14:18:24 > > > > > > Host ovirt-sj-02 HE Deploy 2021-03-08 14:20:51 till 2021-03-08 14:23:22 > > > > I do see errors in the agent and broker and vdsm, but I do not see why it happened. > > > > Thank you for helping, let me know if any additional files are needed. > > > > > > ----- > > kind regards/met vriendelijke groeten > > > > Marko Vrgotic > Sr. System Engineer @ System Administration > > > ActiveVideo > > o: +31 (35) 6774131 > > m: +31 (65) 5734174 > > e: m.vrgotic(a)activevideo.com > w: https://nam10.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.active… > > > > ActiveVideo Networks BV. Mediacentrum 3745 Joop van den Endeplein 1.1217 WJ Hilversum, The Netherlands. The information contained in this message may be legally privileged and confidential. It is intended to be read only by the individual or entity to whom it is addressed or by their designee. If the reader of this message is not the intended recipient, you are on notice that any distribution of this message, in any form, is strictly prohibited. If you have received this message in error, please immediately notify the sender and/or ActiveVideo Networks, LLC by telephone at +1 408.931.9200 and delete or destroy any copy of this message. > > > > > > > > From: Yedidyah Bar David <didi(a)redhat.com> > Date: Monday, 8 March 2021 at 09:25 > To: Marko Vrgotic <M.Vrgotic(a)activevideo.com> > Cc: users(a)ovirt.org <users(a)ovirt.org> > Subject: Re: [ovirt-users] Re: Upgrade from 4.3.5 to 4.3.10 HE Host issue > > ***CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender!!!*** > > Hi, > > On Mon, Mar 8, 2021 at 10:13 AM Marko Vrgotic <M.Vrgotic(a)activevideo.com> wrote: > > > > I cannot find the reason why the re-Deployment on this Hosts fails, as it was already deployed on it before. > > > > No errors, found int the deployment, but it seems half done, based on messages I sent in previous email. > > Please check/share all relevant logs. Thanks. Can be all of /var/log > from engine and hosts, and at least: > > /var/log/ovirt-engine/engine.log > > /var/log/vdsm/* > > /var/log/ovirt-hosted-engine-ha/* > > Best regards, > -- > Didi -- Didi

1 0

Re: Upgrade from 4.3.5 to 4.3.10 HE Host issue
by Marko Vrgotic 15 Apr '21

15 Apr '21

Looking further onto storage part, checking the host which I am unable to re-add to HE Host pool: [root@ovirt-sj-02 10.210.13.64:_hosted__engine]# ls -la total 8 drwxr-xr-x. 3 nobody nobody 4096 Apr 15 20:47 . drwxr-xr-x. 3 vdsm kvm 42 Apr 15 14:30 .. drwxr-xr-x. 6 nobody nobody 4096 Aug 20 2019 054c43fc-1924-4106-9f80-0f2ac62b9886 -rwxr-xr-x. 1 nobody nobody 0 Feb 18 2020 __DIRECT_IO_TEST__ [root@ovirt-sj-02 10.210.13.64:_hosted__engine]# cd 054c43fc-1924-4106-9f80-0f2ac62b9886/ [root@ovirt-sj-02 054c43fc-1924-4106-9f80-0f2ac62b9886]# ls dom_md ha_agent images master [root@ovirt-sj-02 054c43fc-1924-4106-9f80-0f2ac62b9886]# cd ha_agent/ [root@ovirt-sj-02 ha_agent]# ls hosted-engine.lockspace hosted-engine.metadata [root@ovirt-sj-02 ha_agent]# cat hosted-engine.lockspace cat: hosted-engine.lockspace: No such file or directory [root@ovirt-sj-02 ha_agent]# ls -la total 16 drwxr-xr-x. 2 nobody nobody 4096 Mar 31 10:30 . drwxr-xr-x. 6 nobody nobody 4096 Aug 20 2019 .. lrwxrwxrwx. 1 nobody nobody 132 Mar 31 10:30 hosted-engine.lockspace -> /var/run/vdsm/storage/054c43fc-1924-4106-9f80-0f2ac62b9886/e08188be-f733-4d5c-9222-a4b4e2228955/081f81c5-b2b2-46d5-9f82-9d9041ccc108 lrwxrwxrwx. 1 nobody nobody 132 Mar 31 10:30 hosted-engine.metadata -> /var/run/vdsm/storage/054c43fc-1924-4106-9f80-0f2ac62b9886/16b3e5ac-e70b-46e3-bf81-322954fe0b44/b6326e48-a7d2-4cba-af91-441db9f353c2 [root@ovirt-sj-02 ha_agent]# cat ^C [root@ovirt-sj-02 ha_agent]# cat /var/run/vdsm/storage/054c43fc-1924-4106-9f80-0f2ac62b9886/e08188be-f733-4d5c-9222-a4b4e2228955/081f81c5-b2b2-46d5-9f82-9d9041ccc108 cat: /var/run/vdsm/storage/054c43fc-1924-4106-9f80-0f2ac62b9886/e08188be-f733-4d5c-9222-a4b4e2228955/081f81c5-b2b2-46d5-9f82-9d9041ccc108: No such file or directory It looks like there is still lockspace and metalinks which point to location thatno longer exists – the links are marked with red. The broker.log is showing the following: Main Thread WARNING storage_broker ovirt_hosted_engine_ha.broker.storage_broker.Storage Broker Can't connect vdsm storage: 'metadata_image_UUID can't be 'None' I am starting to think that I need to run the lockspace reinitialization: 1. on each HE host systemctl stop ovirt-ha-agent ovirt-ha-brokersanlock client shutdown -f 1 # carefully, it could trigger the watchdog and reboot 2. on a single hosthosted-engine --reinitialize-lockspace 3. on each HE hostsystemctl start ovirt-ha-agent ovirt-ha-broker Is action 2 required to be executed only on Host with an issue or the action itself is gonna reinitialize lockspace on all HE Hosts? ----- kind regards/met vriendelijke groeten Marko Vrgotic Sr. System Engineer @ System Administration ActiveVideo o: +31 (35) 6774131 m: +31 (65) 5734174 e: m.vrgotic(a)activevideo.com<mailto:m.vrgotic@activevideo.com> w: www.activevideo.com<http://www.activevideo.com> ActiveVideo Networks BV. Mediacentrum 3745 Joop van den Endeplein 1.1217 WJ Hilversum, The Netherlands. The information contained in this message may be legally privileged and confidential. It is intended to be read only by the individual or entity to whom it is addressed or by their designee. If the reader of this message is not the intended recipient, you are on notice that any distribution of this message, in any form, is strictly prohibited. If you have received this message in error, please immediately notify the sender and/or ActiveVideo Networks, LLC by telephone at +1 408.931.9200 and delete or destroy any copy of this message. From: Marko Vrgotic <M.Vrgotic(a)activevideo.com> Date: Thursday, 15 April 2021 at 16:57 To: Yedidyah Bar David <didi(a)redhat.com> Cc: users(a)ovirt.org <users(a)ovirt.org> Subject: Re: [ovirt-users] Re: Upgrade from 4.3.5 to 4.3.10 HE Host issue Hi Didi, I compared the hosted-engine.conf on all three machines and indeed, host 1 and 3 have identical ones , except hosted. Hosted-engine.conf on host2 that I am trying to add back contains only hostid and ca path: ca_cert=/etc/pki/vdsm/libvirt-spice/ca-cert.pem host_id=2 Can someone help me how to check if there is DB or Storage corruption? Would it be dectructive or risky to try to populate the hosted-engine.conf of host 2 with missing values? Any advices? ----- kind regards/met vriendelijke groeten Marko Vrgotic Sr. System Engineer @ System Administration ActiveVideo o: +31 (35) 6774131 m: +31 (65) 5734174 e: m.vrgotic(a)activevideo.com<mailto:m.vrgotic@activevideo.com> w: www.activevideo.com<http://www.activevideo.com> ActiveVideo Networks BV. Mediacentrum 3745 Joop van den Endeplein 1.1217 WJ Hilversum, The Netherlands. The information contained in this message may be legally privileged and confidential. It is intended to be read only by the individual or entity to whom it is addressed or by their designee. If the reader of this message is not the intended recipient, you are on notice that any distribution of this message, in any form, is strictly prohibited. If you have received this message in error, please immediately notify the sender and/or ActiveVideo Networks, LLC by telephone at +1 408.931.9200 and delete or destroy any copy of this message. From: Marko Vrgotic <M.Vrgotic(a)activevideo.com> Date: Wednesday, 14 April 2021 at 16:16 To: Yedidyah Bar David <didi(a)redhat.com> Cc: users(a)ovirt.org <users(a)ovirt.org> Subject: Re: [ovirt-users] Re: Upgrade from 4.3.5 to 4.3.10 HE Host issue Hi Didi, It looks like the issue was with Hosted-engine Undeploy, being incomplete – the other HE Hosts still had the entries of the Host I was trying to remove, so any following HE Deploy on that Host was failing. I was able to get the other hosts to forget about this one, by running hosted-engine –clean-metadate –host-id=2 Now I would like to try to add the host back to HE pool, but I have a question: “Is there a time I should wait, between cleaning metadata and re-adding the host?” Kindly awaiting your reply. ----- kind regards/met vriendelijke groeten Marko Vrgotic Sr. System Engineer @ System Administration ActiveVideo o: +31 (35) 6774131 m: +31 (65) 5734174 e: m.vrgotic(a)activevideo.com<mailto:m.vrgotic@activevideo.com> w: www.activevideo.com<http://www.activevideo.com> ActiveVideo Networks BV. Mediacentrum 3745 Joop van den Endeplein 1.1217 WJ Hilversum, The Netherlands. The information contained in this message may be legally privileged and confidential. It is intended to be read only by the individual or entity to whom it is addressed or by their designee. If the reader of this message is not the intended recipient, you are on notice that any distribution of this message, in any form, is strictly prohibited. If you have received this message in error, please immediately notify the sender and/or ActiveVideo Networks, LLC by telephone at +1 408.931.9200 and delete or destroy any copy of this message. From: Yedidyah Bar David <didi(a)redhat.com> Date: Thursday, 18 March 2021 at 15:09 To: Marko Vrgotic <M.Vrgotic(a)activevideo.com> Cc: users(a)ovirt.org <users(a)ovirt.org> Subject: Re: [ovirt-users] Re: Upgrade from 4.3.5 to 4.3.10 HE Host issue ***CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender!!!*** Hi, On Mon, Mar 8, 2021 at 4:55 PM Marko Vrgotic <M.Vrgotic(a)activevideo.com> wrote: > > The broker log, these lines are pretty much repeating: > > > > MainThread::WARNING::2021-03-03 09:19:12,086::storage_broker::97::ovirt_hosted_engine_ha.broker.storage_broker.StorageBroker::(__init__) Can't connect vdsm storage: 'metadata_image_UUID can't be 'None' Please compare the content of /etc/ovirt-hosted-engine/hosted-engine.conf between all your hosts. host id should be unique per host, but otherwise they should be identical. If they are not, most likely there is some corruption somewhere - in the engine db or shared storage. You might want to skim this for a general rather-low-level overview: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt… Do you see no errors on your other hosts? In -ha logs? Please also note that 4.3 is EOL. The deploy process was completely rewritten in 4.4 (in ansible, previous was python), although should in principle behave similarly - so if your data is corrupted, upgrade to 4.4 probably won't fix it. Good luck and best regards, > > MainThread::INFO::2021-03-03 09:19:12,829::broker::47::ovirt_hosted_engine_ha.broker.broker.Broker::(run) ovirt-hosted-engine-ha broker 2.3.6 started > > MainThread::INFO::2021-03-03 09:19:12,829::monitor::40::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Searching for submonitors in /usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/broker/sub > > monitors > > MainThread::INFO::2021-03-03 09:19:12,829::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor cpu-load > > MainThread::INFO::2021-03-03 09:19:12,832::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor cpu-load-no-engine > > MainThread::INFO::2021-03-03 09:19:12,832::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor engine-health > > MainThread::INFO::2021-03-03 09:19:12,832::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor mem-free > > MainThread::INFO::2021-03-03 09:19:12,833::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor mgmt-bridge > > MainThread::INFO::2021-03-03 09:19:12,833::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor network > > MainThread::INFO::2021-03-03 09:19:12,833::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor storage-domain > > MainThread::INFO::2021-03-03 09:19:12,833::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor cpu-load > > MainThread::INFO::2021-03-03 09:19:12,834::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor cpu-load-no-engine > > MainThread::INFO::2021-03-03 09:19:12,835::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor engine-health > > MainThread::INFO::2021-03-03 09:19:12,835::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor mem-free > > MainThread::INFO::2021-03-03 09:19:12,835::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor mgmt-bridge > > MainThread::INFO::2021-03-03 09:19:12,835::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor network > > MainThread::INFO::2021-03-03 09:19:12,836::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor storage-domain > > MainThread::INFO::2021-03-03 09:19:12,836::monitor::50::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Finished loading submonitors > > MainThread::WARNING::2021-03-03 09:19:12,836::storage_broker::97::ovirt_hosted_engine_ha.broker.storage_broker.StorageBroker::(__init__) Can't connect vdsm storage: 'metadata_image_UUID can't be 'None' > > MainThread::INFO::2021-03-03 09:19:13,574::broker::47::ovirt_hosted_engine_ha.broker.broker.Broker::(run) ovirt-hosted-engine-ha broker 2.3.6 started > > MainThread::INFO::2021-03-03 09:19:13,575::monitor::40::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Searching for submonitors in /usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/broker/submonitors > > MainThread::INFO::2021-03-03 09:19:13,575::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor cpu-load > > MainThread::INFO::2021-03-03 09:19:13,577::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor cpu-load-no-engine > > MainThread::INFO::2021-03-03 09:19:13,578::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor engine-health > > > > > > > > ----- > > kind regards/met vriendelijke groeten > > > > Marko Vrgotic > Sr. System Engineer @ System Administration > > > ActiveVideo > > o: +31 (35) 6774131 > > m: +31 (65) 5734174 > > e: m.vrgotic(a)activevideo.com > w: https://nam10.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.active… > > > > ActiveVideo Networks BV. Mediacentrum 3745 Joop van den Endeplein 1.1217 WJ Hilversum, The Netherlands. The information contained in this message may be legally privileged and confidential. It is intended to be read only by the individual or entity to whom it is addressed or by their designee. If the reader of this message is not the intended recipient, you are on notice that any distribution of this message, in any form, is strictly prohibited. If you have received this message in error, please immediately notify the sender and/or ActiveVideo Networks, LLC by telephone at +1 408.931.9200 and delete or destroy any copy of this message. > > > > > > > > From: Marko Vrgotic <M.Vrgotic(a)activevideo.com> > Date: Monday, 8 March 2021 at 15:34 > To: Yedidyah Bar David <didi(a)redhat.com> > Cc: users(a)ovirt.org <users(a)ovirt.org> > Subject: Re: [ovirt-users] Re: Upgrade from 4.3.5 to 4.3.10 HE Host issue > > Hi Didi, > > > > Please find the attached logs from Host and Engine. > > > > Host ovirt-sj-02 HE Undeploy 2021-03-08 14:15:52 till 2021-03-08 14:18:24 > > > > > > Host ovirt-sj-02 HE Deploy 2021-03-08 14:20:51 till 2021-03-08 14:23:22 > > > > I do see errors in the agent and broker and vdsm, but I do not see why it happened. > > > > Thank you for helping, let me know if any additional files are needed. > > > > > > ----- > > kind regards/met vriendelijke groeten > > > > Marko Vrgotic > Sr. System Engineer @ System Administration > > > ActiveVideo > > o: +31 (35) 6774131 > > m: +31 (65) 5734174 > > e: m.vrgotic(a)activevideo.com > w: https://nam10.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.active… > > > > ActiveVideo Networks BV. Mediacentrum 3745 Joop van den Endeplein 1.1217 WJ Hilversum, The Netherlands. The information contained in this message may be legally privileged and confidential. It is intended to be read only by the individual or entity to whom it is addressed or by their designee. If the reader of this message is not the intended recipient, you are on notice that any distribution of this message, in any form, is strictly prohibited. If you have received this message in error, please immediately notify the sender and/or ActiveVideo Networks, LLC by telephone at +1 408.931.9200 and delete or destroy any copy of this message. > > > > > > > > From: Yedidyah Bar David <didi(a)redhat.com> > Date: Monday, 8 March 2021 at 09:25 > To: Marko Vrgotic <M.Vrgotic(a)activevideo.com> > Cc: users(a)ovirt.org <users(a)ovirt.org> > Subject: Re: [ovirt-users] Re: Upgrade from 4.3.5 to 4.3.10 HE Host issue > > ***CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender!!!*** > > Hi, > > On Mon, Mar 8, 2021 at 10:13 AM Marko Vrgotic <M.Vrgotic(a)activevideo.com> wrote: > > > > I cannot find the reason why the re-Deployment on this Hosts fails, as it was already deployed on it before. > > > > No errors, found int the deployment, but it seems half done, based on messages I sent in previous email. > > Please check/share all relevant logs. Thanks. Can be all of /var/log > from engine and hosts, and at least: > > /var/log/ovirt-engine/engine.log > > /var/log/vdsm/* > > /var/log/ovirt-hosted-engine-ha/* > > Best regards, > -- > Didi -- Didi

1 0

[ANN] oVirt 4.4.6 Fourth Release Candidate is now available for testing
by Sandro Bonazzola 15 Apr '21

15 Apr '21

oVirt 4.4.6 Fourth Release Candidate is now available for testing The oVirt Project is pleased to announce the availability of oVirt 4.4.6 Fourth Release Candidate for testing, as of April 15th, 2021. This update is the sixth in a series of stabilization updates to the 4.4 series. Rebase on CentOS Stream Starting with oVirt 4.4.6 RC4 both oVirt Node and oVirt Engine Appliance are based on CentOS Stream. You can still install oVirt 4.4.6 on Red Hat Enterprise Linux, CentOS Linux or equivalent. Please note that when 4.4.6 will be released as generally available, existing oVirt Nodes updating to 4.4.6 will automatically be based on CentOS Stream. Help testing this release candidate will help ensuring a smooth experience for your main installation. 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. Known issues: - Bug 1946095 <https://bugzilla.redhat.com/show_bug.cgi?id=1946095> - "No valid network interface has been found" when starting HE deployment via cockpit - For testing purposes you can use the command line <https://ovirt.org/documentation/installing_ovirt_as_a_self-hosted_engine_us…> 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 8 Stream * 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 8 Stream * CentOS Linux (or similar) 8.3 or newer * oVirt Node 4.4 based on CentOS 8 Stream (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 based on CentOS 8 Stream - oVirt Node NG is already available based on CentOS 8 Stream 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/ -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/> *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

1 0

Re: Upgrade from 4.3.5 to 4.3.10 HE Host issue
by Marko Vrgotic 15 Apr '21

15 Apr '21

Hi Didi, I compared the hosted-engine.conf on all three machines and indeed, host 1 and 3 have identical ones , except hosted. Hosted-engine.conf on host2 that I am trying to add back contains only hostid and ca path: ca_cert=/etc/pki/vdsm/libvirt-spice/ca-cert.pem host_id=2 Can someone help me how to check if there is DB or Storage corruption? Would it be dectructive or risky to try to populate the hosted-engine.conf of host 2 with missing values? Any advices? ----- kind regards/met vriendelijke groeten Marko Vrgotic Sr. System Engineer @ System Administration ActiveVideo o: +31 (35) 6774131 m: +31 (65) 5734174 e: m.vrgotic(a)activevideo.com<mailto:m.vrgotic@activevideo.com> w: www.activevideo.com<http://www.activevideo.com> ActiveVideo Networks BV. Mediacentrum 3745 Joop van den Endeplein 1.1217 WJ Hilversum, The Netherlands. The information contained in this message may be legally privileged and confidential. It is intended to be read only by the individual or entity to whom it is addressed or by their designee. If the reader of this message is not the intended recipient, you are on notice that any distribution of this message, in any form, is strictly prohibited. If you have received this message in error, please immediately notify the sender and/or ActiveVideo Networks, LLC by telephone at +1 408.931.9200 and delete or destroy any copy of this message. From: Marko Vrgotic <M.Vrgotic(a)activevideo.com> Date: Wednesday, 14 April 2021 at 16:16 To: Yedidyah Bar David <didi(a)redhat.com> Cc: users(a)ovirt.org <users(a)ovirt.org> Subject: Re: [ovirt-users] Re: Upgrade from 4.3.5 to 4.3.10 HE Host issue Hi Didi, It looks like the issue was with Hosted-engine Undeploy, being incomplete – the other HE Hosts still had the entries of the Host I was trying to remove, so any following HE Deploy on that Host was failing. I was able to get the other hosts to forget about this one, by running hosted-engine –clean-metadate –host-id=2 Now I would like to try to add the host back to HE pool, but I have a question: “Is there a time I should wait, between cleaning metadata and re-adding the host?” Kindly awaiting your reply. ----- kind regards/met vriendelijke groeten Marko Vrgotic Sr. System Engineer @ System Administration ActiveVideo o: +31 (35) 6774131 m: +31 (65) 5734174 e: m.vrgotic(a)activevideo.com<mailto:m.vrgotic@activevideo.com> w: www.activevideo.com<http://www.activevideo.com> ActiveVideo Networks BV. Mediacentrum 3745 Joop van den Endeplein 1.1217 WJ Hilversum, The Netherlands. The information contained in this message may be legally privileged and confidential. It is intended to be read only by the individual or entity to whom it is addressed or by their designee. If the reader of this message is not the intended recipient, you are on notice that any distribution of this message, in any form, is strictly prohibited. If you have received this message in error, please immediately notify the sender and/or ActiveVideo Networks, LLC by telephone at +1 408.931.9200 and delete or destroy any copy of this message. From: Yedidyah Bar David <didi(a)redhat.com> Date: Thursday, 18 March 2021 at 15:09 To: Marko Vrgotic <M.Vrgotic(a)activevideo.com> Cc: users(a)ovirt.org <users(a)ovirt.org> Subject: Re: [ovirt-users] Re: Upgrade from 4.3.5 to 4.3.10 HE Host issue ***CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender!!!*** Hi, On Mon, Mar 8, 2021 at 4:55 PM Marko Vrgotic <M.Vrgotic(a)activevideo.com> wrote: > > The broker log, these lines are pretty much repeating: > > > > MainThread::WARNING::2021-03-03 09:19:12,086::storage_broker::97::ovirt_hosted_engine_ha.broker.storage_broker.StorageBroker::(__init__) Can't connect vdsm storage: 'metadata_image_UUID can't be 'None' Please compare the content of /etc/ovirt-hosted-engine/hosted-engine.conf between all your hosts. host id should be unique per host, but otherwise they should be identical. If they are not, most likely there is some corruption somewhere - in the engine db or shared storage. You might want to skim this for a general rather-low-level overview: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt… Do you see no errors on your other hosts? In -ha logs? Please also note that 4.3 is EOL. The deploy process was completely rewritten in 4.4 (in ansible, previous was python), although should in principle behave similarly - so if your data is corrupted, upgrade to 4.4 probably won't fix it. Good luck and best regards, > > MainThread::INFO::2021-03-03 09:19:12,829::broker::47::ovirt_hosted_engine_ha.broker.broker.Broker::(run) ovirt-hosted-engine-ha broker 2.3.6 started > > MainThread::INFO::2021-03-03 09:19:12,829::monitor::40::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Searching for submonitors in /usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/broker/sub > > monitors > > MainThread::INFO::2021-03-03 09:19:12,829::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor cpu-load > > MainThread::INFO::2021-03-03 09:19:12,832::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor cpu-load-no-engine > > MainThread::INFO::2021-03-03 09:19:12,832::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor engine-health > > MainThread::INFO::2021-03-03 09:19:12,832::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor mem-free > > MainThread::INFO::2021-03-03 09:19:12,833::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor mgmt-bridge > > MainThread::INFO::2021-03-03 09:19:12,833::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor network > > MainThread::INFO::2021-03-03 09:19:12,833::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor storage-domain > > MainThread::INFO::2021-03-03 09:19:12,833::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor cpu-load > > MainThread::INFO::2021-03-03 09:19:12,834::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor cpu-load-no-engine > > MainThread::INFO::2021-03-03 09:19:12,835::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor engine-health > > MainThread::INFO::2021-03-03 09:19:12,835::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor mem-free > > MainThread::INFO::2021-03-03 09:19:12,835::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor mgmt-bridge > > MainThread::INFO::2021-03-03 09:19:12,835::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor network > > MainThread::INFO::2021-03-03 09:19:12,836::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor storage-domain > > MainThread::INFO::2021-03-03 09:19:12,836::monitor::50::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Finished loading submonitors > > MainThread::WARNING::2021-03-03 09:19:12,836::storage_broker::97::ovirt_hosted_engine_ha.broker.storage_broker.StorageBroker::(__init__) Can't connect vdsm storage: 'metadata_image_UUID can't be 'None' > > MainThread::INFO::2021-03-03 09:19:13,574::broker::47::ovirt_hosted_engine_ha.broker.broker.Broker::(run) ovirt-hosted-engine-ha broker 2.3.6 started > > MainThread::INFO::2021-03-03 09:19:13,575::monitor::40::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Searching for submonitors in /usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/broker/submonitors > > MainThread::INFO::2021-03-03 09:19:13,575::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor cpu-load > > MainThread::INFO::2021-03-03 09:19:13,577::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor cpu-load-no-engine > > MainThread::INFO::2021-03-03 09:19:13,578::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor engine-health > > > > > > > > ----- > > kind regards/met vriendelijke groeten > > > > Marko Vrgotic > Sr. System Engineer @ System Administration > > > ActiveVideo > > o: +31 (35) 6774131 > > m: +31 (65) 5734174 > > e: m.vrgotic(a)activevideo.com > w: https://nam10.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.active… > > > > ActiveVideo Networks BV. Mediacentrum 3745 Joop van den Endeplein 1.1217 WJ Hilversum, The Netherlands. The information contained in this message may be legally privileged and confidential. It is intended to be read only by the individual or entity to whom it is addressed or by their designee. If the reader of this message is not the intended recipient, you are on notice that any distribution of this message, in any form, is strictly prohibited. If you have received this message in error, please immediately notify the sender and/or ActiveVideo Networks, LLC by telephone at +1 408.931.9200 and delete or destroy any copy of this message. > > > > > > > > From: Marko Vrgotic <M.Vrgotic(a)activevideo.com> > Date: Monday, 8 March 2021 at 15:34 > To: Yedidyah Bar David <didi(a)redhat.com> > Cc: users(a)ovirt.org <users(a)ovirt.org> > Subject: Re: [ovirt-users] Re: Upgrade from 4.3.5 to 4.3.10 HE Host issue > > Hi Didi, > > > > Please find the attached logs from Host and Engine. > > > > Host ovirt-sj-02 HE Undeploy 2021-03-08 14:15:52 till 2021-03-08 14:18:24 > > > > > > Host ovirt-sj-02 HE Deploy 2021-03-08 14:20:51 till 2021-03-08 14:23:22 > > > > I do see errors in the agent and broker and vdsm, but I do not see why it happened. > > > > Thank you for helping, let me know if any additional files are needed. > > > > > > ----- > > kind regards/met vriendelijke groeten > > > > Marko Vrgotic > Sr. System Engineer @ System Administration > > > ActiveVideo > > o: +31 (35) 6774131 > > m: +31 (65) 5734174 > > e: m.vrgotic(a)activevideo.com > w: https://nam10.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.active… > > > > ActiveVideo Networks BV. Mediacentrum 3745 Joop van den Endeplein 1.1217 WJ Hilversum, The Netherlands. The information contained in this message may be legally privileged and confidential. It is intended to be read only by the individual or entity to whom it is addressed or by their designee. If the reader of this message is not the intended recipient, you are on notice that any distribution of this message, in any form, is strictly prohibited. If you have received this message in error, please immediately notify the sender and/or ActiveVideo Networks, LLC by telephone at +1 408.931.9200 and delete or destroy any copy of this message. > > > > > > > > From: Yedidyah Bar David <didi(a)redhat.com> > Date: Monday, 8 March 2021 at 09:25 > To: Marko Vrgotic <M.Vrgotic(a)activevideo.com> > Cc: users(a)ovirt.org <users(a)ovirt.org> > Subject: Re: [ovirt-users] Re: Upgrade from 4.3.5 to 4.3.10 HE Host issue > > ***CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender!!!*** > > Hi, > > On Mon, Mar 8, 2021 at 10:13 AM Marko Vrgotic <M.Vrgotic(a)activevideo.com> wrote: > > > > I cannot find the reason why the re-Deployment on this Hosts fails, as it was already deployed on it before. > > > > No errors, found int the deployment, but it seems half done, based on messages I sent in previous email. > > Please check/share all relevant logs. Thanks. Can be all of /var/log > from engine and hosts, and at least: > > /var/log/ovirt-engine/engine.log > > /var/log/vdsm/* > > /var/log/ovirt-hosted-engine-ha/* > > Best regards, > -- > Didi -- Didi

1 0

Failed certificate expiration
by Fabrice Bacchella 15 Apr '21

15 Apr '21

I missed the certificate expiration for the oVirt PKI. So the engine is now totally unable to talk to the hosts. Is there any documentation for this kind of failure recovery ?

1 0

hosted-engine volume removed 3 bricks (replica 3) out of 12 bricks, now I cant start hosted-engine vm
by adrianquintero＠gmail.com 15 Apr '21

15 Apr '21

Hi, I tried removing a replica 3 brick from a distributed replicated volume which holds the ovirt hosted-engine VM. As soon as I hit commit the VM went into pause, I tried to recover the volume ID "daa292aa-be5c-426e-b124-64263bf8a3ee" from the remvoed bricks and now I am able to do a "hosted-engine --vm-status Error I see in the logs: --------------------------------- MainThread::WARNING::2021-04-14 17:26:12,348::storage_broker::97::ovirt_hosted_engine_ha.broker.storage_broker.StorageBroker::(__init__) Can't connect vdsm storage: Command Image.prepare with args {'imageID': '9feffcfa-6af2-4de3-b7d8-e57b84d56003', 'storagepoolID': '00000000-0000-0000-0000-000000000000', 'volumeID': 'daa292aa-be5c-426e-b124-64263bf8a3ee', 'storagedomainID': '8db17b28-ecbb-4853-8a90-6ed2f69301eb'} failed: (code=201, message=Volume does not exist: (u'daa292aa-be5c-426e-b124-64263bf8a3ee',)) --------------------------------- on the following mount I see the volumeID twice: ------------------------ [root@vmm10 images]# find /rhev/data-center/mnt/glusterSD/192.168.0.4\:_engine/ -name "daa292aa-be5c-426e-b124-64263bf8a3ee" /rhev/data-center/mnt/glusterSD/192.168.0.4:_engine/8db17b28-ecbb-4853-8a90-6ed2f69301eb/images/9feffcfa-6af2-4de3-b7d8-e57b84d56003/daa292aa-be5c-426e-b124-64263bf8a3ee /rhev/data-center/mnt/glusterSD/192.168.0.4:_engine/8db17b28-ecbb-4853-8a90-6ed2f69301eb/images/9feffcfa-6af2-4de3-b7d8-e57b84d56003/daa292aa-be5c-426e-b124-64263bf8a3ee [root@vmm10 9feffcfa-6af2-4de3-b7d8-e57b84d56003]# ls -lh total 131M -rw-rw----. 1 vdsm kvm 64M Apr 14 19:40 daa292aa-be5c-426e-b124-64263bf8a3ee -rw-rw----. 1 vdsm kvm 64M Apr 14 19:40 daa292aa-be5c-426e-b124-64263bf8a3ee -rw-rw----. 1 vdsm kvm 1.0M Jul 1 2020 daa292aa-be5c-426e-b124-64263bf8a3ee.lease -rw-rw----. 1 vdsm kvm 1.0M Jul 1 2020 daa292aa-be5c-426e-b124-64263bf8a3ee.lease -rw-r--r--. 1 vdsm kvm 329 Jul 1 2020 daa292aa-be5c-426e-b124-64263bf8a3ee.meta -rw-r--r--. 1 vdsm kvm 329 Jul 1 2020 daa292aa-be5c-426e-b124-64263bf8a3ee.meta Any ideas on how to recover ?

1 0

Can't Create VM from Template in VM portal
by Andrey Rusakov 14 Apr '21

14 Apr '21

We are trying to orginize self manage VM portal for our customers. And there is VM portal in oVirt. What did we do - Create user, Crate group, create quota, create Vm template. All permissions by default + VmCreator (to allow user create disks from template). Problem Can't Create VM from Template - we got "No Disks Defined" on "Storage" page (create new VM) Posible solution - Grant "Disk Operator" Role, But in this case, All users can see All VMs. Is it posible to limit users to see VMs in a users group and permissions to create new VMs from template?

1 0

Ovirt node - 4.4.4 -> 4.4.5 upgrade failed - do i need a reinstall ? tried removing /dev/onn/ovirt-node-ng-4.4.5.1-0.20210323.0+1 to reinstall rpm..
by morgan cox 14 Apr '21

14 Apr '21

Hi. I have a 2 node cluster (both installed from the Ovirt-node iso) , 1 server is 100% fine, but one server I tried to update when there were issues with the ovirtmgmt network (I wasn't aware of at the time) - as a result the server update failed, and was still on ovirt-node 4.4.4 after - I could see the LVM layer for 4.4.5 though. The network is fine now (hence the other server being ok) - I tried reinstalling the package ovirt-node-ng-image-update-4.4.5.1-1.el8.noarch.rpm but it failed due to LVM lv for 4.4.5 already existing ... So I tried removing the LV - i.e # lvremove /dev/onn/ovirt-node-ng-4.4.5.1-0.20210323.0+1 however now I'm sure I have less 4.4.4 lvs .. i.e ------ [root@ng2-ovirt-kvm3 mcox]# lvs LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert home onn Vwi-aotz-- 1.00g pool00 10.05 ovirt-node-ng-4.4.4.1-0.20210208.0+1 onn Vwi-aotz-- 191.00g pool00 2.27 pool00 onn twi-aotz-- 218.00g 2.48 1.92 swap onn -wi-ao---- 4.00g tmp onn Vwi-aotz-- 1.00g pool00 2.24 var onn Vwi-aotz-- 15.00g pool00 2.80 var_crash onn Vwi-aotz-- 10.00g pool00 0.21 var_log onn Vwi-aotz-- 8.00g pool00 5.97 var_log_audit onn Vwi-aotz-- 2.00g pool00 1.14 ---- Where as on the working server I have these Ovirt Node LVs ovirt-node-ng-4.4.4.1-0.20210208.0 onn Vwi---tz-k 191.00g pool00 root ovirt-node-ng-4.4.4.1-0.20210208.0+1 onn Vwi-a-tz-- 191.00g pool00 ovirt-node-ng-4.4.4.1-0.20210208.0 1.86 ovirt-node-ng-4.4.5.1-0.20210323.0 onn Vri---tz-k 191.00g pool00 ovirt-node-ng-4.4.5.1-0.20210323.0+1 onn Vwi-aotz-- 191.00g pool00 ovirt-node-ng-4.4.5.1-0.20210323.0 1.58 Anyway I tried to reinstall the ovirt-node-ng-image-update-4.4.5.1-1.el8.noarch.rpm package after removal of lv and files in /boot But install still fails .. Is there anything I can do to update this node - or should I bite the bullet and reinstall ? this is from /var/log/imgbased.log -> -------------------------------------- 2021-04-14 16:05:56,634 [INFO] (MainThread) Adding a new layer after <Base ovirt-node-ng-4.4.5.1-0.20210323.0 [] /> 2021-04-14 16:05:56,634 [INFO] (MainThread) Adding a new layer after <Base ovirt-node-ng-4.4.5.1-0.20210323.0 [] /> 2021-04-14 16:05:56,634 [DEBUG] (MainThread) Basing new layer on previous: <Base ovirt-node-ng-4.4.5.1-0.20210323.0 [] /> 2021-04-14 16:05:56,634 [DEBUG] (MainThread) Finding next layer based on <Base ovirt-node-ng-4.4.5.1-0.20210323.0 [] /> 2021-04-14 16:05:56,634 [DEBUG] (MainThread) Suggesting for layer for base ovirt-node-ng-4.4.5.1-0.20210323.0 2021-04-14 16:05:56,635 [DEBUG] (MainThread) ... without layers 2021-04-14 16:05:56,635 [INFO] (MainThread) New layer will be: <Layer ovirt-node-ng-4.4.5.1-0.20210323.0+1 /> 2021-04-14 16:05:56,635 [DEBUG] (MainThread) Calling: (['vgs', '--noheadings', '--ignoreskippedcluster', '--select', 'vg_tags = imgbased:vg', '-o', 'vg_name'],) {'stderr': <_io.TextIOWrapper name='/dev/null' mode='w' encoding='UTF-8'>, 'close_fds': True} 2021-04-14 16:05:56,697 [DEBUG] (MainThread) Returned: b'onn' 2021-04-14 16:05:56,698 [DEBUG] (MainThread) Calling: (['vgs', '--noheadings', '--ignoreskippedcluster', '@imgbased:pool', '-o', 'lv_full_name'],) {'stderr': <_io.TextIOWrapper name='/dev/null' mode='w' encoding='UTF-8'>, 'close_fds': True} 2021-04-14 16:05:56,757 [DEBUG] (MainThread) Returned: b'onn/pool00' 2021-04-14 16:05:56,758 [DEBUG] (MainThread) Calling: (['lvs', '--noheadings', '--ignoreskippedcluster', '--nosuffix', '--units', 'm', '-o', 'metadata_percent,lv_metadata_size', 'onn/pool00'],) {'stderr': <_io.TextIOWrapper name='/dev/null' mode='w' encoding='UTF-8'>, 'close_fds': True} 2021-04-14 16:05:56,829 [DEBUG] (MainThread) Returned: b'2.05 1024.00' 2021-04-14 16:05:56,830 [DEBUG] (MainThread) Pool: onn/pool00, metadata size=1024.0M (2.05%) 2021-04-14 16:05:56,830 [DEBUG] (MainThread) Calling: (['lvchange', '--activate', 'y', 'onn/ovirt-node-ng-4.4.5.1-0.20210323.0', '--ignoreactivationskip'],) {'stderr': <_io.TextIOWrapper name='/dev/null' mode='w' encoding='UTF-8'>, 'close_fds': True} 2021-04-14 16:05:56,953 [DEBUG] (MainThread) Calling: (['lvcreate', '--snapshot', '--name', 'ovirt-node-ng-4.4.5.1-0.20210323.0+1', 'onn/ovirt-node-ng-4.4.5.1-0.20210323.0'],) {'close_fds': True, 'stderr': -2} 2021-04-14 16:05:57,111 [DEBUG] (MainThread) Returned: b'WARNING: Sum of all thin volume sizes (610.00 GiB) exceeds the size of thin pool onn/pool00 and the size of whole volume group (<277.78 GiB).\n Logical volume "ovirt-node-ng-4.4.5.1-0.20210323.0+1" created.' 2021-04-14 16:05:57,112 [DEBUG] (MainThread) Calling: (['lvchange', '--activate', 'y', 'onn/ovirt-node-ng-4.4.5.1-0.20210323.0+1', '--ignoreactivationskip'],) {'stderr': <_io.TextIOWrapper name='/dev/null' mode='w' encoding='UTF-8'>, 'close_fds': True} 2021-04-14 16:05:57,231 [DEBUG] (MainThread) Calling: (['lvchange', '--addtag', 'imgbased:layer', 'onn/ovirt-node-ng-4.4.5.1-0.20210323.0+1'],) {'stderr': <_io.TextIOWrapper name='/dev/null' mode='w' encoding='UTF-8'>, 'close_fds': True} 2021-04-14 16:05:57,310 [DEBUG] (MainThread) Returned: b'Logical volume onn/ovirt-node-ng-4.4.5.1-0.20210323.0+1 changed.' 2021-04-14 16:05:57,311 [DEBUG] (MainThread) Calling: (['lvs', '--noheadings', '--ignoreskippedcluster', '-olv_path', 'onn/ovirt-node-ng-4.4.5.1-0.20210323.0+1'],) {'stderr': <_io.TextIOWrapper name='/dev/null' mode='w' encoding='UTF-8'>, 'close_fds': True} 2021-04-14 16:05:57,383 [DEBUG] (MainThread) Returned: b'/dev/onn/ovirt-node-ng-4.4.5.1-0.20210323.0+1' 2021-04-14 16:05:57,400 [DEBUG] (MainThread) Calling: (['mktemp', '-d', '--tmpdir', 'mnt.XXXXX'],) {'close_fds': True, 'stderr': -2} 2021-04-14 16:05:57,404 [DEBUG] (MainThread) Returned: b'/tmp/mnt.aGJ3A' 2021-04-14 16:05:57,404 [DEBUG] (MainThread) Calling: (['mount', '-onouuid', '/dev/onn/ovirt-node-ng-4.4.5.1-0.20210323.0+1', '/tmp/mnt.aGJ3A'],) {'close_fds': True, 'stderr': -2} 2021-04-14 16:05:57,537 [DEBUG] (MainThread) Calling: (['umount', '-l', '/tmp/mnt.aGJ3A'],) {'close_fds': True, 'stderr': -2} 2021-04-14 16:05:57,561 [DEBUG] (MainThread) Calling: (['rmdir', '/tmp/mnt.aGJ3A'],) {'close_fds': True, 'stderr': -2} 2021-04-14 16:05:57,565 [DEBUG] (MainThread) Running: ['xfs_admin', '-U', 'generate', '/dev/onn/ovirt-node-ng-4.4.5.1-0.20210323.0+1'] 2021-04-14 16:05:57,566 [DEBUG] (MainThread) Calling: (['xfs_admin', '-U', 'generate', '/dev/onn/ovirt-node-ng-4.4.5.1-0.20210323.0+1'],) {'stderr': -2, 'close_fds': True} 2021-04-14 16:05:57,957 [DEBUG] (MainThread) Calling: (['lvchange', '--setactivationskip', 'n', 'onn/ovirt-node-ng-4.4.5.1-0.20210323.0+1'],) {'stderr': <_io.TextIOWrapper name='/dev/null' mode='w' encoding='UTF-8'>, 'close_fds': True} 2021-04-14 16:05:58,040 [DEBUG] (MainThread) Returned: b'Logical volume onn/ovirt-node-ng-4.4.5.1-0.20210323.0+1 changed.' 2021-04-14 16:05:58,041 [DEBUG] (MainThread) Calling: (['lvchange', '--setactivationskip', 'y', 'onn/ovirt-node-ng-4.4.5.1-0.20210323.0'],) {'stderr': <_io.TextIOWrapper name='/dev/null' mode='w' encoding='UTF-8'>, 'close_fds': True} 2021-04-14 16:05:58,116 [DEBUG] (MainThread) Returned: b'Logical volume onn/ovirt-node-ng-4.4.5.1-0.20210323.0 changed.' 2021-04-14 16:05:58,117 [DEBUG] (MainThread) Got: <LV 'onn/ovirt-node-ng-4.4.5.1-0.20210323.0+1' /> and <LV 'onn/ovirt-node-ng-4.4.5.1-0.20210323.0' /> 2021-04-14 16:05:58,117 [DEBUG] (MainThread) Calling: (['mount', '--make-rprivate', '/var'],) {'close_fds': True, 'stderr': -2} 2021-04-14 16:05:58,122 [DEBUG] (MainThread) Calling: (['systemctl', 'is-active', 'vdsmd'],) {'close_fds': True, 'stderr': -2} 2021-04-14 16:05:58,141 [DEBUG] (MainThread) Returned: b'active' 2021-04-14 16:05:58,141 [DEBUG] (MainThread) Calling: (['systemctl', 'stop', 'vdsmd'],) {'close_fds': True, 'stderr': -2} 2021-04-14 16:06:08,940 [DEBUG] (MainThread) Calling: (['systemctl', 'stop', 'supervdsmd'],) {'close_fds': True, 'stderr': -2} 2021-04-14 16:06:09,072 [DEBUG] (MainThread) Calling: (['systemctl', 'stop', 'vdsm-network'],) {'close_fds': True, 'stderr': -2} 2021-04-14 16:06:09,090 [DEBUG] (MainThread) Calling: (['vgchange', '-ay', '--select', 'vg_tags = imgbased:vg'],) {'stderr': <_io.TextIOWrapper name='/dev/null' mode='w' encoding='UTF-8'>, 'close_fds': True} 2021-04-14 16:06:09,167 [DEBUG] (MainThread) Returned: b'11 logical volume(s) in volume group "onn" now active' 2021-04-14 16:06:09,168 [DEBUG] (MainThread) Calling: (['lvs', '--noheadings', '--ignoreskippedcluster', '-o', 'lv_full_name', '--select', 'lv_tags = imgbased:base || lv_tags = imgbased:layer'],) {'stderr': <_io.TextIOWrapper name='/dev/null' mode='w' encoding='UTF-8'>, 'close_fds': True} 2021-04-14 16:06:09,229 [DEBUG] (MainThread) Returned: b'onn/ovirt-node-ng-4.4.4.1-0.20210208.0+1\n onn/ovirt-node-ng-4.4.5.1-0.20210323.0 \n onn/ovirt-node-ng-4.4.5.1-0.20210323.0+1' 2021-04-14 16:06:09,230 [DEBUG] (MainThread) All LV names: ['onn/ovirt-node-ng-4.4.4.1-0.20210208.0+1', 'onn/ovirt-node-ng-4.4.5.1-0.20210323.0', 'onn/ovirt-node-ng-4.4.5.1-0.20210323.0+1'] 2021-04-14 16:06:09,230 [DEBUG] (MainThread) All LVS: [<LV 'onn/ovirt-node-ng-4.4.4.1-0.20210208.0+1' />, <LV 'onn/ovirt-node-ng-4.4.5.1-0.20210323.0' />, <LV 'onn/ovirt-node-ng-4.4.5.1-0.20210323.0+1' />] 2021-04-14 16:06:09,230 [DEBUG] (MainThread) Calling: (['lvs', '--noheadings', '--ignoreskippedcluster', '-olv_tags', 'onn/ovirt-node-ng-4.4.4.1-0.20210208.0+1'],) {'stderr': <_io.TextIOWrapper name='/dev/null' mode='w' encoding='UTF-8'>, 'close_fds': True} 2021-04-14 16:06:09,293 [DEBUG] (MainThread) Returned: b'imgbased:layer' 2021-04-14 16:06:09,294 [DEBUG] (MainThread) Calling: (['lvs', '--noheadings', '--ignoreskippedcluster', '-olv_tags', 'onn/ovirt-node-ng-4.4.4.1-0.20210208.0+1'],) {'stderr': <_io.TextIOWrapper name='/dev/null' mode='w' encoding='UTF-8'>, 'close_fds': True} 2021-04-14 16:06:09,357 [DEBUG] (MainThread) Returned: b'imgbased:layer' 2021-04-14 16:06:09,358 [DEBUG] (MainThread) Calling: (['lvs', '--noheadings', '--ignoreskippedcluster', '-olv_tags', 'onn/ovirt-node-ng-4.4.5.1-0.20210323.0'],) {'stderr': <_io.TextIOWrapper name='/dev/null' mode='w' encoding='UTF-8'>, 'close_fds': True} 2021-04-14 16:06:09,417 [DEBUG] (MainThread) Returned: b'imgbased:base' 2021-04-14 16:06:09,418 [DEBUG] (MainThread) Calling: (['lvs', '--noheadings', '--ignoreskippedcluster', '-olv_tags', 'onn/ovirt-node-ng-4.4.5.1-0.20210323.0+1'],) {'stderr': <_io.TextIOWrapper name='/dev/null' mode='w' encoding='UTF-8'>, 'close_fds': True} 2021-04-14 16:06:09,490 [DEBUG] (MainThread) Returned: b'imgbased:layer' 2021-04-14 16:06:09,491 [DEBUG] (MainThread) Calling: (['lvs', '--noheadings', '--ignoreskippedcluster', '-olv_tags', 'onn/ovirt-node-ng-4.4.5.1-0.20210323.0+1'],) {'stderr': <_io.TextIOWrapper name='/dev/null' mode='w' encoding='UTF-8'>, 'close_fds': True} 2021-04-14 16:06:09,557 [DEBUG] (MainThread) Returned: b'imgbased:layer' 2021-04-14 16:06:09,558 [DEBUG] (MainThread) Our LVS: [<LV 'onn/ovirt-node-ng-4.4.4.1-0.20210208.0+1' />, <LV 'onn/ovirt-node-ng-4.4.5.1-0.20210323.0' />, <LV 'onn/ovirt-node-ng-4.4.5.1-0.20210323.0+1' />] 2021-04-14 16:06:09,558 [DEBUG] (MainThread) Names: ['ovirt-node-ng-4.4.4.1-0.20210208.0+1', 'ovirt-node-ng-4.4.5.1-0.20210323.0', 'ovirt-node-ng-4.4.5.1-0.20210323.0+1'] 2021-04-14 16:06:09,558 [DEBUG] (MainThread) Images: [<Layer ovirt-node-ng-4.4.4.1-0.20210208.0+1 />, <Base ovirt-node-ng-4.4.5.1-0.20210323.0 [] />, <Layer ovirt-node-ng-4.4.5.1-0.20210323.0+1 />] 2021-04-14 16:06:09,558 [DEBUG] (MainThread) Calling: (['umount', '-l', '/tmp/mnt.o5bFp'],) {'close_fds': True, 'stderr': -2} 2021-04-14 16:06:09,579 [DEBUG] (MainThread) Calling: (['rmdir', '/tmp/mnt.o5bFp'],) {'close_fds': True, 'stderr': -2} 2021-04-14 16:06:09,583 [DEBUG] (MainThread) Calling: (['umount', '-l', '/tmp/mnt.CcHrE'],) {'close_fds': True, 'stderr': -2} 2021-04-14 16:06:09,601 [DEBUG] (MainThread) Calling: (['rmdir', '/tmp/mnt.CcHrE'],) {'close_fds': True, 'stderr': -2} 2021-04-14 16:06:09,605 [ERROR] (MainThread) Update failed, resetting registered LVs 2021-04-14 16:06:09,606 [DEBUG] (MainThread) Calling: (['sync'],) {'close_fds': True, 'stderr': -2} 2021-04-14 16:06:09,615 [DEBUG] (MainThread) Calling: (['lvs', '--noheadings', '--ignoreskippedcluster', '-olv_dm_path', 'onn/ovirt-node-ng-4.4.5.1-0.20210323.0'],) {'stderr': <_io.TextIOWrapper name='/dev/null' mode='w' encoding='UTF-8'>, 'close_fds': True} 2021-04-14 16:06:09,683 [DEBUG] (MainThread) Returned: b'/dev/mapper/onn-ovirt--node--ng--4.4.5.1--0.20210323.0' 2021-04-14 16:06:09,684 [DEBUG] (MainThread) Calling: (['lvremove', '-ff', 'onn/ovirt-node-ng-4.4.5.1-0.20210323.0'],) {'stderr': <_io.TextIOWrapper name='/dev/null' mode='w' encoding='UTF-8'>, 'close_fds': True} 2021-04-14 16:06:09,820 [DEBUG] (MainThread) Returned: b'Logical volume "ovirt-node-ng-4.4.5.1-0.20210323.0" successfully removed' 2021-04-14 16:06:09,821 [DEBUG] (MainThread) Calling: (['lvs', '--noheadings', '--ignoreskippedcluster', '-olv_dm_path', 'onn/ovirt-node-ng-4.4.5.1-0.20210323.0+1'],) {'stderr': <_io.TextIOWrapper name='/dev/null' mode='w' encoding='UTF-8'>, 'close_fds': True} 2021-04-14 16:06:09,886 [DEBUG] (MainThread) Returned: b'/dev/mapper/onn-ovirt--node--ng--4.4.5.1--0.20210323.0+1' 2021-04-14 16:06:09,887 [DEBUG] (MainThread) Calling: (['lvremove', '-ff', 'onn/ovirt-node-ng-4.4.5.1-0.20210323.0+1'],) {'stderr': <_io.TextIOWrapper name='/dev/null' mode='w' encoding='UTF-8'>, 'close_fds': True} 2021-04-14 16:06:10,207 [DEBUG] (MainThread) Returned: b'Logical volume "ovirt-node-ng-4.4.5.1-0.20210323.0+1" successfully removed' Traceback (most recent call last): File "/usr/lib64/python3.6/runpy.py", line 193, in _run_module_as_main "__main__", mod_spec) File "/usr/lib64/python3.6/runpy.py", line 85, in _run_code exec(code, run_globals) File "/tmp/tmp.cyXrOTxRgb/usr/lib/python3.6/site-packages/imgbased/__main__.py", line 53, in <module> CliApplication() File "/tmp/tmp.cyXrOTxRgb/usr/lib/python3.6/site-packages/imgbased/__init__.py", line 82, in CliApplication app.hooks.emit("post-arg-parse", args) File "/tmp/tmp.cyXrOTxRgb/usr/lib/python3.6/site-packages/imgbased/hooks.py", line 120, in emit cb(self.context, *args) File "/tmp/tmp.cyXrOTxRgb/usr/lib/python3.6/site-packages/imgbased/plugins/update.py", line 75, in post_argparse six.reraise(*exc_info) File "/tmp/tmp.cyXrOTxRgb/usr/lib/python3.6/site-packages/six.py", line 703, in reraise raise value File "/tmp/tmp.cyXrOTxRgb/usr/lib/python3.6/site-packages/imgbased/plugins/update.py", line 66, in post_argparse base, _ = LiveimgExtractor(app.imgbase).extract(args.FILENAME) File "/tmp/tmp.cyXrOTxRgb/usr/lib/python3.6/site-packages/imgbased/plugins/update.py", line 148, in extract "%s" % size, nvr) File "/tmp/tmp.cyXrOTxRgb/usr/lib/python3.6/site-packages/imgbased/plugins/update.py", line 128, in add_base_with_tree new_layer_lv = self.imgbase.add_layer(new_base) File "/tmp/tmp.cyXrOTxRgb/usr/lib/python3.6/site-packages/imgbased/imgbase.py", line 213, in add_layer self.hooks.emit("new-layer-added", prev_lv, new_lv) File "/tmp/tmp.cyXrOTxRgb/usr/lib/python3.6/site-packages/imgbased/hooks.py", line 120, in emit cb(self.context, *args) File "/tmp/tmp.cyXrOTxRgb/usr/lib/python3.6/site-packages/imgbased/plugins/osupdater.py", line 88, in on_new_layer previous_layer_lv = get_prev_layer_lv(imgbase, new_lv) File "/tmp/tmp.cyXrOTxRgb/usr/lib/python3.6/site-packages/imgbased/plugins/osupdater.py", line 143, in get_prev_layer_lv layer_before = imgbase.naming.layer_before(new_layer) File "/tmp/tmp.cyXrOTxRgb/usr/lib/python3.6/site-packages/imgbased/naming.py", line 74, in layer_before layers = self.layers() File "/tmp/tmp.cyXrOTxRgb/usr/lib/python3.6/site-packages/imgbased/naming.py", line 58, in layers for b in self.tree(): File "/tmp/tmp.cyXrOTxRgb/usr/lib/python3.6/site-packages/imgbased/naming.py", line 226, in tree bases[img.base.nvr].layers.append(img) KeyError: <NVR ovirt-node-ng-4.4.4.1-0.20210208.0 /> --------------------

1 0

Re: Upgrade from 4.3.5 to 4.3.10 HE Host issue
by Yedidyah Bar David 14 Apr '21

14 Apr '21

Hi, On Mon, Mar 8, 2021 at 4:55 PM Marko Vrgotic <M.Vrgotic(a)activevideo.com> wrote: > > The broker log, these lines are pretty much repeating: > > > > MainThread::WARNING::2021-03-03 09:19:12,086::storage_broker::97::ovirt_hosted_engine_ha.broker.storage_broker.StorageBroker::(__init__) Can't connect vdsm storage: 'metadata_image_UUID can't be 'None' Please compare the content of /etc/ovirt-hosted-engine/hosted-engine.conf between all your hosts. host id should be unique per host, but otherwise they should be identical. If they are not, most likely there is some corruption somewhere - in the engine db or shared storage. You might want to skim this for a general rather-low-level overview: https://www.ovirt.org/images/Hosted-Engine-4.3-deep-dive.pdf Do you see no errors on your other hosts? In -ha logs? Please also note that 4.3 is EOL. The deploy process was completely rewritten in 4.4 (in ansible, previous was python), although should in principle behave similarly - so if your data is corrupted, upgrade to 4.4 probably won't fix it. Good luck and best regards, > > MainThread::INFO::2021-03-03 09:19:12,829::broker::47::ovirt_hosted_engine_ha.broker.broker.Broker::(run) ovirt-hosted-engine-ha broker 2.3.6 started > > MainThread::INFO::2021-03-03 09:19:12,829::monitor::40::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Searching for submonitors in /usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/broker/sub > > monitors > > MainThread::INFO::2021-03-03 09:19:12,829::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor cpu-load > > MainThread::INFO::2021-03-03 09:19:12,832::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor cpu-load-no-engine > > MainThread::INFO::2021-03-03 09:19:12,832::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor engine-health > > MainThread::INFO::2021-03-03 09:19:12,832::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor mem-free > > MainThread::INFO::2021-03-03 09:19:12,833::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor mgmt-bridge > > MainThread::INFO::2021-03-03 09:19:12,833::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor network > > MainThread::INFO::2021-03-03 09:19:12,833::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor storage-domain > > MainThread::INFO::2021-03-03 09:19:12,833::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor cpu-load > > MainThread::INFO::2021-03-03 09:19:12,834::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor cpu-load-no-engine > > MainThread::INFO::2021-03-03 09:19:12,835::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor engine-health > > MainThread::INFO::2021-03-03 09:19:12,835::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor mem-free > > MainThread::INFO::2021-03-03 09:19:12,835::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor mgmt-bridge > > MainThread::INFO::2021-03-03 09:19:12,835::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor network > > MainThread::INFO::2021-03-03 09:19:12,836::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor storage-domain > > MainThread::INFO::2021-03-03 09:19:12,836::monitor::50::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Finished loading submonitors > > MainThread::WARNING::2021-03-03 09:19:12,836::storage_broker::97::ovirt_hosted_engine_ha.broker.storage_broker.StorageBroker::(__init__) Can't connect vdsm storage: 'metadata_image_UUID can't be 'None' > > MainThread::INFO::2021-03-03 09:19:13,574::broker::47::ovirt_hosted_engine_ha.broker.broker.Broker::(run) ovirt-hosted-engine-ha broker 2.3.6 started > > MainThread::INFO::2021-03-03 09:19:13,575::monitor::40::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Searching for submonitors in /usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/broker/submonitors > > MainThread::INFO::2021-03-03 09:19:13,575::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor cpu-load > > MainThread::INFO::2021-03-03 09:19:13,577::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor cpu-load-no-engine > > MainThread::INFO::2021-03-03 09:19:13,578::monitor::49::ovirt_hosted_engine_ha.broker.monitor.Monitor::(_discover_submonitors) Loaded submonitor engine-health > > > > > > > > ----- > > kind regards/met vriendelijke groeten > > > > Marko Vrgotic > Sr. System Engineer @ System Administration > > > ActiveVideo > > o: +31 (35) 6774131 > > m: +31 (65) 5734174 > > e: m.vrgotic(a)activevideo.com > w: www.activevideo.com > > > > ActiveVideo Networks BV. Mediacentrum 3745 Joop van den Endeplein 1.1217 WJ Hilversum, The Netherlands. The information contained in this message may be legally privileged and confidential. It is intended to be read only by the individual or entity to whom it is addressed or by their designee. If the reader of this message is not the intended recipient, you are on notice that any distribution of this message, in any form, is strictly prohibited. If you have received this message in error, please immediately notify the sender and/or ActiveVideo Networks, LLC by telephone at +1 408.931.9200 and delete or destroy any copy of this message. > > > > > > > > From: Marko Vrgotic <M.Vrgotic(a)activevideo.com> > Date: Monday, 8 March 2021 at 15:34 > To: Yedidyah Bar David <didi(a)redhat.com> > Cc: users(a)ovirt.org <users(a)ovirt.org> > Subject: Re: [ovirt-users] Re: Upgrade from 4.3.5 to 4.3.10 HE Host issue > > Hi Didi, > > > > Please find the attached logs from Host and Engine. > > > > Host ovirt-sj-02 HE Undeploy 2021-03-08 14:15:52 till 2021-03-08 14:18:24 > > > > > > Host ovirt-sj-02 HE Deploy 2021-03-08 14:20:51 till 2021-03-08 14:23:22 > > > > I do see errors in the agent and broker and vdsm, but I do not see why it happened. > > > > Thank you for helping, let me know if any additional files are needed. > > > > > > ----- > > kind regards/met vriendelijke groeten > > > > Marko Vrgotic > Sr. System Engineer @ System Administration > > > ActiveVideo > > o: +31 (35) 6774131 > > m: +31 (65) 5734174 > > e: m.vrgotic(a)activevideo.com > w: www.activevideo.com > > > > ActiveVideo Networks BV. Mediacentrum 3745 Joop van den Endeplein 1.1217 WJ Hilversum, The Netherlands. The information contained in this message may be legally privileged and confidential. It is intended to be read only by the individual or entity to whom it is addressed or by their designee. If the reader of this message is not the intended recipient, you are on notice that any distribution of this message, in any form, is strictly prohibited. If you have received this message in error, please immediately notify the sender and/or ActiveVideo Networks, LLC by telephone at +1 408.931.9200 and delete or destroy any copy of this message. > > > > > > > > From: Yedidyah Bar David <didi(a)redhat.com> > Date: Monday, 8 March 2021 at 09:25 > To: Marko Vrgotic <M.Vrgotic(a)activevideo.com> > Cc: users(a)ovirt.org <users(a)ovirt.org> > Subject: Re: [ovirt-users] Re: Upgrade from 4.3.5 to 4.3.10 HE Host issue > > ***CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender!!!*** > > Hi, > > On Mon, Mar 8, 2021 at 10:13 AM Marko Vrgotic <M.Vrgotic(a)activevideo.com> wrote: > > > > I cannot find the reason why the re-Deployment on this Hosts fails, as it was already deployed on it before. > > > > No errors, found int the deployment, but it seems half done, based on messages I sent in previous email. > > Please check/share all relevant logs. Thanks. Can be all of /var/log > from engine and hosts, and at least: > > /var/log/ovirt-engine/engine.log > > /var/log/vdsm/* > > /var/log/ovirt-hosted-engine-ha/* > > Best regards, > -- > Didi -- Didi

2 1

Install oVirt using the Cockpit wizard
by rajkumar madhu 14 Apr '21

14 Apr '21

Hi Team, I have installed oVirt repo in my centos8 server ( dnf install https://resources.ovirt.org/pub/yum-repo/ovirt-release44.rpm ) then while executing Engine-setup command in my server .I am getting the below error message.Could you please check and give me some suggestions to resolve the issue . engine-setup [ INFO ] Stage: Initializing [ INFO ] Stage: Environment setup Configuration files: /etc/ovirt-engine-setup.conf.d/10-packaging-jboss.conf, /etc/ovirt-engine-setup.conf.d/10-packaging.conf, /etc/ovirt-engine-setup.conf.d/20-setup-ovirt-post.conf Log file: /var/log/ovirt-engine/setup/ovirt-engine-setup-20210412024224-fvaq4e.log Version: otopi-1.9.4 (otopi-1.9.4-1.el8) [ ERROR ] Failed to execute stage 'Environment setup': Cannot connect to ovirt cinderlib database using existing credentials: ovirt_cinderlib@localhost:5432 [ INFO ] Stage: Clean up Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20210412024224-fvaq4e.log [ INFO ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20210412024227-setup.conf' [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ ERROR ] Execution of setup failed Regards, Rajkumar M 9176772077.

2 1

Ovirt with Oracle Linux 8.3 & Cockpit - Direct Luns
by hansontodd＠gmail.com 14 Apr '21

14 Apr '21

Is Ovirt compatible with Oracle Linux 8.3? I have KVM & Cockpit running on Oracle Linux 8.3 but don't see a way to map direct luns (like RDM's) to the VM in the Cockpit interface. Do I need to move back to Centos 7.x or RHEL 7.x with Ovirt to be able to use direct luns? Can Ovirt and Cockpit coexist?

3 2

Error hosted-engine: Engine status: {"reason": "bad vm status", "health": "bad", "vm": "down_unexpected", "detail": "Down"}
by jesado74＠gmail.com 14 Apr '21

14 Apr '21

Hello. I have a 4 host infrastructure in ovirt and a few days ago the hosted-engine was turned off and I cannot turn it on from any host. Any ideas? Thanks. --== Host host1.myhost.com (id: 7) status ==-- conf_on_shared_storage : True Status up-to-date : True Hostname : host1.myhost.com Host ID : 7 Engine status : {"reason": "bad vm status", "health": "bad", "vm": "down_unexpected", "detail": "Down"} Score : 0 stopped : False Local maintenance : False crc32 : d5633613 local_conf_timestamp : 31176590 Host timestamp : 31176590

3 3

Add Gluster only nodes?
by mathias.westerlund＠wdmab.se 14 Apr '21

14 Apr '21

Hello! We have a medium sized hyper converged setup where we run SSD based bricks on the hosts. we also have an iscsi storage domain towards some spinner boxes for slow bulk storage but now we would like to add an medium sized storage option where mid sized requirements and mid level I/O requirements can exist. Our hyperconverged is NVME Our spinner is Sata. We now want to add an sata SSD storage option. We have some 25 slot hosts that are going to fill this usecase and we are now wondering, is there a way we can deploy gluster on these nodes using ovirt without giving them the VM role? Due to this storage being aimed towards things such as databases and other intensive (But not as intensive as our NVME layer) use cases we dont want there to be any VM load on these machines because of the pure number of bricks on the machines and the redhat best practice of 1 core per brick. Can i use cockpit/ovirt to deploy the above or do i have to set up an gluster cluster manually and then add it to ovirt???

1 0

New Setup - hosts - are not synchronized with their Logical Network configuration: ovirtmgmt.
by morgan cox 14 Apr '21

14 Apr '21

Hi After installing new hosts they show as status 'up'. however I get a warning such as Host ng2-ovirt-kvm4's following network(s) are not synchronized with their Logical Network configuration: ovirtmgmt. Which means ovirtmgmt is not working. I realise the issue is due to no network config for it - its set to DHCP and there is no server. The way I have setup the network on the hosts is (I used the ovirt-node 4.4.4 iso to install the nodes) /var/lib/vdsm/persistence/ ├── netconf -> /var/lib/vdsm/persistence/netconf.JkcBbtya └── netconf.JkcBbtya ├── bonds │ └── bond0 ├── devices └── nets ├── ovirtmgmt └── td-hv td-hv - is a bonded bridge + VLAN and has the network config with correct ip and where the firewall access is allowing the ports used for ovirt (see config below) Can I make the existing td-hv profile replace ovirtmgmt ? (i.e add ovirtmgmt functionality to existing network device td-hv) Or should I use the existing settings from td-hv and add them to ovirtmgmt and remove td-hv ? Config below - any advice would be great --- /etc/sysconfig/network-scripts/ifcfg-bond0.1700 BONDING_OPTS="mode=active-backup downdelay=0 miimon=100 updelay=0" TYPE=Bond BONDING_MASTER=yes NAME=bond0 UUID=5ab633aa-cd30-4ca8-9109-dbb4541f039b DEVICE=bond0 ONBOOT=yes HWADDR= MACADDR=3C:A8:2A:15:F6:12 MTU=1500 LLDP=no BRIDGE=ovirtmgmt --- --- [root@ng2-ovirt-kvm4 mcox]# cat /etc/sysconfig/network-scripts/ifcfg-bond0.1700 VLAN=yes TYPE=Vlan PHYSDEV=bond0 VLAN_ID=1700 REORDER_HDR=yes GVRP=no MVRP=no HWADDR= NAME=bond0.1700 UUID=e2b318e8-83af-4573-a637-fe20326f2c1a DEVICE=bond0.1700 ONBOOT=yes MTU=1500 LLDP=no BRIDGE=td-hv --- --- [root@ng2-ovirt-kvm4 mcox]# cat /etc/sysconfig/network-scripts/ifcfg-ovirtmgmt STP=no TYPE=Bridge HWADDR= MTU=1500 PROXY_METHOD=none BROWSER_ONLY=no BOOTPROTO=dhcp DEFROUTE=yes DHCP_CLIENT_ID=mac IPV4_DHCP_TIMEOUT=2147483647 IPV4_FAILURE_FATAL=no IPV6_DISABLED=yes IPV6INIT=no NAME=ovirtmgmt UUID=202586b0-ebe7-48ae-b316-e2cfd2dc4cc8 DEVICE=ovirtmgmt ONBOOT=yes AUTOCONNECT_SLAVES=yes LLDP=no ---

2 3

Need help recovering ovirt engine (was: New Management VLAN for hyperconverged cluster)
by David White 13 Apr '21

13 Apr '21

I was able to fix the connectivity issues between all 3 hosts. It turned out that I hadn't completely deleted the old vlan settings from the host. I re-ran "nmcli connection delete" on the old vlan. After that, I had to edit a network-scripts file and change/fix the bridge to use ifcfg-ovirtmgmt. After I did all that, the problematic host was accessible again. All 3 Gluster peers are now able to see each other and communicate over the management network. From the command line, I was then able to successfully run "hosted-engine --connect-storage" without errors. I was also able to then run "hosted-engine --vm-start". Unfortunately, the engine itself is still unstable, and when I access the web UI / oVirt Manager, it shows that all 3 hosts are inaccessible and down. I don't understand how the web UI is operational at all if the engine thinks that all 3 hosts are inaccessible. What's going on there? Although the initial problem was my own doing (I changed the management vlan), I'm deeply concerned with how unstable everything became - and has continued to be- ever since I lost connectivity to the 1 host. I thought the point of all of this was that things would (should) continue to work if 1 of the hosts went away. Anyway, at that point, all 3 hosts are able to communicate with each other over the management network, but the engine still thinks that all 3 hosts are down, and is unable to manage anything. Any suggestions on how to proceed would be much appreciated. Sent with ProtonMail Secure Email. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Wednesday, April 7, 2021 8:28 PM, David White <dmwhite823(a)protonmail.com> wrote: > I still haven't been able to resurrect the 1st host, so I've spent some time trying to get the hosted engine stable. I would welcome input on how to fix the problematic host so that it can be accessible again. > > As per my original email, this all started when I tried to change the management vlan. I honestly cannot remember what I did (if anything) to the actual hosts when this all started, but my troubleshooting steps today have been to try to fiddle with the vlan settings and /etc/sysconfig/network-scripts/ files on the problematic host to switch from the original vlan (1) to the new vlan (10). > > Until then, I'm troubleshooting why the hosted engine isn't really working, since the other two hosts are operational. > > The hosted engine is "running" -- I can access and navigate around the oVirt Manager. > However, it appears that all of the storage domains are down, and all of the hosts are "NonOperational". I was, however, able to put two of the hosts into Maintenance Mode, including the problematic 1st host. > > This is what I see on the 2nd host: > > [root@cha2-storage network-scripts]# gluster peer status > Number of Peers: 2 > > Hostname: cha1-storage.mgt.example.com > Uuid: 348de1f3-5efe-4e0c-b58e-9cf48071e8e1 > State: Peer in Cluster (Disconnected) > > Hostname: cha3-storage.mgt.example.com > Uuid: 0563c3e8-237d-4409-a09a-ec51719b0da6 > State: Peer in Cluster (Connected) > > [root@cha2-storage network-scripts]# hosted-engine --vm-status > The hosted engine configuration has not been retrieved from shared storage. Please ensure that ovirt-ha-agent is running and the storage server is reachable. > > [root@cha2-storage network-scripts]# hosted-engine --connect-storage > Traceback (most recent call last): > File "/usr/lib64/python3.6/runpy.py", line 193, in _run_module_as_main > "__main__", mod_spec) > File "/usr/lib64/python3.6/runpy.py", line 85, in _run_code > exec(code, run_globals) > File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_setup/connect_storage_server.py", line 30, in <module> > timeout=ohostedcons.Const.STORAGE_SERVER_TIMEOUT, > File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/client/client.py", line 312, in connect_storage_server > sserver.connect_storage_server(timeout=timeout) > File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/lib/storage_server.py", line 394, in connect_storage_server > 'Connection to storage server failed' > RuntimeError: Connection to storage server failed > > The ovirt-engine-ha service seems to be continuously trying to load / activate, but failing: > [root@cha2-storage network-scripts]# systemctl status -l ovirt-ha-agent > ● ovirt-ha-agent.service - oVirt Hosted Engine High Availability Monitoring Agent > Loaded: loaded (/usr/lib/systemd/system/ovirt-ha-agent.service; enabled; vendor preset: disabled) > Active: activating (auto-restart) (Result: exit-code) since Wed 2021-04-07 20:24:46 EDT; 60ms ago > Process: 124306 ExecStart=/usr/share/ovirt-hosted-engine-ha/ovirt-ha-agent (code=exited, status=157) > Main PID: 124306 (code=exited, status=157) > > Some recent entries in /var/log/ovirt-hosted-engine-ha/agent.log > MainThread::ERROR::2021-04-07 20:22:59,115::agent::144::ovirt_hosted_engine_ha.agent.agent.Agent::(_run_agent) Trying to restart agent > MainThread::INFO::2021-04-07 20:22:59,115::agent::89::ovirt_hosted_engine_ha.agent.agent.Agent::(run) Agent shutting down > MainThread::INFO::2021-04-07 20:23:09,717::agent::67::ovirt_hosted_engine_ha.agent.agent.Agent::(run) ovirt-hosted-engine-ha agent 2.4.6 started > MainThread::INFO::2021-04-07 20:23:09,742::hosted_engine::242::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_get_hostname) Certificate common name not found, using hostname to identify host > MainThread::INFO::2021-04-07 20:23:09,837::hosted_engine::548::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_initialize_broker) Initializing ha-broker connection > MainThread::INFO::2021-04-07 20:23:09,838::brokerlink::82::ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink::(start_monitor) Starting monitor network, options {'addr': '10.1.0.1', 'network_test': 'dns', 'tcp_t_address': '', 'tcp_t_port': ''} > MainThread::ERROR::2021-04-07 20:23:09,839::hosted_engine::564::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_initialize_broker) Failed to start necessary monitors > MainThread::ERROR::2021-04-07 20:23:09,842::agent::143::ovirt_hosted_engine_ha.agent.agent.Agent::(_run_agent) Traceback (most recent call last): > File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/lib/brokerlink.py", line 85, in start_monitor > response = self._proxy.start_monitor(type, options) > File "/usr/lib64/python3.6/xmlrpc/client.py", line 1112, in __call__ > return self.__send(self.__name, args) > File "/usr/lib64/python3.6/xmlrpc/client.py", line 1452, in __request > verbose=self.__verbose > File "/usr/lib64/python3.6/xmlrpc/client.py", line 1154, in request > return self.single_request(host, handler, request_body, verbose) > File "/usr/lib64/python3.6/xmlrpc/client.py", line 1166, in single_request > http_conn = self.send_request(host, handler, request_body, verbose) > File "/usr/lib64/python3.6/xmlrpc/client.py", line 1279, in send_request > self.send_content(connection, request_body) > File "/usr/lib64/python3.6/xmlrpc/client.py", line 1309, in send_content > connection.endheaders(request_body) > File "/usr/lib64/python3.6/http/client.py", line 1249, in endheaders > self._send_output(message_body, encode_chunked=encode_chunked) > File "/usr/lib64/python3.6/http/client.py", line 1036, in _send_output > self.send(msg) > File "/usr/lib64/python3.6/http/client.py", line 974, in send > self.connect() > File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/lib/unixrpc.py", line 74, in connect > self.sock.connect(base64.b16decode(self.host)) > FileNotFoundError: [Errno 2] No such file or directory > > During handling of the above exception, another exception occurred: > > Traceback (most recent call last): > File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/agent/agent.py", line 131, in _run_agent > return action(he) > File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/agent/agent.py", line 55, in action_proper > return he.start_monitoring() > File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/agent/hosted_engine.py", line 437, in start_monitoring > self._initialize_broker() > File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/agent/hosted_engine.py", line 561, in _initialize_broker > m.get('options', {})) > File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/lib/brokerlink.py", line 91, in start_monitor > ).format(t=type, o=options, e=e) > ovirt_hosted_engine_ha.lib.exceptions.RequestError: brokerlink - failed to start monitor via ovirt-ha-broker: [Errno 2] No such file or directory, [monitor: 'network', options: {'addr': '10.1.0.1', 'network_test': 'dns', 'tcp_t_address': '', 'tcp_t_port': ''}] > > MainThread::ERROR::2021-04-07 20:23:09,842::agent::144::ovirt_hosted_engine_ha.agent.agent.Agent::(_run_agent) Trying to restart agent > MainThread::INFO::2021-04-07 20:23:09,842::agent::89::ovirt_hosted_engine_ha.agent.agent.Agent::(run) Agent shutting down > > Sent with ProtonMail Secure Email. > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ > On Wednesday, April 7, 2021 5:36 PM, David White via Users <users(a)ovirt.org> wrote: > > > 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.

3 7

what host os version or ovirt node version I choose for my production setup
by dhanaraj.ramesh＠yahoo.com 13 Apr '21

13 Apr '21

We had done successful POC of ovirt node & HE with 4.4.5 version and now planning for production. However since 4.4.5 ovirt node& HE based on centOS 8.3, yet Red hat announced CentOs8.3 EOL by End of this year, is there any progress/plan to release ovirt nodes with CentOS stream soon? if we choose to go with Centos 8.3 based oVirt node, what could be the consequences in near term especially when it's come to next production release upgrade? Kindly suggest me which Host version I should choose for Production setup?

2 1

Adding physical RAM to the hosts
by David White 13 Apr '21

13 Apr '21

As readers will already know, I have three oVirt hosts in a hyperconverged cluster. I had a DIMM with too many errors on it, so I scavenged from a spare server that I had in my office precisely for this purpose. I went ahead and replaced all of the RAM, because the DIMMs in my spare were a different speed. While I was at it, I doubled the RAM on this 1 oVirt host. So now, two hosts have 32GB each. And the 3rd host now has 64GB. So total, I should have 128GB of RAM available to the cluster. The engine recognizes that the host now has 64GB of RAM. Screenshot below: [Screenshot from 2021-04-12 19-59-59.png] However, the engine dashboard still shows that only ~93GB of RAM are available to the cluster (screenshot below). [Screenshot from 2021-04-12 19-58-15.png] Should I be worried that the oVirt dashboard hasn't updated to ~128GB (or a bit less, I guess)? Do I need to do anything else? Sent with ProtonMail Secure Email.

2 2

Re: Engine Upgrade to 4.4.5 Version Number Question
by Yedidyah Bar David 13 Apr '21

13 Apr '21

On Tue, Apr 13, 2021 at 7:42 AM Nur Imam Febrianto <nur_imam(a)outlook.com> wrote: > > Fixes the issue by changing OVESETUP_ENGINE_CORE/enable=bool:'False' to OVESETUP_ENGINE_CORE/enable=bool:'True’ > > Still don’t know why it shows false, but now I can confirm after changing that to True, running engine-setup again upgraded my Engien to 4.4.5. > > > > Thanks for your help. Glad that it worked, and thanks for the report! I strongly recommend that you spend some time investigating what/who/why it was changed. This is most likely a mistake someone made at some point. It might be broader than just this file, or it might be some other kind of problem (e.g. a machine crashed in the middle of engine-setup and left files corrupted). If you can't find why/who, and suspect it's a bug, we'd definitely like to get more information. Some things you can check (other than usual site-specific things like who logged in, when you changed stuff there, etc.): - All /var/log/ovirt-engine/setup/* logs, their timestamps, and their contents (e.g. grep them all for "OVESETUP_ENGINE_CORE/enable"). - /etc/ovirt-engine-setup.conf.d/20-setup-ovirt-post.conf* - the file itself, and backups (made by engine-setup or otherwise), timestamps etc. - /etc/ovirt-engine/uninstall.d/* - engine-setup (and other related tools) keep there information about all files it created/chagned - mainly used by engine-cleanup Good luck and best regards, -- Didi

1 0

Re: Engine Upgrade to 4.4.5 Version Number Question
by Yedidyah Bar David 13 Apr '21

13 Apr '21

On Sun, Apr 11, 2021 at 10:19 AM Nur Imam Febrianto <nur_imam(a)outlook.com> wrote: > > Only DWH are deployed on another machine. Please provide more details. The setup log you provided shows nothing as configured - all of engine+dwh+grafana are disabled. Best regards, > I don't edit any configuration manually beside the one that used for SSO. Any clue why is this happened? > > Thanks before. > > Regards, > > Nur Imam Febrianto > Sent from Nine > ________________________________ > From: Yedidyah Bar David <didi(a)redhat.com> > Sent: Sunday, April 11, 2021 13:45 > To: Nur Imam Febrianto > Cc: oVirt Users > Subject: Re: [ovirt-users] Engine Upgrade to 4.4.5 Version Number Question > > On Sat, Apr 10, 2021 at 8:08 AM Nur Imam Febrianto <nur_imam(a)outlook.com> wrote: > > > > Here is the setup logs. > > Do you have "everything" (engine, dwh, etc.) on the same machine, or > different stuff set up on different machines? > > Any chance you manually edited > /etc/ovirt-engine-setup.conf.d/20-setup-ovirt-post.conf for any > reason? > > I see there: > > 2021-03-18 22:45:25,952+0700 DEBUG otopi.context > context.dumpEnvironment:775 ENV > OVESETUP_ENGINE_CORE/enable=bool:'False' > > This normally happens only if the engine was not configured on this machine. > > Best regards, > > > > > Thanks. > > > > > > > > From: Yedidyah Bar David > > Sent: 07 April 2021 12:36 > > To: Nur Imam Febrianto > > Cc: oVirt Users > > Subject: Re: [ovirt-users] Engine Upgrade to 4.4.5 Version Number Question > > > > > > > > On Tue, Apr 6, 2021 at 6:49 PM Nur Imam Febrianto <nur_imam(a)outlook.com> wrote: > > > > > > 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 ? > > > > Please share the setup log (in /var/log/ovirt-engine/setup). Thanks. > > > > Best regards, > > -- > > Didi > > > > > > > > -- > Didi > -- Didi

2 1

Ovirt with Oracle Linux 8.3 & Cockpit - Direct Luns
by hansontodd＠gmail.com 12 Apr '21

12 Apr '21

Is Ovirt compatible with Oracle Linux 8.3? I have KVM & Cockpit running on Oracle Linux 8.3 but don't see a way to map direct luns (like RDM's) to the VM in the Cockpit interface. Do I need to move back to Centos 7.x or RHEL 7.x with Ovirt to be able to use direct luns? Can Ovirt and Cockpit coexist?

1 0

Cannot edit VM. Maximum SATA devices exceeded
by adm＠m-go.ru 12 Apr '21

12 Apr '21

I tried to delete one of the disks, but I can't do it. https://m-go.ru/stream/item/4780 Disk as SATA

2 2

ipxe support with Q35 chipset and UEFI
by Gianluca Cecchi 12 Apr '21

12 Apr '21

Hello, I'm doing some tests with iPXE (downloaded latest version cloning the git repo some days ago). I'm using oVirt 4.4.5 with VMs configured with different chipset/firmware type. It seems that using dhcpd.conf directive of type if exists user-class and option user-class = "iPXE" { filename "http://my_http_server/..."; } else { ... } the VM boot catches it when I use Q35 Chipset with BIOS, while it goes inside the "else" section if using Q35 Chipset with UEFI (not the SecureBoot one) Does this mean that the Q35 UEFI doesn't support iPXE? BTW: if anyone has suggestions about an utility that can let me boot via network and give the user a general menu from which he/she can go and choose standard pxe with bios or uefi boot, to be able to install both Linux based systems and other ones, such as ESXi hosts, both with BIOS and UEFI, it is welcome Gianluca

1 0

where I can find 4.4.5 Data warehouse repo
by dhanaraj.ramesh＠yahoo.com 12 Apr '21

12 Apr '21

below repo is not working in CentOS 7 OS, is there any repo available for centos? yum install https://resources.ovirt.org/pub/yum-repo/ovirt-release44.rpm

2 2

Re: Engine Upgrade to 4.4.5 Version Number Question
by Yedidyah Bar David 11 Apr '21

11 Apr '21

On Sat, Apr 10, 2021 at 8:08 AM Nur Imam Febrianto <nur_imam(a)outlook.com> wrote: > > Here is the setup logs. Do you have "everything" (engine, dwh, etc.) on the same machine, or different stuff set up on different machines? Any chance you manually edited /etc/ovirt-engine-setup.conf.d/20-setup-ovirt-post.conf for any reason? I see there: 2021-03-18 22:45:25,952+0700 DEBUG otopi.context context.dumpEnvironment:775 ENV OVESETUP_ENGINE_CORE/enable=bool:'False' This normally happens only if the engine was not configured on this machine. Best regards, > > Thanks. > > > > From: Yedidyah Bar David > Sent: 07 April 2021 12:36 > To: Nur Imam Febrianto > Cc: oVirt Users > Subject: Re: [ovirt-users] Engine Upgrade to 4.4.5 Version Number Question > > > > On Tue, Apr 6, 2021 at 6:49 PM Nur Imam Febrianto <nur_imam(a)outlook.com> wrote: > > > > 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 ? > > Please share the setup log (in /var/log/ovirt-engine/setup). Thanks. > > Best regards, > -- > Didi > > -- Didi

2 1

Re: Engine Upgrade to 4.4.5 Version Number Question
by Yedidyah Bar David 10 Apr '21

10 Apr '21

On Tue, Apr 6, 2021 at 6:49 PM Nur Imam Febrianto <nur_imam(a)outlook.com> wrote: > > 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 ? Please share the setup log (in /var/log/ovirt-engine/setup). Thanks. Best regards, -- Didi

2 1

How to detach FC Storage Domain
by Miguel Garcia 09 Apr '21

09 Apr '21

I have added some FC storage domains into incorrect Data Center, I'm trying to detach them by moving to Storage -> Storage domain select storage domain -> Data Center tab and click on detach button then got the following error: Failing detaching storage domain from Data Center In log files so far found next lines: 2021-03-25 22:58:41,621-04 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.DetachStorageDomainVDSCommand] (EE-ManagedThreadFactory-engine-Thread-2636) [0a08dff7-13c4-49c2-b451-0dea136941ec] START, DetachStorageDomainVDSCommand( DetachStorageDomainVDSCommandParameters:{storagePoolId='68b8d8e9-af51-457d-9b9d-36e37ad60d55', ignoreFailoverLimit='false', storageDomainId='a1f6a779-a65f-427c-b034-174e1150361d', masterDomainId='00000000-0000-0000-0000-000000000000', masterVersion='1', force='false'}), log id: 42974429 2021-03-25 22:58:42,941-04 ERROR [org.ovirt.engine.core.vdsbroker.irsbroker.DetachStorageDomainVDSCommand] (EE-ManagedThreadFactory-engine-Thread-2636) [0a08dff7-13c4-49c2-b451-0dea136941ec] Failed in 'DetachStorageDomainVDS' method 2021-03-25 22:58:42,944-04 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-2636) [0a08dff7-13c4-49c2-b451-0dea136941ec] EVENT_ID: IRS_BROKER_COMMAND_FAILURE(10,803), VDSM command DetachStorageDomainVDS failed: Storage domain does not exist: (u'a1f6a779-a65f-427c-b034-174e1150361d',) 2021-03-25 22:58:42,945-04 ERROR [org.ovirt.engine.core.vdsbroker.irsbroker.DetachStorageDomainVDSCommand] (EE-ManagedThreadFactory-engine-Thread-2636) [0a08dff7-13c4-49c2-b451-0dea136941ec] Command 'DetachStorageDomainVDSCommand( DetachStorageDomainVDSCommandParameters:{storagePoolId='68b8d8e9-af51-457d-9b9d-36e37ad60d55', ignoreFailoverLimit='false', storageDomainId='a1f6a779-a65f-427c-b034-174e1150361d', masterDomainId='00000000-0000-0000-0000-000000000000', masterVersion='1', force='false'})' execution failed: IRSGenericException: IRSErrorException: Failed to DetachStorageDomainVDS, error = Storage domain does not exist: (u'a1f6a779-a65f-427c-b034-174e1150361d',), code = 358 Seems that the storage domain does not exists. Is there a way to force detach action? Thanks in advance

3 4

extending vm disk when vm is up
by Nathanaël Blanchet 08 Apr '21

08 Apr '21

Hello, Why it is not possible to extend disk size into UI when a vm is up while it is possible to do the same with API/SDK/ansible? -- Nathanaël Blanchet Supervision réseau SIRE 227 avenue Professeur-Jean-Louis-Viala 34193 MONTPELLIER CEDEX 5 Tél. 33 (0)4 67 54 84 55 Fax 33 (0)4 67 54 84 14 blanchet(a)abes.fr

2 1

Destroyed VM blocking hosts/filling logs
by davidk＠riavera.com 08 Apr '21

08 Apr '21

Hello, I've somehow gotten one of my VMs stuck in a state that ovirt seems to be rather confused about its existence of now. I'm running oVirt 4.3.10 and using oVirt Node on all the hosts. My engine and host event logs are now filling up very rapidly with this error: VDSM node217 command DestroyVDS failed: General Exception: ("'1048576'",) I was playing with hugetable support, and that error number or string looks suspiciously like the "hugetable size" custom property I set on the VM. This VM was migrated to another host at one point as well, and now that host is also generating the same error as well. When I try to move these hosts to maintenance mode, they get stuck in "Preparing for Maintenance" while it tries to migrate/deal with the VM that's not there any more. Forcibly rebooting the hosts does not change anything. The VM state/host seems to be captured somewhere persistent in this case. The VM in question is not running, and I can start it up on another host successfully, but ovirt still thinks it exists on the other 2 hosts no matter what I do. Is there perhaps some way to delete it from the engine database directly to straighten things out? Here's a dump of the vdsm log on one of the hosts. I haven't been able to pinpoint what the exact issue is or how to fix it, but hopefully someone here will have seen this before? 2021-04-03 04:40:35,515+0000 INFO (jsonrpc/1) [api.virt] START destroy(gracefulAttempts=1) from=::ffff:10.100.0.210,58150, vmId=58abf0cf-d7b9-4067-a86a-e619928368e7 (api:48) 2021-04-03 04:40:35,516+0000 INFO (jsonrpc/1) [virt.vm] (vmId='58abf0cf-d7b9-4067-a86a-e619928368e7') Release VM resources (vm:5186) 2021-04-03 04:40:35,516+0000 WARN (jsonrpc/1) [virt.vm] (vmId='58abf0cf-d7b9-4067-a86a-e619928368e7') trying to set state to Powering down when already Down (vm:626) 2021-04-03 04:40:35,516+0000 INFO (jsonrpc/1) [virt.vm] (vmId='58abf0cf-d7b9-4067-a86a-e619928368e7') Stopping connection (guestagent:455) 2021-04-03 04:40:35,517+0000 INFO (jsonrpc/1) [vdsm.api] START teardownImage(sdUUID='a08af6be-3802-4bb1-9fa5-4b6a10227290', spUUID='78dc095a-5238-11e8-b8bf-00163e6a7af9', imgUUID='9c896907-59b0-4983-9478-b36b2c2eb01e', volUUID=None) from=::ffff:10.100.0.210,58150, task_id=fc946d20-126a-4fd0-9078-91 4b4a64b1d9 (api:48) 2021-04-03 04:40:35,518+0000 INFO (jsonrpc/1) [storage.StorageDomain] Removing image rundir link u'/var/run/vdsm/storage/a08af6be-3802-4bb1-9fa5-4b6a10227290/9c896907-59b0-4983-9478-b36b2c2eb01e' (fileSD:592) 2021-04-03 04:40:35,518+0000 INFO (jsonrpc/1) [vdsm.api] FINISH teardownImage return=None from=::ffff:10.100.0.210,58150, task_id=fc946d20-126a-4fd0-9078-914b4a64b1d9 (api:54) 2021-04-03 04:40:35,519+0000 INFO (jsonrpc/1) [vdsm.api] START teardownImage(sdUUID='b891448d-dd92-4a7b-a51a-22abc3d7da67', spUUID='78dc095a-5238-11e8-b8bf-00163e6a7af9', imgUUID='c0e95483-35f1-4a61-958e-4e308b70d3f8', volUUID=None) from=::ffff:10.100.0.210,58150, task_id=77c0fdca-e13a-44b5-9a00-29 0522b194b2 (api:48) 2021-04-03 04:40:35,520+0000 INFO (jsonrpc/1) [storage.StorageDomain] Removing image rundir link u'/var/run/vdsm/storage/b891448d-dd92-4a7b-a51a-22abc3d7da67/c0e95483-35f1-4a61-958e-4e308b70d3f8' (fileSD:592) 2021-04-03 04:40:35,520+0000 INFO (jsonrpc/1) [vdsm.api] FINISH teardownImage return=None from=::ffff:10.100.0.210,58150, task_id=77c0fdca-e13a-44b5-9a00-290522b194b2 (api:54) 2021-04-03 04:40:35,521+0000 INFO (jsonrpc/1) [virt.vm] (vmId='58abf0cf-d7b9-4067-a86a-e619928368e7') Stopping connection (guestagent:455) 2021-04-03 04:40:35,521+0000 WARN (jsonrpc/1) [root] File: /var/lib/libvirt/qemu/channels/58abf0cf-d7b9-4067-a86a-e619928368e7.ovirt-guest-agent.0 already removed (fileutils:54) 2021-04-03 04:40:35,521+0000 WARN (jsonrpc/1) [root] Attempting to remove a non existing network: ovirtmgmt/58abf0cf-d7b9-4067-a86a-e619928368e7 (libvirtnetwork:198) 2021-04-03 04:40:35,522+0000 WARN (jsonrpc/1) [root] Attempting to remove a non existing net user: ovirtmgmt/58abf0cf-d7b9-4067-a86a-e619928368e7 (libvirtnetwork:205) 2021-04-03 04:40:35,526+0000 WARN (jsonrpc/1) [root] Attempting to remove a non existing network: ovirtmgmt/58abf0cf-d7b9-4067-a86a-e619928368e7 (libvirtnetwork:198) 2021-04-03 04:40:35,526+0000 WARN (jsonrpc/1) [root] Attempting to remove a non existing net user: ovirtmgmt/58abf0cf-d7b9-4067-a86a-e619928368e7 (libvirtnetwork:205) 2021-04-03 04:40:35,527+0000 WARN (jsonrpc/1) [root] File: /var/lib/libvirt/qemu/channels/58abf0cf-d7b9-4067-a86a-e619928368e7.org.qemu.guest_agent.0 already removed (fileutils:54) 2021-04-03 04:40:35,528+0000 WARN (jsonrpc/1) [virt.vm] (vmId='58abf0cf-d7b9-4067-a86a-e619928368e7') timestamp already removed from stats cache (vm:2445) 2021-04-03 04:40:35,531+0000 ERROR (jsonrpc/1) [api] FINISH destroy error='1048576' (api:134) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/common/api.py", line 124, in method ret = func(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/API.py", line 333, in destroy res = self.vm.destroy(gracefulAttempts) File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 5283, in destroy result = self.doDestroy(gracefulAttempts, reason) File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 5302, in doDestroy return self.releaseVm(gracefulAttempts) File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 5207, in releaseVm self._cleanup() File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 2382, in _cleanup self._cleanup_hugepages() File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 2393, in _cleanup_hugepages self.nr_hugepages, self.hugepagesz File "/usr/lib/python2.7/site-packages/vdsm/hugepages.py", line 243, in calculate_required_deallocation _preallocated_hugepages(vm_hugepagesz)) File "/usr/lib/python2.7/site-packages/vdsm/hugepages.py", line 262, in _preallocated_hugepages kernel_args['hugepagesz'] File "/usr/lib/python2.7/site-packages/vdsm/hugepages.py", line 291, in _cmdline_hugepagesz_to_kb }[cmdline] KeyError: '1048576' 2021-04-03 04:40:35,531+0000 INFO (jsonrpc/1) [api.virt] FINISH destroy return={'status': {'message': 'General Exception: ("\'1048576\'",)', 'code': 100}} from=::ffff:10.100.0.210,58150, vmId=58abf0cf-d7b9-4067-a86a-e619928368e7 (api:54) 2021-04-03 04:40:35,532+0000 INFO (jsonrpc/1) [jsonrpc.JsonRpcServer] RPC call VM.destroy failed (error 100) in 0.02 seconds (__init__:312)

4 9

[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

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

01 Apr '21

oVirt 4.4.6 Second Release Candidate is now available for testing The oVirt Project is pleased to announce the availability of oVirt 4.4.6 Second Release Candidate for testing, as of April 1st, 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

Locked disks
by Giulio Casella 01 Apr '21

01 Apr '21

Since yesterday I found a couple VMs with locked disk. I don't know the reason, I suspect some interaction made by our backup system (vprotect, snapshot based), despite it's working for more than a year. I'd give a chance to unlock_entity.sh script, but it reports: CAUTION, this operation may lead to data corruption and should be used with care. Please contact support prior to running this command Do you think I should trust? Is it safe? VMs are in production... My manager is 4.4.4.7-1.el8 (CentOS stream 8), hosts are oVirt Node 4.4.4 TIA, Giulio

3 7