June 2024 - Users - oVirt List Archives

VM Migration Failed
by KSNull Zero 10 Jul '24

10 Jul '24

Running oVirt 4.4.5 VM cannot migrate between hosts. vdsm.log contains the following error: libvirt.libvirtError: operation failed: Failed to connect to remote libvirt URI qemu+tls://ovhost01.local/system: authentication failed: Failed to verify peer's certificate Certificates on hosts was renewed some time ago. How this issue can be fixed ? Thank you.

4 6

problem on dnf update
by g.vasilopoulos＠uoc.gr 09 Jul '24

09 Jul '24

Hi I tried dnf update today and got the error bellow. Is there a solution for this?: [root@*****~]# dnf update Last metadata expiration check: 3:42:36 ago on Mon 17 Jun 2024 08:47:59 AM EEST. Error: Problem 1: package python3-boto3-1.18.58-1.el9s.noarch from @System requires (python3.9dist(botocore) < 1.22 with python3.9dist(botocore) >= 1.21.58), but none of the providers can be installed - cannot install both python3-botocore-1.31.62-1.el9.noarch from appstream and python3-botocore-1.21.58-1.el9s.noarch from @System - cannot install both python3-botocore-1.21.58-1.el9s.noarch from ovirt-master-centos-stream-openstack-yoga-testing and python3-botocore-1.31.62-1.el9.noarch from appstream - cannot install the best update candidate for package python3-botocore-1.21.58-1.el9s.noarch - cannot install the best update candidate for package python3-boto3-1.18.58-1.el9s.noarch Problem 2: package python3-pyngus-2.3.0-8.el9s.noarch from @System requires python3.9dist(python-qpid-proton), but none of the providers can be installed - cannot install both python3-qpid-proton-0.39.0-2.el9s.x86_64 from ovirt-master-centos-stream-opstools-collectd5-testing and python3-qpid-proton-0.35.0-2.el9s.x86_64 from @System - cannot install both python3-qpid-proton-0.35.0-2.el9s.x86_64 from ovirt-master-centos-stream-openstack-yoga-testing and python3-qpid-proton-0.39.0-2.el9s.x86_64 from ovirt-master-centos-stream-opstools-collectd5-testing - cannot install the best update candidate for package python3-qpid-proton-0.35.0-2.el9s.x86_64 - cannot install the best update candidate for package python3-pyngus-2.3.0-8.el9s.noarch Problem 3: package python3-oslo-messaging-12.13.3-1.el9s.noarch from @System requires python3-pyngus, but none of the providers can be installed - package python3-pyngus-2.3.0-8.el9s.noarch from @System requires python3.9dist(python-qpid-proton), but none of the providers can be installed - package python3-pyngus-2.3.0-8.el9s.noarch from ovirt-master-centos-stream-openstack-yoga-testing requires python3.9dist(python-qpid-proton), but none of the providers can be installed - package python3-qpid-proton-0.35.0-2.el9s.x86_64 from @System requires qpid-proton-c(x86-64) = 0.35.0-2.el9s, but none of the providers can be installed - package python3-qpid-proton-0.35.0-2.el9s.x86_64 from ovirt-master-centos-stream-openstack-yoga-testing requires qpid-proton-c(x86-64) = 0.35.0-2.el9s, but none of the providers can be installed - cannot install both qpid-proton-c-0.39.0-2.el9s.x86_64 from ovirt-master-centos-stream-opstools-collectd5-testing and qpid-proton-c-0.35.0-2.el9s.x86_64 from @System - cannot install both qpid-proton-c-0.35.0-2.el9s.x86_64 from ovirt-master-centos-stream-openstack-yoga-testing and qpid-proton-c-0.39.0-2.el9s.x86_64 from ovirt-master-centos-stream-opstools-collectd5-testing - cannot install the best update candidate for package qpid-proton-c-0.35.0-2.el9s.x86_64 - cannot install the best update candidate for package python3-oslo-messaging-12.13.3-1.el9s.noarch (try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)

2 2

Disk blocked
by Louis Barbonnais 03 Jul '24

03 Jul '24

Hello, I apologize, I am new to oVirt and I am lost. I have just installed oVirt on CentOS 9 with local storage. I am trying to add ISO images to my disk, but they are blocked. I cannot delete or unblock them. Could you please assist me?

2 6

Install the oVirt engine on CentOS 9 Stream. However, I encountered an error while enabling the Java package tool, pki-deps, and the PostgreSQL
by Sachendra Shukla 02 Jul '24

02 Jul '24

Hi All, I am trying to install the oVirt engine on CentOS 9 Stream. However, I encountered an error while enabling the Java package tool, pki-deps, and the PostgreSQL module. Below is the error message I received. Could anyone please assist with a resolution for this issue? [image: image.png] -- Regards, *Sachendra Shukla* IT Administrator Yagna iQ, Inc. and subsidiaries Email: Sachendra.shukla(a)yagnaiq.com <dnyanesh.tisge(a)yagnaiq.com> Website: https://yagnaiq.com Privacy Policy: https://www.yagnaiq.com/privacy-policy/ <https://www.linkedin.com/company/yagnaiq/mycompany/> <https://www.youtube.com/channel/UCeHXOpcUxWvOJO0aegD99Jg> This communication and any attachments may contain confidential information and/or Yagna iQ, Inc. copyright material. All unauthorized use, disclosure, or distribution is prohibited. If you are not the intended recipient, please notify Yagna iQ immediately by replying to the email and destroy all copies of this communication. This email has been scanned for all known viruses. The sender does not accept liability for any damage inflicted by viewing the content of this email.

2 1

Any plans on oVirt Major release with new feature?
by De Lee 28 Jun '24

28 Jun '24

Hi, I would like to know if there is any plans for major release with new feature for consider alternative of other hypervisor? I've been using the oracle ovirt for couple of years pretty good one. I would like know the future of oVirt as well along with feature plans.

9 10

How to re-enroll (or renew) host certificates for a single-host hosted-engine deployment?
by Derek Atkins 28 Jun '24

28 Jun '24

Hi, I've got a single-host hosted-engine deployment that I originally installed with 4.0 and have upgraded over the years to 4.3.10. I and some of my users have upgraded remote-viewer and now I get an error when I try to view the console of my VMs: (remote-viewer:8252): Spice-WARNING **: 11:30:41.806: ../subprojects/spice-common/common/ssl_verify.c:477:openssl_verify: Error in server certificate verification: CA signature digest algorithm too weak (num=68:depth0:/O=<My Org Name>/CN=<Host's Name>) I am 99.99% sure this is because the old certs use SHA1. I reran engine-setup on the engine and it asked me if I wanted to renew the PKI, and I answered yes. This replaced many[1] of the certificates in /etc/pki/ovirt-engine/certs on the engine, but it did not update the Host's certificate. All the documentation I've seen says that to refresh this certificate I need to put the host into maintenance mode and then re-enroll.. However I cannot do that, because this is a single-host system so I cannot put the host in local mode -- there is no place to migrate the VMs (let alone the Engine VM). So.... Is there a command-line way to re-enroll manually and update the host certs? Or some other way to get all the leftover certs renewed? Thanks, -derek [1] Not only did it not update the Host's cert, it did not update any of the vmconsole-proxy certs, nor the certs in /etc/pki/ovirt-vmconsole/, and obviously nothing in /etc/pki/ on the host itself. -- Derek Atkins 617-623-3745 derek(a)ihtfp.com www.ihtfp.com Computer and Internet Security Consultant

8 16

python-nmstate 2.2.27 and ovirt network setup
by Bill James 28 Jun '24

28 Jun '24

We have a ovirt-host-4.5.0-3.el9.x86_64 cluster. I just recently ran yum update and it upgraded python-nmstate from python3-libnmstate-2.0.0-2.el9.noarch to python3-libnmstate- 2.2.27-2.el9_4.x86_64. This broken ovirt's ability to update the network config: 2024-06-27 13:22:39,716-07 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.HostSetupNetworksVDSCommand] (EE-ManagedThreadFa ctory-engine-Thread-24) [ea3bc347-156d-4631-a196-c93a9f79c6c1] Command 'HostSetupNetworksVDSCommand(HostName = ovirt-b2n.j2n oc.com, HostSetupNetworksVdsCommandParameters:{hostId='12cd7cbc-0f02-4474-aaa5-b29cde8b56a4', vds='Host[ovirt-b2n.j2noc.com, 12cd7cbc-0f02-4474-aaa5-b29cde8b56a4]', rollbackOnFailure='true', commitOnSuccess='true', connectivityTimeout='120', network s='[HostNetwork:{defaultRoute='true', bonding='false', networkName='ovirtmgmt', vdsmName='ovirtmgmt', nicName='eno12429', vl an='110', vmNetwork='false', stp='false', properties='[]', ipv4BootProtocol='DHCP', ipv4Address='null', ipv4Netmask='null', ipv4Gateway='null', ipv6BootProtocol='NONE', ipv6Address='null', ipv6Prefix='null', ipv6Gateway='null', nameServers='null'}] ', removedNetworks='[]', bonds='[]', removedBonds='[]', clusterSwitchType='LEGACY', managementNetworkChanged='true'})' execu tion failed: VDSGenericException: VDSErrorException: Failed to HostSetupNetworksVDS, error = Internal JSON-RPC error: {'reas on': "[Errno 2] No such file or directory: ' */usr/lib/python3.9/site-packages/libnmstate/VERSION*'"}, code = -32603 that VERSION file, along with many other files, are not in 2.2.27 version of python-nmstate rpm. My fix was to downgrade the rpm. dnf install python3-libnmstate-2.0.0-2.el9.noarch I'm sure that's not the best solution as I can no longer run dnf update. Ideas?

1 0

Re: 4.5.4 Hosted-Engine: change hosted-engine storage
by Novak, Sam 27 Jun '24

27 Jun '24

I'm in the midst of deploying a new EL9 hosted-engine for an existing cluster and it has been an absolute nightmare, and I haven't found any documentation or guidance to account for this type of scenario, which is odd, considering that the EOL for Cent 8 was announced a while ago. I know this is all best effort type work, and I'm very appreciative of that effort, but it's really making me re-think my use case unfortunately. * Sam

1 0

Re: Failed to read or parse '/etc/pki/ovirt-engine/keys/engine.p12'
by Novak, Sam 27 Jun '24

27 Jun '24

Yeah I has to convert all of my P12's to use AES cd /etc/pki/ovirt-engine/keys/ for E in $(ls *.p12); do openssl pkcs12 -in $E -out $E.key -nocerts -nodes -passin file:pass.txt openssl pkcs12 -in $E -out $E.crt -nokeys -nodes -passin file:pass.txt openssl pkcs12 -in ./$E.crt -inkey ./$E.key -export -out $E.test.p12 -keypbe aes-256-cbc -certpbe aes-256-cbc -passin file:pass.txt done You'll also need to make sure you set the file owners and permissions like the original files.

1 0

Re: [ovirt-announce] Re: Reminder: CentOS Stream 8 is now EOL
by Sandro Bonazzola 27 Jun '24

27 Jun '24

Sadly I have no procedure ready for it and no time for working on it. My best advice would be to migrate from a hosted engine on el8 to a stand alone engine on el9 by installing a fresh centos stream 9 engine and re-importing the backup there. Il giorno gio 27 giu 2024 alle ore 12:01 <trockey(a)uw.edu> ha scritto: > Hi Sanbro, > I have 3 production oVirt clusters running and I missed upgrading HE > before May 31, 2024. If I am reading everything that you stated correctly I > will need to point HE CentOS Stream release 8 to vault.centos.org and > then upgrade to CentOS Stream 9. > Do you have the procedures for taking a HE CentOS Stream release 8 pointed > at vault.contos.org and upgrading it to CentOS Stream 9? > _______________________________________________ > Announce mailing list -- announce(a)ovirt.org > To unsubscribe send an email to announce-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/announce@ovirt.org/message/M5HSQFLZLF… > -- Sandro Bonazzola

1 0