- Users - oVirt List Archives

Help needed
by less foobar 22 Jul '22

22 Jul '22

I'm installing self hosted engine and there is an error that I can't understand can somebody help me? The logs are here: https://termbin.com/vht61

3 6

HostedEngine Upgrade from 4.4.5.10 fails - dnf distrosync
by simon＠justconnect.ie 22 Jul '22

22 Jul '22

Hi All, No matter what I try I cannot update/upgrade my hosted engine. All mirrors are local and have been updated. I have changed the repo files to Stream and carried out a dnf update --nobest But I cannot go any further. # rpm -q ovirt-engine ovirt-engine-4.4.5.10-1.el8.noarch # cat /etc/centos* [root@ddmcomhartestengine yum.repos.d]# dnf distrosync Last metadata expiration check: 0:02:12 ago on Thu 21 Jul 2022 11:12:18 PM UTC. Error: Problem 1: package collectd-write_syslog-5.11.0-2.el8.x86_64 requires collectd(x86-64) = 5.11.0-2.el8, but none of the providers can be installed - collectd-5.11.0-2.el8.x86_64 does not belong to a distupgrade repository - problem with installed package collectd-write_syslog-5.11.0-2.el8.x86_64 - package collectd-5.11.0-2.el8.x86_64 is filtered out by exclude filtering Problem 2: package python3-ansible-runner-1.4.6-1.el8.noarch requires python3dist(pexpect) >= 4.6, but none of the providers can be installed - python3-pexpect-4.7.0-4.el8.noarch does not belong to a distupgrade repository - problem with installed package python3-ansible-runner-1.4.6-1.el8.noarch - package python3-pexpect-4.7.0-4.el8.noarch is filtered out by exclude filtering Problem 3: package python3-ansible-runner-1.4.6-1.el8.noarch requires python3dist(pexpect) >= 4.6, but none of the providers can be installed - cannot install both python3-pexpect-4.3.1-3.el8.noarch and python3-pexpect-4.7.0-4.el8.noarch - package ansible-runner-service-1.0.7-1.el8.noarch requires python3-ansible-runner, but none of the providers can be installed - cannot install the best update candidate for package python3-pexpect-4.7.0-4.el8.noarch - problem with installed package ansible-runner-service-1.0.7-1.el8.noarch - package python3-ansible-runner-1.4.6-1.el8.noarch is filtered out by exclude filtering - package python3-pexpect-4.7.0-4.el8.noarch is filtered out by exclude filtering Problem 4: package collectd-write_syslog-5.11.0-2.el8.x86_64 requires collectd(x86-64) = 5.11.0-2.el8, but none of the providers can be installed - cannot install both collectd-5.9.0-5.el8.x86_64 and collectd-5.11.0-2.el8.x86_64 - package ovirt-engine-4.4.5.10-1.el8.noarch requires collectd-write_syslog, but none of the providers can be installed - cannot install the best update candidate for package collectd-5.11.0-2.el8.x86_64 - problem with installed package ovirt-engine-4.4.5.10-1.el8.noarch - package collectd-write_syslog-5.12.0-7.el8s.x86_64 is filtered out by exclude filtering - package collectd-5.11.0-2.el8.x86_64 is filtered out by exclude filtering - package collectd-write_syslog-5.10.0-1.el8.x86_64 is filtered out by exclude filtering - package collectd-write_syslog-5.10.0-3.el8.x86_64 is filtered out by exclude filtering - package collectd-write_syslog-5.11.0-1.el8.x86_64 is filtered out by exclude filtering - package collectd-write_syslog-5.11.0-2.el8.x86_64 is filtered out by exclude filtering Problem 5: package collectd-write_syslog-5.11.0-2.el8.x86_64 requires collectd(x86-64) = 5.11.0-2.el8, but none of the providers can be installed - cannot install both collectd-5.9.0-5.el8.x86_64 and collectd-5.11.0-2.el8.x86_64 - package ovirt-engine-4.4.5.10-1.el8.noarch requires collectd-write_syslog, but none of the providers can be installed - package collectd-disk-5.9.0-5.el8.x86_64 requires collectd(x86-64) = 5.9.0-5.el8, but none of the providers can be installed - package ovirt-engine-backend-4.4.5.10-1.el8.noarch requires ovirt-engine = 4.4.5.10-1.el8, but none of the providers can be installed - cannot install the best update candidate for package collectd-disk-5.11.0-2.el8.x86_64 - problem with installed package ovirt-engine-backend-4.4.5.10-1.el8.noarch - package ovirt-engine-4.4.5.10-1.el8.noarch is filtered out by exclude filtering - package collectd-write_syslog-5.12.0-7.el8s.x86_64 is filtered out by exclude filtering - package collectd-5.11.0-2.el8.x86_64 is filtered out by exclude filtering - package collectd-write_syslog-5.10.0-1.el8.x86_64 is filtered out by exclude filtering - package collectd-write_syslog-5.10.0-3.el8.x86_64 is filtered out by exclude filtering - package collectd-write_syslog-5.11.0-1.el8.x86_64 is filtered out by exclude filtering - package collectd-write_syslog-5.11.0-2.el8.x86_64 is filtered out by exclude filtering Problem 6: package collectd-write_syslog-5.11.0-2.el8.x86_64 requires collectd(x86-64) = 5.11.0-2.el8, but none of the providers can be installed - cannot install both collectd-5.9.0-5.el8.x86_64 and collectd-5.11.0-2.el8.x86_64 - package ovirt-engine-4.4.5.10-1.el8.noarch requires collectd-write_syslog, but none of the providers can be installed - package collectd-postgresql-5.9.0-5.el8.x86_64 requires collectd(x86-64) = 5.9.0-5.el8, but none of the providers can be installed - package ovirt-engine-dbscripts-4.4.5.10-1.el8.noarch requires ovirt-engine = 4.4.5.10-1.el8, but none of the providers can be installed - cannot install the best update candidate for package collectd-postgresql-5.11.0-2.el8.x86_64 - problem with installed package ovirt-engine-dbscripts-4.4.5.10-1.el8.noarch - package ovirt-engine-4.4.5.10-1.el8.noarch is filtered out by exclude filtering - package collectd-write_syslog-5.12.0-7.el8s.x86_64 is filtered out by exclude filtering - package collectd-5.11.0-2.el8.x86_64 is filtered out by exclude filtering - package collectd-write_syslog-5.10.0-1.el8.x86_64 is filtered out by exclude filtering - package collectd-write_syslog-5.10.0-3.el8.x86_64 is filtered out by exclude filtering - package collectd-write_syslog-5.11.0-1.el8.x86_64 is filtered out by exclude filtering - package collectd-write_syslog-5.11.0-2.el8.x86_64 is filtered out by exclude filtering Problem 7: package collectd-write_syslog-5.11.0-2.el8.x86_64 requires collectd(x86-64) = 5.11.0-2.el8, but none of the providers can be installed - cannot install both collectd-5.9.0-5.el8.x86_64 and collectd-5.11.0-2.el8.x86_64 - package ovirt-engine-4.4.5.10-1.el8.noarch requires collectd-write_syslog, but none of the providers can be installed - package collectd-write_http-5.9.0-5.el8.x86_64 requires collectd(x86-64) = 5.9.0-5.el8, but none of the providers can be installed - package ovirt-engine-restapi-4.4.5.10-1.el8.noarch requires ovirt-engine = 4.4.5.10-1.el8, but none of the providers can be installed - cannot install the best update candidate for package collectd-write_http-5.11.0-2.el8.x86_64 - problem with installed package ovirt-engine-restapi-4.4.5.10-1.el8.noarch - package ovirt-engine-4.4.5.10-1.el8.noarch is filtered out by exclude filtering - package collectd-write_syslog-5.12.0-7.el8s.x86_64 is filtered out by exclude filtering - package collectd-5.11.0-2.el8.x86_64 is filtered out by exclude filtering - package collectd-write_syslog-5.10.0-1.el8.x86_64 is filtered out by exclude filtering - package collectd-write_syslog-5.10.0-3.el8.x86_64 is filtered out by exclude filtering - package collectd-write_syslog-5.11.0-1.el8.x86_64 is filtered out by exclude filtering - package collectd-write_syslog-5.11.0-2.el8.x86_64 is filtered out by exclude filtering Problem 8: cannot install both collectd-5.9.0-5.el8.x86_64 and collectd-5.11.0-2.el8.x86_64 - package collectd-write_syslog-5.11.0-2.el8.x86_64 requires collectd(x86-64) = 5.11.0-2.el8, but none of the providers can be installed - package collectd-disk-5.9.0-5.el8.x86_64 requires collectd(x86-64) = 5.9.0-5.el8, but none of the providers can be installed - package ovirt-engine-4.4.5.10-1.el8.noarch requires collectd-write_syslog, but none of the providers can be installed - package ovirt-engine-4.4.5.10-1.el8.noarch requires collectd-disk, but none of the providers can be installed - package ovirt-engine-setup-plugin-ovirt-engine-4.4.5.10-1.el8.noarch requires ovirt-engine >= 4.4.0, but none of the providers can be installed - collectd-disk-5.11.0-2.el8.x86_64 does not belong to a distupgrade repository - problem with installed package ovirt-engine-setup-plugin-ovirt-engine-4.4.5.10-1.el8.noarch - package ovirt-engine-4.4.0.3-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.1-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.10-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.2-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.3-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.4-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.5-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.6-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.7-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.8-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.10.4-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.10.5-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.10.6-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.10.7-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.2.6-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.10-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.11-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.12-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.3-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.4-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.5-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.6-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.7-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.8-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.9-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.4-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.4.1-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.4.2-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.4.3-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.4.4-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.4.5-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.4.7-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.5.10-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.5.11-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.6.6-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.6.7-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.6.8-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.7.6-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.7.7-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.8.4-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.8.5-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.8.6-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.9.3-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.9.4-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.9.5-1.el8.noarch is filtered out by exclude filtering - package collectd-disk-5.12.0-7.el8s.x86_64 is filtered out by exclude filtering - package collectd-write_syslog-5.12.0-7.el8s.x86_64 is filtered out by exclude filtering - package collectd-5.11.0-2.el8.x86_64 is filtered out by exclude filtering - package collectd-disk-5.10.0-1.el8.x86_64 is filtered out by exclude filtering - package collectd-disk-5.10.0-3.el8.x86_64 is filtered out by exclude filtering - package collectd-disk-5.11.0-1.el8.x86_64 is filtered out by exclude filtering - package collectd-disk-5.11.0-2.el8.x86_64 is filtered out by exclude filtering - package collectd-write_syslog-5.10.0-1.el8.x86_64 is filtered out by exclude filtering - package collectd-write_syslog-5.10.0-3.el8.x86_64 is filtered out by exclude filtering - package collectd-write_syslog-5.11.0-1.el8.x86_64 is filtered out by exclude filtering - package collectd-write_syslog-5.11.0-2.el8.x86_64 is filtered out by exclude filtering Problem 9: cannot install both collectd-5.9.0-5.el8.x86_64 and collectd-5.11.0-2.el8.x86_64 - package collectd-write_syslog-5.11.0-2.el8.x86_64 requires collectd(x86-64) = 5.11.0-2.el8, but none of the providers can be installed - package collectd-postgresql-5.9.0-5.el8.x86_64 requires collectd(x86-64) = 5.9.0-5.el8, but none of the providers can be installed - package ovirt-engine-4.4.5.10-1.el8.noarch requires collectd-write_syslog, but none of the providers can be installed - package ovirt-engine-4.4.5.10-1.el8.noarch requires collectd-postgresql, but none of the providers can be installed - package ovirt-engine-tools-4.4.5.10-1.el8.noarch requires ovirt-engine = 4.4.5.10-1.el8, but none of the providers can be installed - collectd-postgresql-5.11.0-2.el8.x86_64 does not belong to a distupgrade repository - problem with installed package ovirt-engine-tools-4.4.5.10-1.el8.noarch - package ovirt-engine-4.4.5.10-1.el8.noarch is filtered out by exclude filtering - package collectd-postgresql-5.12.0-7.el8s.x86_64 is filtered out by exclude filtering - package collectd-write_syslog-5.12.0-7.el8s.x86_64 is filtered out by exclude filtering - package collectd-5.11.0-2.el8.x86_64 is filtered out by exclude filtering - package collectd-postgresql-5.10.0-1.el8.x86_64 is filtered out by exclude filtering - package collectd-postgresql-5.10.0-3.el8.x86_64 is filtered out by exclude filtering - package collectd-postgresql-5.11.0-1.el8.x86_64 is filtered out by exclude filtering - package collectd-postgresql-5.11.0-2.el8.x86_64 is filtered out by exclude filtering - package collectd-write_syslog-5.10.0-1.el8.x86_64 is filtered out by exclude filtering - package collectd-write_syslog-5.10.0-3.el8.x86_64 is filtered out by exclude filtering - package collectd-write_syslog-5.11.0-1.el8.x86_64 is filtered out by exclude filtering - package collectd-write_syslog-5.11.0-2.el8.x86_64 is filtered out by exclude filtering Problem 10: cannot install both collectd-5.9.0-5.el8.x86_64 and collectd-5.11.0-2.el8.x86_64 - package collectd-write_syslog-5.11.0-2.el8.x86_64 requires collectd(x86-64) = 5.11.0-2.el8, but none of the providers can be installed - package collectd-write_http-5.9.0-5.el8.x86_64 requires collectd(x86-64) = 5.9.0-5.el8, but none of the providers can be installed - package ovirt-engine-4.4.5.10-1.el8.noarch requires collectd-write_syslog, but none of the providers can be installed - package ovirt-engine-4.4.5.10-1.el8.noarch requires collectd-write_http, but none of the providers can be installed - package ovirt-engine-webadmin-portal-4.4.5.10-1.el8.noarch requires ovirt-engine = 4.4.5.10-1.el8, but none of the providers can be installed - collectd-write_http-5.11.0-2.el8.x86_64 does not belong to a distupgrade repository - problem with installed package ovirt-engine-webadmin-portal-4.4.5.10-1.el8.noarch - package ovirt-engine-4.4.5.10-1.el8.noarch is filtered out by exclude filtering - package collectd-write_http-5.12.0-7.el8s.x86_64 is filtered out by exclude filtering - package collectd-write_syslog-5.12.0-7.el8s.x86_64 is filtered out by exclude filtering - package collectd-5.11.0-2.el8.x86_64 is filtered out by exclude filtering - package collectd-write_http-5.10.0-1.el8.x86_64 is filtered out by exclude filtering - package collectd-write_http-5.10.0-3.el8.x86_64 is filtered out by exclude filtering - package collectd-write_http-5.11.0-1.el8.x86_64 is filtered out by exclude filtering - package collectd-write_http-5.11.0-2.el8.x86_64 is filtered out by exclude filtering - package collectd-write_syslog-5.10.0-1.el8.x86_64 is filtered out by exclude filtering - package collectd-write_syslog-5.10.0-3.el8.x86_64 is filtered out by exclude filtering - package collectd-write_syslog-5.11.0-1.el8.x86_64 is filtered out by exclude filtering - package collectd-write_syslog-5.11.0-2.el8.x86_64 is filtered out by exclude filtering (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@ddmcomhartestengine yum.repos.d]# If I add --allowerasing then I get the following: [root@ddmcomhartestengine yum.repos.d]# dnf distrosync --allowerasing Last metadata expiration check: 0:00:22 ago on Thu 21 Jul 2022 11:12:18 PM UTC. Dependencies resolved. ================================================================================================================================================================================================ Package Architecture Version Repository Size ================================================================================================================================================================================================ Reinstalling: python3-websocket-client noarch 0.56.0-5.el8 epel 61 k Removing dependent packages: ansible-runner-service noarch 1.0.7-1.el8 @ovirt-4.4-centos-ovirt44 259 k collectd-write_syslog x86_64 5.11.0-2.el8 @ovirt-4.4-centos-opstools 22 k ovirt-engine noarch 4.4.5.10-1.el8 @ovirt-4.4 38 M ovirt-engine-backend noarch 4.4.5.10-1.el8 @ovirt-4.4 8.2 M ovirt-engine-dbscripts noarch 4.4.5.10-1.el8 @ovirt-4.4 1.6 M ovirt-engine-restapi noarch 4.4.5.10-1.el8 @ovirt-4.4 25 M ovirt-engine-setup noarch 4.4.5.10-1.el8 @ovirt-4.4 671 ovirt-engine-setup-plugin-cinderlib noarch 4.4.5.10-1.el8 @ovirt-4.4 66 k ovirt-engine-setup-plugin-imageio noarch 4.4.5.10-1.el8 @ovirt-4.4 21 k ovirt-engine-setup-plugin-ovirt-engine noarch 4.4.5.10-1.el8 @ovirt-4.4 783 k ovirt-engine-setup-plugin-vmconsole-proxy-helper noarch 4.4.5.10-1.el8 @ovirt-4.4 60 k ovirt-engine-tools noarch 4.4.5.10-1.el8 @ovirt-4.4 467 k ovirt-engine-ui-extensions noarch 1.2.5-1.el8 @ovirt-4.4 38 M ovirt-engine-vmconsole-proxy-helper noarch 4.4.5.10-1.el8 @ovirt-4.4 16 k ovirt-engine-webadmin-portal noarch 4.4.5.10-1.el8 @ovirt-4.4 294 M python3-ansible-runner noarch 1.4.6-1.el8 @ovirt-4.4-centos-ovirt44 341 k Downgrading: collectd x86_64 5.9.0-5.el8 epel 716 k collectd-disk x86_64 5.9.0-5.el8 epel 35 k collectd-postgresql x86_64 5.9.0-5.el8 epel 46 k collectd-write_http x86_64 5.9.0-5.el8 epel 43 k javapackages-filesystem noarch 5.3.0-1.module_el8.0.0+11+5b8c10bd appstream 30 k javapackages-tools noarch 5.3.0-1.module_el8.0.0+11+5b8c10bd appstream 44 k nodejs x86_64 1:10.23.1-1.module_el8.4.0+645+9ce14ba2 appstream 8.9 M nodejs-full-i18n x86_64 1:10.23.1-1.module_el8.4.0+645+9ce14ba2 appstream 7.3 M npm x86_64 1:6.14.10-1.10.23.1.1.module_el8.4.0+645+9ce14ba2 appstream 3.7 M python3-bcrypt x86_64 3.1.6-2.el8.1 epel 44 k python3-cairo x86_64 1.16.3-6.el8 appstream 90 k python3-lockfile noarch 1:0.11.0-13.el8.1 epel 38 k python3-paramiko noarch 2.4.3-1.el8 epel 289 k python3-pbr noarch 5.1.2-3.el8 epel 88 k python3-pexpect noarch 4.3.1-3.el8 appstream 138 k python3-psutil x86_64 5.4.3-11.el8 appstream 373 k python3-pyasn1 noarch 0.3.7-6.el8 appstream 126 k python3-pyasn1-modules noarch 0.3.7-6.el8 appstream 110 k python3-pyyaml x86_64 3.12-12.el8 baseos 193 k python3-six noarch 1.11.0-8.el8 baseos 38 k Enabling module streams: javapackages-runtime 201801 Transaction Summary ================================================================================================================================================================================================ Remove 16 Packages Downgrade 20 Packages Total download size: 22 M Is this ok [y/N]: Any ideas please? Thanks Simon...

1 0

cockpit-ovirt-dashboard
by less foobar 21 Jul '22

21 Jul '22

When you try to follow the documentation for rhel 9 you can't install the cockpit-ovirt-dashboard. The package is missing. Even on ovirt version 9 the dashboard is missing from the cockpit interface.

2 2

node non-operational can't connect to gluster domains
by Staniforth, Paul 20 Jul '22

20 Jul '22

Hello I have a problem activating a host running ovirt-node-ng-4.4.10.2. The engine is running 4.5.1.3-1.el8 The error message in the host event log has Activation of host *.* initiated by admin@internal-authz. Failed to connect Host *.* to the Storage Domains hosted_storage. Failed to connect Host *.* to the Storage Domains extra,vmstore,data. Failed to connect Host *.* to Storage Servers Failed to connect Host *.* to Storage Pool Default Host *.* cannot access the Storage Domain(s) <UNKNOWN> attached to the Data Center Default. Setting Host state to Non-Operational If I manually mount the gluster domains it activates. The othe 2 nodes activate without intervention. Thanks Paul S. To view the terms under which this email is distributed, please go to:- https://leedsbeckett.ac.uk/disclaimer/email

1 0

Template import in 4.5
by Gianluca Cecchi 20 Jul '22

20 Jul '22

Hello, I have a problem importing templates in downstream product 4.4-SP1 that should match in some way oVirt 4.5.x. I get a ui exception preventing me from importing the template. I have already opened a case for it (03270063). Just wondering if it can be a general problem and in particular an oVirt problem too. I have not at hand an oVirt 4.5 env. Can anyone in oVirt 4.5.x confirm that Template Import through export domains work as expected in that environment? In my case the template has been exported from a 4.4.x environment, so the perfect match would be to export a template in 4.4 and then import it in 4.5 Thanks in advance Gianluca

3 4

Incorrect Max CPU's per VM in libvirt if cluster compatibility 4.6 or 4.7
by David Sekne 20 Jul '22

20 Jul '22

Hello, I recently upgraded our cluster from 4.3 to 4.5 (4.5.1.3-1.el8), I raised the cluster compatibility afterwards to 4.7 as well. I noticed that the CPU hot plugging does not work above 16 CPU's if cluster compatibility is set to 4.6 or 4.7. Error I get is: Failed to hot set number of CPUS to VM testVM-3. Underlying error message: invalid argument: requested vcpus is greater than max allowable vcpus for the live domain: 32 > 16 Issue here I believe is that the MaxNumOfVmSockets values set on the engine per cluster version is not correctly set on libvirt when VM is started. My values on the engine: MaxNumOfVmSockets: 32 version: 4.2 MaxNumOfVmSockets: 32 version: 4.3 MaxNumOfVmSockets: 32 version: 4.4 MaxNumOfVmSockets: 32 version: 4.5 MaxNumOfVmSockets: 64 version: 4.6 MaxNumOfVmSockets: 10000 version: 4.7 Values on libvirt for VM's for all cluster compatibility versions: 4.3 <vcpu placement='static' current='4'>32</vcpu> 4.4 <vcpu placement='static' current='4'>32</vcpu> 4.5 <vcpu placement='static' current='4'>32</vcpu> 4.6 <vcpu placement='static' current='4'>16</vcpu> 4.7 <vcpu placement='static' current='4'>16</vcpu> Is anyone else experiencing this issue (possible BUG)? Regards, David

2 4

GUIDE: oVirt 4.4.7 to 4.4.10 Upgrade + Switch to CentOS Stream
by Andrei Verovski 19 Jul '22

19 Jul '22

Hi, Having a LOT of trouble upgrading oVirt to 4.4.10 while switching to CentOS Stream, I posted a short guide in my blog. https://www.vacuum-tube.eu/wp/?p=399 Look at entry: [2022-07-19] oVirt 4.4.7 to 4.4.10 Upgrade + Switch to CentOS Stream Thanks for everyone who helped me !

1 0

extract qcow2 or raw disks from ovirt OVA
by dhanaraj.ramesh＠yahoo.com 19 Jul '22

19 Jul '22

Hi Team May I know how do I extract qcow2 or raw disks out of ovirt OVA file please. Basically I want to move some of the vms to Nutanix AHV or Vmware cluster, for that I need either qcow2 or raw disks of each of the running vms.

2 1

SSO error during hosted engine deployment with 4.5.1
by Dax Kelson 19 Jul '22

19 Jul '22

On the final setup of using the cockpit ovirt wizard to install the hosted engine with 4.5.1, this occurs: [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Obtain SSO token using username/password credentials] [ ERROR ] fatal: [localhost]: FAILED! => {"msg": "The field 'environment' has an invalid value, which includes an undefined variable. The error was: 'he_admin_username' is undefined\n\nThe error appears to be in '/usr/share/ansible/collections/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/auth_sso.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: Obtain SSO token using username/password credentials\n ^ here\n"}

3 2

Grafana login
by markeczzz＠gmail.com 19 Jul '22

19 Jul '22

Hi! I have installed oVirt 4.5.1 and I am using KeyCloak to login. I have created users in keycloak and with them i can login to ovirt Manager, but I can't login to Grafana. Also, I can login to Keycloak only with user "admin" and not with newly created users. I have tried to add @ovirt or @ovirt@internal, but every time i get "Invalid username or password" I haven't really changed default options in keycloak and can't find good manual for ovirt + keyclock. Can anyone tell me how to create user in keycloak that cant login to Grafana? Regards,

3 3

Please help: Failure Restoring Data on Clean Engine After Migration
by Andrei Verovski 19 Jul '22

19 Jul '22

Hi, I have oVirt engine 4.4.7 running on dedicated PC (not hosted engine). After several unsuccessful upgrade attempts of 4.4.7 to 4.4.10 decided to install clean 4.4.10 and migrate data. On old engine engine-backup --scope=all --mode=backup On new engine engine-backup --mode=restore --provision-all-databases --no-restore-permissions --file=ovirt-engine-backup-20220713160717.backup Result: [ ERROR ] Failed to execute stage 'Environment setup': Cannot connect to database for grafana using existing credentials: ovirt_engine_history_grafana@localhost:5432 How to Remove Grafana Completely During Engine Migration, or skip it during backup? In fact it would be nice to delete it on active 4.4.7 setup, I don’t need it anyway. Thanks in advance. # — LOG ——————————————————————— Start of engine-backup with mode 'restore' scope: all archive file: ovirt-engine-backup-20220713160717.backup log file: /var/log/ovirt-engine-backup/ovirt-engine-restore-20220714170603.log Preparing to restore: - Unpacking file 'ovirt-engine-backup-20220713160717.backup' Restoring: - Files Provisioning PostgreSQL users/databases: - user 'engine', database 'engine' - user 'ovirt_engine_history', database 'ovirt_engine_history' Restoring: - Engine database 'engine' - Cleaning up temporary tables in engine database 'engine' - Updating DbJustRestored VdcOption in engine database - Resetting DwhCurrentlyRunning in dwh_history_timekeeping in engine database - Resetting HA VM status ------------------------------------------------------------------------------ Please note: The engine database was backed up at 2022-07-13 16:07:21.000000000 +0300 . Objects that were added, removed or changed after this date, such as virtual machines, disks, etc., are missing in the engine, and will probably require recovery or recreation. ------------------------------------------------------------------------------ - DWH database 'ovirt_engine_history' - Grafana database '/var/lib/grafana/grafana.db' You should now run engine-setup. Done. [root@node00 ovirt-engine-backup]# engine-setup [ INFO ] Stage: Initializing [ INFO ] Stage: Environment setup Configuration files: /etc/ovirt-engine-setup.conf.d/10-packaging-jboss.conf, /etc/ovirt-engine-setup.conf.d/10-packaging.conf, /etc/ovirt-engine-setup.conf.d/20-setup-ovirt-post.conf Log file: /var/log/ovirt-engine/setup/ovirt-engine-setup-20220714170757-7072xx.log Version: otopi-1.9.6 (otopi-1.9.6-1.el8) [ INFO ] The engine DB has been restored from a backup [ ERROR ] Failed to execute stage 'Environment setup': Cannot connect to database for grafana using existing credentials: ovirt_engine_history_grafana@localhost:5432 [ INFO ] Stage: Clean up Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20220714170757-7072xx.log [ INFO ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20220714170806-setup.conf' [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ ERROR ] Execution of setup failed

3 7

How to Fix: oVirt 4.4.10 Internal server error 500 after engine-setup (vdsm-jsonrpc-java )
by Andrei Verovski 19 Jul '22

19 Jul '22

Hi, Finally I managed to migrate 4.4.7 to fresh installation of 4.4.10. However, after successful engine-setup I’ve got 500 - Internal Server Error I found this: https://bugzilla.redhat.com/show_bug.cgi?id=1918022 Bug 1918022 - oVirt Manager is not loading after engine-setup Article suggested to downgrade vdsm-jsonrpc-java to 1.5.x. However, this is not possible: dnf --showduplicates list vdsm-jsonrpc-java dnf install vdsm-jsonrpc-java-1.5.7-1.el8 Last metadata expiration check: 0:39:52 ago on Fri 15 Jul 2022 02:32:36 PM EEST. Error: Problem: problem with installed package ovirt-engine-backend-4.4.10.7-1.el8.noarch - package ovirt-engine-backend-4.4.10.7-1.el8.noarch requires vdsm-jsonrpc-java >= 1.6.0, but none of the providers can be installed - cannot install both vdsm-jsonrpc-java-1.5.7-1.el8.noarch and vdsm-jsonrpc-java-1.6.0-1.el8.noarch - cannot install both vdsm-jsonrpc-java-1.6.0-1.el8.noarch and vdsm-jsonrpc-java-1.5.7-1.el8.noarch How to fix this? Thanks in advance. ***************** SERVER LOG ********************* 2022-07-15 14:45:44,969+03 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "engine.ear")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.subunit.\"engine.ear\".\"bll.jar\".component.Backend.START" => "java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance Caused by: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance Caused by: javax.ejb.EJBException: org.jboss.weld.exceptions.WeldException: WELD-000049: Unable to invoke protected void org.ovirt.engine.core.bll.TagsDirector.init() on org.ovirt.engine.core.bll.TagsDirector@648487d3 Caused by: org.jboss.weld.exceptions.WeldException: WELD-000049: Unable to invoke protected void org.ovirt.engine.core.bll.TagsDirector.init() on org.ovirt.engine.core.bll.TagsDirector@648487d3 Caused by: java.lang.reflect.InvocationTargetException Caused by: org.springframework.dao.InvalidDataAccessApiUsageException: Unable to determine the correct call signature - no procedure/function/signature for 'gettagsbyparent_id'"}} 2022-07-15 14:45:44,981+03 INFO [org.jboss.as.server] (ServerService Thread Pool -- 25) WFLYSRV0010: Deployed "restapi.war" (runtime-name : "restapi.war") 2022-07-15 14:45:44,982+03 INFO [org.jboss.as.server] (ServerService Thread Pool -- 25) WFLYSRV0010: Deployed "engine.ear" (runtime-name : "engine.ear") 2022-07-15 14:45:44,982+03 INFO [org.jboss.as.server] (ServerService Thread Pool -- 25) WFLYSRV0010: Deployed "apidoc.war" (runtime-name : "apidoc.war") 2022-07-15 14:45:44,982+03 INFO [org.jboss.as.server] (ServerService Thread Pool -- 25) WFLYSRV0010: Deployed "ovirt-web-ui.war" (runtime-name : "ovirt-web-ui.war") 2022-07-15 14:45:45,015+03 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report WFLYCTL0186: Services which failed to start: service jboss.deployment.subunit."engine.ear"."bll.jar".component.Backend.START: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance WFLYCTL0448: 2 additional services are down due to their dependencies being missing or failed

1 1

No valid network interface has been found
by naiajae＠icloud.com 19 Jul '22

19 Jul '22

Hey im kinda new to ovirt im getting this error when i try to create a "hosted engine" i hope this is where i can get help "FULL MSG" No valid network interface has been found If you are using Bonds or VLANs Use the following naming conventions: - VLAN interfaces: physical_device.VLAN_ID (for example, eth0.23, eth1.128, enp3s0.50) - Bond interfaces: bond*number* (for example, bond0, bond1) - VLANs on bond interfaces: bond*number*.VLAN_ID (for example, bond0.50, bond1.128) * Supported bond modes: active-backup, balance-xor, broadcast, 802.3ad * Networking teaming is not supported and will cause errors

1 0

Console does not work on run once
by suporte＠logicworks.pt 18 Jul '22

18 Jul '22

Hi, In run once, when open console nothing shows. But it works on any other VM. Version 4.5.1.3-1.el8 Any idea? -- Jose Ferradeira http://www.logicworks.pt

1 1

Cannot deserialize - engine doesn't start
by Giulio Casella 18 Jul '22

18 Jul '22

Hi guys, I'm in big troubles. Since last night my ovirt engine is unavailable (won't correctly start). Process ovirt-engine is running, and systemd doesn't complain (systemctl status is ok). Digging in engine.log I can find an error: 2022-07-13 09:57:48,314+02 ERROR [org.ovirt.engine.core.utils.serialization.json.JsonObjectDeserializer] (ServerService Thread Pool -- 45) [] Cannot deserialize { "@class" : "org.ovirt.engine.core.common.action.CreateSnapshotDiskParameters", "commandId" : [ "org.ovirt.engine.core.compat.Guid", { "uuid" : "6ae544f6-b608-4d8d-9f99-eabd5d5db0ad" } ], [...cut...] "domain" : "my.dom.ain"[truncated 5971 chars]; line: 72, column: 89] (through reference chain: org.ovirt.engine.core.common.action.CreateSnapshotDiskParameters["diskImagesMap"]) 2022-07-13 09:57:48,315+02 ERROR [org.ovirt.engine.core.bll.InitBackendServicesOnStartupBean] (ServerService Thread Pool -- 45) [] Failed to initialize backend: org.jboss.weld.exceptions.WeldException: WELD-000049: Unable to invoke public void org.ovirt.engine.core.bll.tasks.CommandContextsCacheImpl.initContextsMap() on org.ovirt.engine.core.bll.tasks.CommandContextsCacheImpl@3f52ccce [...cut...] During the night there was a job that was moving a disk (2.5TB) from a storage domain to another. I think it's related. Any ideas? TIA, gc

2 10

oVirt 4.5.1 Hyperconverge Gluster install fails
by david.lennox＠frontlinedigital.com.au 18 Jul '22

18 Jul '22

Hello all, I am hoping someone can help me with a oVirt installation that has just gotten the better of me after weeks of trying. After setting up ssh-keys and making sure each host is known to the primary host (sr-svr04), I go though Cockpit and "Configure Gluster storage and oVirt hosted engine", enter all of the details with <host>.san.lennoxconsulting.com.au for the storage network FQDN and <host>.core.lennoxconsulting.com.au for the public interfaces. Connectivity on each of the VLAN's test out as basically working (everything is pingable and ssh connections work) and the hosts are generally usable on the network. But the install ultimately dies with the following ansible error: ----------- gluster-deployment.log --------- : : TASK [gluster.infra/roles/backend_setup : Create volume groups] **************** task path: /etc/ansible/roles/gluster.infra/roles/backend_setup/tasks/vg_create.yml:63 failed: [sr-svr04.san.lennoxconsulting.com.au] (item={'key': 'gluster_vg_sdb', 'value': [{'vgname': 'gluster_vg_sdb', 'pvname': '/dev/sdb'}]}) => {"ansible_loop_var": "item", "changed": true, "cmd": ["vgcreate", "--dataalignment", "1536K", "-s", "1536K", "gluster_vg_sdb", "/dev/sdb"], "delta": "0:00:00.058528", "end": "2022-07-16 16:18:37.018563", "item": {"key": "gluster_vg_sdb", "value": [{"pvname": "/dev/sdb", "vgname": "gluster_vg_sdb"}]}, "msg": "non-zero return code", "rc": 5, "start": "2022-07-16 16:18:36.960035", "stderr": " A volume group called gluster_vg_sdb already exists.", "stderr_lines": [" A volume group called gluster_vg_sdb already exists."], "stdout": "", "stdout_lines": []} failed: [sr-svr05.san.lennoxconsulting.com.au] (item={'key': 'gluster_vg_sdb', 'value': [{'vgname': 'gluster_vg_sdb', 'pvname': '/dev/sdb'}]}) => {"ansible_loop_var": "item", "changed": true, "cmd": ["vgcreate", "--dataalignment", "1536K", "-s", "1536K", "gluster_vg_sdb", "/dev/sdb"], "delta": "0:00:00.057186", "end": "2022-07-16 16:18:37.784063", "item": {"key": "gluster_vg_sdb", "value": [{"pvname": "/dev/sdb", "vgname": "gluster_vg_sdb"}]}, "msg": "non-zero return code", "rc": 5, "start": "2022-07-16 16:18:37.726877", "stderr": " A volume group called gluster_vg_sdb already exists.", "stderr_lines": [" A volume group called gluster_vg_sdb already exists."], "stdout": "", "stdout_lines": []} failed: [sr-svr06.san.lennoxconsulting.com.au] (item={'key': 'gluster_vg_sdb', 'value': [{'vgname': 'gluster_vg_sdb', 'pvname': '/dev/sdb'}]}) => {"ansible_loop_var": "item", "changed": true, "cmd": ["vgcreate", "--dataalignment", "1536K", "-s", "1536K", "gluster_vg_sdb", "/dev/sdb"], "delta": "0:00:00.062212", "end": "2022-07-16 16:18:37.250371", "item": {"key": "gluster_vg_sdb", "value": [{"pvname": "/dev/sdb", "vgname": "gluster_vg_sdb"}]}, "msg": "non-zero return code", "rc": 5, "start": "2022-07-16 16:18:37.188159", "stderr": " A volume group called gluster_vg_sdb already exists.", "stderr_lines": [" A volume group called gluster_vg_sdb already exists."], "stdout": "", "stdout_lines": []} NO MORE HOSTS LEFT ************************************************************* NO MORE HOSTS LEFT ************************************************************* PLAY RECAP ********************************************************************* sr-svr04.san.lennoxconsulting.com.au : ok=32 changed=13 unreachable=0 failed=1 skipped=27 rescued=0 ignored=1 sr-svr05.san.lennoxconsulting.com.au : ok=31 changed=12 unreachable=0 failed=1 skipped=27 rescued=0 ignored=1 sr-svr06.san.lennoxconsulting.com.au : ok=31 changed=12 unreachable=0 failed=1 skipped=27 rescued=0 ignored=1 ----------- gluster-deployment.log --------- A "gluster v status" gives me no volumes present and that is where I am stuck! Any ideas of what I start trying next? I have tried this with oVirt Node 4.5.1 el8 and el9 images as well as 4.5 el8 images so it has got to be somewhere in my infrastructure configuration but I am out of ideas. My hardware configuration is 3 x HP DL360's with oVirt Node 4.5.1 el8 installed on 2x146gb RAID1 array and a gluster 6x900gb RAID5 array. Network configuration is: root@sr-svr04 ~]# ip addr show up 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eno1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP group default qlen 1000 link/ether 1c:98:ec:29:41:68 brd ff:ff:ff:ff:ff:ff 3: eno2: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP group default qlen 1000 link/ether 1c:98:ec:29:41:68 brd ff:ff:ff:ff:ff:ff permaddr 1c:98:ec:29:41:69 4: eno3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 1c:98:ec:29:41:6a brd ff:ff:ff:ff:ff:ff 5: eno4: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether 1c:98:ec:29:41:6b brd ff:ff:ff:ff:ff:ff 6: eno3.3@eno3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 1c:98:ec:29:41:6a brd ff:ff:ff:ff:ff:ff inet 192.168.3.11/24 brd 192.168.3.255 scope global noprefixroute eno3.3 valid_lft forever preferred_lft forever inet6 fe80::ec:d7be:760e:8eda/64 scope link noprefixroute valid_lft forever preferred_lft forever 7: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 1c:98:ec:29:41:68 brd ff:ff:ff:ff:ff:ff 8: bond0.4@bond0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 1c:98:ec:29:41:68 brd ff:ff:ff:ff:ff:ff inet 192.168.4.11/24 brd 192.168.4.255 scope global noprefixroute bond0.4 valid_lft forever preferred_lft forever inet6 fe80::f503:a54:8421:ea8b/64 scope link noprefixroute valid_lft forever preferred_lft forever 9: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000 link/ether 52:54:00:5b:fd:ac brd ff:ff:ff:ff:ff:ff inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0 valid_lft forever preferred_lft forever The public network is core.lennoxconsulting.com.au which is 192.168.4.0/24 and the storage network is san.lennoxconsulting.com.au which is 192.168.3.0/24 Any help to move forward please is appreciated. - Dave.

2 2

Engine storage Domain path change
by michael＠wiswm.com 17 Jul '22

17 Jul '22

Hello I installed oVirt on 3 servers(hv1,hv2,hv3) with Self Hosted Engine couple years ago. Gluster is used as storage for VMs. The engine has its own storage volume. Then I added 3 more servers(hv4,hv5,hv6). Now I would like to replace the first 3 servers. I added 3 more servers(hv7,hv8,hv9). I created new gluster volumes on hv7-hv9, moved disks from old volumes. Now the question is how to migrate engine storage? I decided to do it on Gluster level by replacing each of the brick from the old servers(hv1-hv3) with new ones (hv7-hv9). I successfully replaced bricks from hv1 and hv2 to hv7 and hv8. InoVirt engine storage Domain is created with the path hv3:/engine. I am afraid to replace hv3 brick with hv9, to not break the HostedEngine VM. To change storage Domain path I need to move it to Maintenance, but it will unmount it from all the hosts and HostedEngine will stop working. Is there any otherway to change a storage Domain path? I already changed storage value in /etc/ovirt-hosted-engine/hosted-engine.conf. I did something like this: # on hv7 hosted-engine --vm-shutdown # on all hosts systemctl stop ovirt-ha-agent systemctl stop ovirt-ha-broker hosted-engine --disconnect-storage sed -i 's/hv3/hv7/g' /etc/ovirt-hosted-engine/hosted-engine.conf hosted-engine --connect-storage systemctl restart ovirt-ha-broker systemctl status ovirt-ha-broker systemctl restart ovirt-ha-agent # on hv7 hosted-engine --vm-start and now the Hosted Engine is up and running and Gluster engine volume is mounted like hv7:/engine So the main question remains - how to change the engine storage Domain path?

2 1

Stuck in Manager upgrade. Can't set Cluster to maintenance mode.
by johannes.lutz＠diamontech.de 16 Jul '22

16 Jul '22

Hi Folks, like many others, the ovirt hosted engine certificates expired on my installation. We tried to follow this knowledge base article: https://access.redhat.com/solutions/6865861 I set the host which runs the hosted engine via the "hosted-engine --set-maintenance --mode=global" command into the global maintenance mode. Then i try to execute the "engine-setup --offline" command. There we anwser all questions and the script recognizes the expired certificates. But when we try to execute the last step it aborts with following error message. Output of engine-setup --offline: [WARNING] Failed to read or parse '/etc/pki/ovirt-engine/keys/apache.p12' Perhaps it was changed since last Setup. Error was: Mac verify error: invalid password? One or more of the certificates should be renewed, because they expire soon, or include an invalid expiry date, or they were created with validity period longer than 398 days, or do not include the subjectAltName extension, which can cause them to be rejected by recent browsers and up to date hosts. See https://www.ovirt.org/develop/release-management/features/infra/pki-renew/ for more details. Renew certificates? (Yes, No) [No]: Yes --== APACHE CONFIGURATION ==-- --== SYSTEM CONFIGURATION ==-- --== MISC CONFIGURATION ==-- --== END OF CONFIGURATION ==-- [ INFO ] Stage: Setup validation During execution engine service will be stopped (OK, Cancel) [OK]: Ok [ 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. [ ERROR ] Failed to execute stage 'Setup validation': Hosted Engine setup detected, but Global Maintenance is not set. [ INFO ] Stage: Clean up Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20220701205812-yu1osl.log [ INFO ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20220701205843-setup.conf' [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ ERROR ] Execution of setup failed Any ideas how to get the hosted engine into global maintenance mode? Thanks for your help in advance! Best Regard J. Lutz

3 3

Not able to login as admin after successfull deployment of hosted engine (OVirt 4.5.1)
by Ralf Schenk 15 Jul '22

15 Jul '22

Hello List, I successfully deployed a fresh hosted-engine, but I'm not able to login to Administration-Portal. I'm perferctly sure about the password I had to type multiple times.... I'm running ovirt-node-ng-4.5.1-0.20220622.0 and deployed engine via cli-based ovirt-hosted-engine-setup. Neither "admin" nor "admin@internal" are working (A profile cannot be choosen as in earlier versions). I can login to the monitoring part (grafana !) and also Cockpit but not Administration-Portal nor VM-Portal. I can ssh into the engine and lookup the user-database which has the user. root@engine02 ~]# ovirt-aaa-jdbc-tool query --what=user Picked up JAVA_TOOL_OPTIONS: -Dcom.redhat.fips=false -- User admin(2be16cf0-5eb7-4b0e-923e-7bdc7bc2aa6f) -- Namespace: * Name: admin ID: 2be16cf0-5eb7-4b0e-923e-7bdc7bc2aa6f Display Name: Email: root@localhost First Name: admin Last Name: Department: Title: Description: Account Disabled: false Account Locked: false Account Unlocked At: 1970-01-01 00:00:00Z Account Valid From: 2022-07-15 18:23:47Z Account Valid To: 2222-07-15 18:23:47Z Account Without Password: false Last successful Login At: 1970-01-01 00:00:00Z Last unsuccessful Login At: 1970-01-01 00:00:00Z Password Valid To: 2222-05-28 18:23:49Z However no groups by default ??? [root@engine02 ~]# ovirt-aaa-jdbc-tool query --what=group Picked up JAVA_TOOL_OPTIONS: -Dcom.redhat.fips=false Any solution ? I don't want to repeat the hosted-engine deployment a fourth time after I mastered all problems with NFS permissions, GUI deployment not accepting my Bond which is perfectly ok called "bond0" etc.... Bye -- Databay AG Logo *Ralf Schenk * fon: 02405 / 40 83 70 mail: rs(a)databay.de web: www.databay.de <https://www.databay.de> Databay AG Jens-Otto-Krag-Str. 11 52146 Würselen Sitz/Amtsgericht Aachen • HRB:8437 • USt-IdNr.: DE 210844202 Vorstand: Ralf Schenk, Dipl.-Ing. Jens Conze, Aresch Yavari, Dipl.Kfm. Philipp Hermanns Aufsichtsratsvorsitzender: Dr. Jan Scholzen

2 2

Q: oVirt 4.4.10 and vdsm-jsonrpc-java (Internal server error 500 after engine-setup)
by Andrei Verovski 15 Jul '22

15 Jul '22

Hi, Finally I managed to migrate 4.4.7 to fresh installation of 4.4.10. However, after successful engine-setup I’ve got 500 - Internal Server Error I found this: https://bugzilla.redhat.com/show_bug.cgi?id=1918022 Bug 1918022 - oVirt Manager is not loading after engine-setup Article suggested to downgrade vdsm-jsonrpc-java to 1.5.x. However, this is not possible: dnf --showduplicates list vdsm-jsonrpc-java dnf install vdsm-jsonrpc-java-1.5.7-1.el8 Last metadata expiration check: 0:39:52 ago on Fri 15 Jul 2022 02:32:36 PM EEST. Error: Problem: problem with installed package ovirt-engine-backend-4.4.10.7-1.el8.noarch - package ovirt-engine-backend-4.4.10.7-1.el8.noarch requires vdsm-jsonrpc-java >= 1.6.0, but none of the providers can be installed - cannot install both vdsm-jsonrpc-java-1.5.7-1.el8.noarch and vdsm-jsonrpc-java-1.6.0-1.el8.noarch - cannot install both vdsm-jsonrpc-java-1.6.0-1.el8.noarch and vdsm-jsonrpc-java-1.5.7-1.el8.noarch How to fix this? Thanks in advance. ***************** SERVER LOG ********************* 2022-07-15 14:45:44,969+03 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "engine.ear")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.subunit.\"engine.ear\".\"bll.jar\".component.Backend.START" => "java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance Caused by: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance Caused by: javax.ejb.EJBException: org.jboss.weld.exceptions.WeldException: WELD-000049: Unable to invoke protected void org.ovirt.engine.core.bll.TagsDirector.init() on org.ovirt.engine.core.bll.TagsDirector@648487d3 Caused by: org.jboss.weld.exceptions.WeldException: WELD-000049: Unable to invoke protected void org.ovirt.engine.core.bll.TagsDirector.init() on org.ovirt.engine.core.bll.TagsDirector@648487d3 Caused by: java.lang.reflect.InvocationTargetException Caused by: org.springframework.dao.InvalidDataAccessApiUsageException: Unable to determine the correct call signature - no procedure/function/signature for 'gettagsbyparent_id'"}} 2022-07-15 14:45:44,981+03 INFO [org.jboss.as.server] (ServerService Thread Pool -- 25) WFLYSRV0010: Deployed "restapi.war" (runtime-name : "restapi.war") 2022-07-15 14:45:44,982+03 INFO [org.jboss.as.server] (ServerService Thread Pool -- 25) WFLYSRV0010: Deployed "engine.ear" (runtime-name : "engine.ear") 2022-07-15 14:45:44,982+03 INFO [org.jboss.as.server] (ServerService Thread Pool -- 25) WFLYSRV0010: Deployed "apidoc.war" (runtime-name : "apidoc.war") 2022-07-15 14:45:44,982+03 INFO [org.jboss.as.server] (ServerService Thread Pool -- 25) WFLYSRV0010: Deployed "ovirt-web-ui.war" (runtime-name : "ovirt-web-ui.war") 2022-07-15 14:45:45,015+03 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report WFLYCTL0186: Services which failed to start: service jboss.deployment.subunit."engine.ear"."bll.jar".component.Backend.START: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance WFLYCTL0448: 2 additional services are down due to their dependencies being missing or failed

1 0

Seeking best performance on oVirt cluster
by David Johnson 14 Jul '22

14 Jul '22

Good morning all, I am trying to get the best performance out of my cluster possible, Here are the details of what I have now: Ovirt version: 4.4.10.7-1.el8 Bare metal for the ovirt engine two hosts TrueNAS cluster storage 1 NFS share 3 vdevs, 6 drives in raidz2 in each vdev 2 nvme drives for silog Storage network is 10 GBit all static IP addresses Tonight, I built a new VM from a template. It had 5 attached disks totalling 100 GB. It took 30 minutes to deploy the new VM from the template. Global utilization was 9%. The SPM has 50% of its memory free and never showed more than 12% network utilization 62 out of 65 TB are available on the newly created NFS backing store (no fragmentation). The TureNAS system is probably overprovisioned for our use. There were peak throughputs of up to 4 GBytes/second (on a 10 GBit network), but overall throughput on the NAS and the network were low. ARC hits were 95 to 100% L2 hits were 0 to 70% Here's the NFS usage stats: [image: image.png] I believe the first peak is where the silog buffered the initial burst of instructions, followed by sustained IO as the VM volumes were built in parallel, and then finally tapering off to the one 50 GB volume that took 40 minutes to copy. The indications of the NFS stats graph are that the network performance is just fine. Here are the disk IO stats covering the same time frame, plus a bit before to show a spike IO: [image: image.png] The spike at 2250 (10 minutes before I started building my VM) shows that the spinners actually hit write speed of almost 20 MBytes per second briefly, then settled in at a sustained 3 to 4 MBytes per second. The silog absorbs several spikes, but remains mostly idle, with activity measured in kilobytes per second. The HGST HUS726060AL5210 drives boast a spike throughput of 12 GB/S, and sustained throughput of 227 Mbps. ------ Now to the questions: 1. Am I asking the on the right list? Does this look like something where tuning ovirt might make a difference, or is this more likely a configuration issue with my storage appliances? 2. Am I expecting too much? Is this well within the bounds of acceptable (expected) performance? 3. How would I go about identifying the bottleneck, should I need to dig deeper? Thanks, David Johnson

8 15

unable to create iso domain
by Moritz Baumann 14 Jul '22

14 Jul '22

Hi I have removed the iso domain of an existing data center, and now I am unable to create a new iso domain /var/log/ovirt-engine/engine.log shows: 2022-07-14 08:04:40,684+02 INFO [org.ovirt.engine.core.bll.storage.connection.AddStorageServerConnectionCommand] (default task-34) [8db814e3-43ab-4921-ad35-2b3acd51c385] Lock Acquired to object 'EngineLock:{exclusiveLocks='[ovirt.storage.inf.ethz.ch:/export/ovirt/iso=STORAGE_CONNECTION]', sharedLocks=''}' 2022-07-14 08:04:40,689+02 WARN [org.ovirt.engine.core.bll.storage.connection.AddStorageServerConnectionCommand] (default task-34) [8db814e3-43ab-4921-ad35-2b3acd51c385] Validation of action 'AddStorageServerConnection' failed for user xxx@ethz.ch@ethz.ch-authz. Reasons: VAR__ACTION__ADD,VAR__TYPE__STORAGE__CONNECTION,$connectionId c39c64ef-fb8b-4e87-9803-420c7fb2dd4a,$storageDomainName ,ACTION_TYPE_FAILED_STORAGE_CONNECTION_ALREADY_EXISTS 2022-07-14 08:04:40,690+02 INFO [org.ovirt.engine.core.bll.storage.connection.AddStorageServerConnectionCommand] (default task-34) [8db814e3-43ab-4921-ad35-2b3acd51c385] Lock freed to object 'EngineLock:{exclusiveLocks='[ovirt.scratch.inf.ethz.ch:/export/ovirt/iso=STORAGE_CONNECTION]', sharedLocks=''}' 2022-07-14 08:04:40,756+02 INFO [org.ovirt.engine.core.bll.storage.connection.DisconnectStorageServerConnectionCommand] (default task-34) [4148e0fd-58ae-4375-8dc8-a08f47402ed6] Running command: DisconnectStorageServerConnectionCommand internal: false. Entities affected : ID: aaa00000-0000-0000-0000-123456789aaa Type: SystemAction group CREATE_STORAGE_DOMAIN with role type ADMIN 2022-07-14 08:04:40,756+02 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DisconnectStorageServerVDSCommand] (default task-34) [4148e0fd-58ae-4375-8dc8-a08f47402ed6] START, DisconnectStorageServerVDSCommand(HostName = ovirt-node01, StorageServerConnectionManagementVDSParameters:{hostId='d942c8fe-9a0c-4761-9be2-2f88b622070b', storagePoolId='00000000-0000-0000-0000-000000000000', storageType='NFS', connectionList='[StorageServerConnections:{id='null', connection='ovirt.storage.inf.ethz.ch:/export/ovirt/iso', iqn='null', vfsType='null', mountOptions='null', nfsVersion='null', nfsRetrans='null', nfsTimeo='null', iface='null', netIfaceName='null'}]', sendNetworkEventOnFailure='true'}), log id: 3043bbfd 2022-07-14 08:04:43,017+02 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DisconnectStorageServerVDSCommand] (default task-34) [4148e0fd-58ae-4375-8dc8-a08f47402ed6] FINISH, DisconnectStorageServerVDSCommand, return: {00000000-0000-0000-0000-000000000000=100}, log id: 3043bbfd [root@ovirt-engine ovirt-engine]# showmount -e ovirt.storage.inf.ethz.ch | grep ovirt Export list for ovirt.scratch.inf.ethz.ch: /export/ovirt/export @ovirt-storage /export/ovirt/data @ovirt-storage /export/ovirt/iso @ovirt-storage the other two domains still work just fine and the netgroup contains all ovirt-nodes. storage-node1[0]:/export/ovirt/iso# ls -la total 2 drwx------. 2 vdsm kvm 2 Jul 14 07:58 . drwxr-xr-x. 5 root root 5 Aug 19 2020 .. storage-node1[0]:/export/ovirt/iso# df . Filesystem 1K-blocks Used Available Use% Mounted on fs1/ovirt/iso 524288000 256 524287744 1% /export/ovirt/iso storage-node1[0]:/export/ovirt/iso# storage-node1[0]:/export/ovirt/iso# exportfs -v | grep ovirt/ -A1 /export/ovirt/iso @ovirt-storage(sync,wdelay,hide,no_subtree_check,fsid=215812,sec=sys:krb5:krb5i:krb5p,rw,secure,root_squash,no_all_squash) /export/ovirt/data @ovirt-storage(sync,wdelay,hide,no_subtree_check,fsid=215811,sec=sys:krb5:krb5i:krb5p,rw,secure,root_squash,no_all_squash) -- /export/ovirt/export @ovirt-storage(sync,wdelay,hide,no_subtree_check,fsid=215813,sec=sys:krb5:krb5i:krb5p,rw,secure,root_squash,no_all_squash) It appears that there is stille some reference to an iso domain (c39c64ef-fb8b-4e87-9803-420c7fb2dd4a ??) in the database. How can I get rid of it ? Best Moritz

1 1

4.3.10 cannot start VMs because of an error with USB
by Pascal D 14 Jul '22

14 Jul '22

I am still running 4.3.10 and suddenly I get this error everytime I restart a VM, any Vm on any host (I have 13 hosts in 2 different clusters) VM FLEETGEN-PCC-001 is down with error. Exit message: XML error: there is no hub at port 1 in USB address bus: 0 port: 1.1. Any idea what could be different. Template hasn't changed

2 1

Import KVM VMs on individual iSCSI luns
by spierce＠cts1.com 13 Jul '22

13 Jul '22

Greetings, Is it possible with oVirt to import existing VMs where the underlying storage is on raw iSCSI luns and to keep them on those luns? The historical scenario is that we have Virtual farms in multiple sites managed by an ancient Orchestration tool that does not support modern OS's as the hypervisor. - In each site, there are clusters of hypervisors/Hosts that have visibility to the same iSCSI luns. - Each VM has it's own set of iscsi luns that are totally dedicated to that VM - Each VM is using LVM to manage the disk - Each Host has LVM filtering configured to NOT manage the VM's iscsi luns - The VMs can be live migrated from any Hypervisor within the cluster to any other Hypervisor in that same cluster We are attempting to bring this existing environment into oVirt without replacing the storage model. Is there any documentation that will serve as a guide for this scenario? In a lab environment, we have successfully - Added 2 hypervisors (hosts) and oVirt can see their VMs as external-ovtest1 and external-ovtest2 - Removed the LVM filtering on the hosts - Created a storage domain that is able to see the iscsi luns, but we have not yet done the 'add' of each lun Is it possible to import these luns as raw block devices without LVM being layered on top of them? Is it required to actually import the luns into a storage domain, or can the VM's still be imported if all luns are visible on all hosts in the cluster? In the grand scheme of things, are we trying to do something that is not possible with oVirt? If it is possible, we would greatly appreciate tips, pointers, links to docs etc that will help us migrate this environment to oVirt. Thanks in Advance - S

3 2

Q: Instaling Ovirt Engine 4.4.10 on Clean CentOS 8 Stream
by Andrei Verovski 13 Jul '22

13 Jul '22

Hi, Since I run into a lot of problems upgrading 4.4.7 to 4.4.10, is it OK to install clean CentOS-Stream-8-x86_64-20220712-dvd1.iso and restore from backup? 4.4.10 release long before Stream 20220712, may I run again into similar problems, or I need to use earlier snapshot of Stream 8 ? I use dedicated engine PC, not hosted engine. Thanks in advance for any suggestion(s) Andrei

1 0