- Users - oVirt List Archives

oVirt 4.5.5 - Prb with qemu-kvm after upgrade
by Christophe GRENIER 02 Feb '24

02 Feb '24

Hello I have a standalone oVirt Manager 4.5.5-1.el8 and two small clusters. After upgrading ovir01001 in the "PreProd" cluster from AlmaLinux 8.8 to 8.9, the host was successfully activated but failed to take any VM. centos-release-ceph-pacific.noarch 1.0-2.el8 @cs8-extras centos-release-gluster10.noarch 1.0-1.el8s @cs8-extras-common centos-release-nfv-common.noarch 1-3.el8 @cs8-extras centos-release-nfv-openvswitch.noarch 1-3.el8 @cs8-extras centos-release-opstools.noarch 1-12.el8 @cs8-extras centos-release-ovirt45.noarch 8.9-1.el8s @cs8-extras-common centos-release-storage-common.noarch 2-2.el8 @cs8-extras centos-release-stream.x86_64 8.1-1.1911.0.7.el8 @cs8-extras centos-release-virt-common.noarch 1-2.el8 @cs8-extras vdsm.x86_64 4.50.5.1-1.el8 @centos-ovirt45 The problem has been "solved" by downgrading all qemu-* packages to the version in AlmaLinux 8.8 ie. qemu-kvm-6.2.0-40.module_el8.9.0+3681+41cbbcc0.1.alma.1 => qemu-kvm-6.2.0-33.module_el8.8.0+3612+f18d2b89.alma.1.x86_64 Please find the relevent log: - engine_when_failed.log https://pastebin.com/7MG6fYGY - engine_when_ok.log https://pastebin.com/MegqmMbg - vdsm_when_failed.log https://pastebin.com/ae4w0pix - vdsm_when_ok.log https://pastebin.com/d7P0BWDN Has someone tried to update to 8.9 ? Regards -- ,-~~-.___. ._. / | ' \ | |--------. Christophe GRENIER ( ) 0 | | | grenier(a)cgsecurity.org \_/-, ,----' | | | ==== !_!-v---v--. / \-'~; .--------. TestDisk & PhotoRec / __/~| ._-""|| | Data Recovery =( _____|_|____||________| https://www.cgsecurity.org

1 0

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

Low confirmed free space on gluster volume
by Jonas 27 Jan '24

27 Jan '24

Hello list I am regularly getting the following error on a Gluster volume hosted on a three node hyperconverged oVirt-Cluster: Warning! Low confirmed free space on gluster volume tier1-owncloud-users-01 This volume is configured with 3TiB (2.5TIB used) and is used as the name implies to store data of an ownCloud instance. It is not used as a storage domain in oVirt. I don't really want to resize the volume just to make the warning go away. While clicking through the oVirt web interface i found the configuration "Warning Low Confirmed Space Indicator" in the advanced parameters of the storage domains but did not find any similar setting in the configuration of the gluster volumes. Do you know of way to configure this setting for a gluster volume which is not used as a storage domain? Thank you Jonas

1 0

Change Hosted Engine VM MAC address
by Sergei Panchenko 26 Jan '24

26 Jan '24

Good morning, colleagues! Due some network issues I need to change HostedEngine VM MAC address. The additional diffeculty is unaccessebility of the HE Web-interface via the network (the cause of - those network issues -)). Is there any way to change the HE vNIC's MAC using command line (on the host where HE VM works or on the HE VM)? Thanks in advance, Sergei.

2 2

Need help again, new issue with VM import
by Michaal R 24 Jan '24

24 Jan '24

I have a VM that's a little over 4TB in size that won't import for whatever reason. I've tried changing the export from the streaming disk format to a flat vmdk,thinking that might be it, but it didn't work. I've gone through the OVF and don't see anything that stands out. Same for the logs, I see where it's having issues importing the 4TB drive from the VM, but I can't decipher the error messages well enough to know how to fix it. The drives had chkdsk run on them before they were exported, and the VM was cleanly shut down, so I don't understand what the issue is. Not even sure at this point how to run a filesystem repair on the vmdk, in case the export corrupted something. And I can't export it directly from ESXi either, for some reason. Each attempt fails with an unspecified error. Below is a snip from the import log where it's reading the drives. It has one of the first errors: [ 2.492229] scsi host0: Virtio SCSI HBA [ 2.501365] scsi 0:0:0:0: Direct-Access QEMU QEMU HARDDISK 2.5+ PQ: 0 ANSI: 5 [ 2.504080] scsi 0:0:1:0: Direct-Access QEMU QEMU HARDDISK 2.5+ PQ: 0 ANSI: 5 [ 2.506035] scsi 0:0:2:0: Direct-Access QEMU QEMU HARDDISK 2.5+ PQ: 0 ANSI: 5 [ 2.540737] sd 0:0:0:0: Power-on or device reset occurred [ 2.540790] sd 0:0:1:0: Power-on or device reset occurred [ 2.540899] sd 0:0:2:0: Power-on or device reset occurred [ 2.541130] sd 0:0:0:0: [sda] 8589934592 512-byte logical blocks: (4.40 TB/4.00 TiB) [ 2.541168] sd 0:0:2:0: [sdc] 8388608 512-byte logical blocks: (4.29 GB/4.00 GiB) [ 2.541319] sd 0:0:2:0: [sdc] Write Protect is off [ 2.541391] sd 0:0:0:0: [sda] Write Protect is off [ 2.541592] sd 0:0:2:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 2.542019] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 2.544060] sd 0:0:2:0: [sdc] Attached SCSI disk [ 2.545294] sd 0:0:1:0: [sdb] 251658240 512-byte logical blocks: (129 GB/120 GiB) [ 2.545437] sd 0:0:1:0: [sdb] Write Protect is off [ 2.545966] sd 0:0:1:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 2.551250] sdb: sdb1 sdb2 [ 2.556698] sd 0:0:1:0qemu-nbd: Disconnect client, due to: Failed to send reply: reading from file failed: Invalid argument : [sdb] Attached SCSI disk qemu-nbd: Disconnect client, due to: Failed to send reply: reading from file failed: Invalid argument qemu-nbd: Disconnect client, due to: Failed to send reply: reading from file failed: Invalid argument [ 2.618883] sd 0:0:0:0: [sda] tag#157 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s [ 2.618890] sd 0:0:0:0: [sda] tag#157 Sense Key : Aborted Command [current] [ 2.618892] sd 0:0:0:0: [sda] tag#157 Add. Sense: I/O process terminated [ 2.618894] sd 0:0:0:0: [sda] tag#157 CDB: Read(16) 88 00 00 00 00 01 ff ff ff f8 00 00 00 08 00 00 [ 2.618897] I/O error, dev sda, sector 8589934584 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 supermin: intern[ 2.618902] Buffer I/O error on dev sda, logical block 1073741823, async page read al insmod virtio[ 2.618927] Alternate GPT is invalid, using primary GPT. The rest of the log is peppered with Buffer I/O error entries on /dev/sda (the 4TB vmdk). Could someone please help? I think I've been looking at these logs and trying to fix the drive for so long I've gone logic blind and can't see the answer right in front of my eyes. Here's a link to the logs pulled from the host: https://www.dropbox.com/scl/fi/570t279s0k3pfgafuvv01/felicity-import-1.18.2…

1 0

Re: [External] : Re: can hosted engine deploy use local repository mirrors instead of internet ones?
by iucounu＠gmail.com 24 Jan '24

24 Jan '24

Hi Marcos, > > The dnsmasq service running on the KVM host manages the IP assignment during the first > deployment phase. > How did you deploy your KVM host? Which configurations have you done on it before running > the hosted-engine --deploy? > Also, what is your full hosted-engine deployment command? > I deployed the KVM hosts using the guide at: https://www.ovirt.org/documentation/installing_ovirt_as_a_self-hosted_engin… (section 4.2 Installing Enterprise Linux Hosts) and https://www.ovirt.org/download/install_on_rhel.html Most of the ovirt packages were installed from the installation of the ovirt-engine-appliance. The KVM hosts are using EL 9.3. I've tried on two different EL hosts: one with the standard ovirt-45 repos, and the other had the nightly builds enabled. I observed the same issues on both. I haven't changed any specific settings, such as networking or storage. The full command to deploy the engine VM was done via: hosted-engine --deploy --4 I have just setup glusterfs just as a temporary storage option now (yet to run the deploy again), though I'm not sure how to get ovirt to use it. As mentioned I don't know whether this or the networking is causing it to fail. In case it is important, I notice that virtnetworkd.socket systemd unit gets killed during the deployment, and has to be restarted otherwise the deployment fails prematurely. It also masks all the libvirtd systemd units as part of the cleanup, and these have to manually unmasked and several need manually restarting (virtnetword.socket, virtqemud.socket and virtstoraged.sock) before the deployment is run again or the deploy will fail on trying to communicate with these. Thanks very much for the help, let me know if any further information needed. Cam > > -----Original Message----- > From: iucounu(a)gmail.com <iucounu(a)gmail.com> > Sent: Tuesday, January 23, 2024 12:49 PM > To: users(a)ovirt.org > Subject: [ovirt-users] Re: [External] : Re: can hosted engine deploy use local repository > mirrors instead of internet ones? > > Thanks very for the reply Marcos. I tried another deployment, just to see if "wait > for the host to be up" would time out, and I saw a couple of errors in the log: > > From the ovirt-hosted-engine-setup-ansible-final_clean log, it mentions that the VM IP is > undefined: > > 2024-01-23 12:50:19,554+0000 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils > ansible_utils._process_output:109 {'msg': "The task includes an option with > an undefined variable. The error was: 'local_vm_ip' is undefined. > 'local_vm_ip' is undefined\n\nThe error appears to be in > '/usr/share/ansible/collections/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/sync_on_engine_machine.yml': > line 2, column 3, but may\nbe elsewhere in the file depending on the exact syntax > problem.\n\nThe offending line appears to be:\n\n---\n- name: Set the name for add_host\n > ^ here\n", '_ansible_no_log': False} > > In the ovirt-hosted-engine-setuplog, it mentions not being able to get the storage pool: > > > 2024-01-23 12:50:35,787+0000 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils > ansible_utils._process_output:109 {'changed': True, 'stdout': '', > 'stderr': "error: failed to get pool 'localvmvy8whst5'\nerror: > Storage pool not found: no storage pool with matching name > 'localvmvy8whst5'", 'rc': 1, 'cmd': ['virsh', > '-c', 'qemu:///system?authfile=/etc/ovirt-hosted-engine/virsh_auth.conf', > 'pool-destroy', 'localvmvy8whst5'], 'start': '2024-01-23 > 12:50:35.558666', 'end': '2024-01-23 12:50:35.611808', > 'delta': '0:00:00.053142', 'msg': 'non-zero return code', > 'invocation': {'module_args': {'_raw_params': 'virsh -c > qemu:///system?authfile=/etc/ovirt-hosted-engine/virsh_auth.conf pool-destroy > localvmvy8whst5', '_uses_shell': False, 'stdin_add_newline': True, > 'strip_empty_ends': True, 'argv': None, 'chdir': None, > 'executable': None, 'creates': None, 'removes': None, > 'stdin': None}}, 'stdout_lines': [], 'stderr_lines': ["error: > failed to get pool 'localvmvy8whst5'", "error: Storage pool not fou > nd: no storage pool with matching name 'localvmvy8whst5'"], > '_ansible_no_log': None} > > I set the IP to the one I have assigned in DNS, but when I attach to the console of the VM > (which is still running, though the disk image has been deleted) via virsh, it shows me a > completely different IP: In hosted-engine --deploy, I set a 10.0.0.x address, however, it > shows a 192.168.1.x address on the VM. Do I need to set this somewhere else, e.g., with > '--ansible-extra-vars=he_ipv4_subnet_prefix='? > > As for the storage pool, is that for later VM deployment? The deploy script did not ask me > for a storage location. If I need to specify this, where do I do this? > > Thanks again for any help, > > Kind regards, > > Cam > > PS: is there a simple way to have the answers saved so I don't have to keep running > through all the questions every time I try a deployment > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org Privacy Statement: > https://urldefense.com/v3/__https://www.ovirt.org/privacy-policy.html__;!... > oVirt Code of Conduct: > https://urldefense.com/v3/__https://www.ovirt.org/community/about/communi... > List Archives: > https://urldefense.com/v3/__https://lists.ovirt.org/archives/list/users@o...

1 0

Re: [External] : Re: can hosted engine deploy use local repository mirrors instead of internet ones?
by iucounu＠gmail.com 24 Jan '24

24 Jan '24

Thanks very for the reply Marcos. I tried another deployment, just to see if "wait for the host to be up" would time out, and I saw a couple of errors in the log: From the ovirt-hosted-engine-setup-ansible-final_clean log, it mentions that the VM IP is undefined: 2024-01-23 12:50:19,554+0000 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:109 {'msg': "The task includes an option with an undefined variable. The error was: 'local_vm_ip' is undefined. 'local_vm_ip' is undefined\n\nThe error appears to be in '/usr/share/ansible/collections/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/sync_on_engine_machine.yml': line 2, column 3, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n---\n- name: Set the name for add_host\n ^ here\n", '_ansible_no_log': False} In the ovirt-hosted-engine-setuplog, it mentions not being able to get the storage pool: 2024-01-23 12:50:35,787+0000 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:109 {'changed': True, 'stdout': '', 'stderr': "error: failed to get pool 'localvmvy8whst5'\nerror: Storage pool not found: no storage pool with matching name 'localvmvy8whst5'", 'rc': 1, 'cmd': ['virsh', '-c', 'qemu:///system?authfile=/etc/ovirt-hosted-engine/virsh_auth.conf', 'pool-destroy', 'localvmvy8whst5'], 'start': '2024-01-23 12:50:35.558666', 'end': '2024-01-23 12:50:35.611808', 'delta': '0:00:00.053142', 'msg': 'non-zero return code', 'invocation': {'module_args': {'_raw_params': 'virsh -c qemu:///system?authfile=/etc/ovirt-hosted-engine/virsh_auth.conf pool-destroy localvmvy8whst5', '_uses_shell': False, 'stdin_add_newline': True, 'strip_empty_ends': True, 'argv': None, 'chdir': None, 'executable': None, 'creates': None, 'removes': None, 'stdin': None}}, 'stdout_lines': [], 'stderr_lines': ["error: failed to get pool 'localvmvy8whst5'", "error: Storage pool not fou nd: no storage pool with matching name 'localvmvy8whst5'"], '_ansible_no_log': None} I set the IP to the one I have assigned in DNS, but when I attach to the console of the VM (which is still running, though the disk image has been deleted) via virsh, it shows me a completely different IP: In hosted-engine --deploy, I set a 10.0.0.x address, however, it shows a 192.168.1.x address on the VM. Do I need to set this somewhere else, e.g., with '--ansible-extra-vars=he_ipv4_subnet_prefix='? As for the storage pool, is that for later VM deployment? The deploy script did not ask me for a storage location. If I need to specify this, where do I do this? Thanks again for any help, Kind regards, Cam PS: is there a simple way to have the answers saved so I don't have to keep running through all the questions every time I try a deployment

2 1

Apple Mac Pro 2013 install hangs with oVirt Node installer 4.5 but ok with 4.3.10
by john＠alwayson.net.au 24 Jan '24

24 Jan '24

This hardware (6 Core Xeon E5-1650v2) successfully runs Fedora 39 and oVirt 4.3.10 (CentOS 7) but freezes immediately when attempting to boot from either of the latest node installer ISOs: ovirt-node-ng-installer-latest-el8.iso ovirt-node-ng-installer-latest-el9.iso I suspect it will require tweaks to the kernel parameters which will need to be made to the ISO installer image prior to booting. Any suggestions would be appreciated. Thanks

2 2

Upgrade host from 4.5.4 to 4.5.5 failed
by Jacob M. Nielsen 23 Jan '24

23 Jan '24

Upgrade host from Ovirt manager - Result Install Failed Here log 2024-01-23 23:08:38 CET - TASK [ovirt-host-upgrade : Upgrade packages] *********************************** 2024-01-23 23:11:47 CET - { "uuid" : "a7ac6634-4644-4416-a818-183b42b3c925", "counter" : 191, "stdout" : "", "start_line" : 186, "end_line" : 186, "runner_ident" : "0b7adac9-6ff4-4934-a9c1-ad0785877978", "event" : "runner_on_failed", "pid" : 135486, "created" : "2024-01-23T22:11:45.029493", "parent_uuid" : "000c2930-20d1-ae10-b6a7-000000000042", "event_data" : { "playbook" : "ovirt-host-upgrade.yml", "playbook_uuid" : "89cebab6-f73e-4a2f-bb30-b8de7e04367a", "play" : "all", "play_uuid" : "000c2930-20d1-ae10-b6a7-000000000002", "play_pattern" : "all", "task" : "Upgrade packages", "task_uuid" : "000c2930-20d1-ae10-b6a7-000000000042", "task_action" : "ansible.builtin.yum", "task_args" : "", "task_path" : "/usr/share/ovirt-engine/ansible-runner-service-project/project/roles/ovirt-host-upgrade/tasks/main.yml:69", "role" : "ovirt-host-upgrade", "host" : "10.63.0.6", "remote_addr" : "10.63.0.6", "res" : { "results" : [ { "failed" : true, "msg" : "Failed to validate GPG signature for ovirt-node-ng-image-update-4.5.5-1.el8.noarch: Public key for ovirt-node-ng-image-update-4.5.5-1.el8.noarch.rpm is not installed", "invocation" : { "module_args" : { Tried to just do the yum update on the host Got this result Tried to upgrade host from Ovirt manager , and got InstallFailed 2024-01-23 23:08:38 CET - TASK [ovirt-host-upgrade : Upgrade packages] *********************************** 2024-01-23 23:11:47 CET - { "uuid" : "a7ac6634-4644-4416-a818-183b42b3c925", "counter" : 191, "stdout" : "", "start_line" : 186, "end_line" : 186, "runner_ident" : "0b7adac9-6ff4-4934-a9c1-ad0785877978", "event" : "runner_on_failed", "pid" : 135486, "created" : "2024-01-23T22:11:45.029493", "parent_uuid" : "000c2930-20d1-ae10-b6a7-000000000042", "event_data" : { "playbook" : "ovirt-host-upgrade.yml", "playbook_uuid" : "89cebab6-f73e-4a2f-bb30-b8de7e04367a", "play" : "all", "play_uuid" : "000c2930-20d1-ae10-b6a7-000000000002", "play_pattern" : "all", "task" : "Upgrade packages", "task_uuid" : "000c2930-20d1-ae10-b6a7-000000000042", "task_action" : "ansible.builtin.yum", "task_args" : "", "task_path" : "/usr/share/ovirt-engine/ansible-runner-service-project/project/roles/ovirt-host-upgrade/tasks/main.yml:69", "role" : "ovirt-host-upgrade", "host" : "10.63.0.6", "remote_addr" : "10.63.0.6", "res" : { "results" : [ { "failed" : true, "msg" : "Failed to validate GPG signature for ovirt-node-ng-image-update-4.5.5-1.el8.noarch: Public key for ovirt-node-ng-image-update-4.5.5-1.el8.noarch.rpm is not installed", "invocation" : { "module_args" : { Tried to make the yum update Last metadata expiration check: 0:55:29 ago on 2024-01-23T22:43:18 CET. Dependencies resolved. =========================================================================================================================================== Package Architecture Version Repository Size =========================================================================================================================================== Installing: ovirt-node-ng-image-update noarch 4.5.5-1.el8 ovirt-45-upstream 1.3 G replacing ovirt-node-ng-image-update-placeholder.noarch 4.5.4-1.el8 Transaction Summary =========================================================================================================================================== Install 1 Package Total download size: 1.3 G Is this ok [y/N]: y Downloading Packages: ovirt-node-ng-image-update-4.5.5-1.el8.noarch.rpm 7.3 MB/s | 1.3 GB 02:59 ------------------------------------------------------------------------------------------------------------------------------------------- Total 7.2 MB/s | 1.3 GB 03:02 oVirt upstream for CentOS Stream 8 - oVirt 4.5 2.8 MB/s | 2.9 kB 00:00 Importing GPG key 0xFE590CB7: Userid : "oVirt <infra(a)ovirt.org>" Fingerprint: 31A5 D783 7FAD 7CB2 86CD 3469 AB8C 4F9D FE59 0CB7 From : /etc/pki/rpm-gpg/RPM-GPG-KEY-oVirt-4.5 Is this ok [y/N]: y Key imported successfully Import of key(s) didn't help, wrong key(s)? Public key for ovirt-node-ng-image-update-4.5.5-1.el8.noarch.rpm is not installed. Failing package is: ovirt-node-ng-image-update-4.5.5-1.el8.noarch GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-oVirt-4.5 The downloaded packages were saved in cache until the next successful transaction. You can remove cached packages by executing 'yum clean packages'. Error: GPG check FAILED Anyone seen this and found a solution ??

1 0

oVirt nodes with local storage
by Wild Star 21 Jan '24

21 Jan '24

On the weekend I upgraded my self-hosted oVirt engine to 4.56. All went well with that! I also spotted that there was an update for all my 4.54 nodes, but something has changed with the repo overnight because none of my nodes see updates anymore, though the update remains available here … https://resources.ovirt.org/pub/ovirt-4.5/iso/ovirt-node-ng-installer/. Yesterday, I attempted to update just one of my nodes and ran into this snag… “Local storage domains were found on the same filesystem as / ! Please migrate the data to a new LV before upgrading, or you will lose the VMs”. I’ve always stored my VMs in a separate /DATA directory off the root filesystem, and shared the local storage using NFS. I know it’s not ideal, but with good frequent regular backups, it has served me well for many years. A Google search revealed, that others have also had similar local storage issues, and suggestions on ways to mitigate the issue, including the oVirt documentation found here… https://www.ovirt.org/documentation/upgrade_guide/index.html#Upgrading_hype…, is not my preferred fix. In the past node updates with my local storage were not a problem and were easy peasy! From some of the discussions I saw at Red Hat, I have deduced (maybe wrongly) that there was an issue that necessitated a fix, which introduced a required check for local storage during the upgrade process. I probably should move all the local storage off the oVirt nodes, but at this time, that is easier said than done. I’m posting here only to see if there are perhaps other ideas or perspectives I may not have thought of and should consider with my local storage. Thank you all in advance, much appreciated, and of course, thank you all for supporting oVirt!

3 5

Odd behavior after upgrade to 4.5
by Seann G. Clark 19 Jan '24

19 Jan '24

All, I just recently upgraded from 4.3 to 4.5, and while most of the upgrade went smoothly and I didn't see any major issues, I have noticed a few things that are causing problems. The one piece that I had to sneak in to make the install successful, is push my CA and intermediate CA certs into the engine after it came up the first time, but before it fully installed, otherwise it would fail restoring the backup. This is to address using a custom Apache cert for the hosted engine, instead of the default self-signed CA. The biggest issue is with keycloak. To make the upgrade succeed I had to skip keycloak installation, after doing some digging related to this error: "Failed to execute stage 'Misc configuration': 'OVESETUP_OVN/ovirtProviderOvnSecret'" I don't actively use OVN in my environment right now, and I think it is all pretty much in the default install state. This is the same error I get when I loop back to install keycloak now that the engine is up. This is what is in the logs for the last few lines preceding the error and failure event: 2024-01-19 19:09:32,602+0000 DEBUG otopi.plugins.ovirt_engine_setup.ovirt_engine.network.ovirtproviderovn plugin.execute:921 execute-output: ('ovn-sbctl', 'set-connection', 'pssl:6642:[::]') stdout: 2024-01-19 19:09:32,602+0000 DEBUG otopi.plugins.ovirt_engine_setup.ovirt_engine.network.ovirtproviderovn plugin.execute:926 execute-output: ('ovn-sbctl', 'set-connection', 'pssl:6642:[::]') stderr: 2024-01-19 19:09:32,626+0000 DEBUG otopi.context context._executeMethod:127 Stage misc METHOD otopi.plugins.ovirt_engine_setup.ovirt_engine.network.ovirtproviderovn.Plugin._misc_configure_ovn_timeout 2024-01-19 19:09:32,627+0000 INFO otopi.plugins.ovirt_engine_setup.ovirt_engine.network.ovirtproviderovn ovirtproviderovn._misc_configure_ovn_timeout:1076 Updating OVN timeout configuration 2024-01-19 19:09:32,628+0000 DEBUG otopi.plugins.ovirt_engine_setup.ovirt_engine.network.ovirtproviderovn plugin.executeRaw:813 execute: ('ovn-sbctl', 'set', 'connection', '.', 'inactivity_probe=60000'), executable='None', cwd='None', env=None 2024-01-19 19:09:32,652+0000 DEBUG otopi.plugins.ovirt_engine_setup.ovirt_engine.network.ovirtproviderovn plugin.executeRaw:863 execute-result: ('ovn-sbctl', 'set', 'connection', '.', 'inactivity_probe=60000'), rc=0 2024-01-19 19:09:32,653+0000 DEBUG otopi.plugins.ovirt_engine_setup.ovirt_engine.network.ovirtproviderovn plugin.execute:921 execute-output: ('ovn-sbctl', 'set', 'connection', '.', 'inactivity_probe=60000') stdout: 2024-01-19 19:09:32,653+0000 DEBUG otopi.plugins.ovirt_engine_setup.ovirt_engine.network.ovirtproviderovn plugin.execute:926 execute-output: ('ovn-sbctl', 'set', 'connection', '.', 'inactivity_probe=60000') stderr: 2024-01-19 19:09:32,677+0000 DEBUG otopi.context context._executeMethod:127 Stage misc METHOD otopi.plugins.ovirt_engine_setup.ovirt_engine.network.ovirtproviderovn.Plugin._misc_configure_provider 2024-01-19 19:09:32,678+0000 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/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/network/ovirtproviderovn.py", line 1113, in _misc_configure_provider self._configure_ovirt_provider_ovn() File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/network/ovirtproviderovn.py", line 796, in _configure_ovirt_provider_ovn content = self._create_config_content() File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/network/ovirtproviderovn.py", line 761, in _create_config_content OvnEnv.OVIRT_PROVIDER_OVN_SECRET KeyError: 'OVESETUP_OVN/ovirtProviderOvnSecret' 2024-01-19 19:09:32,682+0000 ERROR otopi.context context._executeMethod:154 Failed to execute stage 'Misc configuration': 'OVESETUP_OVN/ovirtProviderOvnSecret' 2024-01-19 19:09:32,683+0000 DEBUG otopi.transaction transaction.abort:124 aborting 'DNF Transaction' I have spent a fair amount of time researching this but haven't found a specific root cause, or solution on this issue. Thank you in advance, Seann

1 0

Cannot update oVirt Node
by Gianluca Amato 19 Jan '24

19 Jan '24

Hello, I am trying to update my oVirt installation to 4.5.5, but while I had no problems upgrading the self-hosted ovirt-engine, I am not able to upgrade any node (running oVirt Node NG 4.5.4 or older). I just click Upgrade in the oVirt Manager, and I get a bunch of events telling me that everything was OK and the upgrade succeeded, but in reality nothing happened on the nodes: the result of "nodectl info" before and after the upgrade process is exactly the same. I gave a look to the engine.log and to the relevant ovirt-host-mgmt-ansible log in the ovirt-engine VM, but I cannot find the problem. Do any of you have any ideas ? I am attaching some relevant files. Note that the upgrade consistently fails in the same way on other nodes, which have other versions of oVirt Node NG (always in the 4.5 family). Thanks for your help --gianluca

5 7

hosted-engine --deploy: No module named 'he_ansible'
by iucounu＠gmail.com 19 Jan '24

19 Jan '24

Hi, I'm trying to install hosted engine on a server (4.5.5-1.el9) and it reports 'No module named 'he_ansible'. I have what could an he_ansible module under /usr/share/ovirt-hosted-engine-setup: /usr/share/ovirt-hosted-engine-setup/he_ansible /usr/share/ovirt-hosted-engine-setup/he_ansible/__pycache__ /usr/share/ovirt-hosted-engine-setup/he_ansible/ansible.cfg /usr/share/ovirt-hosted-engine-setup/he_ansible/callback_plugins /usr/share/ovirt-hosted-engine-setup/he_ansible/constants.py /usr/share/ovirt-hosted-engine-setup/he_ansible/trigger_role.yml /usr/share/ovirt-hosted-engine-setup/he_ansible/__pycache__/constants.cpython-39.opt-1.pyc /usr/share/ovirt-hosted-engine-setup/he_ansible/__pycache__/constants.cpython-39.pyc /usr/share/ovirt-hosted-engine-setup/he_ansible/callback_plugins/1_otopi_json.py /usr/share/ovirt-hosted-engine-setup/he_ansible/callback_plugins/2_ovirt_logger.py Is there a missing include/path somewhere? Thanks for any help. Full error: bash# hosted-engine --deploy <string>:1: DeprecationWarning: distro.linux_distribution() is deprecated. It should only be used as a compatibility shim with Python's platform.linux_distribution(). Please use distro.id(), distro.version() and distro.name() instead. <string>:1: DeprecationWarning: distro.linux_distribution() is deprecated. It should only be used as a compatibility shim with Python's platform.linux_distribution(). Please use distro.id(), distro.version() and distro.name() instead. ***L:ERROR Internal error: No module named 'he_ansible' Traceback (most recent call last): File "/usr/lib/python3.9/site-packages/otopi/main.py", line 141, in execute self.context.loadPlugins() File "/usr/lib/python3.9/site-packages/otopi/context.py", line 803, in loadPlugins self._loadPluginGroups(plugindir, needgroups, loadedgroups) File "/usr/lib/python3.9/site-packages/otopi/context.py", line 112, in _loadPluginGroups self._loadPlugins(path, path, groupname) File "/usr/lib/python3.9/site-packages/otopi/context.py", line 69, in _loadPlugins self._loadPlugins(base, d, groupname) File "/usr/lib/python3.9/site-packages/otopi/context.py", line 95, in _loadPlugins util.loadModule( File "/usr/lib/python3.9/site-packages/otopi/util.py", line 110, in loadModule spec.loader.exec_module(module) File "<frozen importlib._bootstrap_external>", line 850, in exec_module File "<frozen importlib._bootstrap>", line 228, in _call_with_frames_removed File "/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/gr-he-ansiblesetup/core/__init__.py", line 25, in <module> from . import misc File "/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/gr-he-ansiblesetup/core/misc.py", line 34, in <module> from ovirt_hosted_engine_setup import ansible_utils File "/usr/lib/python3.9/site-packages/ovirt_hosted_engine_setup/ansible_utils.py", line 33, in <module> from he_ansible.constants import AnsibleCallback ModuleNotFoundError: No module named 'he_ansible' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3.9/site-packages/otopi/__main__.py", line 88, in main installer.execute() File "/usr/lib/python3.9/site-packages/otopi/main.py", line 143, in execute util.raiseExceptionInformation( File "/usr/lib/python3.9/site-packages/otopi/util.py", line 85, in raiseExceptionInformation raise info[1].with_traceback(info[2]) File "/usr/lib/python3.9/site-packages/otopi/main.py", line 141, in execute self.context.loadPlugins() File "/usr/lib/python3.9/site-packages/otopi/context.py", line 803, in loadPlugins self._loadPluginGroups(plugindir, needgroups, loadedgroups) File "/usr/lib/python3.9/site-packages/otopi/context.py", line 112, in _loadPluginGroups self._loadPlugins(path, path, groupname) File "/usr/lib/python3.9/site-packages/otopi/context.py", line 69, in _loadPlugins self._loadPlugins(base, d, groupname) File "/usr/lib/python3.9/site-packages/otopi/context.py", line 95, in _loadPlugins util.loadModule( File "/usr/lib/python3.9/site-packages/otopi/util.py", line 110, in loadModule spec.loader.exec_module(module) File "<frozen importlib._bootstrap_external>", line 850, in exec_module File "<frozen importlib._bootstrap>", line 228, in _call_with_frames_removed File "/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/gr-he-ansiblesetup/core/__init__.py", line 25, in <module> from . import misc File "/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/gr-he-ansiblesetup/core/misc.py", line 34, in <module> from ovirt_hosted_engine_setup import ansible_utils File "/usr/lib/python3.9/site-packages/ovirt_hosted_engine_setup/ansible_utils.py", line 33, in <module> from he_ansible.constants import AnsibleCallback otopi.main.PluginLoadException: No module named 'he_ansible' root@lonovirt1 /u/cmcl bash#

1 1

virt-viewer - lost partialy connectivity
by paf1＠email.cz 19 Jan '24

19 Jan '24

Hello, after update centos9-stream to latest packages with ovirt 4.5.5 I lost VMs console connectivity . For html5 option I lost all ( can't connect anyway ) For virt-viewer option only partially, can view output screen, but keyboard has no input ( sometimes accept enter ) I tried to reinstall ovirt-vmconsole-host-1.0.9-3.el9.noarch and ovirt- vmconsole-1.0.9-3.el9.noarch , but with no success, the same situation with reinstall virt-viewer 11.0 locally ( ubuntu 23.04 last updates ). This stopped my VMs deploying :( . Exists any fix or workaround about this issue ?? thx. a lot regs. Pavel

1 0

Re: [EXT]Re: Re: [SOLVED] Re: Re: How to re-enroll (or renew) host certificates for a single-host hosted-engine deployment?
by Strahil Nikolov 18 Jan '24

18 Jan '24

Actually , the vdsmd trick is needed only to fool the engine that the host has failed (you need to disable the fencing or prevent it somehow - like changing the ipmi user's password).The engine itself uses ssh to distribute the new certificate to the host. Best Regards,Strahil Nikolov On Wed, Jan 17, 2024 at 18:07, Michael Douglass<mikedoug(a)certida.com> wrote: Ah, the steps I list here work for non-single node environments as well. The problem with vdsm-tool doing the certificate renewal in that setup is that the certificate needs to be signed by the engine host and not the local host. Apologies if this causes any confusion for single-node users. From: Strahil Nikolov <hunter86_bg(a)yahoo.com> Sent: Saturday, January 13, 2024 6:57 PM To: Michael Douglass <mikedoug(a)certida.com>; mikedoug--- via Users <users(a)ovirt.org> Subject: [EXT]Re: [ovirt-users] Re: [SOLVED] Re: Re: How to re-enroll (or renew) host certificates for a single-host hosted-engine deployment? CAUTION: Be careful of links - This email originated from outside of Certida.Hi, Recently I found another way to renew the certificates on a one-node self-hosted environment.The trick is to stop vdsmd and wait till the engine shows the system unresponsive. Then you can trigger a certificate renewal and just power on vdsmd again. Best Regards,Strahil Nikolov On Sun, Jan 14, 2024 at 2:54, mikedoug--- via Users<users(a)ovirt.org> wrote:This is the only place we found the answer we needed concerning how to sign a host key from the engine! Saved our bacon! The only tweak I would make is that there were a few more destinations at the end to copy the files into, and instead of rebooting the host we found that just restarting vdsmd and libvirtd got everything working without any existing VMs having to stop. Here's a complete update of what you have above intermingling some extra bits for anyone who has to do this in the future. If the certs on your oVirt host expire, it can be a PITA to figure out how to fix it. It's actually simple, but takes a LOT of manual work. Make sure every part of every script makes sense as I made some modifications as I documented it! I do not warrant that I didn't make a mistake somewhere. :) ########### On the ENGINE HOST ########### ## Check the CA Cert on the ENGINE openssl x509 -in /etc/pki/ovirt-engine/ca.pem -noout -dates ## If it is expired, then on the ENGINE, rebuild the CA Cert with this in a script: ## NOTE: these are steps from another post I didn't need to do them -- could be dangerous... ``` set -x ## Make the script echo everything out, so if it fails you know where set -e ## Make the script STOP on any error set my_date="$(date +"%Y%m%d%H%M%S")" # Backup the existing CA files /bin/cp -p /etc/pki/ovirt-engine/private/ca.pem /etc/pki/ovirt-engine/private/ca.pem.$my_date /bin/cp -p /etc/pki/ovirt-engine/ca.pem{,.$my_date} /bin/mv /etc/pki/ovirt-engine/certs/ca.der{,.$my_date} # Sign the key openssl x509 -signkey /etc/pki/ovirt-engine/private/ca.pem -in /etc/pki/ovirt-engine/ca.pem -out /etc/pki/ovirt-engine/ca.pem.new -days 3650 -sha256 openssl x509 -in /etc/pki/ovirt-engine/ca.pem.new -text > /etc/pki/ovirt-engine/ca.pem.new.full # Put the files into place /bin/mv -f /etc/pki/ovirt-engine/ca.pem.new.full /etc/pki/ovirt-engine/ca.pem /bin/cp -p /etc/pki/ovirt-engine/ca.pem.new /etc/pki/ovirt-engine/certs/ca.der ``` Now you need to copy the new CA file over to the host: Source: ENGINE `/etc/pki/ovirt-engine/ca.pem` Dest: HOST `/tmp/new-ca.pem` ########### On the oVirt Host ########### # Create a CSR using the information from the existing certificate and the existing key: openssl x509 -x509toreq -in /etc/pki/libvirt/clientcert.pem -out /tmp/HOST.csr -signkey /etc/pki/libvirt/private/clientkey.pem Now you need to copy the new CA file over to the host: Source: HOST `/tmp/HOST.csr` Dest: ENGINE `/etc/pki/ovirt-engine/requests/full.hostname.com.req` ########### On the ENGINE HOST ########### # Now sign it: /usr/share/ovirt-engine/bin/pki-enroll-request.sh --name=full.hostname.com # NB -- adding --san results in an error: --san=host.na.me (So no Subject Alternate Names) Now you need to copy the new Certificate file over to the host: Source: ENGINE /etc/pki/ovirt-engine/certs/full.hostname.com.cer Dest: HOST /tmp/new-cert.pem ########### On the oVirt Host ########### Run this script to put the cert and CA in place. Note if you don't put a ca into /tmp/new-ca.pem it skips that step. ``` set -x set -e set my_date="$(date +"%Y%m%d%H%M%S")" for x in /etc/pki/libvirt/clientcert.pem /etc/pki/vdsm/certs/vdsmcert.pem /etc/pki/vdsm/libvirt-migrate/server-cert.pem /etc/pki/vdsm/libvirt-spice/server-cert.pem /etc/pki/vdsm/libvirt-vnc/server-cert.pem; do /bin/mv -n $x ${x}.${mydate} /bin/cp /tmp/new-cert.pem ${x} chmod 644 ${x} chown root:kvm ${x} done if -f /tmp/new-ca.pem; then for x in /etc/pki/vdsm/libvirt-migrate/ca-cert.pem /etc/pki/vdsm/certs/cacert.pem /etc/pki/vdsm/libvirt-vnc/ca-cert.pem /etc/pki/vdsm/libvirt-spice/ca-cert.pem /etc/pki/CA/cacert.pem; do /bin/mv -n $x ${x}.${mydate} /bin/cp /tmp/new-ca.pem ${x} chmod 644 ${x} chown root:kvm ${x} done fi ``` Now you're ready to restart two vital services -- some people say "reboot the host" -- but we found that unecessary. Running this restart was safe for us and didn't cause any running VMs to crash or reboot -- they kept going without issue. Once we did this, waited a few minutes, the host came back up on the engine and everything was happy. Specifically a VM we were unable to get running was a click away from full functionality again! # Restart the two services affected by the key/cert changes systemctl restart vdsmd libvirtd _______________________________________________ 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/2EBSBWXFCEAND…

2 1

gluster on iSCSI devices in ovirt environment
by paf1＠email.cz 18 Jan '24

18 Jan '24

hello dears, can anybody explain me HOWTO realize 2 nodes + aribiter gluster from two (three) locations on block iSCSI devices ? Something like this: gluster volume create TEST replica 3 arbiter 1 <location-one-host1 - iSCSI target > <location-two-host2 - iSCSI target> < location-three-host3 - /dev/sda5 e.g. > - ALL applied on multinode ovirt cluster thx a lot for any help regs. Pa.

3 4