- Users - oVirt List Archives

Re: New VM from Template and Storage size
by Nir Soffer 17 Jun '20

17 Jun '20

On Tue, Jun 16, 2020 at 5:32 PM Erez Zarum <erezz(a)nanosek.com> wrote: > > Hey, > > I have created a template that the disk is a thick (raw) with a size of 15GB. > > I am trying to create a VM from that template but having the disk with a much larger size, both template and the VM are set to use thick and I create the new VM with the clone option, so there’s no link between the new VM and the template. > > So far the only solution I managed to find is to adjust the size after creating the VM. This looks like reasonable flow. You create the vm from a template, so you inherit the disk size from the template. Then you modify the disk to the required size. > For example, this situation causes a problematic step when using Foreman/Satelite as trying to provision a VM based on a template but with different size for the OS disk. Why is this problematic? > I assume that one of the ways to solve it is to convert the template somehow into an “image”? like using OpenStack Glance as a place to store “templates” as images? Any other way besides using Glance? If you always need to resize the template, why not create another templated with the right size based on this template? Nir

2 1

Re: oVirt noVNC
by Anton Louw 17 Jun '20

17 Jun '20

Hi Paul, Apologies for the late response. So we only have a cert bundle on the one that is currently not working. The env that is working still has all the default certs. Thanks Anton Louw Cloud Engineer: Storage and Virtualization ______________________________________ D: 087 805 1572 | M: N/A A: Rutherford Estate, 1 Scott Street, Waverley, Johannesburg anton.louw(a)voxtelecom.co.za www.vox.co.za From: Staniforth, Paul <P.Staniforth(a)leedsbeckett.ac.uk> Sent: 12 June 2020 13:13 To: Anton Louw <Anton.Louw(a)voxtelecom.co.za>; users(a)ovirt.org Subject: Re: oVirt noVNC Sorry Anton, I'm trying to get a lot of things sorted before the weekend. This seems the wrong way round, if you follow the documentation you shouldn't have the symbolic link on the working system unless you replaced the file it was pointing to. Do you have certificate bundles for both systems? Regards, Paul S. ________________________________ From: Anton Louw <Anton.Louw(a)voxtelecom.co.za<mailto:Anton.Louw@voxtelecom.co.za>> Sent: 12 June 2020 11:44 To: Staniforth, Paul <P.Staniforth(a)leedsbeckett.ac.uk<mailto:P.Staniforth@leedsbeckett.ac.uk>>; users(a)ovirt.org<mailto:users@ovirt.org> <users(a)ovirt.org<mailto:users@ovirt.org>> Subject: RE: oVirt noVNC Caution External Mail: Do not click any links or open any attachments unless you trust the sender and know that the content is safe. Thanks Paul, So the symbolic link has then been removed, as per the below. Not quite sure where to go from here. 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<mailto:anton.louw@voxtelecom.co.za> A: Rutherford Estate, 1 Scott Street, Waverley, Johannesburg www.vox.co.za<https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.vox.co…> [F]<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.faceb…> [T]<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.twitt…> [I]<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.insta…> [L]<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.linke…> [Y]<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.youtu…> From: Staniforth, Paul <P.Staniforth(a)leedsbeckett.ac.uk<mailto:P.Staniforth@leedsbeckett.ac.uk>> Sent: 12 June 2020 12:30 To: Anton Louw <Anton.Louw(a)voxtelecom.co.za<mailto:Anton.Louw@voxtelecom.co.za>>; users(a)ovirt.org<mailto:users@ovirt.org> Subject: Re: oVirt noVNC Yes Anton, I think it's in the documentation it's Steps 2 & 3 • • The Engine has been configured to use /etc/pki/ovirt-engine/apache-ca.pem, which is symbolically linked to /etc/pki/ovirt-engine/ca.pem. Remove the symbolic link. # rm /etc/pki/ovirt-engine/apache-ca.pem • Save your CA certificate as /etc/pki/ovirt-engine/apache-ca.pem. # cp /tmp/3rd-party-ca-cert.pem /etc/pki/ovirt-engine/apache-ca.pem Regards, Paul S. ________________________________ From: Anton Louw <Anton.Louw(a)voxtelecom.co.za<mailto:Anton.Louw@voxtelecom.co.za>> Sent: 12 June 2020 11:06 To: Staniforth, Paul <P.Staniforth(a)leedsbeckett.ac.uk<mailto:P.Staniforth@leedsbeckett.ac.uk>>; users(a)ovirt.org<mailto:users@ovirt.org> <users(a)ovirt.org<mailto:users@ovirt.org>> Subject: RE: oVirt noVNC Caution External Mail: Do not click any links or open any attachments unless you trust the sender and know that the content is safe. Hi Paul, Double checked the permissions as well. All seems to be fine. The only thing that does look different between the environments are the below: ENV1 (Not working) [cid:image008.png@01D64474.A4312E70] ENV2 (Working) [cid:image009.png@01D64474.A4312E70] It seems that on the working environment, there is a shortcut file (apached-ca.pem) which points to the ca.pem file, but on the environment that is not working, the apache-ca.pem file is not a shortcut. Could this perhaps be an issue? 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<mailto:anton.louw@voxtelecom.co.za> A: Rutherford Estate, 1 Scott Street, Waverley, Johannesburg www.vox.co.za<https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.vox.co…> [F]<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.faceb…> [T]<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.twitt…> [I]<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.insta…> [L]<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.linke…> [Y]<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.youtu…> From: Staniforth, Paul <P.Staniforth(a)leedsbeckett.ac.uk<mailto:P.Staniforth@leedsbeckett.ac.uk>> Sent: 12 June 2020 10:44 To: Anton Louw <Anton.Louw(a)voxtelecom.co.za<mailto:Anton.Louw@voxtelecom.co.za>>; users(a)ovirt.org<mailto:users@ovirt.org> Subject: Re: oVirt noVNC No worries, If all is pointing to the correct files I would check permissions. Regards, Paul S. ________________________________ From: Anton Louw <Anton.Louw(a)voxtelecom.co.za<mailto:Anton.Louw@voxtelecom.co.za>> Sent: 12 June 2020 09:34 To: Staniforth, Paul <P.Staniforth(a)leedsbeckett.ac.uk<mailto:P.Staniforth@leedsbeckett.ac.uk>>; users(a)ovirt.org<mailto:users@ovirt.org> <users(a)ovirt.org<mailto:users@ovirt.org>> Subject: RE: oVirt noVNC Caution External Mail: Do not click any links or open any attachments unless you trust the sender and know that the content is safe. Hi Paul, Thanks for the reply. Apologies, I should have added that I have installed our own certificates. The main problem I am facing is that the noVNC console just refuses to open, I get the attached error with any VM I try and access. I should have perhaps started with this issue in my first mail, apologies 😊 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<mailto:anton.louw@voxtelecom.co.za> A: Rutherford Estate, 1 Scott Street, Waverley, Johannesburg www.vox.co.za<https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.vox.co…> [F]<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.faceb…> [T]<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.twitt…> [I]<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.insta…> [L]<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.linke…> [Y]<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.youtu…> From: Staniforth, Paul <P.Staniforth(a)leedsbeckett.ac.uk<mailto:P.Staniforth@leedsbeckett.ac.uk>> Sent: 12 June 2020 10:29 To: users(a)ovirt.org<mailto:users@ovirt.org>; Anton Louw <Anton.Louw(a)voxtelecom.co.za<mailto:Anton.Louw@voxtelecom.co.za>> Subject: Re: oVirt noVNC Hello Anton, if your organisation has it's own CA you can install your own certificates or get certificates from a trusted CA. https://www.ovirt.org/documentation/admin-guide/appe-oVirt_and_SSL.html<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt…> Paul S. ________________________________ From: Anton Louw via Users <users(a)ovirt.org<mailto:users@ovirt.org>> Sent: 12 June 2020 08:56 To: users(a)ovirt.org<mailto:users@ovirt.org> <users(a)ovirt.org<mailto:users@ovirt.org>> Subject: [ovirt-users] oVirt noVNC Caution External Mail: Do not click any links or open any attachments unless you trust the sender and know that the content is safe. Hi Everybody, With regards to noVNC, is it a requirement to install the CA into your local browser? I would like users to access their VM console, but with no additional work from their side, ie. Downloading the CA and importing it. Thank you 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<mailto:anton.louw@voxtelecom.co.za> A: Rutherford Estate, 1 Scott Street, Waverley, Johannesburg www.vox.co.za<https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.vox.co…> [F]<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.faceb…> [T]<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.twitt…> [I]<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.insta…> [L]<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.linke…> [Y]<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.youtu…> [#VoxBrand]<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.vox.c…> 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://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.voxte…>. To view the terms under which this email is distributed, please go to:- http://leedsbeckett.ac.uk/disclaimer/email/<http://leedsbeckett.ac.uk/disclaimer/email/> To view the terms under which this email is distributed, please go to:- http://leedsbeckett.ac.uk/disclaimer/email/<http://leedsbeckett.ac.uk/disclaimer/email/> To view the terms under which this email is distributed, please go to:- http://leedsbeckett.ac.uk/disclaimer/email/<http://leedsbeckett.ac.uk/disclaimer/email/> To view the terms under which this email is distributed, please go to:- http://leedsbeckett.ac.uk/disclaimer/email/<http://leedsbeckett.ac.uk/disclaimer/email/>

1 0

help: renamed master volume
by Philip Brown 16 Jun '20

16 Jun '20

Im pretty new to ovirt. Trying to upgrade an old install from 4.1 to 4.3 on the way, I browsed into the Storage area, in one of the nodes. Noticed under the "Volume groups", area that the volumes were named after some loong ID string. Saw there was a "rename" button. figured it would be just like renaming a VM. thigns would just get auto adjusted. but after I renamed to something in english, the cluster is freaking out, "cant find master domain: u'spUUID=xxxxxxx, msdUUID=xxxxxxx' " and under Storage: Storage DOmains, the Data(Master) is down. How can I recover from this ASAP? :-(

2 4

New VM from Template and Storage size
by Erez Zarum 16 Jun '20

16 Jun '20

Hey, I have created a template that the disk is a thick (raw) with a size of 15GB. I am trying to create a VM from that template but having the disk with a much larger size, both template and the VM are set to use thick and I create the new VM with the clone option, so there’s no link between the new VM and the template. So far the only solution I managed to find is to adjust the size after creating the VM. For example, this situation causes a problematic step when using Foreman/Satelite as trying to provision a VM based on a template but with different size for the OS disk. I assume that one of the ways to solve it is to convert the template somehow into an “image”? like using OpenStack Glance as a place to store “templates” as images? Any other way besides using Glance? Thanks!

1 0

oVirt 4.4 Self-hosted Engine and Intel Skylake CPUs
by Erez Zarum 16 Jun '20

16 Jun '20

Hey, I was trying to install oVirt with SE on a node that has Intel Skylake CPU (Intel Xeon Gold 6238R CPU to be precise) which by Intel supports TSX. When the SE was provisioned as a local VM all was working well, it was using a different CPU type for local provisioning. After the local SE VM was migrated to the shared Storage (iSCSI) and was configured, it failed to start. When checking the XML (and vm.conf) that was created and provided to libvirt I noticed it uses the "Secure Intel Skylake" type CPU with +tsx-ctrl as a required flag. My assumption as this is a fresh install of oVirt with SE is that the newly created Cluster was set to this CPU compatibility. This specific CPU by Intel does not expose any tsx flags, while it does indeed support TSX libvirt has no way of knowing it, more strange, some other CPUs from that same range/models do expose the tsx flag. I have tried to set the kernel cmdline to tsx=yes|auto|off and none of those helped. The quick solution was to start the engine manually by editing the XML file (hosted-engine --vm-shutdown and then start it with libvirt) and change the Cluster CPU type and the HostedEngine CPU type as well to "Intel Skylake" and then start it (hosted-engine --vm-start) Another solution which i haven't tried is to get the correct string from the oVirt-Engine API of the non-secure Intel Skylake CPU and hardcode it into the cpu_model fact in the SE ansible role (task). At the end i opted not to try any workaround and decided to go on with oVirt 4.3 which went smooth, it chose "Intel Skylake Server IBRS SSBD MDS Family" as the Cluster CPU compatibility and installation went without any errors/issues. 1) What will happen if i decide to upgrade to 4.4? I will first have to reinstall a node with CentOS 8 and then migrate the HostedEngine to there as well, will it keep the current cluster CPU type or will it try to upgrade and these fail the upgrade? 2) Are you aware of this situation? I understand this is a new solution because you had to update everytime the CPU databases but on the other hand, Intel is not helping here by not being strict about exposing the tsx flags, perhaps the best will be to let the user chose which CPU type use on the first Cluster created by the SE ansible role? (As far as i remember, this was available in the previous versions of oVirt) Thanks!

2 2

oVirt-4.4 on CetOS 8.2
by Dominik Holler 16 Jun '20

16 Jun '20

Hello, CentOS 8.2 was released before oVirt was prepared for CentOS 8.2 . Currently oVirt-4.4 fails to install on CentOS 8.2 . This will be fixed soon. Dominik

2 2

Continuing HE install from lost connection
by Glenn Marcy 16 Jun '20

16 Jun '20

I ran the Prepare VM stage of the GUI HostedEngine install and when I came back it had disconnected. Looking at the logs and the current status everything appears to be just fine, but there doesn't seem to be any way in the GUI to continue where it left off. I was wondering if there was some way to provide the hosted_storage information requested in the next panel and complete the installation, perhaps with the command line, instead of redoing all of the work that has already been completed successfully? Regards, Glenn Marcy

2 1

Advise Needed - Hosted Engine Minor Update
by jrbdeguzman05＠gmail.com 16 Jun '20

16 Jun '20

Hi Guys! How do you usually backup your hosted engine prior minor updates? I’ve tried to perform a minor update from 4.3.8 to 4.3.9 recently. I’ve used engine-backup before updating and for restore. However, the problem I’m encountering now is that, it looks like the hosted-engine settings are only being restored. The version is still 4.3.9 when I’m trying to revert it to 4.3.8. Am I missing some steps aside from engine-backup —restore? I saw on old posts that snapshots of hosted engine is not a recommended step before upgrade/update. Appreciate your help in advance!

3 3

LDAP setup fails on 4.4 reading PEM file
by Stack Korora 15 Jun '20

15 Jun '20

Greetings, I'm having some issues getting LDAP working on CentOS 8 with oVirt 4.4. I would appreciate some help please. When I run ovirt-engine-extension-aaa-ldap-setup I choose "11 - RFC-2307 Schema (Generic)" because that's what my LDAP guy said I should do. :-) Next I select the default Yes for "Use DNS". I select 4 for "Failover between multiple hosts". I put in my two hosts "svr1.my.domain srv2.my.domain". To select the protocol I type "ldaps". To select the method to obtain the PEM I type "File". Then the "File path". A full path to the file. Not quoted. Yes, I checked that I typed it correct. I can copy-paste into "ls" and it's fine with the correct read permissions and everything. (I can't copy paste into the script but that's another issue.) It immediately fails with: [ ERROR ] Failed to execute stage 'Environment customization': a byte-like object is required, not 'str' There is a log file, here is the snippet at the point it goes wrong. 2020-06-11 11:35:49,915-0500 DEBUG otopi.plugins.otopi.dialog.human dialog.__logString:204 DIALOG:SEND File path: 2020-06-11 11:36:24,373-0500 DEBUG otopi.plugins.otopi.dialog.human dialog.__logString:204 DIALOG:RECEIVE /etc/pki/ca-trust/source/anchors/Infrastructure.pem 2020-06-11 11:36:24,375-0500 DEBUG otopi.context context._executeMethod:145 method exception Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/otopi/context.py", line 132, in _executeMethod method['method']() File "/usr/share/ovirt-engine-extension-aaa-ldap/setup/bin/../plugins/ovirt-engine-extension-aaa-ldap/ldap/common.py", line 781, in _customization_late cacert, cacertfile, insecure = self._getCACert() File "/usr/share/ovirt-engine-extension-aaa-ldap/setup/bin/../plugins/ovirt-engine-extension-aaa-ldap/ldap/common.py", line 357, in _getCACert _cacertfile.write('\n'.join(cacert) + '\n') File "/usr/lib64/python3.6/tempfile.py", line 485, in func_wrapper return func(*args, **kwargs) TypeError: a bytes-like object is required, not 'str' 2020-06-11 11:36:24,376-0500 ERROR otopi.context context._executeMethod:154 Failed to execute stage 'Environment customization': a bytes-like object is required, not 'str' 2020-06-11 11:36:24,376-0500 DEBUG otopi.context context.dumpEnvironment:765 ENVIRONMENT DUMP - BEGIN 2020-06-11 11:36:24,376-0500 DEBUG otopi.context context.dumpEnvironment:775 ENV BASE/error=bool:'True' 2020-06-11 11:36:24,376-0500 DEBUG otopi.context context.dumpEnvironment:775 ENV BASE/exceptionInfo=list:'[(<class 'TypeError'>, TypeError("a bytes-like object is required, not 'str'",), <traceback object at 0x7f7e053a4448>)]' 2020-06-11 11:36:24,377-0500 DEBUG otopi.context context.dumpEnvironment:775 ENV OVAAALDAP_LDAP/hosts=str:'svr1.my.domain srv2.my.domain' 2020-06-11 11:36:24,377-0500 DEBUG otopi.context context.dumpEnvironment:775 ENV OVAAALDAP_LDAP/protocol=str:'ldaps' 2020-06-11 11:36:24,377-0500 DEBUG otopi.context context.dumpEnvironment:775 ENV OVAAALDAP_LDAP/serverset=str:'failover' 2020-06-11 11:36:24,377-0500 DEBUG otopi.context context.dumpEnvironment:775 ENV OVAAALDAP_LDAP/useDNS=bool:'True' 2020-06-11 11:36:24,378-0500 DEBUG otopi.context context.dumpEnvironment:775 ENV QUESTION/1/OVAAALDAP_LDAP_CACERT_FILE=str:'/etc/pki/ca-trust/source/anchors/Infrastructure.pem' 2020-06-11 11:36:24,378-0500 DEBUG otopi.context context.dumpEnvironment:775 ENV QUESTION/1/OVAAALDAP_LDAP_CACERT_METHOD=str:'file' 2020-06-11 11:36:24,378-0500 DEBUG otopi.context context.dumpEnvironment:775 ENV QUESTION/1/OVAAALDAP_LDAP_PROTOCOL=str:'ldaps' 2020-06-11 11:36:24,378-0500 DEBUG otopi.context context.dumpEnvironment:775 ENV QUESTION/1/OVAAALDAP_LDAP_SERVERSET=str:'4' 2020-06-11 11:36:24,378-0500 DEBUG otopi.context context.dumpEnvironment:775 ENV QUESTION/1/OVAAALDAP_LDAP_USE_DNS=str:'yes' 2020-06-11 11:36:24,378-0500 DEBUG otopi.context context.dumpEnvironment:775 ENV QUESTION/2/OVAAALDAP_LDAP_SERVERSET=str:'svr1.my.domain srv2.my.domain' 2020-06-11 11:36:24,378-0500 DEBUG otopi.context context.dumpEnvironment:779 ENVIRONMENT DUMP - END Can someone help please? Thanks!

2 4

It looks like big changes are happening, Centos moving from 8.1.1911 to 8.2.2004 perhaps
by Glenn Marcy 15 Jun '20

15 Jun '20

I hope this situation settles down before rc5 trying to run 4.4.1-rc4 hosted engine setup, got [ ERROR ] fatal: [localhost -> ovirt-engine.example.com] FAILED! => {"changed": false, "failures": [], "msg": "Depsolve Error occured: Problem: package ovirt-engine-4.4.1.3-1.el8.noarch requires ovirt-provider-ovn >= 1.2.1, but none of the providers can be installed - package ovirt-provider-ovn-1.2.30-1.el8.noarch requires openvswitch >= 2.7, but none of the providers can be installed - cannot install the best candidate for the job - nothing provides librte_bitratestats.so.2()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_bus_pci.so.2()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_bus_vdev.so.2()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_bus_vmbus.so.2()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_cmdline.so.2()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_common_cpt.so.1()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_eal.so.9()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_eal.so.9(DPDK_17.08)(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_eal.so.9(DPDK_18.11)(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_eal.so.9(DPDK_2.0)(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_ethdev.so.11()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_ethdev.so.11(DPDK_16.07)(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_ethdev.so.11(DPDK_17.05)(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_ethdev.so.11(DPDK_18.05)(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_ethdev.so.11(DPDK_18.08)(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_ethdev.so.11(DPDK_18.11)(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_ethdev.so.11(DPDK_2.2)(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_gro.so.1()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_gso.so.1()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_hash.so.2()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_ip_frag.so.1()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_kvargs.so.1()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_latencystats.so.1()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_mbuf.so.4()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_mbuf.so.4(DPDK_2.1)(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_member.so.1()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_mempool.so.5()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_mempool.so.5(DPDK_16.07)(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_mempool.so.5(DPDK_2.0)(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_mempool_bucket.so.1()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_mempool_ring.so.1()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_mempool_stack.so.1()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_meter.so.2()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_meter.so.2(DPDK_18.08)(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_meter.so.2(DPDK_2.0)(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_metrics.so.1()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_net.so.1()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_pci.so.1()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_pdump.so.2()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_pmd_bnxt.so.2()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_pmd_e1000.so.1()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_pmd_enic.so.1()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_pmd_failsafe.so.1()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_pmd_i40e.so.2()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_pmd_ixgbe.so.2()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_pmd_mlx4.so.1()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_pmd_mlx5.so.1()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_pmd_netvsc.so.1()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_pmd_nfp.so.1()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_pmd_qede.so.1()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_pmd_ring.so.2()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_pmd_ring.so.2(DPDK_2.0)(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_pmd_tap.so.1()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_pmd_vdev_netvsc.so.1()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_pmd_vhost.so.2()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_pmd_virtio.so.1()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_ring.so.2()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_ring.so.2(DPDK_2.0)(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_vhost.so.4()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_vhost.so.4(DPDK_16.07)(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_vhost.so.4(DPDK_17.05)(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_vhost.so.4(DPDK_17.08)(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_vhost.so.4(DPDK_2.0)(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_vhost.so.4(DPDK_2.1)(64bit) needed by openvswitch-2.11.1-5.el8.x86_64", "rc": 1, "results": []}

2 1