- Users - oVirt List Archives

oVirt 4.5.6-1.el9 standalone engine - older VM's on centos 6 or rhel 6 hangs on live migration with ovirt node 5.14.0-388.el9.x86_64
by Sumit Basu 01 Jul '24

01 Jul '24

Hi All, In our new oVirt 4.5.6-1.el9 cluster we find older vm's on el6 (centos/rhel) keeps hanging after live migrations. we find this typically with el6 vm's, our other el'7 and windows vm's do not face this issue. All these VM's were imported from an oVirt 4.3.10.4-1.el7 cluster by importing the storage domain into the new cluster. Initially we installed all the latest ovirt-node-ng-installer-latest-el9 on all our nodes(8 of them) and we found this live migration hang issue, later we installed ovirt-node-ng-installer-4.5.2-2022081013.el9 on the nodes and tested - we found the issue resolved and we could migrate the el6 vm's without any issues at all, later, after doing an upgrade on the nodes we find the issue has come back again. The nodes where there are no live migration issues have kernel 5.14.0-142.el9.x86_64, the nodes with the latest version 5.14.0-388.el9.x86_64 seems to have this issue. Has anybody faced this issue? - any patches needed/available? Thanks

1 0

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

Problem importing storage domain from oVirt 4.3.10 to 4.5.5
by Sumit Basu 26 Jun '24

26 Jun '24

Hi, I want to import a FC storage domain from an oVirt 4.3.10 setup to a fresh installed oVirt 4.5.5. I could move domain to maintenance, detach, remove from 4.3.10 and import with activate option to 4.5.5 for one FC LUN fine. When i tried for the second FC lun - during import,activate i get "Error while executing action Attach Storage Domain: Internal Engine Error" and in engine.log i get " Query 'GetUnregisteredDisksQuery' failed: null', and on the standalone engine, i get :- 2024-06-26 07:15:07,277+05 ERROR [org.ovirt.engine.core.bll.storage.domain.AttachStorageDomainToPoolCommand] (default task-102) [] An error occurred while fetching unregistered disks from Storage Domain id 'a5a72b44-f9bc-4e5b-ab43-ca2b1d97b429' 2024-06-26 07:15:07,277+05 ERROR [org.ovirt.engine.core.bll.storage.domain.AttachStorageDomainToPoolCommand] (default task-102) [] Command 'org.ovirt.engine.core.bll.storage.domain.AttachStorageDomainToPoolCommand' failed: Failed to retrieve unregistered disks 2024-06-26 07:15:07,277+05 ERROR [org.ovirt.engine.core.bll.storage.domain.AttachStorageDomainToPoolCommand] (default task-102) [] Exception: java.lang.RuntimeException: Failed to retrieve unregistered disks I have checked using "Scan Disk" on the FC lun before exporting from 4.3.10 and there were no floating disks. I have checked if any of the VM's on the domain have any of their disks on any other storage domain - there are none. On the host used for importing the domain, i get :- 2024-06-26 07:15:04,829+0530 INFO (jsonrpc/5) [storage.hba] Scanning FC devices (hba:42) 2024-06-26 07:15:04,938+0530 INFO (periodic/0) [vdsm.api] START repoStats(domains=()) from=internal, task_id=9f03d412-56a7-4f3f-85b6-c3fd72a68817 (api:31) 2024-06-26 07:15:04,938+0530 INFO (periodic/0) [vdsm.api] FINISH repoStats return={'7c9e748c-442b-48d0-9b35-a769d349c73b': {'code': 0, 'lastCheck': '3.7', 'delay': '0.000974057', 'valid': True, 'version': 0, 'acquired': True, 'actual': True}, 'a589fe14-f40a-4d67-afcd-ec74b07009cf': {'code': 0, 'lastCheck': '3.7', 'delay': '0.000501601', 'valid': True, 'version': 0, 'acquired': True, 'actual': True}, '6b625ecb-1cd1-43c5-b533-32000cd050ec': {'code': 0, 'lastCheck': '3.7', 'delay': '0.000570869', 'valid': True, 'version': 5, 'acquired': True, 'actual': True}} from=internal, task_id=9f03d412-56a7-4f3f-85b6-c3fd72a68817 (api:37) 2024-06-26 07:15:04,968+0530 INFO (jsonrpc/5) [storage.hba] Scanning FC devices: 0.14 seconds (utils:373) 2024-06-26 07:15:04,968+0530 INFO (jsonrpc/5) [storage.multipath] Waiting until multipathd is ready (multipath:95) 2024-06-26 07:15:07,003+0530 INFO (jsonrpc/5) [storage.multipath] Waited 2.04 seconds for multipathd (tries=2, ready=2) (multipath:120) 2024-06-26 07:15:07,003+0530 INFO (jsonrpc/5) [storage.multipath] Resizing multipath devices (multipath:223) 2024-06-26 07:15:07,014+0530 INFO (jsonrpc/5) [storage.multipath] Resizing multipath devices: 0.01 seconds (utils:373) 2024-06-26 07:15:07,014+0530 INFO (jsonrpc/5) [storage.storagedomaincache] Refreshing storage domain cache: 2.60 seconds (utils:373) 2024-06-26 07:15:07,263+0530 INFO (jsonrpc/5) [storage.volumemanifest] Creating image directory '/rhev/data-center/mnt/blockSD/a5a72b44-f9bc-4e5b-ab43-ca2b1d97b429/images/f054c394-2b49-4087-9e9d-0490b23e34e4' (blockVolume:106) 2024-06-26 07:15:07,263+0530 ERROR (jsonrpc/5) [storage.volumemanifest] Unexpected error (blockVolume:110) Traceback (most recent call last): File "/usr/lib/python3.9/site-packages/vdsm/storage/blockVolume.py", line 108, in validateImagePath os.mkdir(imageDir, 0o755) FileNotFoundError: [Errno 2] No such file or directory: '/rhev/data-center/mnt/blockSD/a5a72b44-f9bc-4e5b-ab43-ca2b1d97b429/images/f054c394-2b49-4087-9e9d-0490b23e34e4' 2024-06-26 07:15:07,263+0530 INFO (jsonrpc/5) [vdsm.api] FINISH prepareImage error=Image path does not exist or cannot be accessed/created: ('/rhev/data-center/mnt/blockSD/a5a72b44-f9bc-4e5b-ab43-ca2b1d97b429/images/f054c394-2b49-4087-9e9d-0490b23e34e4',) from=::ffff:10.10.99.100,51116, flow_id=872d7930-e487-4fe4-8e0a-599074105d7b, task_id=523690f8-24b3-4f1f-801e-8391ebb087a2 (api:35) 2024-06-26 07:15:07,263+0530 ERROR (jsonrpc/5) [storage.taskmanager.task] (Task='523690f8-24b3-4f1f-801e-8391ebb087a2') Unexpected error (task:860) Traceback (most recent call last): File "/usr/lib/python3.9/site-packages/vdsm/storage/blockVolume.py", line 108, in validateImagePath os.mkdir(imageDir, 0o755) FileNotFoundError: [Errno 2] No such file or directory: '/rhev/data-center/mnt/blockSD/a5a72b44-f9bc-4e5b-ab43-ca2b1d97b429/images/f054c394-2b49-4087-9e9d-0490b23e34e4' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3.9/site-packages/vdsm/storage/task.py", line 867, in _run return fn(*args, **kargs) File "<decorator-gen-169>", line 2, in prepareImage File "/usr/lib/python3.9/site-packages/vdsm/common/api.py", line 33, in method ret = func(*args, **kwargs) File "/usr/lib/python3.9/site-packages/vdsm/storage/hsm.py", line 2958, in prepareImage legality = dom.produceVolume(imgUUID, volUUID).getLegality() File "/usr/lib/python3.9/site-packages/vdsm/storage/sd.py", line 1188, in produceVolume return self.getVolumeClass()(self.mountpoint, self.sdUUID, imgUUID, File "/usr/lib/python3.9/site-packages/vdsm/storage/volume.py", line 881, in __init__ self._manifest = self.manifestClass(repoPath, sdUUID, imgUUID, volUUID) File "/usr/lib/python3.9/site-packages/vdsm/storage/blockVolume.py", line 40, in __init__ volume.VolumeManifest.__init__(self, repoPath, sdUUID, imgUUID, File "/usr/lib/python3.9/site-packages/vdsm/storage/volume.py", line 67, in __init__ self.validate() File "/usr/lib/python3.9/site-packages/vdsm/storage/blockVolume.py", line 135, in validate volume.VolumeManifest.validate(self) File "/usr/lib/python3.9/site-packages/vdsm/storage/volume.py", line 99, in validate self.validateImagePath() File "/usr/lib/python3.9/site-packages/vdsm/storage/blockVolume.py", line 111, in validateImagePath raise se.ImagePathError(imageDir) vdsm.storage.exception.ImagePathError: Image path does not exist or cannot be accessed/created: ('/rhev/data-center/mnt/blockSD/a5a72b44-f9bc-4e5b-ab43-ca2b1d97b429/images/f054c394-2b49-4087-9e9d-0490b23e34e4',) 2024-06-26 07:15:07,263+0530 INFO (jsonrpc/5) [storage.taskmanager.task] (Task='523690f8-24b3-4f1f-801e-8391ebb087a2') aborting: Task is aborted: "value=Image path does not exist or cannot be accessed/created: ('/rhev/data-center/mnt/blockSD/a5a72b44-f9bc-4e5b-ab43-ca2b1d97b429/images/f054c394-2b49-4087-9e9d-0490b23e34e4',) abortedcode=254" (task:1165) 2024-06-26 07:15:07,264+0530 ERROR (jsonrpc/5) [storage.dispatcher] FINISH prepareImage error=Image path does not exist or cannot be accessed/created: ('/rhev/data-center/mnt/blockSD/a5a72b44-f9bc-4e5b-ab43-ca2b1d97b429/images/f054c394-2b49-4087-9e9d-0490b23e34e4',) (dispatcher:66) 2024-06-26 07:15:07,264+0530 INFO (jsonrpc/5) [jsonrpc.JsonRpcServer] RPC call Image.prepare failed (error 254) in 2.85 seconds (__init__:300) Any help will be useful, we are moving from 4.3.10 on IBM servers and storage to 4.5.5 on DELL servers and storage Regards Sumit Basu

1 0

4.5.4 with Ceph only storage
by Maurice Burrows 25 Jun '24

25 Jun '24

Hey ... A long story short ... I have an existing Red Hat Virt / Gluster hyperconverged solution that I am moving away from. I have an existing Ceph cluster that I primarily use for OpenStack and a small requirement for S3 via RGW. I'm planning to build a new oVirt 4.5.4 cluster on RHEL9 using Ceph for all storage requirements. I've read many online articles on oVirt and Ceph, and they all seem to use the Ceph iSCSI gateway, which is now in maintenance, so I'm not real keen to commit to iSCSI. So my question is, IS there any reason I cannot use CephFS for both hosted-engine and as a data storage domain? I'm currently running Ceph Pacific FWIW. Cheers

5 10

After restoring the failed host and synchronizing the data, it prompts that there are unsynchronized items
by ziyi Liu 25 Jun '24

25 Jun '24

gluster volume info Volume Name: data Type: Replicate Number of Bricks: 1 x (2 + 1) = 3 Bricks: Brick1: node-gfs1:/gluster_bricks/data/data1 Brick2: node-gfs2:/gluster_bricks/data/data1 Brick3: node-gfs3:/gluster_bricks/data/data1 (arbiter) gluster volume heal data info Number of entries: 39 /var/log/glusterfs/glustershd.log The log appears client-rpc-fops_v2.c:785:client4_0_fsync_cbk] 0-data-client-0: remote operation failed. [{errno=5}, {error=Input/output error}] How should I solve these unrepaired entries

2 2