- Users - oVirt List Archives

Upgrade oVirt from 4.3.10 to 4.4.2 and AD users
by Gianluca Cecchi 06 Oct '20

06 Oct '20

Hello, I'm upgrading a standalone engine with local database and with 3 hosts from oVirt 4.3.10 to 4.4.2 and I'm cross checking both oVirt and RHV documents. In my oVirt environment I have integration with AD for web admin access. Inside RHV upgrade guide docs there is this statement regarding manager upgrade: " Install optional extension packages if they were installed on the Red Hat Virtualization Manager 4.3 machine. # yum install ovirt-engine-extension-aaa-ldap ovirt-engine-extension-aaa-misc ovirt-engine-extension-logger-log4j NOTE The configuration for these package extensions must be manually reapplied because they are not migrated as part of the backup and restore process. " In my case I had ovirt-engine-extension-aaa-ldap and ovirt-engine-extension-aaa-misc installed on 4.3.10. So after "engine-backup --mode=restore ...." command I executed: [root@ovmgr1 ~]# yum install ovirt-engine-extension-aaa-ldap ovirt-engine-extension-aaa-misc Last metadata expiration check: 0:01:11 ago on Tue 06 Oct 2020 11:23:04 AM CEST. Dependencies resolved. ========================================================================================== Package Arch Version Repository Size ========================================================================================== Installing: ovirt-engine-extension-aaa-ldap noarch 1.4.1-1.el8 ovirt-4.4 127 k ovirt-engine-extension-aaa-misc noarch 1.1.0-1.el8 ovirt-4.4 37 k Installing dependencies: unboundid-ldapsdk noarch 4.0.14-2.el8 ovirt-4.4-centos-ovirt44 4.0 M Transaction Summary ========================================================================================== Install 3 Packages Total download size: 4.2 M Installed size: 4.5 M and followed the next upgrade flow steps. After finishing the engine upgrade with the "engine-setup" step, it seems actually that I can still connect to my engine with my AD accounts, so that I don't have to do any manual step described... Does it match any one other experience? Gianluca

2 1

oVirt Node 4.4.2 is now generally available
by Sandro Bonazzola 06 Oct '20

06 Oct '20

oVirt Node 4.4.2 is now generally available The oVirt project is pleased to announce the general availability of oVirt Node 4.4.2 , as of September 25th, 2020. This release completes the oVirt 4.4.2 release published on September 17th Important notes before you install / upgrade Please note that oVirt 4.4 only supports clusters and data centers with compatibility version 4.2 and above. If clusters or data centers are running with an older compatibility version, you need to upgrade them to at least 4.2 (4.3 is recommended). Please note that in RHEL 8 / CentOS 8 several devices that worked on EL7 are no longer supported. For example, the megaraid_sas driver is removed. If you use Enterprise Linux 8 hosts you can try to provide the necessary drivers for the deprecated hardware using the DUD method (See the users’ mailing list thread on this at https://lists.ovirt.org/archives/list/users@ovirt.org/thread/NDSVUZSESOXEFJ… ) How to prevent hosts entering emergency mode after upgrade from oVirt 4.4.1 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.2 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.2 (redeploy in case of already being on 4.4.2). 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>. What’s new in oVirt Node 4.4.2 Release? oVirt Node has been updated, including: - oVirt 4.4.2: http://www.ovirt.org/release/4.4.2/ - Ansible 2.9.13: https://github.com/ansible/ansible/blob/stable-2.9/changelogs/CHANGELOG-v2.… - Glusterfs 7.7: https://docs.gluster.org/en/latest/release-notes/7.7/ - Advanced Virtualization 8.2.1 See the release notes [1] for installation instructions and a list of new features and bugs fixed. Additional resources: - Read more about the oVirt 4.4.2 release highlights: http://www.ovirt.org/release/4.4.2/ - 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.2/ [2] http://resources.ovirt.org/pub/ovirt-4.4/iso/ -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/> *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

6 27

Re: Is it possible to backup stopped vm? (ovirt 4.4)
by Nir Soffer 06 Oct '20

06 Oct '20

On Tue, Oct 6, 2020 at 4:08 PM Łukasz Kołaciński <l.kolacinski(a)storware.eu> wrote: > > Hello, > While trying to backup stopped VM (with POST on /ovirt-engine/api/vms/b79b34c0-d8db-43e5-916e-5528ff7bcfbe/backups) I got the response: > > <?xml version="1.0" encoding="UTF-8" standalone="yes"?> > <fault> > <detail>[Cannot backup VM. The Virtual Machine should be in Up status.]</detail> > <reason>Operation Failed</reason> > </fault> Yes, this is not supported now. > I found here: https://www.ovirt.org/develop/release-management/features/storage/increment… that it should be possible to back up a virtual machine that is not running. > "If the VM is not running, the system will create a paused, stripped-down version of the VM, with only backup disks attached, and use libvirt API to start and stop the backup." This is a possible solution we considered, but it is not implemented yet. The next line is: Since creating special paused VM for backing up non-running VM is a lot of work, we may defer support for backing up non-running VMs. We got a request to implement this from other backup vendor, and we are discussing the possible solutions with platform folks. Nir

1 0

Is it possible to backup stopped vm? (ovirt 4.4)
by Łukasz Kołaciński 06 Oct '20

06 Oct '20

Hello, While trying to backup stopped VM (with POST on /ovirt-engine/api/vms/b79b34c0-d8db-43e5-916e-5528ff7bcfbe/backups) I got the response: <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <fault> <detail>[Cannot backup VM. The Virtual Machine should be in Up status.]</detail> <reason>Operation Failed</reason> </fault> I found here: https://www.ovirt.org/develop/release-management/features/storage/increment… that it should be possible to back up a virtual machine that is not running. "If the VM is not running, the system will create a paused, stripped-down version of the VM, with only backup disks attached, and use libvirt API to start and stop the backup." But it doesn't seem to work. Regards, Łukasz Kołaciński Junior Java Developer e-mail: l.kolacinski(a)storware.eu<mailto:l.kolacinski@storware.eu> <mailto:m.helbert@storware.eu> [STORWARE]<http://www.storware.eu/> ul. Leszno 8/44 01-192 Warszawa www.storware.eu <https://www.storware.eu/> [facebook]<https://www.facebook.com/storware> [twitter]<https://twitter.com/storware> [linkedin]<https://www.linkedin.com/company/storware> [Storware_Stopka_09]<https://www.youtube.com/channel/UCKvLitYPyAplBctXibFWrkw> Storware Spółka z o.o. nr wpisu do ewidencji KRS dla M.St. Warszawa 000510131 , NIP 5213672602. Wiadomość ta jest przeznaczona jedynie dla osoby lub podmiotu, który jest jej adresatem i może zawierać poufne i/lub uprzywilejowane informacje. Zakazane jest jakiekolwiek przeglądanie, przesyłanie, rozpowszechnianie lub inne wykorzystanie tych informacji lub podjęcie jakichkolwiek działań odnośnie tych informacji przez osoby lub podmioty inne niż zamierzony adresat. Jeżeli Państwo otrzymali przez pomyłkę tę informację prosimy o poinformowanie o tym nadawcy i usunięcie tej wiadomości z wszelkich komputerów. This message is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you have received this message in error, please contact the sender and remove the material from all of your computer systems.

1 0

Re: OVN Geneve tunnels not been established
by Konstantinos Betsis 06 Oct '20

06 Oct '20

I did a restart of the ovn-controller, this is the output of the ovn-controller.log 2020-09-11T10:54:07.566Z|00001|vlog|INFO|opened log file /var/log/openvswitch/ovn-controller.log 2020-09-11T10:54:07.568Z|00002|reconnect|INFO|unix:/var/run/openvswitch/db.sock: connecting... 2020-09-11T10:54:07.568Z|00003|reconnect|INFO|unix:/var/run/openvswitch/db.sock: connected 2020-09-11T10:54:07.570Z|00004|main|INFO|OVS IDL reconnected, force recompute. 2020-09-11T10:54:07.571Z|00005|reconnect|INFO|ssl:OVIRT_ENGINE_IP:6642: connecting... 2020-09-11T10:54:07.571Z|00006|main|INFO|OVNSB IDL reconnected, force recompute. 2020-09-11T10:54:07.685Z|00007|stream_ssl|WARN|SSL_connect: unexpected SSL connection close 2020-09-11T10:54:07.685Z|00008|reconnect|INFO|ssl:OVIRT_ENGINE_IP:6642: connection attempt failed (Protocol error) 2020-09-11T10:54:08.685Z|00009|reconnect|INFO|ssl:OVIRT_ENGINE_IP:6642: connecting... 2020-09-11T10:54:08.800Z|00010|stream_ssl|WARN|SSL_connect: unexpected SSL connection close 2020-09-11T10:54:08.800Z|00011|reconnect|INFO|ssl:OVIRT_ENGINE_IP:6642: connection attempt failed (Protocol error) 2020-09-11T10:54:08.800Z|00012|reconnect|INFO|ssl:OVIRT_ENGINE_IP:6642: waiting 2 seconds before reconnect 2020-09-11T10:54:10.802Z|00013|reconnect|INFO|ssl:OVIRT_ENGINE_IP:6642: connecting... 2020-09-11T10:54:10.917Z|00014|stream_ssl|WARN|SSL_connect: unexpected SSL connection close 2020-09-11T10:54:10.917Z|00015|reconnect|INFO|ssl:OVIRT_ENGINE_IP:6642: connection attempt failed (Protocol error) 2020-09-11T10:54:10.917Z|00016|reconnect|INFO|ssl:OVIRT_ENGINE_IP:6642: waiting 4 seconds before reconnect 2020-09-11T10:54:14.921Z|00017|reconnect|INFO|ssl:OVIRT_ENGINE_IP:6642: connecting... 2020-09-11T10:54:15.036Z|00018|stream_ssl|WARN|SSL_connect: unexpected SSL connection close 2020-09-11T10:54:15.036Z|00019|reconnect|INFO|ssl:OVIRT_ENGINE_IP:6642: connection attempt failed (Protocol error) 2020-09-11T10:54:15.036Z|00020|reconnect|INFO|ssl:OVIRT_ENGINE_IP:6642: continuing to reconnect in the background but suppressing further logging I have also done the vdsm-tool ovn-config OVIRT_ENGINE_IP OVIRTMGMT_NETWORK_DC This is how the OVIRT_ENGINE_IP is provided in the ovn controller, i can redo it if you wan. After the restart of the ovn-controller the OVIRT ENGINE still shows only two geneve connections one with DC01-host02 and DC02-host01. Chassis "c4b23834-aec7-4bf8-8be7-aa94a50a6144" hostname: "dc02-host01" Encap geneve ip: "DC02-host01_IP" options: {csum="true"} Chassis "be3abcc9-7358-4040-a37b-8d8a782f239c" hostname: "DC01-host02" Encap geneve ip: "DC01-host02" options: {csum="true"} I've re-done the vdsm-tool command and nothing changed.... again....with the same errors as the systemctl restart ovn-controller On Fri, Sep 11, 2020 at 1:49 PM Dominik Holler <dholler(a)redhat.com> wrote: > Please include ovirt-users list in your reply, to share the knowledge and > experience with the community! > > On Fri, Sep 11, 2020 at 12:12 PM Konstantinos Betsis <k.betsis(a)gmail.com> > wrote: > >> Ok below the output per node and DC >> DC01 >> node01 >> >> [root@dc01-node01 ~]# ovs-vsctl --no-wait get open . >> external-ids:ovn-remote >> "ssl:*OVIRT_ENGINE_IP*:6642" >> [root@ dc01-node01 ~]# ovs-vsctl --no-wait get open . >> external-ids:ovn-encap-type >> geneve >> [root@ dc01-node01 ~]# ovs-vsctl --no-wait get open . >> external-ids:ovn-encap-ip >> >> "*OVIRTMGMT_IP_DC01-NODE01*" >> >> node02 >> >> [root@dc01-node02 ~]# ovs-vsctl --no-wait get open . >> external-ids:ovn-remote >> "ssl:*OVIRT_ENGINE_IP*:6642" >> [root@ dc01-node02 ~]# ovs-vsctl --no-wait get open . >> external-ids:ovn-encap-type >> geneve >> [root@ dc01-node02 ~]# ovs-vsctl --no-wait get open . >> external-ids:ovn-encap-ip >> >> "*OVIRTMGMT_IP_DC01-NODE02*" >> >> DC02 >> node01 >> >> [root@dc02-node01 ~]# ovs-vsctl --no-wait get open . >> external-ids:ovn-remote >> "ssl:*OVIRT_ENGINE_IP*:6642" >> [root@ dc02-node01 ~]# ovs-vsctl --no-wait get open . >> external-ids:ovn-encap-type >> geneve >> [root@ dc02-node01 ~]# ovs-vsctl --no-wait get open . >> external-ids:ovn-encap-ip >> >> "*OVIRTMGMT_IP_DC02-NODE01*" >> >> > Looks good. > > >> DC01 node01 and node02 share the same VM networks and VMs deployed on top >> of them cannot talk to VM on the other hypervisor. >> > > Maybe there is a hint on ovn-controller.log on dc01-node02 ? Maybe > restarting ovn-controller creates more helpful log messages? > > You can also try restart the ovn configuration on all hosts by executing > vdsm-tool ovn-config OVIRT_ENGINE_IP LOCAL_OVIRTMGMT_IP > on each host, this would trigger > > https://github.com/oVirt/ovirt-provider-ovn/blob/master/driver/scripts/setu… > internally. > > >> So I would expect to see the same output for node01 to have a geneve >> tunnel to node02 and vice versa. >> >> > Me too. > > >> On Fri, Sep 11, 2020 at 12:14 PM Dominik Holler <dholler(a)redhat.com> >> wrote: >> >>> >>> >>> On Fri, Sep 11, 2020 at 10:53 AM Konstantinos Betsis <k.betsis(a)gmail.com> >>> wrote: >>> >>>> Hi Dominik >>>> >>>> OVN is selected as the default network provider on the clusters and the >>>> hosts. >>>> >>>> >>> sounds good. >>> This configuration is required already during the host is added to oVirt >>> Engine, because OVN is configured during this step. >>> >>> >>>> The "ovn-sbctl show" works on the ovirt engine and shows only two >>>> hosts, 1 per DC. >>>> >>>> Chassis "c4b23834-aec7-4bf8-8be7-aa94a50a6144" >>>> hostname: "dc01-node02" >>>> Encap geneve >>>> ip: "X.X.X.X" >>>> options: {csum="true"} >>>> Chassis "be3abcc9-7358-4040-a37b-8d8a782f239c" >>>> hostname: "dc02-node1" >>>> Encap geneve >>>> ip: "A.A.A.A" >>>> options: {csum="true"} >>>> >>>> >>>> The new node is not listed (dc01-node1). >>>> >>>> When executed on the nodes the same command (ovn-sbctl show) times-out >>>> on all nodes..... >>>> >>>> The output of the /var/log/openvswitch/ovn-conntroller.log lists on all >>>> logs >>>> >>>> 2020-09-11T08:46:55.197Z|07361|stream_ssl|WARN|SSL_connect: unexpected >>>> SSL connection close >>>> >>>> >>>> >>> Can you please compare the output of >>> >>> ovs-vsctl --no-wait get open . external-ids:ovn-remote >>> ovs-vsctl --no-wait get open . external-ids:ovn-encap-type >>> ovs-vsctl --no-wait get open . external-ids:ovn-encap-ip >>> >>> of the working hosts, e.g. dc01-node02, and the failing host dc01-node1? >>> This should point us the relevant difference in the configuration. >>> >>> Please include ovirt-users list in your replay, to share the knowledge >>> and experience with the community. >>> >>> >>> >>>> Thank you >>>> Best regards >>>> Konstantinos Betsis >>>> >>>> >>>> On Fri, Sep 11, 2020 at 11:01 AM Dominik Holler <dholler(a)redhat.com> >>>> wrote: >>>> >>>>> >>>>> >>>>> On Thu, Sep 10, 2020 at 6:26 PM Konstantinos B <k.betsis(a)gmail.com> >>>>> wrote: >>>>> >>>>>> Hi all >>>>>> >>>>>> We have a small installation based on OVIRT 4.3. >>>>>> 1 Cluster is based on Centos 7 and the other on OVIRT NG Node image. >>>>>> >>>>>> The environment was stable till an upgrade took place a couple of >>>>>> months ago. >>>>>> As such we had to re-install one of the Centos 7 node and start from >>>>>> scratch. >>>>>> >>>>> >>>>> To trigger the automatic configuration of the host, it is required to >>>>> configure ovirt-provider-ovn as the default network provider for the >>>>> cluster before adding the host to oVirt. >>>>> >>>>> >>>>>> Even though the installation completed successfully and VMs are >>>>>> created, the following are not working as expected: >>>>>> 1. ovn geneve tunnels are not established with the other Centos 7 >>>>>> node in the cluster. >>>>>> 2. Centos 7 node is configured by ovirt engine however no geneve >>>>>> tunnel is established when "ovn-sbctl show" is issued on the engine. >>>>>> >>>>> >>>>> Does "ovn-sbctl show" list the hosts? >>>>> >>>>> >>>>>> 3. no flows are shown on the engine on port 6642 for the ovs db. >>>>>> >>>>>> Does anyone have any experience on how to troubleshoot OVN on ovirt? >>>>>> >>>>>> >>>>> /var/log/openvswitch/ovncontroller.log on the host should contain a >>>>> helpful hint. >>>>> >>>>> >>>>> >>>>>> Thank you >>>>>> _______________________________________________ >>>>>> 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/LBVGLQJBWJF3E… >>>>>> >>>>>

3 30

ovirt-engine and host certification is expired in ovirt4.0
by momokch＠yahoo.com.hk 06 Oct '20

06 Oct '20

hello everyone, my ovirt-engine and host certification is expired, is it any method no need to shutdown all the vm can enroll/update the certificate between engine and the host??? i am using the ovirt 4.0 thank you

5 5

Upgrade Host Compatibility Version
by jb 05 Oct '20

05 Oct '20

Hello everybody, for some days I upgrade our environment from ovirt 4.3 to 4.4.2 and now I stuck on upgrading the host compatibility version. It show there a compatibility until version 4.4. The VMs have a limit until version 4.5 and the cluster shows to that I can upgrade them until 4.5. On the cluster page is also a Upgrade guide, but this fails when I try that one. At the moment I have only one host to upgrade (no hosted engine)... Thanks for helping! Jonathan

2 1

oVirt 4.3.10 and ansible default timeouts
by Gianluca Cecchi 05 Oct '20

05 Oct '20

Hello, in the past when I was in 4.3.7 I used this file: /etc/ovirt-engine/engine.conf.d/99-ansible-playbook-timeout.conf with ANSIBLE_PLAYBOOK_EXEC_DEFAULT_TIMEOUT=80 to bypass the default of 30 minutes at that time. I updated in steps to 4.3.8 (in February), 4.3.9 (in April) and 4.3.10 (in July). Due to an error on my side I noticed that the task for which I extended the ansible timeout (this task I didn't execute anymore in latest months) fails with timeout after 80 minutes indeed. With the intent to extend again the custom timeout I went to /usr/share/ovirt-engine/services/ovirt-engine/ovirt-engine.conf, provided by ovirt-engine-backend-4.3.10.4-1.el7.noarch and actually I see this inside: " # Specify the ansible-playbook command execution timeout in minutes. It's used for any task, which executes # AnsibleExecutor class. To change the value permanentaly create a conf file 99-ansible-playbook-timeout.conf in # /etc/ovirt-engine/engine.conf.d/ ANSIBLE_PLAYBOOK_EXEC_DEFAULT_TIMEOUT=120 " and the file seems the original provided, not tampered: [root@ovmgr1 test_backup]# rpm -qvV ovirt-engine-backend-4.3.10.4-1.el7.noarch | grep virt-engine.conf$ ......... /usr/share/ovirt-engine/services/ovirt-engine/ovirt-engine.conf [root@ovmgr1 test_backup]# So the question is: has the default intended value passed to 120 in 4.3.10 (or in any version after 4.3.7)? Thanks, Gianluca

2 1

CEPH - Opinions and ROI
by Jeremey Wise 04 Oct '20

04 Oct '20

I have for many years used gluster because..well. 3 nodes.. and so long as I can pull a drive out.. I can get my data.. and with three copies.. I have much higher chance of getting it. Downsides to gluster: Slower (its my home..meh... and I have SSD to avoid MTBF issues ) and with VDO.. and thin provisioning.. not had issue. BUT.... gluster seems to be falling out of favor. Especially as I move towards OCP. So.. CEPH. I have one SSD in each of the three servers. so I have some space to play. I googled around.. and find no clean deployment notes and guides on CEPH + oVirt. Comments or ideas.. -- p <jeremey.wise(a)gmail.com>enguinpages.

7 8

Is it possible to change scheduler optimization settings of cluster using ansible or some other automation way
by Kushagra Agarwal 03 Oct '20

03 Oct '20

I was hoping if i can get some help with the below oVirt scenario: *Problem Statement*:- Is it possible to change scheduler optimization settings of cluster using ansible or some other automation way *Description*:- Do we have any ansible module or any other CLI based approach which can help us to change 'scheduler optimization' settings of cluster in oVIrt. Scheduler optimization settings of cluster can be found under Scheduling Policy tab ( Compute -> Clusters(select the cluster) -> click on edit and then navigate to scheduling policy Any help in this will be highly appreciated. Thanks, Kushagra

3 7

Question mark VMs
by Vrgotic, Marko 02 Oct '20

02 Oct '20

Hi oVIrt wizards, One of my LocalStorage hypervisors dies. VMs do not need to be rescued. As expected I see them in WebUI with question mark state (picture below): What is the step or are steps to clean ovirt engine db from these VMs and its Storage/Hypervisor/Cluster/DC? [Table Description automatically generated] Kindly awaiting your reply. ----- kind regards/met vriendelijke groeten Marko Vrgotic Sr. System Engineer @ System Administration ActiveVideo o: +31 (35) 6774131 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.

3 3

ovirt-engine and host certification is expired
by momokch＠yahoo.com.hk 02 Oct '20

02 Oct '20

hello everyone, my ovirt-engine and host certification is expired, is it any method no need to shutdown all the vm can enroll/update the certificate between engine and the host??? i am using the ovirt 4.0 thank you

1 0

Re: CEPH - Opinions and ROI
by Philip Brown 02 Oct '20

02 Oct '20

ceph through an iscsi gateway is very.. very.. slow. ----- Original Message ----- From: "Matthew Stier" <Matthew.Stier(a)fujitsu.com> To: "Jeremey Wise" <jeremey.wise(a)gmail.com>, "users" <users(a)ovirt.org> Sent: Wednesday, September 30, 2020 10:03:34 PM Subject: [ovirt-users] Re: CEPH - Opinions and ROI If you can’t go direct, how about round about, with an iSCSI gateway. From: Jeremey Wise <jeremey.wise(a)gmail.com> Sent: Wednesday, September 30, 2020 11:33 PM To: users <users(a)ovirt.org> Subject: [ovirt-users] CEPH - Opinions and ROI I have for many years used gluster because..well. 3 nodes.. and so long as I can pull a drive out.. I can get my data.. and with three copies.. I have much higher chance of getting it. Downsides to gluster: Slower (its my home..meh... and I have SSD to avoid MTBF issues ) and with VDO.. and thin provisioning.. not had issue. BUT.... gluster seems to be falling out of favor. Especially as I move towards OCP. So.. CEPH. I have one SSD in each of the three servers. so I have some space to play. I googled around.. and find no clean deployment notes and guides on CEPH + oVirt. Comments or ideas.. -- [ mailto:jeremey.wise@gmail.com | p ] enguinpages. _______________________________________________ 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/S4V6NKC62LW42…

3 3

[ANN] oVirt 4.4.3 Third Release Candidate is now available for testing
by Lev Veyde 01 Oct '20

01 Oct '20

oVirt 4.4.3 Third Release Candidate is now available for testing The oVirt Project is pleased to announce the availability of oVirt 4.4.3 Third Release Candidate for testing, as of October 1st, 2020. This update is the third 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 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.3 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.3 (redeploy in case of already being on 4.4.3). 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.2 or newer * CentOS Linux (or similar) 8.2 or newer This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 8.2 or newer * CentOS Linux (or similar) 8.2 or newer * oVirt Node 4.4 based on CentOS Linux 8.2 (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 Additional Resources: * Read more about the oVirt 4.4.3 release highlights: http://www.ovirt.org/release/4.4.3/ * 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.3/ [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

VM AutoStart
by Jeremey Wise 01 Oct '20

01 Oct '20

When I have to shut down cluster... ups runs out etc.. I need a sequence set of just a small number of VMs to "autostart" Normally I just use DNS FQND to connect to oVirt engine but as two of my VMs are a DNS HA cluster.. as well as NTP / SMTP /DHCP etc... I need those two infrastructure VMs to be auto boot. I looked at HA settings for those VMs but it seems to be watching for pause /resume.. but it does not imply or state auto start on clean first boot. Options? -- p <jeremey.wise(a)gmail.com>enguinpages

4 12

ovirt-node-4.4.2 grub is not reading new grub.cfg at boot
by Mike Lindsay 01 Oct '20

01 Oct '20

Hey Folks, I've got a bit of a strange one here. I downloaded and installed ovirt-node-ng-installer-4.4.2-2020091810.el8.iso today on an old dev laptop and to get it to install I needed to add acpi=off to the kernel boot param to get the installing to work (known issue with my old laptop). After installation it was still booting with acpi=off, no biggie (seen that happen with Centos 5,6,7 before on occasion) right, just change the line in /etc/defaults/grub and run grub2-mkconfig (ran for both efi and legacy for good measure even knowing EFI isn't used) and reboot...done this hundreds of times without any problems. But this time after rebooting if I hit 'e' to look at the kernel params on boot, acpi=off is still there. Basically any changes to /etc/default/grub are being ignored or over-ridden but I'll be damned if I can't find where. I know I'm missing something simple here, I do this all the time but to be honest this is the first Centos 8 based install I've had time to play with. Any suggestions would be greatly appreciated. The drive layout is a bit weird but had no issues running fedora or centos in the past. boot drive is a mSATA (/dev/sdb) and there is a SSD data drive at /dev/sda...having sda installed or removed makes no difference and /boot is mounted where it should /dev/sdb1....very strange Cheers, Mike [root@ovirt-node01 ~]# cat /etc/default/grub GRUB_TIMEOUT=5 GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)" GRUB_DEFAULT=saved GRUB_DISABLE_SUBMENU=true GRUB_TERMINAL_OUTPUT="console" GRUB_CMDLINE_LINUX='crashkernel=auto resume=/dev/mapper/onn-swap rd.lvm.lv=onn/ovirt-node-ng-4.4.2-0.20200918.0+1 rd.lvm.lv=onn/swap noapic rhgb quiet' GRUB_DISABLE_RECOVERY="true" GRUB_ENABLE_BLSCFG=true GRUB_DISABLE_OS_PROBER='true' [root@ovirt-node01 ~]# cat /boot/grub2/grub.cfg # # DO NOT EDIT THIS FILE # # It is automatically generated by grub2-mkconfig using templates # from /etc/grub.d and settings from /etc/default/grub # ### BEGIN /etc/grub.d/00_header ### set pager=1 if [ -f ${config_directory}/grubenv ]; then load_env -f ${config_directory}/grubenv elif [ -s $prefix/grubenv ]; then load_env fi if [ "${next_entry}" ] ; then set default="${next_entry}" set next_entry= save_env next_entry set boot_once=true else set default="${saved_entry}" fi if [ x"${feature_menuentry_id}" = xy ]; then menuentry_id_option="--id" else menuentry_id_option="" fi export menuentry_id_option if [ "${prev_saved_entry}" ]; then set saved_entry="${prev_saved_entry}" save_env saved_entry set prev_saved_entry= save_env prev_saved_entry set boot_once=true fi function savedefault { if [ -z "${boot_once}" ]; then saved_entry="${chosen}" save_env saved_entry fi } function load_video { if [ x$feature_all_video_module = xy ]; then insmod all_video else insmod efi_gop insmod efi_uga insmod ieee1275_fb insmod vbe insmod vga insmod video_bochs insmod video_cirrus fi } terminal_output console if [ x$feature_timeout_style = xy ] ; then set timeout_style=menu set timeout=5 # Fallback normal timeout code in case the timeout_style feature is # unavailable. else set timeout=5 fi ### END /etc/grub.d/00_header ### ### BEGIN /etc/grub.d/00_tuned ### set tuned_params="" set tuned_initrd="" ### END /etc/grub.d/00_tuned ### ### BEGIN /etc/grub.d/01_users ### if [ -f ${prefix}/user.cfg ]; then source ${prefix}/user.cfg if [ -n "${GRUB2_PASSWORD}" ]; then set superusers="root" export superusers password_pbkdf2 root ${GRUB2_PASSWORD} fi fi ### END /etc/grub.d/01_users ### ### BEGIN /etc/grub.d/08_fallback_counting ### insmod increment # Check if boot_counter exists and boot_success=0 to activate this behaviour. if [ -n "${boot_counter}" -a "${boot_success}" = "0" ]; then # if countdown has ended, choose to boot rollback deployment, # i.e. default=1 on OSTree-based systems. if [ "${boot_counter}" = "0" -o "${boot_counter}" = "-1" ]; then set default=1 set boot_counter=-1 # otherwise decrement boot_counter else decrement boot_counter fi save_env boot_counter fi ### END /etc/grub.d/08_fallback_counting ### ### BEGIN /etc/grub.d/10_linux ### insmod part_msdos insmod ext2 set root='hd1,msdos1' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 b6557c59-e11f-471b-8cb1-70c47b0b4b29 else search --no-floppy --fs-uuid --set=root b6557c59-e11f-471b-8cb1-70c47b0b4b29 fi insmod part_msdos insmod ext2 set boot='hd1,msdos1' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=boot --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 b6557c59-e11f-471b-8cb1-70c47b0b4b29 else search --no-floppy --fs-uuid --set=boot b6557c59-e11f-471b-8cb1-70c47b0b4b29 fi # This section was generated by a script. Do not modify the generated file - all changes # will be lost the next time file is regenerated. Instead edit the BootLoaderSpec files. # # The blscfg command parses the BootLoaderSpec files stored in /boot/loader/entries and # populates the boot menu. Please refer to the Boot Loader Specification documentation # for the files format: https://www.freedesktop.org/wiki/Specifications/BootLoaderSpec/. set default_kernelopts="root=/dev/mapper/onn-ovirt--node--ng--4.4.2--0.20200918.0+1 ro crashkernel=auto resume=/dev/mapper/onn-swap rd.lvm.lv=onn/ovirt-node-ng-4.4.2-0.20200918.0+1 rd.lvm.lv=onn/swap noapic rhgb quiet " insmod blscfg blscfg ### END /etc/grub.d/10_linux ### ### BEGIN /etc/grub.d/10_reset_boot_success ### # Hiding the menu is ok if last boot was ok or if this is a first boot attempt to boot the entry if [ "${boot_success}" = "1" -o "${boot_indeterminate}" = "1" ]; then set menu_hide_ok=1 else set menu_hide_ok=0 fi # Reset boot_indeterminate after a successful boot if [ "${boot_success}" = "1" ] ; then set boot_indeterminate=0 # Avoid boot_indeterminate causing the menu to be hidden more then once elif [ "${boot_indeterminate}" = "1" ]; then set boot_indeterminate=2 fi # Reset boot_success for current boot set boot_success=0 save_env boot_success boot_indeterminate ### END /etc/grub.d/10_reset_boot_success ### ### BEGIN /etc/grub.d/12_menu_auto_hide ### if [ x$feature_timeout_style = xy ] ; then if [ "${menu_show_once}" ]; then unset menu_show_once save_env menu_show_once set timeout_style=menu set timeout=60 elif [ "${menu_auto_hide}" -a "${menu_hide_ok}" = "1" ]; then set orig_timeout_style=${timeout_style} set orig_timeout=${timeout} if [ "${fastboot}" = "1" ]; then # timeout_style=menu + timeout=0 avoids the countdown code keypress check set timeout_style=menu set timeout=0 else set timeout_style=hidden set timeout=1 fi fi fi ### END /etc/grub.d/12_menu_auto_hide ### ### BEGIN /etc/grub.d/20_linux_xen ### ### END /etc/grub.d/20_linux_xen ### ### BEGIN /etc/grub.d/20_ppc_terminfo ### ### END /etc/grub.d/20_ppc_terminfo ### ### BEGIN /etc/grub.d/30_os-prober ### ### END /etc/grub.d/30_os-prober ### ### BEGIN /etc/grub.d/30_uefi-firmware ### ### END /etc/grub.d/30_uefi-firmware ### ### BEGIN /etc/grub.d/40_custom ### # This file provides an easy way to add custom menu entries. Simply type the # menu entries you want to add after this comment. Be careful not to change # the 'exec tail' line above. ### END /etc/grub.d/40_custom ### ### BEGIN /etc/grub.d/41_custom ### if [ -f ${config_directory}/custom.cfg ]; then source ${config_directory}/custom.cfg elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then source $prefix/custom.cfg; fi ### END /etc/grub.d/41_custom ### -- Mike Lindsay Senior Systems Administrator Technological Maintenance and Support CBC/SRC mike.lindsay(a)cbc.ca (o) 416-205-8992 (c) 416-819-2841

3 3

Power on VM - CLI / API
by Jeremey Wise 01 Oct '20

01 Oct '20

Can anyone post link. (with examples.. as most documentation for oVirt lacks this).. where I can power on a VM via CLI or API. As of now I cannot login to oVirt-Engine. No errors when I restart it.. https://lists.ovirt.org/archives/list/users@ovirt.org/thread/45KKF5TN5PRQ3R… BUt... I need to get VMs booted. I tried to follow: http://ovirt.github.io/ovirt-engine-api-model/master/ and my server's API web portal https://ovirte01.penguinpages.local/ovirt-engine/apidoc/#/documents/003_com… And.. even get POSTMAN (real newbie at that tool but ran into how to add exported .pem key from portal to session issues) # failed CLI example: Power on VM "ns01" ########### <<<< DRAFT :: 2020-09-30################ # Get key from oVirt engine and import. Ex: from ovirte01 into server 'thor curl -k ' https://ovirte01.penguinpages.local/ovirt-engine/services/pki-resource?reso…' -o ovirt01_ca.pem sudo cp ovirt01_ca.pem /etc/pki/ca-trust/source/anchors sudo update-ca-trust extract openssl s_client -connect ovirte01.penguinpages.local:443 -showcerts < /dev/null <snip... lots of key info back> # Use key during GET list of VMs ?? <meh? # Power on VM <<fubar still> curl -X POST https://ovirte01.penguinpages.local/post -H /ovirt-engine/api/vms/ns01/start HTTP/1.1 <https://ovirte01.penguinpages.local/post%20-H%20/ovirt-engine/api/vms/ns01/…> ##### I just need to power on VM -- p <jeremey.wise(a)gmail.com>enguinpages

3 2

Re: CEPH - Opinions and ROI
by penguin pages 01 Oct '20

01 Oct '20

These are all storage rich servers. Drives: USB 3 64GB Boot / OS 512GB SSD (Gluster HCI: volumes "engine", "data" , "vmstore" "iso" I added last one to .. well to learn if I could extend with LVM ;) 1TB SSD: (VDO+Gluster Manual build due to brick and fqdn issues in oVirt, It did import once it was created so that is good.. ) 1TB SSD/NVMe: (?? CEPH ?? Goal is I can learn technology and play.. but have several independent volumes where I can move important systems to / from / backup so if my playing around messes things up.. I have a fall back. I would try RedHat Container Storage.. but It is a home lab so my budget is all used up on hardware and so CentOS. I am hoping oVirt had a similar setup process like " yum install -y gluster-ansible-roles " but for CEPH. This video implies something of that ilk exists.. https://www.youtube.com/watch?v=wIw7RjHPhzs but <sigh> jumps right into setup.. and fails to mention "how did you get that plugin in cockpit"... and is their an "oVirt" version.

1 0

java.lang.reflect.UndeclaredThrowableException - oVirt engine UI
by Jeremey Wise 01 Oct '20

01 Oct '20

I tried to post on website but .. it did not seem to work... so sorry if this is double posting. oVirt login this AM. accepted username and password but got java error. Restarted oVirt engine ## hosted-engine --set-maintenance --mode=global hosted-engine --vm-shutdown hosted-engine --vm-status #make sure that the status is shutdown before restarting hosted-engine --vm-start hosted-engine --vm-status #make sure the status is health before leaving maintenance mode hosted-engine --set-maintenance --mode=none ## [root@thor ~]# hosted-engine --vm-status --== Host thor.penguinpages.local (id: 1) status ==-- Host ID : 1 Host timestamp : 65342 Score : 3400 Engine status : {"vm": "down", "health": "bad", "detail": "unknown", "reason": "vm not running on this host"} Hostname : thor.penguinpages.local Local maintenance : False stopped : False crc32 : 824c29fd conf_on_shared_storage : True local_conf_timestamp : 65342 Status up-to-date : True Extra metadata (valid at timestamp): metadata_parse_version=1 metadata_feature_version=1 timestamp=65342 (Wed Sep 30 08:11:45 2020) host-id=1 score=3400 vm_conf_refresh_time=65342 (Wed Sep 30 08:11:45 2020) conf_on_shared_storage=True maintenance=False state=EngineDown stopped=False --== Host medusa.penguinpages.local (id: 3) status ==-- Host ID : 3 Host timestamp : 87556 Score : 3400 Engine status : {"vm": "up", "health": "good", "detail": "Up"} Hostname : medusa.penguinpages.local Local maintenance : False stopped : False crc32 : 63296a70 conf_on_shared_storage : True local_conf_timestamp : 87556 Status up-to-date : True Extra metadata (valid at timestamp): metadata_parse_version=1 metadata_feature_version=1 timestamp=87556 (Wed Sep 30 08:11:39 2020) host-id=3 score=3400 vm_conf_refresh_time=87556 (Wed Sep 30 08:11:39 2020) conf_on_shared_storage=True maintenance=False state=EngineUp stopped=False [root@thor ~]# yum update -y Last metadata expiration check: 0:31:17 ago on Wed 30 Sep 2020 09:17:03 AM EDT. Dependencies resolved. Nothing to do. Complete! [root@thor ~]# Gogled around .. just found this thread. ## https://bugzilla.redhat.com/show_bug.cgi?id=1378045 # pgadmin connect to ovirte01.penguinpages.com as engine to db engine select mac_addr from vm_interface "00:16:3e:57:0d:47" "56:6f:86:41:00:01" "56:6f:86:41:00:00" "56:6f:86:41:00:02" "56:6f:86:41:00:03" "56:6f:86:41:00:04" "56:6f:86:41:00:05" "56:6f:86:41:00:15" "56:6f:86:41:00:16" "56:6f:86:41:00:17" "56:6f:86:41:00:18" "56:6f:86:41:00:19" # Note one field is "null" Question: 1) is this bad? 2) How do I fix? 3) Any idea on root cause? -- p <jeremey.wise(a)gmail.com>enguinpages

3 2

Gluster Volumes - Correct Peer Connection
by Jeremey Wise 01 Oct '20

01 Oct '20

I just noticed when HCI setup bult the gluster engine / data / vmstore volumes... it did use correctly the definition of 10Gb "back end" interfaces / hosts. But.. oVirt Engine is NOT referencing this. it lists bricks as 1Gb "managment / host" interfaces. Is this a GUI issue? I doubt this and how do I correct it? ### Data Volume Example Name: data Volume ID: 0ae7b487-8b87-4192-bd30-621d445902fe Volume Type: Replicate Replica Count: 3 Number of Bricks: 3 Transport Types: TCP Maximum no of snapshots: 256 Capacity: 999.51 GiB total, 269.02 GiB used, 730.49 GiB free, 297.91 GiB Guaranteed free, 78 Deduplication/Compression savings (%) medusa.penguinpages.local medusa.penguinpages.local:/gluster_bricks/data/data 25% OK odin.penguinpages.local odin.penguinpages.local:/gluster_bricks/data/data 25% OK thor.penguinpages.local thor.penguinpages.local:/gluster_bricks/data/data 25% OK # I have storage back end of 172.16.101.x which is 10Gb dedicated for replication. Peers reflect this [root@odin c4918f28-00ce-49f9-91c8-224796a158b9]# gluster peer status Number of Peers: 2 Hostname: thorst.penguinpages.local Uuid: 7726b514-e7c3-4705-bbc9-5a90c8a966c9 State: Peer in Cluster (Connected) Hostname: medusast.penguinpages.local Uuid: 977b2c1d-36a8-4852-b953-f75850ac5031 State: Peer in Cluster (Connected) [root@odin c4918f28-00ce-49f9-91c8-224796a158b9]# -- p <jeremey.wise(a)gmail.com>enguinpages

5 7

Version 4.4.2.6-1.el8 -Console Error: java.lang.reflect.UndeclaredThrowableException
by penguin pages 01 Oct '20

01 Oct '20

Got message this AM when tried to login to oVirt Engine which up till now has been working fine. I can supply username and password and get portal to choose "Administration Portal" or "VM Portal" I have tested both.. both have same response about java.lang.reflect.UndeclaredThrowableException I restarted the engine # hosted-engine --set-maintenance --mode=global hosted-engine --vm-shutdown hosted-engine --vm-status #make sure that the status is shutdown before restarting hosted-engine --vm-start hosted-engine --vm-status #make sure the status is health before leaving maintenance mode hosted-engine --set-maintenance --mode=none # --== Host thor.penguinpages.local (id: 1) status ==-- Host ID : 1 Host timestamp : 70359 Score : 3400 Engine status : {"vm": "down", "health": "bad", "detail": "unknown", "reason": "vm not running on this host"} Hostname : thor.penguinpages.local Local maintenance : False stopped : False crc32 : 25adf6d0 conf_on_shared_storage : True local_conf_timestamp : 70359 Status up-to-date : True Extra metadata (valid at timestamp): metadata_parse_version=1 metadata_feature_version=1 timestamp=70359 (Wed Sep 30 09:35:22 2020) host-id=1 score=3400 vm_conf_refresh_time=70359 (Wed Sep 30 09:35:22 2020) conf_on_shared_storage=True maintenance=False state=EngineDown stopped=False --== Host medusa.penguinpages.local (id: 3) status ==-- Host ID : 3 Host timestamp : 92582 Score : 3400 Engine status : {"vm": "up", "health": "good", "detail": "Up"} Hostname : medusa.penguinpages.local Local maintenance : False stopped : False crc32 : 623359d2 conf_on_shared_storage : True local_conf_timestamp : 92582 Status up-to-date : True Extra metadata (valid at timestamp): metadata_parse_version=1 metadata_feature_version=1 timestamp=92582 (Wed Sep 30 09:35:25 2020) host-id=3 score=3400 vm_conf_refresh_time=92582 (Wed Sep 30 09:35:25 2020) conf_on_shared_storage=True maintenance=False state=EngineUp stopped=False ## I downloaded and installed key from portal.. thinking that may have been issue.. it was not. I googled around /searched forum and nothing jumped out. (only hit I found in forum https://lists.ovirt.org/pipermail/users/2015-June/033421.html but no note about fix)

2 2

update to 4.4 fails with "Domain format is different from master storage domain format" (v4.3 cluster with V4 NFS storage domains)
by Sergey Kulikov 30 Sep '20

30 Sep '20

Hello, I'm trying to update our hosted-engine ovirt to version 4.4 from 4.3.10 and everything goes fine until hosted-engine --deploy tries to add new hosted_storage domain, we have NFS storage domains, and it fails with error: [ INFO ] TASK [ovirt.hosted_engine_setup : Activate storage domain] [ ERROR ] ovirtsdk4.Error: Fault reason is "Operation Failed". Fault detail is "[Domain format is different from master storage domain format]". HTTP response code is 400. [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "Fault reason is \"Operation Failed\". Fault detail is \"[Domain format is different from master storage domain format]\". HTTP response code is 400."} It looks like storage domains in data center should have been upgraded to V5 when DC and cluster compatibility version was updated to 4.3, but looks like it was implemented in ovirt 4.3.3 and this setup was updated from 4.2 to 4.3 before 4.3.3 was released, so I ended up with 4.3 DCs and clusters with V4 storage domain format. Is there any way to convert V4 to V5 (there are running VMs on them) to be able upgrade to 4.4? --

2 3

Replica Question
by C Williams 30 Sep '20

30 Sep '20

Hello, We recently received 5 servers. All have about 3 TB of storage. I want to deploy an oVirt HCI using as much of my storage and compute resources as possible. Would oVirt support a "replica 5" HCI (Compute/Gluster) cluster ? I have deployed replica 3s and know about replica 2 + arbiter -- but an arbiter would not be applicable here -- since I have equal storage on all of the planned bricks. Thank You For Your Help !! C Williams

3 15

Is it possible to change scheduler optimization settings of cluster using ansible or some other automation way
by kushagra2agarwal＠gmail.com 30 Sep '20

30 Sep '20

Do we have any ansible module or any other CLI based approach which can help us to change 'scheduler optimization' settings of cluster in oVIrt. Scheduler optimization settings of cluster can be found under Scheduling Policy tab ( Compute -> Clusters(select the cluster) -> click on edit and than navigate to scheduling policu option) Scheduler Optimization Optimize for Utilization Optimize for Speed

1 0

VM without Host stuck in "Rebooting" State
by Raphael Höser 29 Sep '20

29 Sep '20

I have a VM which was send a "Reboot" and "Shutdown" command in short succession (two admins who were not thinking the same way) and now the VM is Stuck in "Rebooting". It has no Host assigned and when trying to turn it of (via Shutdown or Power Off) it gives this error: Sep 29, 2020, 10:27:10 AM Failed to power off VM <vm_name> (Host: <UNKNOWN>, User: admin@internal-authz). The engine logs don't provide more info either: 2020-09-29 10:42:18,628+02 INFO [org.ovirt.engine.core.bll.StopVmCommand] (EE-ManagedThreadFactory-engine-Thread-68681) [d4c6547e-c326-4907-8c34-36fd5ab81dfa] Running command: StopVmCommand internal: false. Entities affected : ID: 55edef7a-7a0b-42f0-a98f-9150103fa0b1 Type: VMAction group STOP_VM with role type USER 2020-09-29 10:42:18,628+02 WARN [org.ovirt.engine.core.bll.StopVmCommand] (EE-ManagedThreadFactory-engine-Thread-68681) [d4c6547e-c326-4907-8c34-36fd5ab81dfa] Strange, according to the status 'RebootInProgress' virtual machine '55edef7a-7a0b-42f0-a98f-9150103fa0b1' should be running in a host but it isn't. 2020-09-29 10:42:18,635+02 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-68681) [d4c6547e-c326-4907-8c34-36fd5ab81dfa] EVENT_ID: USER_FAILED_STOP_VM(56), Failed to power off VM degum-ci-windows3 (Host: <UNKNOWN>, User: admin@internal-authz). What steps can I do to resolve this? I do not need to restore this machine, I'm totally fine with just deleting it, but it may not impact other running machines.

2 1

oVirt Change hosts to FQDN
by Jeremey Wise 29 Sep '20

29 Sep '20

I posted that I had wiped out the oVirt-engine.. running cleanup on all three nodes. Done a re-deployment. Then to add nodes back.. though all have entries for eachother in /etc/hosts and ssh works fine via short and long name. I added nodes back into cluster.. but had to do it via IP to get past error. Now, if I go to create a volume via the GUI in gluster I get: Error while executing action Create Gluster Volume: Volume create failed: rc=30800 out=() err=["Host 172_16_100_102 is not in 'Peer in Cluster' state"] Which seems to be related to using IP vs DNS to add gluster volumes https://bugzilla.redhat.com/show_bug.cgi?id=1055928 Question: how do i fix the hosts in cluster being defined by IP vs desired hostname? -- jeremey.wise(a)gmail.com

3 8

Source storage domain info in storage live migration
by Gianluca Cecchi 29 Sep '20

29 Sep '20

Hello, having to monitor and check live storage migrations, it seems to me that scrolling through events I can see information about the target storage domain name, but nothing about the source. Is it correct? Can it be added? Which kind of rfe bugzilla should I use in case? Against what? Thanks, Gianluca

2 1

Trouble with restoring hosted engine from backup
by Siddharth Patil 29 Sep '20

29 Sep '20

Dear all, I'm trying to restore hosted-engine from backup, but it fails with the following error message: [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "\"Cluster name cannot be 'Default'. This is a reserved name for the default DataCenter. Please choose\" \" another name for the cluster\""} My DataCenter is called Primary and Cluster is called Default. I have two hosts node01 and node02, with shared storage through NFS. I'm running the restore on node02. I can restore successfully if I change the Cluster name, but then I cannot move node02 to the default cluster, or move node01 to the new cluster, as I cannot shut down the VMs currently running on node01. Please help! Regards, Siddharth

1 0

Newbie question on network
by valerio.luccio＠nyu.edu 28 Sep '20

28 Sep '20

I apologize for asking what is probably a very basic question. I installed and created a self-hosted engine using cockpit on a server. I can reach the self-hosted engine from anywhere within my network. I then created a new VM selecting the default ovirtmgmt for the network. The VM does not seem to connect to the network via the bridge. I the used the console to manually configured the network card and I have connectivity between the VM, the engine and the server, but not beyond. What am I doing wrong ? Can someone point to a good documentation page on the subject ? Thanks in advance, Valerio

5 11

Cannot change Cluster Compatibility Version after 4.4 upgrade
by paolo＠airaldi.it 28 Sep '20

28 Sep '20

Hi all, we have an oVirt 4.3 with 3 Hosts and 20 VMs. 2 Hosts are Dell PowerEdge R610 with 2 Intel(R) Xeon(R) CPU E5540 processor each (Intel Nehalem IBRS SSBD), while the third is an HP ProLiant ML350p Gen8 with 2 Intel(R) Xeon(R) CPU E5-2620 v2 processor (Intel SandyBridge IBRS SSBD MDS) They all are in the same Cluster. Some of the 20 VMs are Windows (Win 10, Win 2012 and Win 2016) We have upgraded to 4.4.2.6-1.el8 following the instruction https://www.ovirt.org/documentation/upgrade_guide/#SHE_Upgrading_from_4-3. We had some minor issues that have been fixed and now we need to change Cluster Compatibility Version, but it fails complaining about Win10 and Win2016 VMs. In agent.log, for each of them I have: WARN [org.ovirt.engine.core.bll.UpdateVmCommand] (default task-122) [292f1983] Validation of action 'UpdateVm' failed for user admin@internal-authz. Reasons: VAR__ACTION__UPDATE,VAR__TYPE__VM,CPU_TYPE_UNSUPPORTED_FOR_THE_GUEST_OS,$uns upportedCpus opteron_g1, conroe, nehalem, penryn The same messages appear even if the VMs are powered off. We tried to change the Operating System in one VM configuration and if we put Win2012 the VM is no more in the error list when we edit the Cluster, but we're not sure the VMs will restart once Cluster compatibility will be to 4.4 How can we proceed? Hosts: # rpm -qa|grep -i ovirt ovirt-ansible-hosted-engine-setup-1.1.8-1.el8.noarch ovirt-host-dependencies-4.4.1-4.el8.x86_64 ovirt-hosted-engine-setup-2.4.6-1.el8.noarch ovirt-python-openvswitch-2.11-0.2020061801.el8.noarch ovirt-imageio-daemon-2.0.10-1.el8.x86_64 ovirt-release44-4.4.2-1.el8.noarch ovirt-vmconsole-1.0.8-1.el8.noarch python3-ovirt-engine-sdk4-4.4.4-1.el8.x86_64 ovirt-imageio-client-2.0.10-1.el8.x86_64 cockpit-ovirt-dashboard-0.14.11-1.el8.noarch ovirt-provider-ovn-driver-1.2.30-1.el8.noarch ovirt-vmconsole-host-1.0.8-1.el8.noarch ovirt-openvswitch-2.11-0.2020061801.el8.noarch ovirt-openvswitch-ovn-common-2.11-0.2020061801.el8.noarch ovirt-openvswitch-ovn-host-2.11-0.2020061801.el8.noarch ovirt-openvswitch-ovn-2.11-0.2020061801.el8.noarch ovirt-ansible-engine-setup-1.2.4-1.el8.noarch ovirt-host-4.4.1-4.el8.x86_64 python3-ovirt-setup-lib-1.3.2-1.el8.noarch ovirt-imageio-common-2.0.10-1.el8.x86_64 ovirt-hosted-engine-ha-2.4.4-1.el8.noarch Engine: # rpm -qa|grep -i ovirt ovirt-engine-extension-aaa-jdbc-1.2.0-1.el8.noarch ovirt-engine-dbscripts-4.4.2.6-1.el8.noarch ovirt-engine-tools-4.4.2.6-1.el8.noarch ovirt-openvswitch-ovn-central-2.11-0.2020061801.el8.noarch ovirt-cockpit-sso-0.1.4-1.el8.noarch ovirt-ansible-infra-1.2.2-1.el8.noarch ovirt-engine-setup-plugin-ovirt-engine-common-4.4.2.6-1.el8.noarch ovirt-engine-tools-backup-4.4.2.6-1.el8.noarch ovirt-engine-vmconsole-proxy-helper-4.4.2.6-1.el8.noarch ovirt-release44-4.4.2-1.el8.noarch python3-ovirt-setup-lib-1.3.2-1.el8.noarch ovirt-openvswitch-ovn-common-2.11-0.2020061801.el8.noarch ovirt-imageio-daemon-2.0.10-1.el8.x86_64 ovirt-python-openvswitch-2.11-0.2020061801.el8.noarch ovirt-ansible-image-template-1.2.2-1.el8.noarch ovirt-ansible-shutdown-env-1.1.0-1.el8.noarch python3-ovirt-engine-lib-4.4.2.6-1.el8.noarch ovirt-provider-ovn-1.2.30-1.el8.noarch ovirt-engine-dwh-grafana-integration-setup-4.4.2.1-1.el8.noarch ovirt-engine-dwh-setup-4.4.2.1-1.el8.noarch ovirt-openvswitch-ovn-2.11-0.2020061801.el8.noarch ovirt-vmconsole-proxy-1.0.8-1.el8.noarch ovirt-imageio-common-2.0.10-1.el8.x86_64 ovirt-ansible-engine-setup-1.2.4-1.el8.noarch ovirt-ansible-hosted-engine-setup-1.1.8-1.el8.noarch ovirt-ansible-repositories-1.2.5-1.el8.noarch ovirt-engine-setup-4.4.2.6-1.el8.noarch ovirt-engine-setup-plugin-vmconsole-proxy-helper-4.4.2.6-1.el8.noarch ovirt-engine-webadmin-portal-4.4.2.6-1.el8.noarch ovirt-engine-extension-aaa-ldap-1.4.1-1.el8.noarch ovirt-engine-extension-aaa-misc-1.1.0-1.el8.noarch ovirt-engine-extensions-api-1.0.1-1.el8.noarch ovirt-engine-setup-plugin-websocket-proxy-4.4.2.6-1.el8.noarch ovirt-engine-api-explorer-0.0.6-1.el8.noarch ovirt-engine-setup-plugin-cinderlib-4.4.2.6-1.el8.noarch ovirt-engine-setup-plugin-ovirt-engine-4.4.2.6-1.el8.noarch ovirt-engine-wildfly-19.1.0-2.el8.x86_64 ovirt-engine-wildfly-overlay-19.1.0-2.el8.noarch ovirt-web-ui-1.6.4-1.el8.noarch ovirt-openvswitch-2.11-0.2020061801.el8.noarch python3-ovirt-engine-sdk4-4.4.4-1.el8.x86_64 ovirt-ansible-cluster-upgrade-1.2.3-1.el8.noarch ovirt-engine-metrics-1.4.1.1-1.el8.noarch ovirt-ansible-manageiq-1.2.1-1.el8.noarch ovirt-engine-4.4.2.6-1.el8.noarch ovirt-engine-extension-logger-log4j-1.1.0-1.el8.noarch ovirt-engine-websocket-proxy-4.4.2.6-1.el8.noarch ovirt-engine-setup-plugin-imageio-4.4.2.6-1.el8.noarch ovirt-engine-backend-4.4.2.6-1.el8.noarch ovirt-vmconsole-1.0.8-1.el8.noarch ovirt-dependencies-4.4.2-1.el8.noarch ovirt-ansible-vm-infra-1.2.3-1.el8.noarch ovirt-ansible-roles-1.2.3-1.el8.noarch ovirt-engine-setup-base-4.4.2.6-1.el8.noarch ovirt-engine-dwh-4.4.2.1-1.el8.noarch ovirt-engine-restapi-4.4.2.6-1.el8.noarch ovirt-engine-ui-extensions-1.2.3-1.el8.noarch ovirt-engine-extension-aaa-ldap-setup-1.4.1-1.el8.noarch ovirt-ansible-disaster-recovery-1.3.0-1.el8.noarch

2 1

Re: oVirt networking.
by dhanaraj.ramesh＠yahoo.com 28 Sep '20

28 Sep '20

Hi 1) trunk all the network including management, VM traffic subnets in both ports and tag the management network as native 2) configure the bonds with active/backup with management IP while installing the OS 3) proceed the hosted engine installation in the same management network 4) once hosted engine is up, add all hosts and create vm traffic network with VLAN tags

1 0

oVirt networking.
by Matthew.Stier＠fujitsu.com 28 Sep '20

28 Sep '20

oVirt newbie starting with 4.4.2. Any good documentation on setting up networking? I want to bond my two network interfaces. The native interface will be uses for management. All other traffic will be over tagged vlans.

1 0

MOM can't run
by duhongyu 27 Sep '20

27 Sep '20

hi I try to start momd by "systemctl restart momd" but it can't run , so I run momd by " /usr/sbin/momd -c /etc/momd.conf " [root@node0 mom]# /usr/sbin/momd -c /etc/momd.conf 2020-09-27 14:31:12,291 - mom - INFO - MOM starting 2020-09-27 14:31:12,381 - mom.HostMonitor - INFO - Host Monitor starting 2020-09-27 14:31:12,381 - mom - INFO - hypervisor interface vdsm 2020-09-27 14:31:12,690 - mom - ERROR - Unable to import hypervisor interface: vdsm 2020-09-27 14:31:12,707 - mom.GuestManager - INFO - Guest Manager starting: multi-thread 2020-09-27 14:31:12,708 - mom.GuestManager - INFO - Guest Manager ending 2020-09-27 14:31:12,708 - mom.PolicyEngine - INFO - Policy Engine starting 2020-09-27 14:31:12,709 - mom.RPCServer - INFO - RPC Server is disabled 2020-09-27 14:31:12,710 - mom - INFO - Shutting down RPC server. 2020-09-27 14:31:12,710 - mom.PolicyEngine - INFO - Policy Engine ending 2020-09-27 14:31:12,710 - mom - INFO - Waiting for RPC server thread. 2020-09-27 14:31:12,710 - mom - INFO - Waiting for policy engine thread. 2020-09-27 14:31:12,710 - mom - INFO - Waiting for guest manager thread. 2020-09-27 14:31:12,710 - mom - INFO - Waiting for host monitor thread. 2020-09-27 14:31:12,828 - mom.HostMonitor - INFO - HostMonitor is ready 2020-09-27 14:31:17,710 - mom - INFO - MOM ending /usr/lib/python2.7/site-packages/mom/HypervisorInterfaces/vdsmInterface.py import sys sys.path.append('/usr/share/vdsm') import API import supervdsm import logging import traceback from mom.HypervisorInterfaces.HypervisorInterface import HypervisorInterface, \ HypervisorInterfaceError after I debug momd, I find not import API and supervdsm, can you give me some suggestion? -- Regards Hongyu Du

2 1

Re: Recreating ISO storage domain
by Strahil Nikolov 27 Sep '20

27 Sep '20

Actually ISO domain is not necessary. You can moutn it via FUSE to a system and either use the python script ( It was mentioned several times in the mailing list) or the API/UI to upload your ISOs to a data storage domain. I think it is about time to get rid of the deprecated ISO domain. Best Regards, Strahil NIkolov В събота, 26 септември 2020 г., 21:44:28 Гринуич+3, Matthew.Stier(a)fujitsu.com <matthew.stier(a)fujitsu.com> написа: I have created a three host oVirt cluster using 4.4.2. I created an ISO storage domain to hold my collection of ISO images, and then decided to migrate it to a better location. I placed the storage domain in maintenance mode, end then removed it. When I when to recreate it add the new location, I found that the ‘ISO’ storage domain was no longer an options. What do I need to do to re-enable it, so I can re-create the storage domain. _______________________________________________ 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/4YVAUMRFWO7FN…

1 0

Re: Random hosts disconnects
by Artur Socha 27 Sep '20

27 Sep '20

On Fri, Sep 18, 2020 at 1:54 PM Anton Louw <Anton.Louw(a)voxtelecom.co.za> wrote: > > > Hi Artur, > > > > Thanks for the reply. I have attached the system logs. There was a > disconnect at 10:54, but no error that is different to the rest. I do see a > whole lot of QEMU Guest Agent and block_io errors in the system logs. Not > entirely sure what this means. > After a very quick search on the internet the first one does not seem to be severe at all - this guest agent provides only some information to VMs about the host. *Sep 18 10:50:41 node05.kvm.voxvm.co.za <http://node05.kvm.voxvm.co.za> libvirtd[23603]: 2020-09-18 08:50:41.493+0000: 23729: error : qemuDomainAgentAvailable:9133 : Guest agent is not responding: QEMU guest agent is not connected* The second one is unknown to me at all: ISep 18 10:50:52 node05.kvm.voxvm.co.za libvirtd[23603]: 2020-09-18 08:50:52.802+0000: 23729: error : qemuMonitorJSONBlockIoThrottleInfo:5005 : internal error: block_io_throttle inserted entry was not in expected format Sep 18 Perhaps someone with more libvirt/qemu background will comment on that. > > Checking the vdsm logs at the time or the error, the only entry is the > below: > > > > “2020-09-18 10:55:57,081+0000 WARN (qgapoller/2) > [virt.periodic.VmDispatcher] could not run <function <lambda> at > 0x7f2170395578> on ['d3838612-70bb-4731-a0d4-8f65d31b40a6', > '59a2f394-48fe-4bd9-91d6-08115f2eec0a', > 'f81e3ab8-c1a9-4674-b238-7e229fd43e7c', > '42189fa1-4381-02c7-d830-20eac408da2c', > '423f1c57-f98e-707f-c0f9-d4958d3f0fec', > '64d1eabc-20ff-4288-98ff-dcfd120fe7d2', > '4218baf0-e2a1-42c7-2efd-077407f47b4d', > '42184650-5a60-5403-d758-840bdbf92dd8', > '492ea3fe-0a27-4dde-abf9-7d146ee1b988', > '4218df00-15cd-bdf9-efd9-c5ead49fd89c', > '9c373379-718b-4906-abc1-960fb1820c2d', > 'b9441c7a-0bfd-4d41-a8de-ee24e4259b36', > 'd810325a-1a45-4054-a870-c8c052a22354', > '42189d3f-4570-45ea-6e5a-94c85a5885a1'] (periodic:289)” > > This WARN does not seem to be the cause ... it may be be the result because VM failed to be dispatched (perhaps due to lack of suitable hosts that got disconnected at a moment) > > I am stumped. Do you think it is worth a shot increasing the vdsConnectionTimeout > and vdsHeartbeatInSeconds to 40 for testing purposes? > I still don't think it will change anything unless your network between those 2 DC is 'tcp over pigeons' kind of setup :) Now, more seriously. Even if increasing timeouts would fix the connectivity I suspect the core issue would still remain ... in the best case scenario it could be postponed a bit. Am I correct assuming those 2 DC are located in 2 different physical locations? If so then I would closely check the network itself first (including hardware like routers/switches). Artur > > > Thanks > > > > *Anton Louw* > *Cloud Engineer: Storage and Virtualization* at *Vox* > ------------------------------ > *T:* 087 805 0000 | *D:* 087 805 1572 > *M:* N/A > *E:* anton.louw(a)voxtelecom.co.za > *A:* Rutherford Estate, 1 Scott Street, Waverley, Johannesburg > www.vox.co.za > > [image: F] <https://www.facebook.com/voxtelecomZA> > [image: T] <https://www.twitter.com/voxtelecom> > [image: I] <https://www.instagram.com/voxtelecomza/> > [image: L] <https://www.linkedin.com/company/voxtelecom> > [image: Y] <https://www.youtube.com/user/VoxTelecom> > > *From:* Artur Socha <asocha(a)redhat.com> > *Sent:* 18 September 2020 13:27 > *To:* Anton Louw <Anton.Louw(a)voxtelecom.co.za> > *Cc:* users(a)ovirt.org > *Subject:* Re: [ovirt-users] Re: Random hosts disconnects > > > > Hi Anton, > > I am not sure if changing this value would fix the issue. Defaults are > pretty high. For example vdsHeartbeatInSeconds=30seconds, > vdsTimeout=180seconds, vdsConnectionTimeout=20seconds. > > > > Do you still have relevant logs from the affected hosts: > > * /var/logs/vdsm/vdsm.log* > > * /var/logs/vdsm/supervdsm.log* > > Please look for any jsonrpc errors ie. write/read errors or (connection) > timeouts. Storage related warnings/errors might also be relevant. > > > > Plus system logs if possible: > > *journalctl -f /usr/share/vdsm/vdsmd* > > *journalctl -f /usr/sbin/libvirtd* > > > > In order to get system logs from particular time period please combine it > with the following example using -S -U options: > > *journalctl -S "2020-01-12 07:00:00" -U "2020-01-12 07:15:00" * > > I haven't a clue what to look there for besides any warnings/errors or > anything else that seems .... unusual. > > > > Artur > > > > > > On Thu, Sep 17, 2020 at 8:09 AM Anton Louw via Users <users(a)ovirt.org> > wrote: > > > > Hi Everybody, > > > > Did some digging around, and saw a few things regarding “vdsHeartbeatInSeconds” > > I had a look at the properties file located at /etc/ovirt-engine/engine-config/engine-config.properties, and do not see an entry for “vdsHeartbeatInSeconds.type=Integer”. > > Seeing as these data centers are geographically split, could the “vdsHeartbeatInSeconds” potentially be the issue? Is it safe to increase this value after I add “vdsHeartbeatInSeconds.type=Integer” into my engine-config.properties file? > > > > Thanks > > > > > > *Anton Louw* > > *Cloud Engineer: Storage and Virtualization* at *Vox* > ------------------------------ > > *T:* 087 805 0000 | *D:* 087 805 1572 > *M:* N/A > *E:* anton.louw(a)voxtelecom.co.za > *A:* Rutherford Estate, 1 Scott Street, Waverley, Johannesburg > www.vox.co.za > > > > [image: F] <https://www.facebook.com/voxtelecomZA> > > > > [image: T] <https://www.twitter.com/voxtelecom> > > > > [image: I] <https://www.instagram.com/voxtelecomza/> > > > > [image: L] <https://www.linkedin.com/company/voxtelecom> > > > > [image: Y] <https://www.youtube.com/user/VoxTelecom> > > > > > > *From:* Anton Louw via Users <users(a)ovirt.org> > *Sent:* 16 September 2020 09:01 > *To:* users(a)ovirt.org > *Subject:* [ovirt-users] Random hosts disconnects > > > > > > Hi All, > > > > I have a strange issue in my oVirt environment. I currently have a > standalone manager which is running in VMware. In my oVirt environment, I > have two Data Centers. The manager is currently sitting on the same subnet > as DC1. Randomly, hosts in DC2 will say “Not Responding” and then 2 seconds > later, the hosts will activate again. > > > > The strange thing is, when the manager was sitting on the same subnet as > DC2, hosts in DC1 will randomly say “Not Responding” > > > > I have tried going through the logs, but I cannot see anything out of the > ordinary regarding why the hosts would drop connection. I have attached the > engine.log for anybody that would like to do a spot check. > > > > Thanks > > > > *Anton Louw* > > *Cloud Engineer: Storage and Virtualization* at *Vox* > ------------------------------ > > *T:* 087 805 0000 | *D:* 087 805 1572 > *M:* N/A > *E:* anton.louw(a)voxtelecom.co.za > *A:* Rutherford Estate, 1 Scott Street, Waverley, Johannesburg > www.vox.co.za > > > > [image: F] <https://www.facebook.com/voxtelecomZA> > > > > [image: T] <https://www.twitter.com/voxtelecom> > > > > [image: I] <https://www.instagram.com/voxtelecomza> > > > > [image: L] <https://www.linkedin.com/company/voxtelecom> > > > > [image: Y] <https://www.youtube.com/user/VoxTelecom> > > > > > > [image: #VoxBrand] > <https://www.vox.co.za/fibre/fibre-to-the-home/?prod=HOME> > > > *Disclaimer* > > The contents of this email are confidential to the sender and the intended > recipient. Unless the contents are clearly and entirely of a personal > nature, they are subject to copyright in favour of the holding company of > the Vox group of companies. Any recipient who receives this email in error > should immediately report the error to the sender and permanently delete > this email from all storage devices. > > This email has been scanned for viruses and malware, and may have been > automatically archived by *Mimecast Ltd*, an innovator in Software as a > Service (SaaS) for business. Providing a *safer* and *more useful* place > for your human generated data. Specializing in; Security, archiving and > compliance. To find out more Click Here > <https://www.voxtelecom.co.za/security/mimecast/?prod=Enterprise>. > > > > > > _______________________________________________ > 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/EJL246IPBGEHI… > > > > -- > > Artur Socha > Senior Software Engineer, RHV > Red Hat > > -- Artur Socha Senior Software Engineer, RHV Red Hat

2 1

Re: Populating ISO storage domain
by Matthew.Stier＠fujitsu.com 26 Sep '20

26 Sep '20

It is being mounted under /rhev/data-center/mnt/ on the hosts, but is not being self-hosted engine. From: Matthew.Stier(a)fujitsu.com <Matthew.Stier(a)fujitsu.com> Sent: Saturday, September 26, 2020 4:17 PM To: Edward Berger <edwberger(a)gmail.com> Cc: users(a)ovirt.org Subject: [ovirt-users] Re: Populating ISO storage domain I setup the folder and the files with 36:36 with a mode of 775 on the directory and 644 on the files. Hours later, still not being read. From: Edward Berger <edwberger(a)gmail.com<mailto:edwberger@gmail.com>> Sent: Saturday, September 26, 2020 2:01 PM To: Stier, Matthew <Matthew.Stier(a)fujitsu.com<mailto:Matthew.Stier@fujitsu.com>> Cc: users(a)ovirt.org<mailto:users@ovirt.org> Subject: Re: [ovirt-users] Populating ISO storage domain If its in an NFS folder, make sure the ownership is vdsm:kvm (36:36) On Sat, Sep 26, 2020 at 2:57 PM Matthew.Stier(a)fujitsu.com<mailto:Matthew.Stier@fujitsu.com> <Matthew.Stier(a)fujitsu.com<mailto:Matthew.Stier@fujitsu.com>> wrote: I’ve created and ISO storage domain, and placed ISO’s in the export path do not show up under Storage > Storage Domains > iso > images; nor as available images which creating a new VM. Haven’t located method get them noticed. There is a greyed out ‘scan disk’ option. What is the proper method to install ISO images. _______________________________________________ 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/M6QYBMNT43MTW…

1 0

Re: Populating ISO storage domain
by Edward Berger 26 Sep '20

26 Sep '20

If its in an NFS folder, make sure the ownership is vdsm:kvm (36:36) On Sat, Sep 26, 2020 at 2:57 PM Matthew.Stier(a)fujitsu.com < Matthew.Stier(a)fujitsu.com> wrote: > I’ve created and ISO storage domain, and placed ISO’s in the export path > do not show up under Storage > Storage Domains > iso > images; nor as > available images which creating a new VM. > > > > Haven’t located method get them noticed. There is a greyed out ‘scan > disk’ option. > > > > What is the proper method to install ISO images. > _______________________________________________ > 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/M6QYBMNT43MTW… >

2 1

Populating ISO storage domain
by Matthew.Stier＠fujitsu.com 26 Sep '20

26 Sep '20

I've created and ISO storage domain, and placed ISO's in the export path do not show up under Storage > Storage Domains > iso > images; nor as available images which creating a new VM. Haven't located method get them noticed. There is a greyed out 'scan disk' option. What is the proper method to install ISO images.

1 0

Re: Recreating ISO storage domain
by Matthew.Stier＠fujitsu.com 26 Sep '20

26 Sep '20

Got this fixed. Ignore. From: Matthew.Stier(a)fujitsu.com <Matthew.Stier(a)fujitsu.com> Sent: Saturday, September 26, 2020 1:39 PM To: users(a)ovirt.org Subject: [ovirt-users] Recreating ISO storage domain I have created a three host oVirt cluster using 4.4.2. I created an ISO storage domain to hold my collection of ISO images, and then decided to migrate it to a better location. I placed the storage domain in maintenance mode, end then removed it. When I when to recreate it add the new location, I found that the 'ISO' storage domain was no longer an options. What do I need to do to re-enable it, so I can re-create the storage domain.

1 0

Recreating ISO storage domain
by Matthew.Stier＠fujitsu.com 26 Sep '20

26 Sep '20

I have created a three host oVirt cluster using 4.4.2. I created an ISO storage domain to hold my collection of ISO images, and then decided to migrate it to a better location. I placed the storage domain in maintenance mode, end then removed it. When I when to recreate it add the new location, I found that the 'ISO' storage domain was no longer an options. What do I need to do to re-enable it, so I can re-create the storage domain.

1 0

Node upgrade to 4.4
by Vincent Royer 26 Sep '20

26 Sep '20

I have 3 nodes running node ng 4.3.9 with a gluster/hci cluster. How do I upgrade to 4.4? Is there a guide?

6 11

oVirt - Engine - VM Reconstitute
by Jeremey Wise 26 Sep '20

26 Sep '20

As expected... this is a learning curve. My three node cluster.. in an attempt to learn how to do admin work on it, debug it... I have now redeployed the engine and even added second one on a node in cluster. But..... I now realize that my "production vms" are gone. In the past, on a manual build with KVM + Gluster .. when I repaired a damaged cluster I would just then browse to the xml file and import. I think with oVirt, those days are gone. As the PostGres engine knows the links to the disk / thin provision volumes / network / VM definition files. ###### Question: 1) Can someone point me to the manual on how to re-constitute a VM and bring it back into oVirt where all "oVirt-engines" were redeployed. It is only three or four VMs I typically care about (HA cluster and OCP ignition/ Ansible tower VM). 2) How do I make sure these core VMs are able to be reconstituted. Can I create a dedicated volume where the VMs are full provisioned, and the path structure is "human understandable". 3) I know that you can backup the engine. If I had been a smart person, how does one backup and recover from this kind of situation. Does anyone have any guides or good articles on this? Thanks, -- p <jeremey.wise(a)gmail.com>enguinpages

3 5

Re: Node 4.4.1 gluster bricks
by Strahil Nikolov 26 Sep '20

26 Sep '20

Since oVirt 4.4 , the stage that deploys the oVirt node/host is adding an lvm filter in /etc/lvm/lvm.conf which is the reason behind that. Best Regards, Strahil Nikolov В петък, 25 септември 2020 г., 20:52:13 Гринуич+3, Staniforth, Paul <p.staniforth(a)leedsbeckett.ac.uk> написа: Thanks, the gluster volume is just a test and the main reason was to test the upgrade of a node with gluster bricks. I don't know why lvm doesn\t work which is what oVirt is using. Regards, Paul S. ________________________________ From: Strahil Nikolov <hunter86_bg(a)yahoo.com> Sent: 25 September 2020 18:28 To: Users <users(a)ovirt.org>; Staniforth, Paul <P.Staniforth(a)leedsbeckett.ac.uk> Subject: Re: [ovirt-users] Node 4.4.1 gluster bricks Caution External Mail: Do not click any links or open any attachments unless you trust the sender and know that the content is safe. >1 node I wiped it clean and the other I left the 3 gluster brick drives untouch. If the last node from the original is untouched you can: 1. Go to the old host and use 'gluster volume remove-brick <VOL> replica 1 wiped_host:/path/to-brick untouched_bricks_host:/path/to-brick force' 2. Remove the 2 nodes that you have kicked away: gluster peer detach node2 gluster peer detach node3 3. Reinstall the wiped node and install gluster there 4. Create the filesystem on the brick: mkfs.xfs -i size=512 /dev/mapper/brick_block_device 5. Mount the Gluster (you can copy the fstab entry from the working node and adapt it) Here is an example: /dev/data/data1 /gluster_bricks/data1 xfs inode64,noatime,nodiratime,inode64,nouuid,context="system_u:object_r:glusterd_brick_t:s0" 0 0 6. Create the selinux label via 'semanage fcontext -a -t glusterd_brick_t "/gluster_bricks/data1(/.*)?"' (remove only the single quotes) and run 'restorecon -RFvv /gluster_bricks/data1' 7. Mount the FS and create a dir inside the mount point 8. Extend the gluster volume: 'gluster volume add-brick <VOL> replica 2 new_host:/gluster_bricks/<dir>/<subdir> 9. Run a full heal gluster volume heal <VOL> full 10. Repeat again and remember to never wipe 2 nodes at a time :) Good luck and take a look at Quick Start Guide - Gluster Docs Best Regards, Strahil Nikolov To view the terms under which this email is distributed, please go to:- http://leedsbeckett.ac.uk/disclaimer/email/

1 0

Re: Node 4.4.1 gluster bricks
by Strahil Nikolov 25 Sep '20

25 Sep '20

>1 node I wiped it clean and the other I left the 3 gluster brick drives untouch. If the last node from the original is untouched you can: 1. Go to the old host and use 'gluster volume remove-brick <VOL> replica 1 wiped_host:/path/to-brick untouched_bricks_host:/path/to-brick force' 2. Remove the 2 nodes that you have kicked away: gluster peer detach node2 gluster peer detach node3 3. Reinstall the wiped node and install gluster there 4. Create the filesystem on the brick: mkfs.xfs -i size=512 /dev/mapper/brick_block_device 5. Mount the Gluster (you can copy the fstab entry from the working node and adapt it) Here is an example: /dev/data/data1 /gluster_bricks/data1 xfs inode64,noatime,nodiratime,inode64,nouuid,context="system_u:object_r:glusterd_brick_t:s0" 0 0 6. Create the selinux label via 'semanage fcontext -a -t glusterd_brick_t "/gluster_bricks/data1(/.*)?"' (remove only the single quotes) and run 'restorecon -RFvv /gluster_bricks/data1' 7. Mount the FS and create a dir inside the mount point 8. Extend the gluster volume: 'gluster volume add-brick <VOL> replica 2 new_host:/gluster_bricks/<dir>/<subdir> 9. Run a full heal gluster volume heal <VOL> full 10. Repeat again and remember to never wipe 2 nodes at a time :) Good luck and take a look at Quick Start Guide - Gluster Docs Best Regards, Strahil Nikolov

2 1

oVirt host "unregistered"
by Jeremey Wise 25 Sep '20

25 Sep '20

Trying to get all the 3 node cluster back fully working... clearing out all the errors. I noted that the HCI wizard.. I thing SHOULD have deployed a hosted engine on the nodes, but this is not the case .. Only thor... the first node in cluster has hosted engine. I tried to redeploy this via the Cockpit wizard to add engine to host.. but I think this may not have been correct repair path. Now node in cluster shows all bricks... green (so it detects after reboot that host is back up and working.. but hosts lists it as "red triangle" with error "unregistered" I also just tried on third node to "edit" -> Host Engine -> and click drop box and choose "deploy" only log in event is "Host medusa configuration was updated by admin@internal-authz. 9/24/208:49:24 PM" but nothing changes. I then ran on odin (node with error) ovirt-hosted-engine-cleanup but no change ################ [root@odin ~]# ovirt-hosted-engine-cleanup This will de-configure the host to run ovirt-hosted-engine-setup from scratch. Caution, this operation should be used with care. Are you sure you want to proceed? [y/n] y -=== Destroy hosted-engine VM ===- You must run deploy first error: failed to get domain 'HostedEngine' -=== Stop HA services ===- -=== Shutdown sanlock ===- shutdown force 1 wait 0 shutdown done 0 -=== Disconnecting the hosted-engine storage domain ===- You must run deploy first -=== De-configure VDSM networks ===- ovirtmgmt ovirtmgmt A previously configured management bridge has been found on the system, this will try to de-configure it. Under certain circumstances you can loose network connection. Caution, this operation should be used with care. Are you sure you want to proceed? [y/n] y -=== Stop other services ===- Warning: Stopping libvirtd.service, but it can still be activated by: libvirtd-ro.socket libvirtd.socket libvirtd-admin.socket -=== De-configure external daemons ===- Removing database file /var/lib/vdsm/storage/managedvolume.db -=== Removing configuration files ===- ? /etc/init/libvirtd.conf already missing - removing /etc/libvirt/nwfilter/vdsm-no-mac-spoofing.xml ? /etc/ovirt-hosted-engine/answers.conf already missing ? /etc/ovirt-hosted-engine/hosted-engine.conf already missing - removing /etc/vdsm/vdsm.conf - removing /etc/pki/vdsm/certs/cacert.pem - removing /etc/pki/vdsm/certs/vdsmcert.pem - removing /etc/pki/vdsm/keys/vdsmkey.pem - removing /etc/pki/vdsm/libvirt-migrate/ca-cert.pem - removing /etc/pki/vdsm/libvirt-migrate/server-cert.pem - removing /etc/pki/vdsm/libvirt-migrate/server-key.pem - removing /etc/pki/vdsm/libvirt-spice/ca-cert.pem - removing /etc/pki/vdsm/libvirt-spice/server-cert.pem - removing /etc/pki/vdsm/libvirt-spice/server-key.pem - removing /etc/pki/vdsm/libvirt-vnc/ca-cert.pem - removing /etc/pki/vdsm/libvirt-vnc/server-cert.pem - removing /etc/pki/vdsm/libvirt-vnc/server-key.pem - removing /etc/pki/CA/cacert.pem - removing /etc/pki/libvirt/clientcert.pem - removing /etc/pki/libvirt/private/clientkey.pem ? /etc/pki/ovirt-vmconsole/*.pem already missing - removing /var/cache/libvirt/qemu ? /var/run/ovirt-hosted-engine-ha/* already missing - removing /var/tmp/localvm69i1jxnd - removing /var/tmp/localvmfyg59713 - removing /var/tmp/localvmmg5y6g52 -=== Removing IP Rules ===- [root@odin ~]# [root@odin ~]# ################ Ideas on how to repair engine install issues on nodes? -- penguinpages

3 3

Re: Node 4.4.1 gluster bricks
by Jayme 25 Sep '20

25 Sep '20

Assuming you don't care about data on the drive you may just need to use wipefs on the device i.e. wipefs -a /dev/sdb On Fri, Sep 25, 2020 at 12:53 PM Staniforth, Paul < P.Staniforth(a)leedsbeckett.ac.uk> wrote: > Hello, > how do you manage a gluster host when upgrading a node? > > I upgraded/replaced 2 nodes with the new install and can't recreate any > gluster bricks. > 1 node I wiped it clean and the other I left the 3 gluster brick drives > untouched. > > If I try to create bricks using the UI on the nodes, I get an internal > server error. When I try to create a PV from the clean disk, I get device > excluded by filter. > > e.g. > > pvcreate /dev/sdb > > Device /dev/sdb excluded by a filter. > > pvcreate /dev/mapper/SSDSC2KB240G7R_BTYS83100E0S240AGN > > Device /dev/mapper/SSDSC2KB240G7R_BTYS83100E0S240AGN excluded by a > filter. > > > > > Thanks, > > > Paul S. > > To view the terms under which this email is distributed, please go to:- > http://leedsbeckett.ac.uk/disclaimer/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/27IUR3H54G2FR… >

2 1

Node 4.4.1 gluster bricks
by Staniforth, Paul 25 Sep '20

25 Sep '20

Hello, how do you manage a gluster host when upgrading a node? I upgraded/replaced 2 nodes with the new install and can't recreate any gluster bricks. 1 node I wiped it clean and the other I left the 3 gluster brick drives untouched. If I try to create bricks using the UI on the nodes, I get an internal server error. When I try to create a PV from the clean disk, I get device excluded by filter. e.g. pvcreate /dev/sdb Device /dev/sdb excluded by a filter. pvcreate /dev/mapper/SSDSC2KB240G7R_BTYS83100E0S240AGN Device /dev/mapper/SSDSC2KB240G7R_BTYS83100E0S240AGN excluded by a filter. Thanks, Paul S. To view the terms under which this email is distributed, please go to:- http://leedsbeckett.ac.uk/disclaimer/email/

1 0

oVirt 4.4.2 is now generally available
by Lev Veyde 25 Sep '20

25 Sep '20

The oVirt project is excited to announce the general availability of oVirt 4.4.2 , as of September 17th, 2020. This release unleashes an altogether more powerful and flexible open source virtualization solution that encompasses hundreds of individual changes and a wide range of enhancements across the engine, storage, network, user interface, and analytics, as compared to oVirt 4.3. Important notes before you install / upgrade Please note that oVirt 4.4 only supports clusters and data centers with compatibility version 4.2 and above. If clusters or data centers are running with an older compatibility version, you need to upgrade them to at least 4.2 (4.3 is recommended). Please note that in RHEL 8 / CentOS 8 several devices that worked on EL7 are no longer supported. For example, the megaraid_sas driver is removed. If you use Enterprise Linux 8 hosts you can try to provide the necessary drivers for the deprecated hardware using the DUD method (See the users’ mailing list thread on this at https://lists.ovirt.org/archives/list/users@ovirt.org/thread/NDSVUZSESOXEFJ… ) 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>. What’s new in oVirt 4.4.2 Release? This update is the second in a series of stabilization updates to the 4.4 series. This release is available now on x86_64 architecture for: - Red Hat Enterprise Linux 8.2 - CentOS Linux (or similar) 8.2 - CentOS Stream (tech preview) This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: - Red Hat Enterprise Linux 8.2 - CentOS Linux (or similar) 8.2 - CentOS Stream (tech preview) oVirt Node 4.4 based on CentOS Linux 8.2 (available for x86_64 only) will be released separately due to a blocker issue (Bug 1837864 <https://bugzilla.redhat.com/show_bug.cgi?id=1837864>). oVirt Node and Appliance have been updated, including: - oVirt 4.4.2: http://www.ovirt.org/release/4.4.2/ - Ansible 2.9.13: https://github.com/ansible/ansible/blob/stable-2.9/changelogs/CHANGELOG-v2.… - Glusterfs 7.7: https://docs.gluster.org/en/latest/release-notes/7.7/ 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 will be available soon for CentOS Linux 8 Additional resources: - Read more about the oVirt 4.4.2 release highlights: http://www.ovirt.org/release/4.4.2/ - 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.2/ [2] http://resources.ovirt.org/pub/ovirt-4.4/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>

3 5

[ANN] oVirt 4.4.3 Second Release Candidate is now available for testing
by Lev Veyde 25 Sep '20

25 Sep '20

oVirt 4.4.3 Second Release Candidate is now available for testing The oVirt Project is pleased to announce the availability of oVirt 4.4.3 Second Release Candidate for testing, as of September 25th, 2020. This update is the third 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 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.3 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.3 (redeploy in case of already being on 4.4.3). 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.2 or newer * CentOS Linux (or similar) 8.2 or newer This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 8.2 or newer * CentOS Linux (or similar) 8.2 or newer * oVirt Node 4.4 based on CentOS Linux 8.2 (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 Additional Resources: * Read more about the oVirt 4.4.3 release highlights: http://www.ovirt.org/release/4.4.3/ * 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.3/ [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

export to ova
by Tommaso - Shellrent 25 Sep '20

25 Sep '20

Hi to all. Hi try to ank another time the same question: in our tests ovirt seems to be able to make only one export to ova at time. also on different hosts and datacenter. Someone can explain to us why?? this is for us a big issue, because we use it in a backup script of more than 50 VMs and counting.... We also already opened a bug without any useful response: https://bugzilla.redhat.com/show_bug.cgi?id=1855782 Regards, -- -- Shellrent - Il primo hosting italiano Security First *Tommaso De Marchi* /COO - Chief Operating Officer/ Shellrent Srl Via dell'Edilizia, 19 - 36100 Vicenza Tel. 0444321155 <tel:+390444321155> | Fax 04441492177

2 1