oVirt fails to update OVF
by Jürgen Walch
Hi everybody,
we are running an oVirt 4.3.10 production cluster with 9 hosts and 5 datastore domains.
Since yesterday we get error messages
26.02.2021 02:00:48 VDSM command SetVolumeDescriptionVDS failed: Could not acquire resource. Probably resource factory threw an exception.: ()
26.02.2021 02:00:48 Failed to update OVF disks 5aa438e3-8d22-4b6c-bccf-a843151ca0be, OVF data isn't updated on those OVF stores (Data Center datacenter01, Storage Domain vmstore13).
26.02.2021 02:00:48 Failed to update VMs/Templates OVF data for Storage Domain vmstore13 in Data Center datacenter01.
every hour.
Only one domain (vmstore13) is affected, this domain is (like 3 others in the cluster) based on glusterfs.
Trying to update the OVF's manually from the engine web-gui leads to the same result followed by (a misleading)
26.02.2021 02:00:49 OVF_STORE for domain vmstore13 was updated by admin@internal-authz.
The vm's with discs on the affected domain are running fine, snapshots are working.
So far I have tried to move the SPM role to another host. This succeeded, but the error messages persist.
The vdsm log on the SPM host contains something like
2021-02-26 03:00:57,701+0100 INFO (jsonrpc/2) [vdsm.api] START setVolumeDescription(sdUUID=u'9f731135-f5d9-4609-9e3b-fa9cae75e314', spUUID=u'33e8dc9e-8bc8-11ea-bd76-00163e741033', imgUUID=u'5aa438e3-8d22-4b6c-bccf-a843151ca0be', volUUID=u'0795e58c-4960-413a-a0b4-e8a6d547fda5', description=u'{"Updated":false,"Last Updated":"Wed Feb 24 17:48:17 CET 2021","Storage Domains":[{"uuid":"9f731135-f5d9-4609-9e3b-fa9cae75e314"}],"Disk Description":"OVF_STORE"}', options=None) from=::ffff:10.70.1.1,46968, flow_id=1f314676, task_id=9101db01-b4f0-447e-a5a9-b6af76278d55 (api:48)
2021-02-26 03:00:57,712+0100 ERROR (jsonrpc/2) [storage.VolumeManifest] [Errno 116] Stale file handle (fileVolume:155)
for each error, I have attached the relevant part of vdsm.log.
Has anyone experienced this behaviour before and can provide help ?
--
juergen
4 years, 2 months
oVirt 4.2 cluster upgrade
by Fedele Stabile
I have a 3 node oVirt 4.2.1 cluster,
i'm using a self-hosted engine architecture and
storage-engine is on a glusterfs replica 3
of the cluster.
The oldest CPU is SandyBridge family (E5-2609)
and incidentally I have connectivity problems with IPMI NIC of one node,
but Hosted Engine HA is enabled and working.
Is it safe to upgrade to the last oVirt 4.4 without a down of vm running on the cluster?
May I just click on the button
Upgrade
that appears on the host page?
4 years, 2 months
VDI and ovirt
by cpo cpo
Is anyone using Ovirt for a Windows 10 VDI deployment? If so are you using a connection broker? If you are what are you using?
Thanks for your time
4 years, 2 months
[ANN] oVirt 4.4.5 Seventh Release Candidate is now available for testing
by Lev Veyde
oVirt 4.4.5 Seventh Release Candidate is now available for testing
The oVirt Project is pleased to announce the availability of oVirt 4.4.5
Seventh Release Candidate for testing, as of February 25th, 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/
--
Lev Veyde
Senior Software Engineer, RHCE | RHCVA | MCITP
Red Hat Israel
<https://www.redhat.com>
lev(a)redhat.com | lveyde(a)redhat.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
4 years, 2 months
Starting a defined VM on a different host
by lavi.buchnik＠exlibrisgroup.com
Hi,
I might be missing something here, but I'm looking for the right API way to start a defined VM on a different host.
The scenario is this:
1. VM is running under Cluster Affinity Host. and there is a need to cold migrate it to another host on that Affinity.
2. for that I will stop the VM.
3. And now I would like to start the VM on another host, I tried few ways like:
vm_service.start(
vm=types.Vm(
host=types.Host(
name='<host name>'
),
)
)
But VM keep starting on the current host.
Can you please show me the right way to do it.
Thanks,
Lavi
4 years, 2 months
FQDN is not reachable | oVirt 4.4.4
by Guillem Liarte
With ovirt-node-ng-installer-4.4.4-2020122111 el8 ISO
I have this setup:
10.91.197.132 ndoamsel001.home.lab
10.91.197.4 ndoamsel002.home.lab
10.91.196.132 ndoamsel003.home.lab
# Storage network - 10.0.1.0/24
# ndoamsel001, interface aggi.2001, IP address 10.0.1.1
# ndoamsel002, interface aggi.2003, IP address 10.0.1.2
# ndoamsel003, interface aggi.2003, IP address 10.0.1.3
10.0.1.1 ndoamsel001s.home.lab ndoamsel001s
10.0.1.2 ndoamsel002s.home.lab ndoamsel002s
10.0.1.3 ndoamsel003s.home.lab ndoamsel003s
# Virtual network - 10.0.2.0/24
# ndoamsel001, interface aggi.2002, IP address 10.0.1.1
# ndoamsel002, interface aggi.2007, IP address 10.0.1.2
# ndoamsel003, interface aggi.2007, IP address 10.0.1.3
10.0.2.1 ndoamsel001v.home.lab ndoamsel001v
10.0.2.2 ndoamsel002v.home.lab ndoamsel002v
10.0.2.3 ndoamsel003v.home.lab ndoamsel003v
----
Installing over Cockpit Gluster deployment HC:
"FQDN is not reachable"
And of course it is! All interfaces are pingable and accessible over SSH without problems.
I am accessing Cockpit from a 4rth, public IP, from a remote computer. So the client browser is remote, and the Cockpit is accessed from a public IP address. Is that the problem?
---
Is there a way to do the 3 node HC from the command line? I see no other error than that, where are the actual logs?
Thanks!
4 years, 2 months
Python SDK - get host VM is running on.
by darkman0101＠hotmail.com
I am having some issues figuring out how to get a list of VMs and the host that they are running on.
I seem to be able to get a reference to the host object, but can't see how to print the name of the host.
See the below code snippet:
#! /usr/bin/python
import ovirtsdk4 as sdk
import ovirtsdk4.types as types
connection = sdk.Connection(
url='https:/<redacted>:443/ovirt-engine/api',
username='admin@internal',
password='<redacted>',
ca_file='ovirt-engine_ca.crt',
)
vms_service = connection.system_service().vms_service()
vms = vms_service.list()
for vm in vms:
print("VM.name = " + vm.name)
vm_service = vms_service.vm_service(vm.id)
#vm = vm_service.get()
print(vm.status)
if vm.name == 'vmexample':
print("HERE")
print(vm.host)
print(vm.host.name)
connection.close()
OUTPUT:
VM.name = vmexample
up
HERE
<ovirtsdk4.types.Host object at 0x7f5ca250e810>
None
What am I missing?
Thanks,
Jason
4 years, 2 months
Q35: disk type view not consistent in edit vm and new disk pages
by Gianluca Cecchi
Hello,
if I create a VM and select Q35 machine type, still the General --> create
image option in edit phase doesn't show sata as an option.
Even if I create the VM without disks and then go to edit General -->
create, I only see IDE, VirtIO-SCSI and VirtIO.
Instead if I click VM name, DIsks --> New, I can select VirtIO-SCSI, VirtIO
and SATA
After the first disk (SATA in my case) has been created, now if I go and
edit VM --> General --> Instance Images + --> Create, I see consistent
options.
I think GUI experience could be improved.
Also because I can reproduce this workflow converging to an error (even if
IDE disks are not so common nowadays...):
New VM
In general I create an IDE disk
In System I select in Advanced parameters, Custom Chipset/Firmware Type Q35
(EFI or BIOS based)
go ahead
At the final OK I get the error:
Cannot add Virtual Disk: The disk interface is not supported by the VM OS:
Other OS.
The result is VM created but without the IDE disk as not supported in Q35
type.
Tested in 4.4.4
Gianluca
4 years, 2 months
