- Users - oVirt List Archives

static IP assignment to VM
by Henry lol 23 Jan '21

23 Jan '21

Hi, I'm trying to use Cloud-Init for assigning static IP to the guest, is there any other way commonly used? and in order to assign IP using cloud-init, "In-guest Network Interface Name" field should be filled but how to know that name in advance?

2 1

CentOS 8 is dead
by Strahil Nikolov 23 Jan '21

23 Jan '21

Hello All, I'm really worried about the following news: https://blog.centos.org/2020/12/future-is-centos-stream/ Did anyone tried to port oVirt to SLES/openSUSE or any Debian-based distro ? Best Regards, Strahil Nikolov

21 44

For data integrity make sure that the server is configured with Quorum (both client and server Quorum)
by tommy 23 Jan '21

23 Jan '21

When I want to create a glusterFS domain, the above words appear. What's meaning of these words?

3 4

Re: VMware Fence Agent
by Strahil Nikolov 23 Jan '21

23 Jan '21

I think it's easier to get the Vmware's CA certificate and import it on all hosts + engine and trust it.By default you should put it at /etc/pki/ca-trust/source/anchors/ and then use "update-ca-trust" to make all certs signed by the Vmware vCenter's CA trusted. Best Regards,Strahil Nikolov В 06:44 +0000 на 21.01.2021 (чт), Robert Tongue написа: > Greetings all, I am new to oVirt, and have a proof of concept setup > with a 3-node oVirt cluster nested inside of VMware VCenter to learn > it, so then I can efficiently migrate that back out to the physical > nodes to replace VCenter. I have gotten all the way > to a working cluster setup, with the exception of fencing. I used > engine-config to pull in the vmware_soap fence agent, and enabled all > the options, however there is one small thing I cannot figure out. > The connection uses a self-signed certificate on the > vcenter side, and I cannot figure out the proper combination of > engine-config -s commands to get the script to be called with the > "ssl-insecure" option, which does contain a value. It just needs the > option passed. Is there anyone out there in the ether > that can help me out? I can provide any information you request. > Thanks in advance. > > > > > > > > > > > The fence agent script is called with the following syntax in my > tests, and returned the proper status: > > > > > > > > [root@cluster2-vm ~]# /usr/sbin/fence_vmware_soap -o status -a > vcenter.address --username="administrator(a)vsphere.local" --password=" > 0bfusc@t3d" --ssl-insecure -n cluster1-vm > > > > > > > > Status: ON > > > > > > > > > > > > > -phunyguy > > > > > > _______________________________________________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/3PTMUPHR3ZOSQ…

1 0

Hosted Engine stuck in bios
by Joseph Gelinas 22 Jan '21

22 Jan '21

Hi, I recently did some updates of ovirt from 4.4.1 or 4.4.3 to 4.4.4, also setting the default datacenter from 4.4 to 4.5 and making the default bios q35+eufi. Unfortunately quite a few things. Now however hosted engine doesn't boot up anymore and `hosted-engine --console` just shows the below bios/firmware output: RHEL RHEL-8.1.0 PC (Q35 + ICH9, 2009) 2.00 GHz 0.0.0 16384 MB RAM Select Language <Standard English> This is the option one adjusts to change > Device Manager the language for the > Boot Manager current system > Boot Maintenance Manager Continue Reset ^v=Move Highlight <Enter>=Select Entry When in this state `hosted-engine --vm-status` says it is up but failed liveliness check hosted-engine --vm-status | grep -i engine\ status Engine status : {"vm": "down", "health": "bad", "detail": "unknown", "reason": "vm not running on this host"} Engine status : {"vm": "up", "health": "bad", "detail": "Up", "reason": "failed liveliness check"} Engine status : {"vm": "down", "health": "bad", "detail": "Down", "reason": "bad vm status"} I assume I am running into https://access.redhat.com/solutions/5341561 (RHV: Hosted-Engine VM fails to start after changing the cluster to Q35/UEFI) however how to fix that isn't really described. I have tried starting hosted engine paused (`hosted-engine --vm-start-paused`) and editing the config (`virsh -c qemu:///system?authfile=/etc/ovirt-hosted-engine/virsh_auth.conf edit HostedEngine`) to have pc-i440fx instead and removing a bunch of pcie lines etc until it will accept the config and then resuming hosted engine (`virsh -c qemu:///system?authfile=/etc/ovirt-hosted-engine/virsh_auth.conf resume HostedEngine`) but haven't come up with something that is able to start. Anyone know how to resolve this? Am I even chasing the right path? /var/log/libvirt/qemu/HostedEngine.log 2021-01-20 15:31:56.500+0000: starting up libvirt version: 6.6.0, package: 7.1.el8 (CBS <cbs(a)centos.org>, 2020-12-10-14:05:40, ), qemu version: 5.1.0qemu-kvm-5.1.0-14.el8.1, kernel: 4.18.0-240.1.1.el8_3.x86_64, hostname: ovirt-3 LC_ALL=C \ PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin \ HOME=/var/lib/libvirt/qemu/domain-25-HostedEngine \ XDG_DATA_HOME=/var/lib/libvirt/qemu/domain-25-HostedEngine/.local/share \ XDG_CACHE_HOME=/var/lib/libvirt/qemu/domain-25-HostedEngine/.cache \ XDG_CONFIG_HOME=/var/lib/libvirt/qemu/domain-25-HostedEngine/.config \ QEMU_AUDIO_DRV=spice \ /usr/libexec/qemu-kvm \ -name guest=HostedEngine,debug-threads=on \ -S \ -object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-25-HostedEngine/master-key.aes \ -blockdev '{"driver":"file","filename":"/usr/share/OVMF/OVMF_CODE.secboot.fd","node-name":"libvirt-pflash0-storage","auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-pflash0-format","read-only":true,"driver":"raw","file":"libvirt-pflash0-storage"}' \ -blockdev '{"driver":"file","filename":"/var/lib/libvirt/qemu/nvram/81816cd3-5816-4185-b553-b5a636156fbd.fd","node-name":"libvirt-pflash1-storage","auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-pflash1-format","read-only":false,"driver":"raw","file":"libvirt-pflash1-storage"}' \ -machine pc-q35-rhel8.1.0,accel=kvm,usb=off,dump-guest-core=off,pflash0=libvirt-pflash0-format,pflash1=libvirt-pflash1-format \ -cpu Cascadelake-Server-noTSX,mpx=off \ -m size=16777216k,slots=16,maxmem=67108864k \ -overcommit mem-lock=off \ -smp 4,maxcpus=64,sockets=16,dies=1,cores=4,threads=1 \ -object iothread,id=iothread1 \ -numa node,nodeid=0,cpus=0-63,mem=16384 \ -uuid 81816cd3-5816-4185-b553-b5a636156fbd \ -smbios type=1,manufacturer=oVirt,product=RHEL,version=8-1.2011.el8,serial=4c4c4544-0051-3710-8032-c8c04f483633,uuid=81816cd3-5816-4185-b553-b5a636156fbd,family=oVirt \ -no-user-config \ -nodefaults \ -device sga \ -chardev socket,id=charmonitor,fd=47,server,nowait \ -mon chardev=charmonitor,id=monitor,mode=control \ -rtc base=2021-01-20T15:31:56,driftfix=slew \ -global kvm-pit.lost_tick_policy=delay \ -no-hpet \ -no-reboot \ -global ICH9-LPC.disable_s3=1 \ -global ICH9-LPC.disable_s4=1 \ -boot strict=on \ -device pcie-root-port,port=0x10,chassis=1,id=pci.1,bus=pcie.0,multifunction=on,addr=0x2 \ -device pcie-root-port,port=0x11,chassis=2,id=pci.2,bus=pcie.0,addr=0x2.0x1 \ -device pcie-root-port,port=0x12,chassis=3,id=pci.3,bus=pcie.0,addr=0x2.0x2 \ -device pcie-root-port,port=0x13,chassis=4,id=pci.4,bus=pcie.0,addr=0x2.0x3 \ -device pcie-root-port,port=0x14,chassis=5,id=pci.5,bus=pcie.0,addr=0x2.0x4 \ -device pcie-root-port,port=0x15,chassis=6,id=pci.6,bus=pcie.0,addr=0x2.0x5 \ -device pcie-root-port,port=0x16,chassis=7,id=pci.7,bus=pcie.0,addr=0x2.0x6 \ -device pcie-root-port,port=0x17,chassis=8,id=pci.8,bus=pcie.0,addr=0x2.0x7 \ -device pcie-root-port,port=0x18,chassis=9,id=pci.9,bus=pcie.0,multifunction=on,addr=0x3 \ -device pcie-root-port,port=0x19,chassis=10,id=pci.10,bus=pcie.0,addr=0x3.0x1 \ -device pcie-root-port,port=0x1a,chassis=11,id=pci.11,bus=pcie.0,addr=0x3.0x2 \ -device pcie-root-port,port=0x1b,chassis=12,id=pci.12,bus=pcie.0,addr=0x3.0x3 \ -device pcie-root-port,port=0x1c,chassis=13,id=pci.13,bus=pcie.0,addr=0x3.0x4 \ -device pcie-root-port,port=0x1d,chassis=14,id=pci.14,bus=pcie.0,addr=0x3.0x5 \ -device pcie-root-port,port=0x1e,chassis=15,id=pci.15,bus=pcie.0,addr=0x3.0x6 \ -device pcie-root-port,port=0x1f,chassis=16,id=pci.16,bus=pcie.0,addr=0x3.0x7 \ -device pcie-root-port,port=0x20,chassis=17,id=pci.17,bus=pcie.0,addr=0x4 \ -device pcie-pci-bridge,id=pci.18,bus=pci.1,addr=0x0 \ -device qemu-xhci,p2=8,p3=8,id=ua-5a52e9e5-0726-4393-b91c-1c76e76c9ac1,bus=pci.3,addr=0x0 \ -device virtio-scsi-pci,iothread=iothread1,id=ua-7127a708-0d2a-42f3-97e4-fc314703f96f,bus=pci.4,addr=0x0 \ -device virtio-serial-pci,id=ua-e654d96c-8a11-42a0-9c83-6dda18d6052e,max_ports=16,bus=pci.5,addr=0x0 \ -device ide-cd,bus=ide.2,id=ua-7653b07c-61d5-4982-95bd-69147c4a2e54,werror=report,rerror=report \ -blockdev '{"driver":"file","filename":"/run/vdsm/storage/634fd4e4-2cc0-42fb-a92f-63223f25a339/105c32f2-c14e-474c-920e-6507e47cc28d/a5047f29-82fe-41a0-b170-3c3592df46be","aio":"threads","node-name":"libvirt-1-storage","cache":{"direct":true,"no-flush":false},"auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-1-format","read-only":false,"cache":{"direct":true,"no-flush":false},"driver":"raw","file":"libvirt-1-storage"}' \ -device virtio-blk-pci,iothread=iothread1,bus=pci.6,addr=0x0,drive=libvirt-1-format,id=ua-105c32f2-c14e-474c-920e-6507e47cc28d,bootindex=1,write-cache=on,serial=105c32f2-c14e-474c-920e-6507e47cc28d,werror=stop,rerror=stop \ -netdev tap,fds=53:54:55:56,id=hostua-972a1ee9-25eb-4613-aac2-4996a7a28fff,vhost=on,vhostfds=57:58:59:60 \ -device virtio-net-pci,mq=on,vectors=10,host_mtu=1500,netdev=hostua-972a1ee9-25eb-4613-aac2-4996a7a28fff,id=ua-972a1ee9-25eb-4613-aac2-4996a7a28fff,mac=00:16:3e:6e:da:39,bus=pci.2,addr=0x0 \ -chardev socket,id=charserial0,fd=61,server,nowait \ -device isa-serial,chardev=charserial0,id=serial0 \ -chardev socket,id=charchannel0,fd=62,server,nowait \ -device virtserialport,bus=ua-e654d96c-8a11-42a0-9c83-6dda18d6052e.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 \ -chardev spicevmc,id=charchannel1,name=vdagent \ -device virtserialport,bus=ua-e654d96c-8a11-42a0-9c83-6dda18d6052e.0,nr=2,chardev=charchannel1,id=channel1,name=com.redhat.spice.0 \ -chardev socket,id=charchannel2,fd=63,server,nowait \ -device virtserialport,bus=ua-e654d96c-8a11-42a0-9c83-6dda18d6052e.0,nr=3,chardev=charchannel2,id=channel2,name=org.ovirt.hosted-engine-setup.0 \ -device usb-tablet,id=input0,bus=ua-5a52e9e5-0726-4393-b91c-1c76e76c9ac1.0,port=1 \ -vnc 10.11.24.20:14,password \ -k en-us \ -spice port=5915,tls-port=5916,addr=10.11.24.20,x509-dir=/etc/pki/vdsm/libvirt-spice,tls-channel=main,tls-channel=display,tls-channel=inputs,tls-channel=cursor,tls-channel=playback,tls-channel=record,tls-channel=smartcard,tls-channel=usbredir,seamless-migration=on \ -device qxl-vga,id=ua-c4d51e81-5bb4-4211-a00c-3d7ab431fef2,ram_size=67108864,vram_size=33554432,vram64_size_mb=0,vgamem_mb=16,max_outputs=1,bus=pcie.0,addr=0x1 \ -device intel-hda,id=ua-68071572-175c-4af5-95f9-29f7e407e700,bus=pci.18,addr=0x1 \ -device hda-duplex,id=ua-68071572-175c-4af5-95f9-29f7e407e700-codec0,bus=ua-68071572-175c-4af5-95f9-29f7e407e700.0,cad=0 \ -device virtio-balloon-pci,id=ua-9d18ed17-c563-4f0a-b946-3d9d664a55e1,bus=pci.7,addr=0x0 \ -object rng-random,id=objua-0b27484d-b9b4-4372-b334-adcf8d3fc1eb,filename=/dev/urandom \ -device virtio-rng-pci,rng=objua-0b27484d-b9b4-4372-b334-adcf8d3fc1eb,id=ua-0b27484d-b9b4-4372-b334-adcf8d3fc1eb,bus=pci.8,addr=0x0 \ -device vmcoreinfo \ -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ -msg timestamp=on 2021-01-20T15:31:56.621216Z qemu-kvm: -numa node,nodeid=0,cpus=0-63,mem=16384: warning: Parameter -numa node,mem is deprecated, use -numa node,memdev instead /etc/libvirt/qemu/HostedEngine.xml  <domain type='kvm'> <name>HostedEngine</name> <uuid>81816cd3-5816-4185-b553-b5a636156fbd</uuid> <metadata xmlns:ns0="http://ovirt.org/vm/tune/1.0" xmlns:ovirt-vm="http://ovirt.org/vm/1.0"> <ns0:qos/> <ovirt-vm:vm xmlns:ovirt-vm="http://ovirt.org/vm/1.0"> <ovirt-vm:balloonTarget type="int">16777216</ovirt-vm:balloonTarget> <ovirt-vm:clusterVersion>4.5</ovirt-vm:clusterVersion> <ovirt-vm:destroy_on_reboot type="bool">False</ovirt-vm:destroy_on_reboot> <ovirt-vm:launchPaused>false</ovirt-vm:launchPaused> <ovirt-vm:memGuaranteedSize type="int">1024</ovirt-vm:memGuaranteedSize> <ovirt-vm:minGuaranteedMemoryMb type="int">1024</ovirt-vm:minGuaranteedMemoryMb> <ovirt-vm:resumeBehavior>auto_resume</ovirt-vm:resumeBehavior> <ovirt-vm:startTime type="float">1611156714.4983754</ovirt-vm:startTime> <ovirt-vm:device mac_address="00:16:3e:6e:da:39"/> <ovirt-vm:device devtype="disk" name="vda"> <ovirt-vm:domainID>634fd4e4-2cc0-42fb-a92f-63223f25a339</ovirt-vm:domainID> <ovirt-vm:imageID>105c32f2-c14e-474c-920e-6507e47cc28d</ovirt-vm:imageID> <ovirt-vm:poolID>00000000-0000-0000-0000-000000000000</ovirt-vm:poolID> <ovirt-vm:shared>exclusive</ovirt-vm:shared> <ovirt-vm:volumeID>a5047f29-82fe-41a0-b170-3c3592df46be</ovirt-vm:volumeID> </ovirt-vm:device> </ovirt-vm:vm> </metadata> <maxMemory slots='16' unit='KiB'>67108864</maxMemory> <memory unit='KiB'>16777216</memory> <currentMemory unit='KiB'>16777216</currentMemory> <vcpu placement='static' current='4'>64</vcpu> <iothreads>1</iothreads> <sysinfo type='smbios'> <system> <entry name='manufacturer'>oVirt</entry> <entry name='product'>RHEL</entry> <entry name='version'>8-1.2011.el8</entry> <entry name='serial'>4c4c4544-0051-3710-8032-c8c04f483633</entry> <entry name='uuid'>81816cd3-5816-4185-b553-b5a636156fbd</entry> <entry name='family'>oVirt</entry> </system> </sysinfo> <os> <type arch='x86_64' machine='pc-q35-rhel8.1.0'>hvm</type> <loader readonly='yes' secure='no' type='pflash'>/usr/share/OVMF/OVMF_CODE.secboot.fd</loader> <nvram template='/usr/share/OVMF/OVMF_VARS.fd'>/var/lib/libvirt/qemu/nvram/81816cd3-5816-4185-b553-b5a636156fbd.fd</nvram> <boot dev='hd'/> <bios useserial='yes'/> <smbios mode='sysinfo'/> </os> <features> <acpi/> <vmcoreinfo state='on'/> </features> <cpu mode='custom' match='exact' check='partial'> <model fallback='allow'>Cascadelake-Server-noTSX</model> <topology sockets='16' dies='1' cores='4' threads='1'/> <feature policy='disable' name='mpx'/> <numa> <cell id='0' cpus='0-63' memory='16777216' unit='KiB'/> </numa> </cpu> <clock offset='variable' adjustment='0' basis='utc'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>destroy</on_reboot> <on_crash>destroy</on_crash> <pm> <suspend-to-mem enabled='no'/> <suspend-to-disk enabled='no'/> </pm> <devices> <emulator>/usr/libexec/qemu-kvm</emulator> <disk type='file' device='cdrom'> <driver name='qemu' type='raw' error_policy='report'/> <source startupPolicy='optional'> <seclabel model='dac' relabel='no'/> </source> <target dev='sdc' bus='sata'/> <readonly/> <alias name='ua-7653b07c-61d5-4982-95bd-69147c4a2e54'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <disk type='file' device='disk' snapshot='no'> <driver name='qemu' type='raw' cache='none' error_policy='stop' io='threads' iothread='1'/> <source file='/run/vdsm/storage/634fd4e4-2cc0-42fb-a92f-63223f25a339/105c32f2-c14e-474c-920e-6507e47cc28d/a5047f29-82fe-41a0-b170-3c3592df46be'> <seclabel model='dac' relabel='no'/> </source> <target dev='vda' bus='virtio'/> <serial>105c32f2-c14e-474c-920e-6507e47cc28d</serial> <alias name='ua-105c32f2-c14e-474c-920e-6507e47cc28d'/> <address type='pci' domain='0x0000' bus='0x06' slot='0x00' function='0x0'/> </disk> <controller type='pci' index='1' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x10'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x11'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x1'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0x12'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0x13'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/> </controller> <controller type='pci' index='5' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='5' port='0x14'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x4'/> </controller> <controller type='pci' index='6' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='6' port='0x15'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x5'/> </controller> <controller type='pci' index='7' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='7' port='0x16'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x6'/> </controller> <controller type='pci' index='8' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='8' port='0x17'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x7'/> </controller> <controller type='pci' index='9' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='9' port='0x18'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='10' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='10' port='0x19'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x1'/> </controller> <controller type='pci' index='11' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='11' port='0x1a'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x2'/> </controller> <controller type='pci' index='12' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='12' port='0x1b'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x3'/> </controller> <controller type='pci' index='13' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='13' port='0x1c'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x4'/> </controller> <controller type='pci' index='14' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='14' port='0x1d'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x5'/> </controller> <controller type='pci' index='15' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='15' port='0x1e'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x6'/> </controller> <controller type='pci' index='16' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='16' port='0x1f'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x7'/> </controller> <controller type='pci' index='17' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='17' port='0x20'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </controller> <controller type='pci' index='18' model='pcie-to-pci-bridge'> <model name='pcie-pci-bridge'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </controller> <controller type='pci' index='0' model='pcie-root'/> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='usb' index='0' model='qemu-xhci' ports='8'> <alias name='ua-5a52e9e5-0726-4393-b91c-1c76e76c9ac1'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </controller> <controller type='scsi' index='0' model='virtio-scsi'> <driver iothread='1'/> <alias name='ua-7127a708-0d2a-42f3-97e4-fc314703f96f'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </controller> <controller type='virtio-serial' index='0' ports='16'> <alias name='ua-e654d96c-8a11-42a0-9c83-6dda18d6052e'/> <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/> </controller> <lease> <lockspace>634fd4e4-2cc0-42fb-a92f-63223f25a339</lockspace> <key>a5047f29-82fe-41a0-b170-3c3592df46be</key> <target path='/rhev/data-center/mnt/glusterSD/ovirt-1:_engine/634fd4e4-2cc0-42fb-a92f-63223f25a339/images/105c32f2-c14e-474c-920e-6507e47cc28d/a5047f29-82fe-41a0-b170-3c3592df46be.lease'/> </lease> <interface type='bridge'> <mac address='00:16:3e:6e:da:39'/> <source bridge='ovirtmgmt'/> <model type='virtio'/> <driver name='vhost' queues='4'/> <link state='up'/> <mtu size='1500'/> <alias name='ua-972a1ee9-25eb-4613-aac2-4996a7a28fff'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </interface> <serial type='unix'> <source mode='bind' path='/var/run/ovirt-vmconsole-console/81816cd3-5816-4185-b553-b5a636156fbd.sock'/> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> </serial> <console type='unix'> <source mode='bind' path='/var/run/ovirt-vmconsole-console/81816cd3-5816-4185-b553-b5a636156fbd.sock'/> <target type='serial' port='0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channels/81816cd3-5816-4185-b553-b5a636156fbd.org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <channel type='spicevmc'> <target type='virtio' name='com.redhat.spice.0'/> <address type='virtio-serial' controller='0' bus='0' port='2'/> </channel> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channels/81816cd3-5816-4185-b553-b5a636156fbd.org.ovirt.hosted-engine-setup.0'/> <target type='virtio' name='org.ovirt.hosted-engine-setup.0'/> <address type='virtio-serial' controller='0' bus='0' port='3'/> </channel> <input type='tablet' bus='usb'> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='vnc' port='-1' autoport='yes' keymap='en-us' passwd='*****' passwdValidTo='1970-01-01T00:00:01'> <listen type='network' network='vdsm-ovirtmgmt'/> </graphics> <graphics type='spice' autoport='yes' passwd='*****' passwdValidTo='1970-01-01T00:00:01'> <listen type='network' network='vdsm-ovirtmgmt'/> <channel name='main' mode='secure'/> <channel name='display' mode='secure'/> <channel name='inputs' mode='secure'/> <channel name='cursor' mode='secure'/> <channel name='playback' mode='secure'/> <channel name='record' mode='secure'/> <channel name='smartcard' mode='secure'/> <channel name='usbredir' mode='secure'/> </graphics> <sound model='ich6'> <alias name='ua-68071572-175c-4af5-95f9-29f7e407e700'/> <address type='pci' domain='0x0000' bus='0x12' slot='0x01' function='0x0'/> </sound> <video> <model type='qxl' ram='65536' vram='32768' vgamem='16384' heads='1' primary='yes'/> <alias name='ua-c4d51e81-5bb4-4211-a00c-3d7ab431fef2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/> </video> <memballoon model='virtio'> <stats period='5'/> <alias name='ua-9d18ed17-c563-4f0a-b946-3d9d664a55e1'/> <address type='pci' domain='0x0000' bus='0x07' slot='0x00' function='0x0'/> </memballoon> <rng model='virtio'> <backend model='random'>/dev/urandom</backend> <alias name='ua-0b27484d-b9b4-4372-b334-adcf8d3fc1eb'/> <address type='pci' domain='0x0000' bus='0x08' slot='0x00' function='0x0'/> </rng> </devices> </domain>

2 5

Managed Block Storage and more
by Shantur Rathore 22 Jan '21

22 Jan '21

Hi all, I am planning my new oVirt cluster on Apple hosts. These hosts can only have one disk which I plan to partition and use for hyper converged setup. As this is my first oVirt cluster I need help in understanding few bits. 1. Is Hyper converged setup possible with Ceph using cinderlib? 2. Can this hyper converged setup be on oVirt Node Next hosts or only Centos? 3. Can I install cinderlib on oVirt Node Next hosts? 4. Are there any pit falls in such a setup? Thanks for your help Regards, Shantur

8 30

[ANN] oVirt 4.4.4 is now generally available
by Sandro Bonazzola 22 Jan '21

22 Jan '21

oVirt 4.4.4 is now generally available The oVirt project is excited to announce the general availability of oVirt 4.4.4 , as of December 21st, 2020. This release unleashes an altogether more powerful and flexible open source virtualization solution that encompasses hundreds of individual changes and a wide range of enhancements across the engine, storage, network, user interface, and analytics, as compared to oVirt 4.3. Important notes before you install / upgrade Please note that oVirt 4.4 only supports clusters and data centers with compatibility version 4.2 and above. If clusters or data centers are running with an older compatibility version, you need to upgrade them to at least 4.2 (4.3 is recommended). Please note that in RHEL 8 / CentOS 8 several devices that worked on EL7 are no longer supported. For example, the megaraid_sas driver is removed. If you use Enterprise Linux 8 hosts you can try to provide the necessary drivers for the deprecated hardware using the DUD method (See the users’ mailing list thread on this at https://lists.ovirt.org/archives/list/users@ovirt.org/thread/NDSVUZSESOXEFJ… ) Documentation - If you want to try oVirt as quickly as possible, follow the instructions on the Download <https://ovirt.org/download/> page. - For complete installation, administration, and usage instructions, see the oVirt Documentation <https://ovirt.org/documentation/>. - For upgrading from a previous version, see the oVirt Upgrade Guide <https://ovirt.org/documentation/upgrade_guide/>. - For a general overview of oVirt, see About oVirt <https://ovirt.org/community/about.html>. What’s new in oVirt 4.4.4 Release? This update is the fourth in a series of stabilization updates to the 4.4 series. This release is available now on x86_64 architecture for: - Red Hat Enterprise Linux 8.3 - CentOS Linux (or similar) 8.3 - CentOS Stream (tech preview) This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: - Red Hat Enterprise Linux 8.3 - CentOS Linux (or similar) 8.3 - oVirt Node (based on CentOS Linux 8.3) - CentOS Stream (tech preview) oVirt Node and Appliance have been updated, including: - oVirt 4.4.4: https://www.ovirt.org/release/4.4.4/ - Ansible 2.9.16: https://github.com/ansible/ansible/blob/stable-2.9/changelogs/CHANGELOG-v2.… - CentOS Linux 8 (2011): https://lists.centos.org/pipermail/centos-announce/2020-December/048207.html - Advanced Virtualization 8.3 See the release notes [1] for installation instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is already available for CentOS Linux 8 - oVirt Node NG is already available for CentOS Linux 8 Additional resources: - Read more about the oVirt 4.4.4 release highlights: https://www.ovirt.org/release/4.4.4/ - Get more oVirt project updates on Twitter: https://twitter.com/ovirt - Check out the latest project news on the oVirt blog: https://blogs.ovirt.org/ [1] https://www.ovirt.org/release/4.4.4/ [2] https://resources.ovirt.org/pub/ovirt-4.4/iso/ -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/> *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

14 32

[ANN] oVirt 4.4.5 Second Release Candidate is now available for testing
by Sandro Bonazzola 22 Jan '21

22 Jan '21

oVirt 4.4.5 Second Release Candidate is now available for testing The oVirt Project is pleased to announce the availability of oVirt 4.4.5 Second Release Candidate for testing, as of January 21st, 2021. This update is the fifth in a series of stabilization updates to the 4.4 series. How to prevent hosts entering emergency mode after upgrade from oVirt 4.4.1 Note: Upgrading from 4.4.2 GA or later should not require re-doing these steps, if already performed while upgrading from 4.4.1 to 4.4.2 GA. These are only required to be done once. Due to Bug 1837864 <https://bugzilla.redhat.com/show_bug.cgi?id=1837864> - Host enter emergency mode after upgrading to latest build If you have your root file system on a multipath device on your hosts you should be aware that after upgrading from 4.4.1 to 4.4.5 you may get your host entering emergency mode. In order to prevent this be sure to upgrade oVirt Engine first, then on your hosts: 1. Remove the current lvm filter while still on 4.4.1, or in emergency mode (if rebooted). 2. Reboot. 3. Upgrade to 4.4.5 (redeploy in case of already being on 4.4.5). 4. Run vdsm-tool config-lvm-filter to confirm there is a new filter in place. 5. Only if not using oVirt Node: - run "dracut --force --add multipath” to rebuild initramfs with the correct filter configuration 6. Reboot. Documentation - If you want to try oVirt as quickly as possible, follow the instructions on the Download <https://ovirt.org/download/> page. - For complete installation, administration, and usage instructions, see the oVirt Documentation <https://ovirt.org/documentation/>. - For upgrading from a previous version, see the oVirt Upgrade Guide <https://ovirt.org/documentation/upgrade_guide/>. - For a general overview of oVirt, see About oVirt <https://ovirt.org/community/about.html>. Important notes before you try it Please note this is a pre-release build. The oVirt Project makes no guarantees as to its suitability or usefulness. This pre-release must not be used in production. Installation instructions For installation instructions and additional information please refer to: https://ovirt.org/documentation/ This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 8.3 or newer * CentOS Linux (or similar) 8.3 or newer This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 8.3 or newer * CentOS Linux (or similar) 8.3 or newer * oVirt Node 4.4 based on CentOS Linux 8.3 (available for x86_64 only) See the release notes [1] for installation instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is already available for CentOS Linux 8 - oVirt Node NG is already available for CentOS Linux 8 - We found a few issues while testing on CentOS Stream so we are still basing oVirt 4.4.5 Node and Appliance on CentOS Linux. Additional Resources: * Read more about the oVirt 4.4.5 release highlights: http://www.ovirt.org/release/4.4.5/ * Get more oVirt project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] http://www.ovirt.org/release/4.4.5/ [2] http://resources.ovirt.org/pub/ovirt-4.4-pre/iso/ -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/> *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

1 0

Cinderlib died after upgrade Cluster Compatibility version 4.4 ->4.5
by Mike Andreev 21 Jan '21

21 Jan '21

hi all, after upgrade oVirt 4.4.7 Cluster Compatibility version 4.4 ->4.5 cinderlib storage is died: tail -f /var/log/ovirt-engine/cinderlib/cinderlib.log 2021-01-20 12:35:28,781 - cinderlib-client - ERROR - Failure occurred when trying to run command 'delete_volume': Volume type with name __DEFAULT__ could not be found. [3d4a9aa9-c5f0-498c-b650-bc64d979f194] 2021-01-20 12:43:31,209 - cinderlib-client - ERROR - Failure occurred when trying to run command 'delete_volume': Volume type with name __DEFAULT__ could not be found. [927a1e82-aa21-4358-b213-120682d85e63] 2021-01-20 13:05:32,833 - cinderlib-client - ERROR - Failure occurred when trying to run command 'create_volume': Volume type with name __DEFAULT__ could not be found. [b645c321-5c64-4c54-972a-f81080bb6b0f] 2021-01-20 15:16:45,667 - cinderlib-client - ERROR - Failure occurred when trying to run command 'connect_volume': Volume type with name __DEFAULT__ could not be found. [19d98e01] 2021-01-20 15:16:48,232 - cinderlib-client - ERROR - Failure occurred when trying to run command 'connect_volume': Volume type with name __DEFAULT__ could not be found. [2088beea] 2021-01-20 15:16:50,320 - cinderlib-client - ERROR - Failure occurred when trying to run command 'disconnect_volume': Volume type with name __DEFAULT__ could not be found. [793923ab] 2021-01-20 15:37:28,423 - cinderlib-client - ERROR - Failure occurred when trying to run command 'connect_volume': Volume type with name __DEFAULT__ could not be found. [5c8f0d73] 2021-01-20 15:37:30,707 - cinderlib-client - ERROR - Failure occurred when trying to run command 'connect_volume': Volume type with name __DEFAULT__ could not be found. [35e96dcd] 2021-01-20 15:55:36,179 - cinderlib-client - ERROR - Failure occurred when trying to run command 'create_volume': Volume type with name __DEFAULT__ could not be found. [b5fbb358-36c7-4d3b-9431-16b3a699f300] 2021-01-20 15:57:33,733 - cinderlib-client - ERROR - Failure occurred when trying to run command 'create_volume': Volume type with name __DEFAULT__ could not be found. [ae879975-d36a-4b2b-9829-2713266f1c1f] in engine.log: 021-01-20 15:57:31,795+01 INFO [org.ovirt.engine.core.bll.storage.disk.AddDiskCommand] (default task-2) [ae879975-d36a-4b2b-9829-2713266f1c1f] Running command: AddDiskCommand internal: false. Entities affected : ID: 32dd7b42-eeb7-4cf5-9bef-bd8f8dd9608e Type: StorageAction group CREATE_DISK with role type USER 2021-01-20 15:57:32,014+01 INFO [org.ovirt.engine.core.bll.storage.disk.managedblock.AddManagedBlockStorageDiskCommand] (EE-ManagedExecutorService-commandCoordinator-Thread-1) [ae879975-d36a-4b2b-9829-2713266f1c1f] Running command: AddManagedBlockStorageDiskCommand internal: true. 2021-01-20 15:57:33,936+01 ERROR [org.ovirt.engine.core.common.utils.cinderlib.CinderlibExecutor] (EE-ManagedExecutorService-commandCoordinator-Thread-1) [ae879975-d36a-4b2b-9829-2713266f1c1f] cinderlib execution failed: 2021-01-20 15:57:34,012+01 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-2) [] EVENT_ID: USER_ADD_DISK_FINISHED_FAILURE(2,022), Add-Disk operation failed to complete. 2021-01-20 15:57:34,090+01 INFO [org.ovirt.engine.core.bll.storage.disk.AddDiskCommandCallback] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-47) [ae879975-d36a-4b2b-9829-2713266f1c1f] Command 'AddDisk' id: 'c7e43317-495e-4b97-96cd-02f02cb20ab2' child commands '[1de7bfa3-09c3-45a5-955a-580236f0296c]' executions were completed, status 'FAILED' 2021-01-20 15:57:35,127+01 ERROR [org.ovirt.engine.core.bll.storage.disk.AddDiskCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-48) [ae879975-d36a-4b2b-9829-2713266f1c1f] Ending command 'org.ovirt.engine.core.bll.storage.disk.AddDiskCommand' with failure. 2021-01-20 15:57:35,135+01 ERROR [org.ovirt.engine.core.bll.storage.disk.managedblock.AddManagedBlockStorageDiskCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-48) [ae879975-d36a-4b2b-9829-2713266f1c1f] Ending command 'org.ovirt.engine.core.bll.storage.disk.managedblock.AddManagedBlockStorageDiskCommand' with failure. I check it on cinderlib 2.0, 2.1, 3.0 installed as from rpm (ussuri) and from pip install - errors the same. on backend we use CEPH 14 rbd pools

2 5

Gluster Hyperconverged fails with single disk partitioned
by Shantur Rathore 21 Jan '21

21 Jan '21

Hi, I am trying to setup a single host Self-Hosted hyperconverged setup with GlusterFS. I have a custom partitioning where I provide 100G for oVirt and its partitions and rest 800G to a physical partition (/dev/sda4). When I try to create gluster deployment with the wizard, it fails TASK [gluster.infra/roles/backend_setup : Create volume groups] **************** failed: [ovirt-macpro-16.lab.ced.bskyb.com] (item={'key': 'gluster_vg_sda4', 'value': [{'vgname': 'gluster_vg_sda4', 'pvname': '/dev/sda4'}]}) => {"ansible_loop_var": "item", "changed": false, "err": " Device /dev/sda4 excluded by a filter.\n", "item": {"key": "gluster_vg_sda4", "value": [{"pvname": "/dev/sda4", "vgname": "gluster_vg_sda4"}]}, "msg": "Creating physical volume '/dev/sda4' failed", "rc": 5} I checked and /etc/lvm/lvm.conf filter doesn't allow /dev/sda4. It only allows PV for onn VG. Once I manually allow /dev/sda4 to lvm filter, it works fine and gluster deployment completes. Fdisk : # fdisk -l /dev/sda Disk /dev/sda: 931.9 GiB, 1000555581440 bytes, 1954210120 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: FE209000-85B5-489A-8A86-4CF0C91B2E7D Device Start End Sectors Size Type /dev/sda1 2048 1230847 1228800 600M EFI System /dev/sda2 1230848 3327999 2097152 1G Linux filesystem /dev/sda3 3328000 213043199 209715200 100G Linux LVM /dev/sda4 213043200 1954209791 1741166592 830.3G Linux filesystem LVS # lvs LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert home onn Vwi-aotz-- 10.00g pool0 0.11 ovirt-node-ng-4.4.4-0.20201221.0 onn Vwi---tz-k 10.00g pool0 root ovirt-node-ng-4.4.4-0.20201221.0+1 onn Vwi-aotz-- 10.00g pool0 ovirt-node-ng-4.4.4-0.20201221.0 25.26 pool0 onn twi-aotz-- 95.89g 2.95 14.39 root onn Vri---tz-k 10.00g pool0 swap onn -wi-ao---- 4.00g tmp onn Vwi-aotz-- 10.00g pool0 0.12 var onn Vwi-aotz-- 20.00g pool0 0.92 var_crash onn Vwi-aotz-- 10.00g pool0 0.11 var_log onn Vwi-aotz-- 10.00g pool0 0.13 var_log_audit onn Vwi-aotz-- 4.00g pool0 0.27 # grep filter /etc/lvm/lvm.conf filter = ["a|^/dev/disk/by-id/lvm-pv-uuid-QrvErF-eaS9-PxbI-wCBV-3OxJ-V600-NG7raZ$|", "r|.*|"] Am I doing something which oVirt isn't expecting? Is there anyway to provide tell gluster deployment to add it to lvm config. Thanks, Shantur

2 3

Change of IP's
by Román Larumbe S. 21 Jan '21

21 Jan '21

Hello, I have a Dell VRTX with 2 M640 servers, we installed oVirt version 4.3.10.4-1.el7, we have 1 cluster, 2 hosts and 2 storage domains. I need to change ALL the network environment solution, that is, from IP's 192.168.11.XX to 172.16.10.XX. Can anybody help me? Thank you. Román Larumbe S. Facebook: Serahp LS

2 1

VMware Fence Agent
by Robert Tongue 21 Jan '21

21 Jan '21

Greetings all, I am new to oVirt, and have a proof of concept setup with a 3-node oVirt cluster nested inside of VMware VCenter to learn it, so then I can efficiently migrate that back out to the physical nodes to replace VCenter. I have gotten all the way to a working cluster setup, with the exception of fencing. I used engine-config to pull in the vmware_soap fence agent, and enabled all the options, however there is one small thing I cannot figure out. The connection uses a self-signed certificate on the vcenter side, and I cannot figure out the proper combination of engine-config -s commands to get the script to be called with the "ssl-insecure" option, which does contain a value. It just needs the option passed. Is there anyone out there in the ether that can help me out? I can provide any information you request. Thanks in advance. The fence agent script is called with the following syntax in my tests, and returned the proper status: [root@cluster2-vm ~]# /usr/sbin/fence_vmware_soap -o status -a vcenter.address --username="administrator(a)vsphere.local" --password="0bfusc@t3d" --ssl-insecure -n cluster1-vm Status: ON -phunyguy

1 0

Why cannot create new volume ?
by tommy 21 Jan '21

21 Jan '21

3 7

Mutually exclusive VMs
by Shantur Rathore 21 Jan '21

21 Jan '21

Hi all, I am trying to figure if there is a way to force oVirt to schedule VMs on different hosts. So if I am cloning 6 VMs from a template, I want oVirt to schedule them on all different hosts. No 2 VMs must schedule on the same host. I know that there is pin-to-host functionality but I don't want to manually pin it to hosts. Thanks Shantur

2 1

Unable to edit DNS connfiguration on hosts
by miguel.garcia＠toshibagcs.com 20 Jan '21

20 Jan '21

I had to replace the DNS server in my network so I want to update the DNS address on each host so in oVirt web interface I go to Compute > Host > Hostname > Network Interfaces > Setup Host Networks Right there I click on the edit button of the vlan for networking, check out (host ip address is static), DNS configuration, check DNS configuration, Type DNS ip address and click ok to save change. I got message: Error while executing action HostSetupNetworks: Unexpected Exception. Into engile.log found message "Operation not permitted" related to this action despite that was executed with my user account (wint admin privileges) and same message was returned using admin@internal user. 2021-01-20 11:35:31,579-05 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HostSetupNetworksVDSCommand] (default task-482931) [b9a19834-3f15-42da-af2c-55e292dfedea] START, HostSetupNetworksVDSCommand(HostName = hyp10.eboss, HostSetupNetworksVdsCommandParameters:{hostId='39c05625-7b59-4a38-a5a9-5d556ae1fe18', vds='Host[hyp10.eboss,39c05625-7b59-4a38-a5a9-5d556ae1fe18]', rollbackOnFailure='true', commitOnSuccess='true', connectivityTimeout='120', networks='[HostNetwork:{defaultRoute='true', bonding='false', networkName='tgcs182vlan', vdsmName='tgcs182vlan', nicName='eno1', vlan='null', vmNetwork='true', stp='false', properties='[]', ipv4BootProtocol='STATIC_IP', ipv4Address='10.89.182.10', ipv4Netmask='255.255.255.0', ipv4Gateway='10.89.182.1', ipv6BootProtocol='AUTOCONF', ipv6Address='null', ipv6Prefix='null', ipv6Gateway='null', nameServers='[NameServer:{address='10.89.182.204'}, NameServer:{address='10.89.176.71'}]'}]', removedNetworks='[]', bonds='[]', removedBonds='[]', clusterSw itchType='OVS', managementNetworkChanged='false'}), log id: 23059843 2021-01-20 11:35:31,582-05 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HostSetupNetworksVDSCommand] (default task-482931) [b9a19834-3f15-42da-af2c-55e292dfedea] FINISH, HostSetupNetworksVDSCommand, return: , log id: 23059843 2021-01-20 11:35:35,665-05 WARN [org.ovirt.engine.core.vdsbroker.vdsbroker.HostSetupNetworksVDSCommand] (default task-482931) [b9a19834-3f15-42da-af2c-55e292dfedea] Unexpected return value: Status [code=-32603, message=Internal JSON-RPC error: {'reason': '[Errno 1] Operation not permitted'}] 2021-01-20 11:35:35,665-05 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.HostSetupNetworksVDSCommand] (default task-482931) [b9a19834-3f15-42da-af2c-55e292dfedea] Failed in 'HostSetupNetworksVDS' method 2021-01-20 11:35:35,666-05 WARN [org.ovirt.engine.core.vdsbroker.vdsbroker.HostSetupNetworksVDSCommand] (default task-482931) [b9a19834-3f15-42da-af2c-55e292dfedea] Unexpected return value: Status [code=-32603, message=Internal JSON-RPC error: {'reason': '[Errno 1] Operation not permitted'}] 2021-01-20 11:35:35,673-05 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-482931) [b9a19834-3f15-42da-af2c-55e292dfedea] EVENT_ID: VDS_BROKER_COMMAND_FAILURE(10,802), VDSM hyp10.eboss command HostSetupNetworksVDS failed: Internal JSON-RPC error: {'reason': '[Errno 1] Operation not permitted'} 2021-01-20 11:35:35,673-05 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.HostSetupNetworksVDSCommand] (default task-482931) [b9a19834-3f15-42da-af2c-55e292dfedea] Error: VDSGenericException: VDSErrorException: Failed to HostSetupNetworksVDS, error = Internal JSON-RPC error: {'reason': '[Errno 1] Operation not permitted'}, code = -32603 2021-01-20 11:35:35,673-05 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.HostSetupNetworksVDSCommand] (default task-482931) [b9a19834-3f15-42da-af2c-55e292dfedea] Command 'HostSetupNetworksVDSCommand(HostName = hyp10.eboss, HostSetupNetworksVdsCommandParameters:{hostId='39c05625-7b59-4a38-a5a9-5d556ae1fe18', vds='Host[hyp10.eboss,39c05625-7b59-4a38-a5a9-5d556ae1fe18]', rollbackOnFailure='true', commitOnSuccess='true', connectivityTimeout='120', networks='[HostNetwork:{defaultRoute='true', bonding='false', networkName='tgcs182vlan', vdsmName='tgcs182vlan', nicName='eno1', vlan='null', vmNetwork='true', stp='false', properties='[]', ipv4BootProtocol='STATIC_IP', ipv4Address='10.89.182.10', ipv4Netmask='255.255.255.0', ipv4Gateway='10.89.182.1', ipv6BootProtocol='AUTOCONF', ipv6Address='null', ipv6Prefix='null', ipv6Gateway='null', nameServers='[NameServer:{address='10.89.182.204'}, NameServer:{address='10.89.176.71'}]'}]', removedNetworks='[]', bonds='[]', removedBonds='[]', cluster SwitchType='OVS', managementNetworkChanged='false'})' execution failed: VDSGenericException: VDSErrorException: Failed to HostSetupNetworksVDS, error = Internal JSON-RPC error: {'reason': '[Errno 1] Operation not permitted'}, code = -32603 2021-01-20 11:35:35,673-05 INFO [org.ovirt.engine.core.bll.network.host.HostSetupNetworksCommand] (default task-482931) [b9a19834-3f15-42da-af2c-55e292dfedea] Host setup networks finished. Lock released. Monitoring can run now for host 'hyp10.eboss' from data-center 'tgcs-gdl-dc1-public' 2021-01-20 11:35:35,673-05 ERROR [org.ovirt.engine.core.bll.network.host.HostSetupNetworksCommand] (default task-482931) [b9a19834-3f15-42da-af2c-55e292dfedea] Command 'org.ovirt.engine.core.bll.network.host.HostSetupNetworksCommand' failed: EngineException: org.ovirt.engine.core.vdsbroker.vdsbroker.VDSErrorException: VDSGenericException: VDSErrorException: Failed to HostSetupNetworksVDS, error = Internal JSON-RPC error: {'reason': '[Errno 1] Operation not permitted'}, code = -32603 (Failed with error unexpected and code 16) 2021-01-20 11:35:35,677-05 INFO [org.ovirt.engine.core.bll.network.host.HostSetupNetworksCommand] (default task-482931) [b9a19834-3f15-42da-af2c-55e292dfedea] Lock freed to object 'EngineLock:{exclusiveLocks='[HOST_NETWORK39c05625-7b59-4a38-a5a9-5d556ae1fe18=HOST_NETWORK]', sharedLocks=''}' This error message happens even in master as in nodes hosts. Any idea how can I solve it? Thanks in advance

1 0

About Enroll Certificate
by tommy 20 Jan '21

20 Jan '21

Hi, What function of the Enroll Certificate ??

2 2

Problems Installing host on brand new 4.4 cluster
by David Johnson 20 Jan '21

20 Jan '21

Hi all, I am standing up a brand new cluster on new hardware. The ovirt controller is installed and appears to be running fine. When I attempt to add the new host, I get the flag that says "Non Operational", and the exclamation mark with the message "Host has no default route". I have confirmed that I have bidirectional ssh connections between the controller and the new host. Selinux is disabled. Firewall is disabled. I can get to the host console via the link in the GUI Compute|Hosts page. This looks like a common symptom of a host of problems, but there is nothing to readily indicate what the actual problem is. In the ovirt-engine log, I found this entry: "Host 'ovirt-host-03' is set to Non-Operational, it is missing the following networks: 'ovirtmgmt'" This seems self-explanatory, but I see no way to add the missing network to the host. Thank you in advance for your help Regards, David Johnson * <http://www.linkedin.com/in/pojoguy>*

2 2

Install of RHV 4.4 failing - "Host is not up, please check logs, perhaps also on the engine machine"
by james.freeman＠a24.io 19 Jan '21

19 Jan '21

Hi all I am in the process of migrating a RHV 4.3 setup to RHV 4.4 and struggling with the setup. I am installing on RHEL 8.3, using settings backed up from the RHV 4.3 install (via 'hosted-engine --deploy --restore-from-file=backup.bck'). The install process always fails at the same point for me at the moment, and I can't figure out how to get past it. As far as install progress goes, the local hosted-engine comes up and runs on the node. I have been able to grep for local_vm_ip in the logs, and can SSH into it with the password I set during the setup phase. However the install playbooks always fail with: 2021-01-18 18:38:00,086-0500 ERROR otopi.plugins.gr_he_common.core.misc misc._terminate:167 Hosted Engine deployment failed: please check the logs for the issue, fix accordingly or re-deploy from scratch. Earlier in the logs, I note the following: 2021-01-18 18:34:51,258-0500 ERROR otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:109 fatal: [localhost]: FAILED! => {"changed": false, "msg": "Host is not up, please check logs, perhaps also on the engine machine"} 2021-01-18 18:37:16,661-0500 ERROR otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:109 fatal: [localhost]: FAILED! => {"changed": false, "msg": "The system may not be provisioned according to the playbook results: please check the logs for the issue, fix accordingly or re-deploy from scratch.\n"} 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-hosted-engine-setup/scripts/../plugins/gr-he-ansiblesetup/core/misc.py", line 435, in _closeup raise RuntimeError(_('Failed executing ansible-playbook')) RuntimeError: Failed executing ansible-playbook 2021-01-18 18:37:18,996-0500 ERROR otopi.context context._executeMethod:154 Failed to execute stage 'Closing up': Failed executing ansible-playbook 2021-01-18 18:37:32,421-0500 ERROR otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:109 fatal: [localhost]: UNREACHABLE! => {"changed": false, "msg": "Failed to connect to the host via ssh: ssh: connect to host rhvm.example.org port 22: No route to host", "skip_reason": "Host localhost is unreachable", "unreachable": true} I find the unreachable message a bit odd, as at this stage all that has happened is that the local hosted-engine has been brought up to be configured, and so it is running on virbr0, not on my actual network. As a result, that DNS address will never resolve, and the IP it resolves to won't be up. I gave the installation script permission to modify the local /etc/hosts but this hasn't improved things. I presume I'm missing something in the install process, or earlier on in the logs, but I've been scanning for errors and possible clues to no avail. Any and all help greatly appreciated!

3 5

VM Disks order
by Erez Zarum 19 Jan '21

19 Jan '21

When attaching a disk it is not possible to set the disk order nor modify the order later. Example: A new VM is provisioned with 5 disks, Disk0 is the OS and then later attached disks by order up to Disk4. Removing Disk3 and then later attaching does not promise it will be attached back as Disk3. In most other platforms it is possible to set the order. Am i missing something? if not, is there a plan to add this feature?

2 1

Why the update hung here ?
by tommy 19 Jan '21

19 Jan '21

Hi , I just update the hosts, but why the log print these info many many times for a long while.

2 1

noVNC error.
by tommy 19 Jan '21

19 Jan '21

Hi: I use novnc console can connect to engine vm. But when I using novnc console connect to other vm in other datacenter, failed. The ovirt-websocket-proxy log is: Jan 19 15:43:32 ooeng.tltd.com ovirt-websocket-proxy.py[1312]: 192.168.10.104 - - [19/Jan/2021 15:43:32] connecting to: ohost2.tltd.com:5900 (using SSL) Jan 19 15:43:32 ooeng.tltd.com ovirt-websocket-proxy.py[1312]: ovirt-websocket-proxy[24096] INFO msg:824 handler exception: [SSL: UNKNOWN_PROTOCOL] unknown protocol (_ssl.c:618) What reason ?

2 1

Guest don't start : Cannot access backing file
by Lionel Caignec 19 Jan '21

19 Jan '21

Hi, i've a big problem, i juste shutdown (power off completely) a guest to make a cold restart. And at startup the guest say : "Cannot access backing file '/rhev/data-center/mnt/blockSD/69348aea-7f55-41be-ae4e-febd86c33855/images/8224b2b0-39ba-44ef-ae41-18fe726f26ca/ca141675-c6f5-4b03-98b0-0312254f91e8'" When i look from shell on Hypervisor the device file is red blinking... Trying to change SPM, look device into all hosts, copy disk etc... no way to get my disk back online. It seems ovirt completely lost (delete?) the block device. There is a way to manually dump (dd) the device in command line in order to import it inside ovirt? My environment Storage : SAN (managed by ovirt) Ovirt-engine 4.4.3.12-1.el8 Host centos 8.2 Vdsm 4.40.26 Thanks for help i'm stuck and it's really urgent -- Lionel Caignec

2 2

oVirt Engine no longer Starting
by penguin pages 18 Jan '21

18 Jan '21

3 node cluster. Gluster for shared storage. CentOS8 Updated to CentOS 8 Streams :P -> https://bugzilla.redhat.com/show_bug.cgi?id=1911910 After several weeks .. I am really in need of direction to get this fixed. I saw several postings about oVirt package issues but not found a fix. [root@thor ~]# dnf update Last metadata expiration check: 2:54:29 ago on Fri 15 Jan 2021 06:49:16 AM EST. Error: Problem 1: package ovirt-host-4.4.1-4.el8.x86_64 requires cockpit-dashboard, but none of the providers can be installed - package cockpit-bridge-234-1.el8.x86_64 conflicts with cockpit-dashboard < 233 provided by cockpit-dashboard-217-1.el8.noarch - cannot install the best update candidate for package ovirt-host-4.4.1-4.el8.x86_64 - cannot install the best update candidate for package cockpit-bridge-217-1.el8.x86_64 Problem 2: problem with installed package ovirt-host-4.4.1-4.el8.x86_64 - package ovirt-host-4.4.1-4.el8.x86_64 requires cockpit-dashboard, but none of the providers can be installed - package cockpit-system-234-1.el8.noarch obsoletes cockpit-dashboard provided by cockpit-dashboard-217-1.el8.noarch - cannot install the best update candidate for package cockpit-dashboard-217-1.el8.noarch Problem 3: package ovirt-hosted-engine-setup-2.4.9-1.el8.noarch requires ovirt-host >= 4.4.0, but none of the providers can be installed - package ovirt-host-4.4.1-4.el8.x86_64 requires cockpit-dashboard, but none of the providers can be installed - package ovirt-host-4.4.1-1.el8.x86_64 requires cockpit-dashboard, but none of the providers can be installed - package ovirt-host-4.4.1-2.el8.x86_64 requires cockpit-dashboard, but none of the providers can be installed - package ovirt-host-4.4.1-3.el8.x86_64 requires cockpit-dashboard, but none of the providers can be installed - package cockpit-system-234-1.el8.noarch obsoletes cockpit-dashboard provided by cockpit-dashboard-217-1.el8.noarch - cannot install the best update candidate for package ovirt-hosted-engine-setup-2.4.9-1.el8.noarch - cannot install the best update candidate for package cockpit-system-217-1.el8.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) [root@thor ~]# yum install cockpit-dashboard --nobest Last metadata expiration check: 2:54:52 ago on Fri 15 Jan 2021 06:49:16 AM EST. Package cockpit-dashboard-217-1.el8.noarch is already installed. Dependencies resolved. Problem: problem with installed package ovirt-host-4.4.1-4.el8.x86_64 - package ovirt-host-4.4.1-4.el8.x86_64 requires cockpit-dashboard, but none of the providers can be installed - package ovirt-host-4.4.1-1.el8.x86_64 requires cockpit-dashboard, but none of the providers can be installed - package ovirt-host-4.4.1-2.el8.x86_64 requires cockpit-dashboard, but none of the providers can be installed - package ovirt-host-4.4.1-3.el8.x86_64 requires cockpit-dashboard, but none of the providers can be installed - package cockpit-system-234-1.el8.noarch obsoletes cockpit-dashboard provided by cockpit-dashboard-217-1.el8.noarch - cannot install the best candidate for the job ========================================================================================================================================================================================================================================= Package Architecture Version Repository Size ========================================================================================================================================================================================================================================= Skipping packages with broken dependencies: ovirt-host x86_64 4.4.1-1.el8 ovirt-4.4 13 k ovirt-host x86_64 4.4.1-2.el8 ovirt-4.4 13 k ovirt-host x86_64 4.4.1-3.el8 ovirt-4.4 13 k Transaction Summary ========================================================================================================================================================================================================================================= Skip 3 Packages Nothing to do. Complete! [root@thor ~]# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 931.5G 0 disk └─WDC_WDS100T2B0B-00YS70_19106A802926 253:3 0 931.5G 0 mpath └─vdo_2926 253:5 0 4T 0 vdo /gluster_bricks/gv0 sdb 8:16 0 931.5G 0 disk └─WDC_WDS100T2B0B-00YS70_192490801828 253:4 0 931.5G 0 mpath sdc 8:32 0 477G 0 disk └─vdo_sdc 253:6 0 2.1T 0 vdo ├─gluster_vg_sdc-gluster_lv_engine 253:7 0 100G 0 lvm /gluster_bricks/engine ├─gluster_vg_sdc-gluster_thinpool_gluster_vg_sdc_tmeta 253:8 0 1G 0 lvm │ └─gluster_vg_sdc-gluster_thinpool_gluster_vg_sdc-tpool 253:10 0 2T 0 lvm │ ├─gluster_vg_sdc-gluster_thinpool_gluster_vg_sdc 253:11 0 2T 1 lvm │ ├─gluster_vg_sdc-gluster_lv_data 253:12 0 1000G 0 lvm /gluster_bricks/data │ └─gluster_vg_sdc-gluster_lv_vmstore 253:13 0 1000G 0 lvm /gluster_bricks/vmstore └─gluster_vg_sdc-gluster_thinpool_gluster_vg_sdc_tdata 253:9 0 2T 0 lvm └─gluster_vg_sdc-gluster_thinpool_gluster_vg_sdc-tpool 253:10 0 2T 0 lvm ├─gluster_vg_sdc-gluster_thinpool_gluster_vg_sdc 253:11 0 2T 1 lvm ├─gluster_vg_sdc-gluster_lv_data 253:12 0 1000G 0 lvm /gluster_bricks/data └─gluster_vg_sdc-gluster_lv_vmstore 253:13 0 1000G 0 lvm /gluster_bricks/vmstore sdd 8:48 1 58.8G 0 disk ├─sdd1 8:49 1 1G 0 part /boot └─sdd2 8:50 1 57.8G 0 part ├─cl-root 253:0 0 36.1G 0 lvm / ├─cl-swap 253:1 0 4G 0 lvm [SWAP] └─cl-home 253:2 0 17.6G 0 lvm /home [root@thor ~]# mount |grep engine /dev/mapper/gluster_vg_sdc-gluster_lv_engine on /gluster_bricks/engine type xfs (rw,noatime,nodiratime,seclabel,attr2,inode64,logbufs=8,logbsize=32k,noquota,_netdev,x-systemd.requires=vdo.service) thorst.penguinpages.local:/engine on /media/engine type fuse.glusterfs (rw,relatime,user_id=0,group_id=0,default_permissions,allow_other,max_read=131072,_netdev) thorst.penguinpages.local:/engine on /rhev/data-center/mnt/glusterSD/thorst.penguinpages.local:_engine type fuse.glusterfs (rw,relatime,user_id=0,group_id=0,default_permissions,allow_other,max_read=131072,_netdev,x-systemd.device-timeout=0) [root@thor ~]# [root@thor ~]# tail -50 /var/log/messages Jan 15 09:46:43 thor platform-python[28088]: detected unhandled Python exception in '/usr/share/ovirt-hosted-engine-ha/ovirt-ha-broker' Jan 15 09:46:43 thor abrt-server[28116]: Not saving repeating crash in '/usr/share/ovirt-hosted-engine-ha/ovirt-ha-broker' Jan 15 09:46:43 thor systemd[1]: ovirt-ha-broker.service: Main process exited, code=exited, status=1/FAILURE Jan 15 09:46:43 thor systemd[1]: ovirt-ha-broker.service: Failed with result 'exit-code'. Jan 15 09:46:43 thor systemd[1]: ovirt-ha-broker.service: Service RestartSec=100ms expired, scheduling restart. Jan 15 09:46:43 thor systemd[1]: ovirt-ha-broker.service: Scheduled restart job, restart counter is at 241. Jan 15 09:46:43 thor systemd[1]: Stopped oVirt Hosted Engine High Availability Communications Broker. Jan 15 09:46:43 thor systemd[1]: Started oVirt Hosted Engine High Availability Communications Broker. Jan 15 09:46:45 thor systemd[1]: Started Session c448 of user root. Jan 15 09:46:45 thor systemd[1]: session-c448.scope: Succeeded. Jan 15 09:46:45 thor upsmon[2232]: Poll UPS [nutmonitor@localhost] failed - [nutmonitor] does not exist on server localhost Jan 15 09:46:48 thor systemd[1]: ovirt-ha-agent.service: Service RestartSec=10s expired, scheduling restart. Jan 15 09:46:48 thor systemd[1]: ovirt-ha-agent.service: Scheduled restart job, restart counter is at 211. Jan 15 09:46:48 thor systemd[1]: Stopped oVirt Hosted Engine High Availability Monitoring Agent. Jan 15 09:46:48 thor systemd[1]: Started oVirt Hosted Engine High Availability Monitoring Agent. Jan 15 09:46:48 thor journal[28118]: ovirt-ha-broker ovirt_hosted_engine_ha.broker.broker.Broker ERROR Failed initializing the broker: [Errno 107] Transport endpoint is not connected: '/rhev/data-center/mnt/glusterSD/thorst.penguinpages.local:_engine/3afc47ba-afb9-413f-8de5-8d9a2f45ecde/ha_agent/hosted-engine.metadata' Jan 15 09:46:48 thor journal[28118]: ovirt-ha-broker ovirt_hosted_engine_ha.broker.broker.Broker ERROR Traceback (most recent call last):#012 File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/broker/broker.py", line 64, in run#012 self._storage_broker_instance = self._get_storage_broker()#012 File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/broker/broker.py", line 143, in _get_storage_broker#012 return storage_broker.StorageBroker()#012 File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/broker/storage_broker.py", line 97, in __init__#012 self._backend.connect()#012 File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/lib/storage_backends.py", line 408, in connect#012 self._check_symlinks(self._storage_path, volume.path, service_link)#012 File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/lib/storage_backends.py", line 105, in _check_symlinks#012 os.unlink(service_link)#012OSError: [Errno 107] Transport endpoint is not connected: '/rhev/data-center/mnt/glusterSD/thorst.penguinpages.local:_engine/3afc47ba-afb9-413f-8de5-8d9a2f45ecde/ha_agent/hosted-engine.metadata' Jan 15 09:46:48 thor journal[28118]: ovirt-ha-broker ovirt_hosted_engine_ha.broker.broker.Broker ERROR Trying to restart the broker Jan 15 09:46:48 thor platform-python[28118]: detected unhandled Python exception in '/usr/share/ovirt-hosted-engine-ha/ovirt-ha-broker' Jan 15 09:46:48 thor systemd[1]: ovirt-ha-broker.service: Main process exited, code=exited, status=1/FAILURE Jan 15 09:46:48 thor systemd[1]: ovirt-ha-broker.service: Failed with result 'exit-code'. Jan 15 09:46:48 thor abrt-server[28144]: Deleting problem directory Python3-2021-01-15-09:46:48-28118 (dup of Python3-2020-09-18-14:25:13-1363) Jan 15 09:46:48 thor systemd[1]: ovirt-ha-broker.service: Service RestartSec=100ms expired, scheduling restart. Jan 15 09:46:48 thor systemd[1]: ovirt-ha-broker.service: Scheduled restart job, restart counter is at 242. Jan 15 09:46:48 thor systemd[1]: Stopped oVirt Hosted Engine High Availability Communications Broker. Jan 15 09:46:48 thor systemd[1]: Started oVirt Hosted Engine High Availability Communications Broker. Jan 15 09:46:48 thor journal[28140]: ovirt-ha-agent ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine ERROR Failed to start necessary monitors Jan 15 09:46:48 thor journal[28140]: ovirt-ha-agent ovirt_hosted_engine_ha.agent.agent.Agent ERROR Traceback (most recent call last):#012 File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/lib/brokerlink.py", line 85, in start_monitor#012 response = self._proxy.start_monitor(type, options)#012 File "/usr/lib64/python3.6/xmlrpc/client.py", line 1112, in __call__#012 return self.__send(self.__name, args)#012 File "/usr/lib64/python3.6/xmlrpc/client.py", line 1452, in __request#012 verbose=self.__verbose#012 File "/usr/lib64/python3.6/xmlrpc/client.py", line 1154, in request#012 return self.single_request(host, handler, request_body, verbose)#012 File "/usr/lib64/python3.6/xmlrpc/client.py", line 1166, in single_request#012 http_conn = self.send_request(host, handler, request_body, verbose)#012 File "/usr/lib64/python3.6/xmlrpc/client.py", line 1279, in send_request#012 self.send_content(connection, request_body)#012 File "/usr/lib64/python3.6/xmlrpc/client.py", line 1309, in send_content#012 connection.endheaders(request_body)#012 File "/usr/lib64/python3.6/http/client.py", line 1264, in endheaders#012 self._send_output(message_body, encode_chunked=encode_chunked)#012 File "/usr/lib64/python3.6/http/client.py", line 1040, in _send_output#012 self.send(msg)#012 File "/usr/lib64/python3.6/http/client.py", line 978, in send#012 self.connect()#012 File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/lib/unixrpc.py", line 74, in connect#012 self.sock.connect(base64.b16decode(self.host))#012FileNotFoundError: [Errno 2] No such file or directory#012#012During handling of the above exception, another exception occurred:#012#012Traceback (most recent call last):#012 File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/agent/agent.py", line 131, in _run_agent#012 return action(he)#012 File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/agent/agent.py", line 55, in action_proper#012 return he.start_monitoring()#012 File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/agent/hosted_engine.py", line 437, in start_monitoring#012 self._initialize_broker()#012 File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/agent/hosted_engine.py", line 561, in _initialize_broker#012 m.get('options', {}))#012 File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/lib/brokerlink.py", line 91, in start_monitor#012 ).format(t=type, o=options, e=e)#012ovirt_hosted_engine_ha.lib.exceptions.RequestError: brokerlink - failed to start monitor via ovirt-ha-broker: [Errno 2] No such file or directory, [monitor: 'network', options: {'addr': '172.16.100.1', 'network_test': 'dns', 'tcp_t_address': '', 'tcp_t_port': ''}] Jan 15 09:46:48 thor journal[28140]: ovirt-ha-agent ovirt_hosted_engine_ha.agent.agent.Agent ERROR Trying to restart agent Jan 15 09:46:48 thor abrt-server[28144]: /bin/sh: reporter-systemd-journal: command not found Jan 15 09:46:48 thor systemd[1]: ovirt-ha-agent.service: Main process exited, code=exited, status=157/n/a Jan 15 09:46:48 thor systemd[1]: ovirt-ha-agent.service: Failed with result 'exit-code'. Jan 15 09:46:49 thor vdsm[8421]: WARN Failed to retrieve Hosted Engine HA info, is Hosted Engine setup finished? Jan 15 09:46:50 thor systemd[1]: Started Session c449 of user root. Jan 15 09:46:50 thor systemd[1]: session-c449.scope: Succeeded. Jan 15 09:46:50 thor upsmon[2232]: Poll UPS [nutmonitor@localhost] failed - [nutmonitor] does not exist on server localhost Jan 15 09:46:53 thor journal[28165]: ovirt-ha-broker ovirt_hosted_engine_ha.broker.broker.Broker ERROR Failed initializing the broker: [Errno 107] Transport endpoint is not connected: '/rhev/data-center/mnt/glusterSD/thorst.penguinpages.local:_engine/3afc47ba-afb9-413f-8de5-8d9a2f45ecde/ha_agent/hosted-engine.metadata' Jan 15 09:46:53 thor journal[28165]: ovirt-ha-broker ovirt_hosted_engine_ha.broker.broker.Broker ERROR Traceback (most recent call last):#012 File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/broker/broker.py", line 64, in run#012 self._storage_broker_instance = self._get_storage_broker()#012 File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/broker/broker.py", line 143, in _get_storage_broker#012 return storage_broker.StorageBroker()#012 File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/broker/storage_broker.py", line 97, in __init__#012 self._backend.connect()#012 File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/lib/storage_backends.py", line 408, in connect#012 self._check_symlinks(self._storage_path, volume.path, service_link)#012 File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/lib/storage_backends.py", line 105, in _check_symlinks#012 os.unlink(service_link)#012OSError: [Errno 107] Transport endpoint is not connected: '/rhev/data-center/mnt/glusterSD/thorst.penguinpages.local:_engine/3afc47ba-afb9-413f-8de5-8d9a2f45ecde/ha_agent/hosted-engine.metadata' Jan 15 09:46:53 thor journal[28165]: ovirt-ha-broker ovirt_hosted_engine_ha.broker.broker.Broker ERROR Trying to restart the broker Jan 15 09:46:53 thor platform-python[28165]: detected unhandled Python exception in '/usr/share/ovirt-hosted-engine-ha/ovirt-ha-broker' Jan 15 09:46:53 thor abrt-server[28199]: Not saving repeating crash in '/usr/share/ovirt-hosted-engine-ha/ovirt-ha-broker' Jan 15 09:46:53 thor systemd[1]: ovirt-ha-broker.service: Main process exited, code=exited, status=1/FAILURE Jan 15 09:46:53 thor systemd[1]: ovirt-ha-broker.service: Failed with result 'exit-code'. Jan 15 09:46:53 thor systemd[1]: ovirt-ha-broker.service: Service RestartSec=100ms expired, scheduling restart. Jan 15 09:46:53 thor systemd[1]: ovirt-ha-broker.service: Scheduled restart job, restart counter is at 243. Jan 15 09:46:53 thor systemd[1]: Stopped oVirt Hosted Engine High Availability Communications Broker. Jan 15 09:46:53 thor systemd[1]: Started oVirt Hosted Engine High Availability Communications Broker. Jan 15 09:46:55 thor systemd[1]: Started Session c450 of user root. Jan 15 09:46:55 thor systemd[1]: session-c450.scope: Succeeded. Jan 15 09:46:55 thor upsmon[2232]: Poll UPS [nutmonitor@localhost] failed - [nutmonitor] does not exist on server localhost Questions: 1) I have two important VMs that have snapshots that I need to boot up. Is their a means with an HCI configuration to manually start the VMs without oVirt engine being up? 2) Is their a means to debug what is going on with the engine failing to start to repair (I hate reloading as the only fix for systems) 3) Is their a means to re-deploy HCI setup wizard, but use the "engine" volume and so retain the VMs and templates?

4 19

VG issue / Non Operational
by Christian Reiss 18 Jan '21

18 Jan '21

Hey folks, quick (I hope) question: On my 3-node cluster I am swapping out all the SSDs with fewer but higher capacity ones. So I took one node down (maintenance, stop), then removed all SSDs, set up a new RAID, set up lvm and gluster, let it resync. Gluster health status shows no unsynced entries. Uppon going from maintenance to online from ovirt management It goes into non-operational status, vdsm log on the node shows: 2021-01-17 11:13:29,051+0100 INFO (jsonrpc/6) [api.host] START getAllVmStats() from=::1,48580 (api:48) 2021-01-17 11:13:29,051+0100 INFO (jsonrpc/6) [api.host] FINISH getAllVmStats return={'status': {'message': 'Done', 'code': 0}, 'statsList': (suppressed)} from=::1,48580 (api:54) 2021-01-17 11:13:29,052+0100 INFO (jsonrpc/6) [jsonrpc.JsonRpcServer] RPC call Host.getAllVmStats succeeded in 0.00 seconds (__init__:312) 2021-01-17 11:13:30,420+0100 WARN (monitor/4a62cdb) [storage.LVM] Reloading VGs failed (vgs=[u'4a62cdb4-b314-4c7f-804e-8e7275518a7f'] rc=5 out=[] err=[' Volume group "4a62cdb4-b314-4c7f-804e-8e7275518a7f" not found', ' Cannot process volume group 4a62cdb4-b314-4c7f-804e-8e7275518a7f']) (lvm:470) 2021-01-17 11:13:30,424+0100 ERROR (monitor/4a62cdb) [storage.Monitor] Setting up monitor for 4a62cdb4-b314-4c7f-804e-8e7275518a7f failed (monitor:330) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/storage/monitor.py", line 327, in _setupLoop self._setupMonitor() File "/usr/lib/python2.7/site-packages/vdsm/storage/monitor.py", line 349, in _setupMonitor self._produceDomain() File "/usr/lib/python2.7/site-packages/vdsm/utils.py", line 159, in wrapper value = meth(self, *a, **kw) File "/usr/lib/python2.7/site-packages/vdsm/storage/monitor.py", line 367, in _produceDomain self.domain = sdCache.produce(self.sdUUID) File "/usr/lib/python2.7/site-packages/vdsm/storage/sdc.py", line 110, in produce domain.getRealDomain() File "/usr/lib/python2.7/site-packages/vdsm/storage/sdc.py", line 51, in getRealDomain return self._cache._realProduce(self._sdUUID) File "/usr/lib/python2.7/site-packages/vdsm/storage/sdc.py", line 134, in _realProduce domain = self._findDomain(sdUUID) File "/usr/lib/python2.7/site-packages/vdsm/storage/sdc.py", line 151, in _findDomain return findMethod(sdUUID) File "/usr/lib/python2.7/site-packages/vdsm/storage/sdc.py", line 176, in _findUnfetchedDomain raise se.StorageDomainDoesNotExist(sdUUID) I assume due to the changed LVM UUID it fails, right? Can I someone fix/change the UUID and get the node back up again? It does not seem to be a major issue, to be honest. I can see the gluster mount (what ovirt mounts when it onlines a node) already, and gluster is happy too. Any help is appreciated! -Chris. -- with kind regards, mit freundlichen Gruessen, Christian Reiss

2 4

encrypted GENEVE traffic
by Pavel Nakonechnyi 18 Jan '21

18 Jan '21

Dear oVirt Community, From my understanding oVirt does not support Open vSwitch IPSEC tunneling for GENEVE traffic (which is described on pages http://docs.openvswitch.org/en/latest/howto/ipsec/ and http://docs.openvswitch.org/en/latest/tutorials/ipsec/) Are there plans to introduce such support? (or explicitly not to..) Is it possible to somehow manually configure such tunneling for existing virtual networks? (even in a limited way) Alternatively, is it possible to deploy oVirt on top of the tunneled (i.e. via VXLAN, IPSec) interfaces? This will allow to encrypt all management traffic. Such requirement arises when using oVirt deployment on third-party premises with untrusted network. Thank in advance for any clarifications. :) -- WBR, Pavel +32478910884

2 7