- Users - oVirt List Archives

Major screwup and now I can't bring anything up
by John Florian 02 Feb '24

02 Feb '24

I have a small home oVirt 4.5 deployment that was struggling a bit and I think I've only made things worse. I was seeing some SSL errors in various places but couldn't find any evidence of an expired cert though maybe I overlooked something. At present, it looks like the most immediate problem is that the engine.log is showing SyncNetworkProviderCommand fails saying EngineException: (Failed with error Unsupported or unrecognized SSL message and code 5050). For now, I'm only concerning myself to one Host that had been running VMs until I tried restarting everything from a power off. I take it that the sync failure prevents this Host from becoming active. I had successfully been using this setup for many years. I do have my own web cert on the engine signed by my CA. While I was getting this same "code 5050" error before with things like ovirt-imageio (what prompted my initial digging), now I'm afraid I've only made things more complex. See, I was running FreeIPA on a pair of VMs. In the past, this pair of VMs would auto-start once the oVirt Engine and Hosts were going and I had no issue. But now I wonder to what extent OSCP being unreachable might affect the SSL errors. What's the best/easiest/safest way out of this mess? Should I just wipe ovirt-engine of all the non-rpm provided files in /etc/pki/ovirt-engine/ and redo the engine-setup? I'm afraid of making things worse before I begin attempting that.

2 1

Re: [ovirt-devel] Foreman needs a release of ovirt-engine-sdk-ruby
by Guillaume Pavese 02 Feb '24

02 Feb '24

We were just starting to depend on this workflow... On Fri, Jan 26, 2024 at 2:02 PM Ewoud Kohl van Wijngaarden < ewoud+ovirt(a)kohlvanwijngaarden.nl> wrote: > Hello everyone, > > Foreman is a bit late in updating Ruby to a newer version. Looking ahead > we're aiming at Ruby 3.1+ but ovirt-engine-sdk-ruby doesn't compile on > it. > > https://github.com/oVirt/ovirt-engine-sdk-ruby/pull/3 was merged in > September 2022 and a request to release it was opened a year ago: > https://github.com/oVirt/ovirt-engine-sdk-ruby/issues/4 > > The Foreman community is currently discussing dropping oVirt support: > https://community.theforeman.org/t/proposal-to-drop-support-for-ovirt/36324 > > Is there anyone who can still perform this release, or should we proceed > with removal? > > Regards, > Ewoud Kohl van Wijngaarden > _______________________________________________ > Devel mailing list -- devel(a)ovirt.org > To unsubscribe send an email to devel-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/devel@ovirt.org/message/ESA4LFSQ5JPQW… > -- Ce message et toutes les pièces jointes (ci-après le “message”) sont établis à l’intention exclusive de ses destinataires et sont confidentiels. Si vous recevez ce message par erreur, merci de le détruire et d’en avertir immédiatement l’expéditeur. Toute utilisation de ce message non conforme a sa destination, toute diffusion ou toute publication, totale ou partielle, est interdite, sauf autorisation expresse. L’internet ne permettant pas d’assurer l’intégrité de ce message . Interactiv-group (et ses filiales) décline(nt) toute responsabilité au titre de ce message, dans l’hypothèse ou il aurait été modifié. IT, ES, UK. <https://interactiv-group.com/disclaimer.html>

2 1

onn pv
by Michael Thomas 01 Feb '24

01 Feb '24

I think I may have just messed up my cluster. I'm running an older 4.4.2.6 cluster on CentOS-8 with 4 nodes and a self-hosted engine. I wanted to assemble the spare drives on 3 of the 4 nodes into a new gluster volume for extra VM storage. Unfortunately, I did not look closely enough at one of the nodes before running sfdisk+parted+pvcreate, and now it looks like I may have broken my onn storage. pvs shows missing uuids: # pvs WARNING: Couldn't find device with uuid RgTaWg-fR1T-J3Nv-uh03-ZTi5-jz9X-cjl1lo . WARNING: Couldn't find device with uuid 0l9CFI-Z7pP-x1P8-AJ78-gRoz-ql0e-2gzXsC . WARNING: Couldn't find device with uuid fl73h2-ztyn-y9NY-4TF4-K2Pd-G2Ow-vH46yH . WARNING: VG onn_ovirt1 is missing PV RgTaWg-fR1T-J3Nv-uh03-ZTi5-jz9X-cjl1lo (l ast written to /dev/nvme0n1p3). WARNING: VG onn_ovirt1 is missing PV 0l9CFI-Z7pP-x1P8-AJ78-gRoz-ql0e-2gzXsC (l ast written to /dev/nvme1n1p1). WARNING: VG onn_ovirt1 is missing PV fl73h2-ztyn-y9NY-4TF4-K2Pd-G2Ow-vH46yH (l ast written to /dev/nvme2n1p1). PV VG Fmt Attr PSize PFree /dev/md2 vg00 lvm2 a-- <928.80g 0 /dev/nvme2n1p1 gluster_vg_nvme2n1p1 lvm2 a-- 2.91t 0 /dev/nvme3n1p1 onn_ovirt1 lvm2 a-- 2.91t 0 [unknown] onn_ovirt1 lvm2 a-m 929.92g 100.00g [unknown] onn_ovirt1 lvm2 a-m <931.51g 0 [unknown] onn_ovirt1 lvm2 a-m 2.91t 0 Here's what I don't understand: * This onn volume group only existed on one of the 4 nodes. I expected it would have been on all 4? * lsblk and /etc/fstab don't show any reference to onn * What is the ONN volume group used for, and how bad is it if it's now missing? I note that my VMs all continue to run and I've been able to migrate them off of this affected node with no apparent problems. * Is it possible that this onn volume group was already broken before I messed with the nvme3n1 disk? When ovirt was originally installed several years ago, I went through the install process multiple times and might not have cleaned up properly each time. --Mike

1 0

Shared and local storage, together
by duparchy＠esrf.fr 01 Feb '24

01 Feb '24

HI, We running some VMs from local storage. These are VMs for managing and monitoring tools such as Dell Storage Manager. So we don't want them to be stored in the shared storages they are managing and monitoring.... If something goes wrong on either the storage or the ISCSI network we want those VM to be up and running. Any way to enable both shared storages and some local storage in a cluster ? For the shake of using a host most efficiently and not for only a couple of VMs ?.

1 0

multiple hypervisors with local storage - template distribution
by marek 01 Feb '24

01 Feb '24

hi, i have multiple hypervisors with local storage (every hypervisor has own DC/cluster. storage type = local on host) any tips howto automatically distribute templates between hypervisors? thanks Marek

2 1

Re: Hosted Engine Deploy Failure
by Mihai Puha 31 Jan '24

31 Jan '24

Hello Gary, How did you found that there were 2 engine VMs competing? Mihai,

1 0

Cannot remove Snapshot. The VM is during a backup operation.
by and＠missme.ro 30 Jan '24

30 Jan '24

Hello! Running ovirt Version 4.5.5-1.el8 I had an issue with the iscsi server during the backup and I have two VMs that cannot be backed up anymore by Veeam. In the ovirt event log i have the following errors: Snapshot 'Auto-generated for Backup VM' creation for VM 'dns-a' has been completed. VDSM ovirt1-02 command StartNbdServerVDS failed: Bitmap does not exist: "{'reason': 'Bitmap does not exist in /rhev/data-center/mnt/blockSD/b2fa3469-a380-4180-a89a-43d65085d1b9/images/6a4de98a-b544-4df8-beb1-e560fd61c0e6/cdb26b8b-c447-48de-affa-d7f778aebac7', 'bitmap': '12d2fb20-74da-4e63-b240-f1a42210760c'}" Transfer was stopped by system. Reason: failed to create a signed image ticket. Image Download with disk dns-a_Disk1 was initiated by veeam@internal-authz Image Download with disk dns-a_Disk1 was cancelled. The error on the Veeam backup proxy: dns-a: Unable to create image transfer: Reason: 'Operation Failed', Detail: '[]' When trying to delete the snapshot from the administration interface I receive the following error in the web interface (and nothing gets logged in the event log) Cannot remove Snapshot. The VM is during a backup operation. How should I go about fixing this issue?

2 1

HE Storage Domain Path Config Setting - Where?
by Matthew J Black 30 Jan '24

30 Jan '24

Hey Guys, Quick Q: In which file (on a Hosted-Engine or Hosted-Engine Host) is the configuration for the path to a Storage Domain kept - in particular, the "hosted-engine" Storage Domain? I've got something "funny" going on: the logs (as far as I can see) are reporting that 2 of my 3 HE-Hosts can't connect to the HE Storage Domain (but don't explain why), and the OVE GUI is reporting an "odd" (ie incorrect; non-existent) path to the HE Storage Domain. Via CLI I have confirmed that all three HE Hosts *can* reach (ie have the correct "findmnt" mappings) to the HE Storage Domain's actual file location, and I can't locate the "ghost" HE Storage Domain path or its config setting anywhere - so I don't even know if that's the issue, but I'd like to eliminate it from my trouble-shooting process. Anyway, if someone could get back to me, please, I'd really appreciate it. Cheers Dulux-Oz

2 1

Geo-replication configuration problem
by Ismet Sonmez 28 Jan '24

28 Jan '24

Hello, Newly installed node version 4.5.5 2 clusters and three nodes each every time I try to replicate the geo in cluster 1 it gives an error 3 errors like this: VDSM node4 command UpdateGlusterGeoRepKeysVDS failed: Internal JSON-RPC error: {'cause': 'Attempting to call function: GlusterVolume.geoRepKeysUpdate bound method of object <vdsm.gluster.apiwrapper.GlusterVolume at address 0x7f1524534f28>> with arguments: (\'root\', \'command="/usr/libexec/glusterfs/gsyncd" ssh-rsa AAAAB3N**** \'command="tar ${SSH_ORIGINAL_COMMAND#* }" ssh-rsa AAAA**** \'command="/usr/libexec/glusterfs/gsyncd" ssh-rsa AAAAB3**** \'command="tar ${SSH_ORIGINAL_COMMAND#* }" ssh-rsa AAAA*** \'command="/usr/libexec/glusterfs/gsyncd" ssh-rsa AAAA******* \'command="tar ${SSH_ORIGINAL_COMMAND#* }" ssh-rsa AAAA**** ]) error: bytes-like object required, not \'str\' } I understand that when creating the rsa key, or sending it to the node. How can I solve it?

1 0

Forbid hosts/nodes from assembling a soft-raid that was created inside a VM
by Vladislav Solovei 27 Jan '24

27 Jan '24

When I create a soft-raid (md-raid) inside a virtual machine (yes, sometimes it's necessary to do this to get a disk inside the VM with a capacity of more than 8TB), the host/node detects this array and assembles it automatically. I tried adding the parameter 'raid=noautodetect' to the kernel boot parameters, but it doesn't help. Is it possible to prevent hosts from doing this? :)

1 0