After a few tricky power issues at a site in a less developed country, I had to restart my 3 node ovirt cluster with hosted engine. Everything seemed to come up fine, but that night when my scheduled snapshots/backups etc ran (vProtect) some weird things happened. It created a couple snapshots and couldn't copy them saying disk is locked (even though in the GUI no disks or snapshots were locked)
After a couple tries all of a sudden the whole VM is 'locked' this means I can't migrate it, cant start it (if it shuts down) couldn't remove old snapshots etc. I had this happen on another VM and my only solution there was to clone it, but now its happened to all of them and im not sure why.
I have run the db utility on command line to unlock everything, nothing is listed as locked, but I still cant run any operations on the VM's. I even cloned them to get them up and running again, but I can't delete the old VM still sitting there (or the disk, snapshots or anything) just keep getting VM is locked.
How the hell do I force an unlock of these entities when everything tells me its not locked? I'm almost at a point where I want to back up all VM's and start again but i'd much rather learn some more so I can manage these issues in future.
Any help is appreciated!
I am trying to pass through a USB Dongle to a Windows virtual machine in
ovirt 4.3.6. This will work if these options aren't used. Below is the
output of lsusb with no iommu enable:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 1604:10c0 Tascam
Bus 001 Device 004: ID 1604:10c0 Tascam
Bus 001 Device 003: ID 1604:10c0 Tascam
Bus 001 Device 002: ID 07f2:0001 Microcomputer Applications, Inc. KEYLOK II
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
The device I am passing through is Bus 001 Device 002.
This is the error I get in vdsmd.log:
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 867, in
File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 2890, in
File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 2466, in
File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 2480, in
File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 2448, in
line 94, in update_device_info
426, in update_device_info
vm, device_conf, device_xml)
223, in update_from_xml
if host_address == dev.hostAddress:
AttributeError: 'MdevDevice' object has no attribute 'hostAddress'
2019-11-18 18:20:06,173-0600 INFO (vm/9944089c) [virt.vm]
(vmId='9944089c-2109-4352-a0c6-7d0d9e04bb3f') Changed state to Down:
'MdevDevice' object has no attribute 'hostAddress' (code=1) (vm:1690)
I am using kernel 3.10.0-957.12.1.el7.x86_64
vdsm is vdsm-4.30.33-1.el7.x86_64
libvirt is libvirt-5.0.0-1.el7.x86_64
qemu is qemu-img-ev-2.12.0-33.1.el7.x86_64
Any help with this issue would be appreciated.
I migrated a hosted ovirt-engine to a standalone machine. To do so, I created a backup with scope=all and imported this back-up into a newly installed engine.
Everything was working fine. Not much later, I made a mistake and wanted to start over, so I decided to do an engine-cleanup and re-import my back-up.
However, when I perform the engine-cleanup, I get this error message:
[ ERROR ] It seems that you are running your engine inside of the hosted-engine VM and are not in "Global Maintenance" mode.
In that case you should put the system into the "Global Maintenance" mode before running engine-setup, or the hosted-engine HA agent might kill the machine, which might corrupt your data.
This is not true. The engine is now running as a standalone server.
There must be a config parameter somewhere in a config file or in the database that tells the engine what mode it is running in, but I haven't found it yet.
I can't find any documentation for this issue, all migration guides tell you how to migrate from standalone to hosted engine, not the other way around.
How can I fix this?
i can't find the documentation on howto recover from a single host OS disk failure in a 3 node HCI cluster.
I already searched the ovirt, RHV and RHHI documentation but i can't find the corresponding documentation.
So can anyone please give me some hints?
In our dev lab i have 3 servers with 2 disks each. sda for ovirt node and sdb for gluster. Let's assume the disk sda of a single node is defunct and needs to be replaced.
So i grab a new disk and reinstall ovirt node from PXE.
After the installation is finished i would like to reinstall the host from ovirt admin portal, but that doesn't work because of an invalid fingerprint.
So how can i re-add that host to ovirt and gluster?
I'm having trouble to create a storage ISO Domain and attach it to a Datacenter. It just give me this error message:
Error while executing action Attach Storage Domain: Could not obtain lock
Also the oVirt's Engine log files show this error message: "setsid: failed to execute /usr/bin/ionice: Permission denied", but I was unable to identify what exactly it's trying to do to get this permission denied.
2019-11-14 16:46:07,779-03 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-7388) [86161370-2aaa-4eff-9aab-c184bdf5bb98] EVENT_ID: IRS_BROKER_COMMAND_FAILURE(10,803), VDSM command AttachStorageDomainVDS failed: Cannot obtain lock: u"id=e6b34c42-0ca6-41f4-be3e-3c9b2af1747b, rc=1, out=, err=['setsid: failed to execute /usr/bin/ionice: Permission denied']"
This behavior just happens on ISO Domains, while Data Domains works fine. I have read oVirt documentation and searched everywhere but I was unable to find the solution for this issue.
I'm using CentOS 7 with last update of all packages (oVirt version 18.104.22.168). Please help!
Ivan de Gusmão Apolonio