- Users - oVirt List Archives

Power failure makes cluster and hosted engine unusable
by Seann G. Clark 29 Mar '21

29 Mar '21

All, After a power failure, and generator failure I lost my cluster, and the Hosted engine refused to restart after power was restored. I would expect, once storage comes up that the hosted engine comes back online without too much of a fight. In practice because the SPM went down as well, there is no (clearly documented) way to clear any of the stale locks, and no way to recover both the hosted engine and the cluster. I have spent the last 12 hours trying to get a functional hosted-engine back online, on a new node and each attempt hits a new error, from the installer not understanding that 16384mb of dedicated VM memory out of 192GB free on the host is indeed bigger than 4096MB, to ansible dying on an error like this "Error while executing action: Cannot add Storage Connection. Storage connection already exists." The memory error referenced above shows up as: [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "Available memory ( {'failed': False, 'changed': False, 'ansible_facts': {u'max_mem': u'180746'}}MB ) is less then the minimal requirement (4096MB). Be aware that 512MB is reserved for the host and cannot be allocated to the engine VM."} That is what I typically get when I try the steps outlined in the KB "CHAPTER 7. RECOVERING A SELF-HOSTED ENGINE FROM AN EXISTING BACKUP" from the RH Customer portal. I have tried this numerous ways, and the cluster still remains in a bad state, with the hosted engine being 100% inoperable. What I do have are the two host that are part of the cluster and can host the engine, and backups of the original hosted engine, both disk and engine-backup generated. I am not sure what I can do next, to recover this cluster, any suggestions would be apricated. Regards, Seann

1 0

VLAN Trunking to Cluster Nodes
by Jason Alexander Hazen Valliant-Saunders 29 Mar '21

29 Mar '21

Good Day Ovirt Users; I am running a the following Setup: [image: image.png] [image: image.png] [image: image.png] I need to setup the BOND1 connector in the Datacenter with 9 VLAN's they Exist on the Ovirt Node already and the Bond is UP: [image: image.png] (bond0 is 10GB Chelsio Storage Network) The idea is to pass through Vlan's on bond1 (bond1.1, 1.2, 1.3, 1.n ) where n = vlanid. However I'm unsure as to how I go about setting up the Provider in the datacenter, so that bond1 is used to trunk vlans into the DC. From what I have read the VLAN"s need to exist on the cluster node (they do); but the ovirt-engine must then have some kind of provider configured (just like it does for ovirt mgt) then i can map the vNic Profiles to that new provider as per their vlan assignment. Regards, Hazen

1 0

Cinderlib problem after upgrade from 4.3.10 to 4.4.5
by Marc-Christian Schröer 29 Mar '21

29 Mar '21

Hello all, first of all thank you very much for this stable virtualization environment. It has been a pillar for our company’s business for more than 5 years now and after migrating from version 3 to 4 it has been so stable ever since. Anyway, I ran into a problem I cannot fix on my own yesterday: After a lot of consideration and hesitation since this is a production environment I followed the upgrade guide (https://www.ovirt.org/documentation/upgrade_guide/ <https://www.ovirt.org/documentation/upgrade_guide/>), configured a vanilla CentOS 8 server as controller, decommissioned the old 4.3 controller and fired up the new one. It worked like a charm until I tried to migrate VMs, start new ones or even create new disks. We use Ceph as managed storage, providing a SSD only and a HDD only pool. The UI simply told me that there was an error. I started investigating the issue and found corresponding log entries in ovirt-engine.log: 2021-03-22 10:36:37,247+01 ERROR [org.ovirt.engine.core.common.utils.cinderlib.CinderlibExecutor] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-24) [67bf193c] cinderlib execution failed: But that was all the engine had to say about the issue. There was no stack trace or additional information. There is no logfile in /var/log/ovirt-engine/cinderlib/, the directory simply is empty while on the other controller it was frequently filed with annoying „already mounted“ messages. Can anyone help me with that issue? I searched the web for a solution or someone else with the same problem, but came up empty. Is there a way to turn up the log level for cinderlib? Are there any dependencies I have to install besides the ovirt packages? Any help is very much appreciated! Kind regards and stay healthy, Marc -- ________________________________________________________________________ Dipl.-Inform. Marc-Christian Schröer schroeer(a)ingenit.com Geschäftsführer / CEO ---------------------------------------------------------------------- ingenit GmbH & Co. KG Tel. +49 (0)231 58 698-120 Emil-Figge-Strasse 76-80 Fax. +49 (0)231 58 698-121 D-44227 Dortmund www.ingenit.com Registergericht: Amtsgericht Dortmund, HRA 13 914 Gesellschafter : Thomas Klute, Marc-Christian Schröer ________________________________________________________________________

2 3

Unable to add hosts to cluster & possible related routing issue
by David White 27 Mar '21

27 Mar '21

Hi all, I used the oVirt installer via cockpit to setup a hyperconverged cluster on 3 physical hosts running Red Hat 8.3. I used the following two resources to guide my work: - https://www.ovirt.org/documentation/gluster-hyperconverged/chap-Deploying_H… - https://blogs.ovirt.org/2018/02/up-and-running-with-ovirt-4-2-and-gluster-s… As I mentioned in a previous email a week ago, it appears as if the wizard successfully setup gluster on all 3 of the servers, and the wizard also successfully setup the ovirt engine on the first host. However, the oVirt engine only recognizes the first host, and only the first host's physical resources are available to the cluster. So I have Gluster 8 installed on the 3 hosts (RHEL 8), and oVirt 4.4.5 installed on the first host, along with the ovirt engine VM. I run `gluster peer status` from the first node, can confirm that the other two physical hosts are healthy: (example.com is replacing actual domain below) [root@cha1-storage ~]# gluster peer statusNumber of Peers: 2Hostname: cha2-storage.mgt.example.comUuid: 240a7ab1-ab52-4e5b-98ed-d978f848835eState: Peer in Cluster (Connected)Hostname: cha3-storage.mgt.example.comUuid: 0563c3e8-237d-4409-a09a-ec51719b0da6State: Peer in Cluster (Connected) I am now trying to get the other two hosts added to the Engine. I navigate to Compute -> Hosts, and click New, fill in the details (hostname, root password, etc..) and begin the installation on the additional hosts. It keeps failing. Checking the error logs in /var/log/ovirt-engine/host-deploy on the Engine VM, I see the following near the bottom: "msg" : "Failed to download metadata for repo 'ovirt-4.4-epel': Cannot prepare internal mirrorlist: Curl error (7): Couldn't connect to server for https://mirrors.fedoraproject.org/metalink?repo=epel-8&arch=x86_64&infra=$i… [Failed to connect to mirrors.fedoraproject.org port 443: No route to host]", I can confirm that the Engine and each of the hosts are able to get to mirrors.fedoraproject.org: I've run the following on both the Engine, as well as each of the hosts (the first host where everything is installed, as well as the 2nd host where I'm trying to get it installed): [root@ovirt-engine1 host-deploy]# curl -i https://mirrors.fedoraproject.org HTTP/2 302 Note, that this traffic is going out the management network. That may be an important distinction -- keep reading. So this does lead me to another issue that may or may not be related. I've discovered that, from the RHEL 8 host's perspective, the public facing network is unable to get out to the internet. Management (Gluster & the Engine VM) is on: 10.1.0.0/24 Each of the hosts are able to ping each other and communicate with each other. Each of the hosts are able to ping 8.8.8.8 whenever the frontend network interface is disabled (see below). The frontend network is on: 192.168.0.0/24 Each of the hosts are able to ping each other on this network But this network isn't able to get out to the internet (yet). Obviously I need to fix the routing and figure out why the 192.168.0.0/24 network is unable to reach the internet. But shouldn't all the traffic to install the ovirt functionality onto the 2nd host go out the management network? So to summarize, I have a few questions: - Why didn't the wizard properly install the ovirt functionality onto all 3 hosts to begin with when I did the initial installation? - From the physical host's perspective, what should be the default route? The internal management, or the front-end network? - Is the following statement accurate? - The ovirt-engine's default route should be management -- it doesn't even have a front-end IP address. - Why would the ovirt engine fail to install, and indicate that it cannot get to mirrors.fedoraproject.org, when clearly it can? - Again, the ovirt-engine VM is able to curl that URL and gets a valid http response. - Any other tips or suggestions on how to troubleshoot this? Sent with ProtonMail Secure Email.

1 1

hosted engine vm don't boot after minor update
by a.cor＠outlook.com 26 Mar '21

26 Mar '21

Hello! I have rhv 4.4.2 and NFS storage type for HE Domain Storage. I updated to 4.4.4 by guide (https://www.ovirt.org/documentation/upgrade_guide/#Updating_a_self-hosted_e…) and reboot Hosted Engine VM. After this VM is not booting. Connected to console I see next error: BdsDxe: failed to load Boot0001 "UEFI Misc Device"... After "Press any key" I got BIOS screen, go to Device Manager -> Drive Health Manager I see nothing. I suggest that something happened with VM config. Check /etc/ovirt-hosted-engine/hosted-engine.conf All looks correctly (I checked UUID to Domain Storage and etc.) Check /var/run/ovirt-hosted-engine-ha/vm.conf. After encoding base64 I found something like this: <source file="/rhev/data-center/0000-0000-0000-0000-0000/6916940d-b21b-4739-9d6b-4f7ff9e72a9e/images/9a17d31d-30f8-480d-a106-2fa7f0d48c40/a817c10b-0366-4c05-b512-e6beb8308b5d All path is correct only zero after data-center/. I changed it to real path, decode to base64 and try to start VM with hosted-engine --vm-start --vm-conf=PATH_TO_NEW_FILE. Nothing. I see similar error. Could someone help me in this case?

1 0

Hosted engine deployment fail because host version does not match cluster version
by emanuele.breuza＠e4company.com 26 Mar '21

26 Mar '21

Hello, I'm Emanuele. I'm interested in setting up a 3 node HA oVirt cluster on RHEL 8.3. Following the oVirt Gluster Hyperconvergence guide, I managed to setup a GlusterFS storage and then I started the procedure to configure a self-hosted engine via cockpit. Unfortunately, I got stack at the "Prepare VM stage". During this procedure, the automated process paused to let you verify inside the ovirt-engine that your host is OK. Since this is a brand new installation of oVirt, I have only one host configured and it is marked as not-good. The reason reported in the web page is that the host is compatible for v. 4.2, 4.3 and 4.4 but the Cluster is v. 4.5. I tried to execute the upgrade procedure on the host but it was unable to go into maintenance mode. I tried both ovirt-release44 and ovirt-release-master RPM to load the latest repository but without success. Do you have any suggestion about how to fix the self-hosted engine procedure? BTW, if I install my server with the oVirt node ISO the procedure works correctly and my host report also 4.5 into the compatibility version list. Thank you very much for your help!!!

1 0

[ANN] oVirt 4.4.6 First Release Candidate is now available for testing
by Lev Veyde 25 Mar '21

25 Mar '21

oVirt 4.4.6 First Release Candidate is now available for testing The oVirt Project is pleased to announce the availability of oVirt 4.4.6 First Release Candidate for testing, as of March 25th, 2021. This update is the sixth in a series of stabilization updates to the 4.4 series. How to prevent hosts entering emergency mode after upgrade from oVirt 4.4.1 Note: Upgrading from 4.4.2 GA or later should not require re-doing these steps, if already performed while upgrading from 4.4.1 to 4.4.2 GA. These are only required to be done once. Due to Bug 1837864 <https://bugzilla.redhat.com/show_bug.cgi?id=1837864> - Host enter emergency mode after upgrading to latest build If you have your root file system on a multipath device on your hosts you should be aware that after upgrading from 4.4.1 to 4.4.6 you may get your host entering emergency mode. In order to prevent this be sure to upgrade oVirt Engine first, then on your hosts: 1. Remove the current lvm filter while still on 4.4.1, or in emergency mode (if rebooted). 2. Reboot. 3. Upgrade to 4.4.6 (redeploy in case of already being on 4.4.6). 4. Run vdsm-tool config-lvm-filter to confirm there is a new filter in place. 5. Only if not using oVirt Node: - run "dracut --force --add multipath” to rebuild initramfs with the correct filter configuration 6. Reboot. Documentation - If you want to try oVirt as quickly as possible, follow the instructions on the Download <https://ovirt.org/download/> page. - For complete installation, administration, and usage instructions, see the oVirt Documentation <https://ovirt.org/documentation/>. - For upgrading from a previous version, see the oVirt Upgrade Guide <https://ovirt.org/documentation/upgrade_guide/>. - For a general overview of oVirt, see About oVirt <https://ovirt.org/community/about.html>. Important notes before you try it Please note this is a pre-release build. The oVirt Project makes no guarantees as to its suitability or usefulness. This pre-release must not be used in production. Installation instructions For installation instructions and additional information please refer to: https://ovirt.org/documentation/ This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 8.3 or newer * CentOS Linux (or similar) 8.3 or newer This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 8.3 or newer * CentOS Linux (or similar) 8.3 or newer * oVirt Node 4.4 based on CentOS Linux 8.3 (available for x86_64 only) See the release notes [1] for installation instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is already available for CentOS Linux 8 - oVirt Node NG is already available for CentOS Linux 8 - We found a few issues while testing on CentOS Stream so we are still basing oVirt 4.4.6 Node and Appliance on CentOS Linux. Additional Resources: * Read more about the oVirt 4.4.6 release highlights: http://www.ovirt.org/release/4.4.6/ * Get more oVirt project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] http://www.ovirt.org/release/4.4.6/ [2] http://resources.ovirt.org/pub/ovirt-4.4-pre/iso/ -- Lev Veyde Senior Software Engineer, RHCE | RHCVA | MCITP Red Hat Israel <https://www.redhat.com> lev(a)redhat.com | lveyde(a)redhat.com <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

1 0

Ovirt Node (iso) - OK to enable Centos-BaseOS/Centos-Appstream repos ?
by morgan cox 25 Mar '21

25 Mar '21

Hi. I have installed Ovirt nodes via the ovirt-node iso (centos8 based) - on a fresh install the standard CentOS repos are disabled (the ovirt 4-4 repo is enabled) As part of our company hardening we need to install a few packages from the Centos repos. Can I enable the CentOS-Linux-AppStream.repo + CentOS-Linux-BaseOS.repo repos or will this cause issues when we update the node ? Thanks

3 4

Problem to create provider
by miguel.garcia＠toshibagcs.com 25 Mar '21

25 Mar '21

We have a problem to create the first provider in the ovirt cluster by following next steps: Go to Administration - Provider - click Add Filled up fields for new provider with next information: Name: ovirt-provider-ovn Type: External Network Provider Network Plugin: oVirt Network Provider for OVN Provider URL: https://ovirthostname:9696 Uncheck Read-only Check Request authentication username : admin@internal Protocol HTTPS Hostname ovirthostname API port: 35357 Click Test Result: Test Failed (unknow error) Log file: 2021-03-23 15:23:50,986-04 ERROR [org.ovirt.engine.core.bll.provider.network.openstack.ExternalNetworkProviderProxy] (default task-118) [501852ef-cd76-40d0-8ef3-6b0826b3c0dd] Failed to communicate with external provider 'ovirt-provider-ovn' due to error 'ConnectException: Connection refused (Connection refused)' [org.ovirt.engine.core.utils.servlet.ServletUtils] (default t2021-03-23 15:23:50,986-04 ERROR [org.ovirt.engine.core.bll.GetProviderCertificateChainQuery] (default task-118) [501852ef-cd76-40d0-8ef3-6b0826b3c0dd] Error in encoding certificate: EngineException: Connection refused (Connection refused) (Failed with error PROVIDER_FAILURE and code 5050) I think I would expect to ask the certificate to complete connection but does not ask for certificate at all. Any idea how to solve this?

2 3

VDSM command failed:Received fatal alert certificate_expire
by fmendoza＠red.com.sv 24 Mar '21

24 Mar '21

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

1 0

websockify + ovirt
by Pascal D 24 Mar '21

24 Mar '21

Hi, I am trying to get the spice-web-client working with ovirt. One area where I am having difficulties is authentication.Looking at remote-viewer on linux I am able to see that the minimum fields to have a successful spice connection are the following: [virt-viewer] type=spice host=70.xxx.176.xxx port=5914 password=WQJQWCo+s8tK tls-port=5915 tls-ciphers=DEFAULT host-subject=O=xxxx.com,CN=d1c1v5.xxx.net ca=-----BEGIN CERTIFICATE-----\nMIIDzDCCArSgAwIBAgICEAAwDQYJKoZIhvcNAQELBQAwSzELMAkGA1UEBhMCVVMxGDAWBgNVBAoM\nD2J1dHRlcmZseWl0LmNvbTEiMCAGA1UEAwwZb3YxLmJ1dHRlcmZseWl0LmNvbS40NTQ2NTAeFw0x\nOTA2MDQwMDMyMDVaFw0yOTA2MDIwMDMyMxxxxxxxxxxxxxxxxxxxxxxxxdXR0\nZXJmbHlpdC5jb20xIjAgBgNVBAMMGW92MS5idXR0ZXJmbHlpdC5jb20uNDU0NjUwggEiMA0GCSqG\nSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDD218EJkIJewgmeDFcUM7vEQ3RQ4nL9ZNEg+zORlruLKON\neZRDfgXei3XTt+VFUNTrxBjepf+yN3WjhVP+lDeDveZU/3OYKj9dSewlz7Mj1XTKE8DXDMIGYc79\nXUrcSoiEjCRG1eB+w+uyP4WK0AlJwGKav3AZuU5awjvYAftkW0RhOgdjp80ofuoC3K9TUPPjemtw\n3EWb4bjRcWiDUj8owfhhAHnb4RfacUSMQmYpVJ5YfRunYrCOixlOeGx7PkvXLqWmu2Rnrnk7TNn6\nv74fHh3ruHmZHLk2i6/yNoOAiJC/M8piCGZ3tiOcnPcYF2ZoX+Ud6BV69Hp6SxnF/eCXAgMBAAGj\ngbkwgbYwHQYDVR0OBBYEFAlrTpLGY5Dq6gtA7d7CXc1QAFmOMHQGA1UdIwRtMGuAFAlrTpLGY5Dq\n6gtA7d7CXc1QAFmOoU+kTTBLMQswCQYDVQQGEwJVUzEYMBYGA1UECgwPYnV0dGVyZmx5aXQuY29t\nMSIwIAYDVQQDDBlvdjEuYnV0dGVyZmx5aXQuY29tLjQ1NDY1ggIQADAPBgNVHRMBAf8EBTADAQH/\nMA4GA1UdDwEB/wQEAwIBBjANBgkqhkiG9w0BAQsFAAOCA QEAoC8Nx/s4Uafgc3iyzxbLPb/chQ8U\n7+lULXTq+ZLOuMDdu6UKt7qKZpJZK8ZhjFh/1yVOnpzm7Np+oP7TQlOUkup8X4HsfAwrCgNK1IT1\nETdbdMYD8HYFjxz/0xbnMkJAHfPEh1vtqplw3YhVgiAZfZfT8HzVY/xGkjurvxSyVjBSbn+4uao1\n6W9URt2rWTHn+XxoT+j+cx8vv1WKsynlMBtUjCFy8eR7ZDngRcM/9iRkRCGHJvWJmi1CRrQeE5RZ\nvBH0zE64J3cOJj4BSlN3wOYWiRq28XLB9epDDyZaRpnsqLCOq/+/LscM7iPW1acdCoCu68nJUwTQ\nh1Jh7vQjCQ==\n-----END CERTIFICATE-----\n with this I can successfully connect to a vm. Now I would like to do the same from spice-web-client but websockify doesn't give me a tls-port. How to could I implement this? Is there a wrapper that exists that I can pass to websockify to do the authentication on the port + 1 (it seems it is always the next port) Thanks in advance for your help

4 12

VM listed as unmanaged external
by miguel.garcia＠toshibagcs.com 24 Mar '21

24 Mar '21

We have a vm that got renamed with prefix "external-*" and in the status of resources for this vm are as unmanaged. Is there a way to turn it back to manage vm and rollback how it was before?

1 0

supervdsm failing during network_caps
by Alan G 24 Mar '21

24 Mar '21

Hi, I have issues with one host where supervdsm is failing in network_caps. I see the following trace in the log. MainProcess|jsonrpc/1::ERROR::2020-01-06 03:01:05,558::supervdsm_server::100::SuperVdsm.ServerCallback::(wrapper) Error in network_caps Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/supervdsm_server.py", line 98, in wrapper res = func(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/network/api.py", line 56, in network_caps return netswitch.configurator.netcaps(compatibility=30600) File "/usr/lib/python2.7/site-packages/vdsm/network/netswitch/configurator.py", line 317, in netcaps net_caps = netinfo(compatibility=compatibility) File "/usr/lib/python2.7/site-packages/vdsm/network/netswitch/configurator.py", line 325, in netinfo _netinfo = netinfo_get(vdsmnets, compatibility) File "/usr/lib/python2.7/site-packages/vdsm/network/netinfo/cache.py", line 150, in get return _stringify_mtus(_get(vdsmnets)) File "/usr/lib/python2.7/site-packages/vdsm/network/netinfo/cache.py", line 59, in _get ipaddrs = getIpAddrs() File "/usr/lib/python2.7/site-packages/vdsm/network/netinfo/addresses.py", line 72, in getIpAddrs for addr in nl_addr.iter_addrs(): File "/usr/lib/python2.7/site-packages/vdsm/network/netlink/addr.py", line 33, in iter_addrs with _nl_addr_cache(sock) as addr_cache: File "/usr/lib64/python2.7/contextlib.py", line 17, in __enter__ return self.gen.next() File "/usr/lib/python2.7/site-packages/vdsm/network/netlink/__init__.py", line 92, in _cache_manager cache = cache_allocator(sock) File "/usr/lib/python2.7/site-packages/vdsm/network/netlink/libnl.py", line 469, in rtnl_addr_alloc_cache raise IOError(-err, nl_geterror(err)) IOError: [Errno 16] Message sequence number mismatch A restart of supervdsm will resolve the issue for a period, maybe 24 hours, then it will occur again. So I'm thinking it's resource exhaustion or a leak of some kind? Running 4.2.8.2 with VDSM at 4.20.46. I've had a look through the bugzilla and can't find an exact match, closest was this one https://bugzilla.redhat.com/show_bug.cgi?id=1666123 which seems to be a RHV only fix. Thanks, Alan

2 3

[ANN] Async release for oVirt 4.4.5
by Sandro Bonazzola 24 Mar '21

24 Mar '21

On March 23rd 2021 the oVirt project released an async update to the following packages: - ovirt-ansible-collection-1.4.1 - vdsm-4.40.50.9 - ovirt-engine-4.4.5.11 - ovirt-release44-4.4.5.1 - ovirt-engine-appliance-4.4-20210323171213.1 - oVirt Node is still building, will follow tomorrow. Fixing the following bugs: - Bug 1940438 <https://bugzilla.redhat.com/show_bug.cgi?id=1940438> - Revoking a token using ovirt_auth module fails hosted_engine_setup ansible role - Bug 1941311 <https://bugzilla.redhat.com/show_bug.cgi?id=1941311> - Live merge after extend disk fails - 'Vm' object has no attribute 'refreshDriveVolume' - Bug 1940448 <https://bugzilla.redhat.com/show_bug.cgi?id=1940448> - Upgrade to 4.4.5 fails schema upgrade if user_profiles table contains duplicate entries -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/> *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

1 1

Exporting ovirt vm's to esxi
by karunamandava＠gmail.com 24 Mar '21

24 Mar '21

Hi Everyone, Is there any way to export Ovirt vm's to ESXi server. Please help me out on this. Thanks in Advance.

1 0

The best HCI config with 8Nodes and 2 sites?
by Arman Khalatyan 23 Mar '21

23 Mar '21

Hello everybody, I would like to deploy HCI with our 2 buildings each with 8 compute nodes. Each host has a mirrored OS disks and 1 slot for the SSD. So I will use SSD for the glusterfs. my question is what is the best type of the glusterfs volume? I can leave with 8way mirror but what happened if the connection between buildings will go down? where will my ovirt-engine start?

2 1

One host 4.4.5 upgade failed
by ozmen62＠hotmail.com 23 Mar '21

23 Mar '21

Hi, We have 2 hosts, upgarded to 4.4.5. Engine and one of the hosts was successfull But, of of the hosts stucked and doesnt upgrade. successful one has these kernels # vmlinuz-4.18.0-240.1.1.el8_3.x86_64 # vmlinuz-4.18.0-240.15.1.el8_3.x86_64 Unsuccessful one has; # vmlinuz-4.18.0-193.28.1.el8_2.x86_64 # vmlinuz-4.18.0-240.1.1.el8_3.x86_64 Unsuccessful one has "/usr/share/ovirt-node-ng-image-update/" directory and image but we dont make it upgrade This is the some part of the log file from engine; FAILED! => {"changed": true, "cmd": ["vdsm-tool", "configure", "--force"], "delta": "0:00:10.773484", "end": "2021-03-23 09:00:08.285785", "msg": "non-zero return code", "rc": 1, "start": "2021-03-23 08:59:57.512301", "stderr": "Error: ServiceOperationError: _systemctlStop failed\nb'Job for vdsmd.service canceled.\\n' ", "stderr_lines": ["Error: ServiceOperationError: _systemctlStop failed", "b'Job for vdsmd.service canceled.\\n' "], "stdout": "\nChecking configuration status...\n\nlibvirt is already configured for vdsm\nSUCCESS: ssl configured to true. No conflicts\nsanlock is configured for vdsm\nlvm is configured for vdsm\nCurrent revision of multipath.conf detected, preserving\nabrt is already configured for vdsm\nManaged volume database is already configured", "stdout_lines": ["", "Checking configuration status...", "", "libvirt is already configured for vdsm", "SUCCESS: ssl configured to true. No conflicts", "sanlock is configured for vdsm", "lvm is configured for vdsm", "Cur rent revision of multipath.conf detected, preserving", "abrt is already configured for vdsm", "Managed volume database is already configured"]} when we triggered the dnf update/upgrade it says "there is no upgrade" both engine web page and cli Is there any suggestion for upgrading the host, it's stucked on "NonOperational" mode

2 5

user portal
by Enrico Becchetti 23 Mar '21

23 Mar '21

Dear all, I'm using ovirt 4.3.2 with its engine on a virtual machine. The nodes are all Centos 7.7. Both engine and hypervisor systems work on a 10.0.0.0 private network. Now I would like to let users access the ovirt web page (user portal) and for this I must necessarily add a second network interface to the engine by inserting a public ip. I can't use NAT. Can you give me any advice for this operation ? Can I add the network interface and then run engine-setup ? Will oVirt be accessible from both ip addresses at the end of this operation ? Lots of thanks. Enrico -- _______________________________________________________________________ Enrico Becchetti Servizio di Calcolo e Reti Istituto Nazionale di Fisica Nucleare - Sezione di Perugia Via Pascoli,c/o Dipartimento di Fisica 06123 Perugia (ITALY) Phone:+39 075 5852777 Skype:enrico_becchetti Mail: Enrico.Becchetti<at>pg.infn.it ______________________________________________________________________

3 4

What do some of the terms mean in the documentation?
by jenia.ivlev＠gmail.com 23 Mar '21

23 Mar '21

Hello I want to install oVirt virtualization software on my ArchLinux as a lab for learning and experimenting. I'm having trouble going through the documentation because I don't understand how the different pieces fit together. Specifically, what are the roles of the oVirt Node, oVirt Host and oVirt Engine? Thanks

5 5

No option to remove OpenStack Glance storage domain.
by Gary Taylor 22 Mar '21

22 Mar '21

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

1 0

libvirtd.service is down
by jenia.ivlev＠gmail.com 22 Mar '21

22 Mar '21

Hello. I have an error in my oVirt node 4.4: internal error: "Network is already in use by interface ens3" This is the output from journalctl: [root@localhost ~]# sudo journalctl --unit libvirtd.service -- Logs begin at Sun 2021-03-21 16:13:11 UTC, end at Sun 2021-03-21 16:20:37 UTC. -- Mar 21 16:13:24 localhost.localdomain systemd[1]: Starting Virtualization daemon... Mar 21 16:13:25 localhost.localdomain systemd[1]: Started Virtualization daemon. Mar 21 16:13:25 localhost.localdomain libvirtd[1626]: libvirt version: 6.6.0, package: 13.el8 (CBS <cbs(a)centos.org>, 2021-03-01-13:29:02, ) Mar 21 16:13:25 localhost.localdomain libvirtd[1626]: hostname: localhost.localdomain Mar 21 16:13:25 localhost.localdomain libvirtd[1626]: internal error: Network is already in use by interface ens3 Mar 21 16:15:25 localhost.localdomain systemd[1]: libvirtd.service: Succeeded. Mar 21 16:19:30 localhost.localdomain systemd[1]: Starting Virtualization daemon... Mar 21 16:19:30 localhost.localdomain systemd[1]: Started Virtualization daemon. And this is the output from systemctl: [root@localhost ~]# sudo systemctl status libvirtd.service â libvirtd.service - Virtualization daemon Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled; vendor preset: enabled) Drop-In: /etc/systemd/system/libvirtd.service.d ââunlimited-core.conf Active: inactive (dead) since Sun 2021-03-21 16:15:25 UTC; 2min 36s ago Docs: man:libvirtd(8) https://libvirt.org Process: 1626 ExecStart=/usr/sbin/libvirtd $LIBVIRTD_ARGS (code=exited, status=0/SUCCESS) Main PID: 1626 (code=exited, status=0/SUCCESS) Mar 21 16:13:24 localhost.localdomain systemd[1]: Starting Virtualization daemon... Mar 21 16:13:25 localhost.localdomain systemd[1]: Started Virtualization daemon. Mar 21 16:13:25 localhost.localdomain libvirtd[1626]: libvirt version: 6.6.0, package: 13.el8 (CBS <cbs(a)centos.org>, 2021-03-01-13:29:02, ) Mar 21 16:13:25 localhost.localdomain libvirtd[1626]: hostname: localhost.localdomain Mar 21 16:13:25 localhost.localdomain libvirtd[1626]: internal error: Network is already in use by interface ens3 Mar 21 16:15:25 localhost.localdomain systemd[1]: libvirtd.service: Succeeded. I managed to successfully start libvirtd.service by doing systemctl start libvirtd.service but I want to correct this bug somehow. Anyone encountered this before? Thanks

2 1

Re: oVirt process that writes to Gluster mount
by Ben 22 Mar '21

22 Mar '21

Well, I'll be -- you're absolutely right, and I'm a bit embarrassed I didn't consider that before. The node that's not healing shows connections from 2 FUSE clients, which I expect, and 3 glustershd, which I also expect. [root@gluster1 ~]# gluster volume status ssd-san client-list Client connections for volume ssd-san Name count ----- ------ glustershd 3 fuse 2 total clients for volume ssd-san : 5 ----------------------------------------------------------------- But the secondary node, which is constantly healing, *shows that it's missing a FUSE connection*: [root@gluster2 ~]# gluster volume status ssd-san client-list Client connections for volume ssd-san Name count ----- ------ glustershd 3 fuse 1 total clients for volume ssd-san : 4 ----------------------------------------------------------------- I had to restart the glusterd service on node 2 twice before the FUSE client reconnected and stayed connected. Thanks a ton, I really appreciate your help! On Mon, Mar 22, 2021 at 12:37 AM Strahil Nikolov <hunter86_bg(a)yahoo.com> wrote: > Healing must happen only after a maintenance (for example patch + reboot) > on any of the nodes . > Once the node is up , the FUSE client (any host) should reconnect to all > gluster bricks and write to all bricks simultaneously. > > If you got constant healing, this indicates that a client is not writing > to all bricks. > > Check with the following command if there is such client: > 'gluster volume status *VOLNAME* clients' > > > Best Regards, > Strahil Nikolov > > On Mon, Mar 22, 2021 at 3:24, Ben > <gravyfish(a)gmail.com> wrote: > Sorry, just saw this -- I'm not sure I understand what you mean, but in > any case, the healing process does complete when I stop all of my VMs, > which I believe indicates that something about the oVirt writes to Gluster > is causing the problem in the first place. > > On Sun, Mar 14, 2021 at 8:06 AM Strahil Nikolov <hunter86_bg(a)yahoo.com> > wrote: > > Are you sure that gluster volume client's count is the same on all nodes ? > > Best Regards, > Strahil Nikolov > > On Sat, Mar 13, 2021 at 23:58, Ben > <gravyfish(a)gmail.com> wrote: > Hi, I could use some help with a problem I'm having with the Gluster > storage servers I use in my oVirt data center. I first noticed the problem > when files would constantly heal after rebooting one of the Gluster nodes > -- in the replica 2/arbiter, the node that remained online and the arbiter > would begin healing files and never finish. > > I raised the issue with the helpful folks over at Gluster: > https://github.com/gluster/glusterfs/issues/2226 > > The short version is this: after running a tcpdump and noticing malformed > RPC calls to Gluster from one of my oVirt nodes, they're looking for a > stack trace of whatever process is running I/O on the Gluster cluster from > oVirt in order to figure out what it's doing and if the write problems > could cause the indefinite healing I'm seeing. After checking the qemu > PIDs, it doesn't look like they are actually performing the writes -- is > there a particular part of the oVirt stack I can look at to find the write > operations to Gluster? I don't see anything else doing read/write on the VM > image files on the Gluster mount, but I could be missing something. > > NB: I'm using a traditional Gluster setup with the FUSE client, not > hyperconverged. > > Thanks in advance for any assistance. > _______________________________________________ > 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/76H5BY6IH55GC… > >

1 0

oVirt process that writes to Gluster mount
by Ben 22 Mar '21

22 Mar '21

Hi, I could use some help with a problem I'm having with the Gluster storage servers I use in my oVirt data center. I first noticed the problem when files would constantly heal after rebooting one of the Gluster nodes -- in the replica 2/arbiter, the node that remained online and the arbiter would begin healing files and never finish. I raised the issue with the helpful folks over at Gluster: https://github.com/gluster/glusterfs/issues/2226 The short version is this: after running a tcpdump and noticing malformed RPC calls to Gluster from one of my oVirt nodes, they're looking for a stack trace of whatever process is running I/O on the Gluster cluster from oVirt in order to figure out what it's doing and if the write problems could cause the indefinite healing I'm seeing. After checking the qemu PIDs, it doesn't look like they are actually performing the writes -- is there a particular part of the oVirt stack I can look at to find the write operations to Gluster? I don't see anything else doing read/write on the VM image files on the Gluster mount, but I could be missing something. NB: I'm using a traditional Gluster setup with the FUSE client, not hyperconverged. Thanks in advance for any assistance.

1 1

virbr0 down in oVirt node 4.4, cannot connect to console
by jenia.ivlev＠gmail.com 21 Mar '21

21 Mar '21

Hello. I'm trying to deploy a oVirt instance on my computer in a virtual machine. I started off by installing into a VM the oVirt Node 4.4 and I expected to be able to login into the web console from my browser at 192.168.122.1:9090. But instead what I realized is that inside the oVirt Node, the virbr0 interface 192.168.122.1 is down: https://photos.app.goo.gl/gARdRKdfvwDALtEC8 When I tried to bridge the virbr0 interface back up, it says "failed to access /etc/resolve.conf: No such file or directory": https://photos.app.goo.gl/epVqSjPsrN41ZVCZ8 What did I do wrong? Thanks

1 1

oVirt4.4.5 and gluster op-version
by Jiří Sléžka 20 Mar '21

20 Mar '21

Hello, I have just upgraded my 2hosts+1arbiter hci cluster to 4.4.5. Gluster is not managed by oVirt and currently is in op.version 70200 gluster volume get all cluster.op-version cluster.op-version 70200 after gluster upgrade max-op-version is gluster volume get all cluster.max-op-version cluster.max-op-version 80000 can I (or should I) switch to 80000 op-version? Thanks, Jiri

2 2