problem on dnf update
by g.vasilopoulos＠uoc.gr
Hi
I tried dnf update today and the result was
[root@kmanage ~]# dnf update
Last metadata expiration check: 3:42:36 ago on Mon 17 Jun 2024 08:47:59 AM EEST.
Error:
Problem 1: package python3-boto3-1.18.58-1.el9s.noarch from @System requires (python3.9dist(botocore) < 1.22 with python3.9dist(botocore) >= 1.21.58), but none of the providers can be installed
- cannot install both python3-botocore-1.31.62-1.el9.noarch from appstream and python3-botocore-1.21.58-1.el9s.noarch from @System
- cannot install both python3-botocore-1.21.58-1.el9s.noarch from ovirt-master-centos-stream-openstack-yoga-testing and python3-botocore-1.31.62-1.el9.noarch from appstream
- cannot install the best update candidate for package python3-botocore-1.21.58-1.el9s.noarch
- cannot install the best update candidate for package python3-boto3-1.18.58-1.el9s.noarch
Problem 2: package python3-pyngus-2.3.0-8.el9s.noarch from @System requires python3.9dist(python-qpid-proton), but none of the providers can be installed
- cannot install both python3-qpid-proton-0.39.0-2.el9s.x86_64 from ovirt-master-centos-stream-opstools-collectd5-testing and python3-qpid-proton-0.35.0-2.el9s.x86_64 from @System
- cannot install both python3-qpid-proton-0.35.0-2.el9s.x86_64 from ovirt-master-centos-stream-openstack-yoga-testing and python3-qpid-proton-0.39.0-2.el9s.x86_64 from ovirt-master-centos-stream-opstools-collectd5-testing
- cannot install the best update candidate for package python3-qpid-proton-0.35.0-2.el9s.x86_64
- cannot install the best update candidate for package python3-pyngus-2.3.0-8.el9s.noarch
Problem 3: package python3-oslo-messaging-12.13.3-1.el9s.noarch from @System requires python3-pyngus, but none of the providers can be installed
- package python3-pyngus-2.3.0-8.el9s.noarch from @System requires python3.9dist(python-qpid-proton), but none of the providers can be installed
- package python3-pyngus-2.3.0-8.el9s.noarch from ovirt-master-centos-stream-openstack-yoga-testing requires python3.9dist(python-qpid-proton), but none of the providers can be installed
- package python3-qpid-proton-0.35.0-2.el9s.x86_64 from @System requires qpid-proton-c(x86-64) = 0.35.0-2.el9s, but none of the providers can be installed
- package python3-qpid-proton-0.35.0-2.el9s.x86_64 from ovirt-master-centos-stream-openstack-yoga-testing requires qpid-proton-c(x86-64) = 0.35.0-2.el9s, but none of the providers can be installed
- cannot install both qpid-proton-c-0.39.0-2.el9s.x86_64 from ovirt-master-centos-stream-opstools-collectd5-testing and qpid-proton-c-0.35.0-2.el9s.x86_64 from @System
- cannot install both qpid-proton-c-0.35.0-2.el9s.x86_64 from ovirt-master-centos-stream-openstack-yoga-testing and qpid-proton-c-0.39.0-2.el9s.x86_64 from ovirt-master-centos-stream-opstools-collectd5-testing
- cannot install the best update candidate for package qpid-proton-c-0.35.0-2.el9s.x86_64
- cannot install the best update candidate for package python3-oslo-messaging-12.13.3-1.el9s.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)
7 months
Incremental backup in Ovirt 4.5.7-el9 and 4.5.6 -el8 not working...
by rvks＠protonmail.com
Hi All,
We are trying out ovirt (self-hosted engine) to replace Vmware and it's important to test the Incremental backup but so far we had no luck to make it work. Full backup working fine but subsequent incrementals are not happening, instead it's doing full backup. Using REST api but we can't enable incremental on disk ( DiskBackupMode enum). Any tips and help appreciated.....
thanks,
rvks
7 months
oVirt engine installation
by andremi001＠gmail.com
Hi,
I'm trying to deploy oVirt engine self hosted, from my Centos 9 stream node, but when I try to run the deploy I always got the error:
"FAILED! => {"changed": false, "msg": "Failed to download metadata for repo 'centos-ceph-pacific': Cannot prepare internal mirrorlist: No URLs in mirrorlist", "rc": 1, "results": []}"
I thinks it is correlated with the end of life of Centos 8 stream.
How can I fix it?
7 months
oVirt 4.5.5 Fresh Installation
by Clemilton
Hope this helps the project to get better;
[ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "hostname 'host01' doesn't uniquely match the interface 'eno1' selected for the management bridge; it matches also interface with IP ['fe80::5a8a:5aff:fe68:4981%2']. Please make sure that the hostname got from the interface for the management network resolves only there.\n"} - THIS IS NOT MENSIONED (AT LEAST I DIDNT SEE ANYWHERE) IN THE DOCUMENTATION.
[ INFO ] TASK [ovirt.ovirt.engine_setup : Check if Engine health page is up]
[ INFO ] ok: [localhost -> 192.168.222.43] - THIS IS NOT THE RIGHT IP ADDRESS. THIS NETWORK DOES NOT EXIST
[ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Wait for the host to be up] - 25 MINUTES WAITING...
[ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "Host is not up, please check logs, perhaps also on the engine machine"} - COURSE! THE SCRIPT IGNORED THE IP ADDRESS I'VE PUT
[ ERROR ] b'[DEPRECATION WARNING]: Encryption using the Python crypt module is deprecated. \n'
[ ERROR ] b'The Python crypt module is deprecated and will be removed from Python 3.13. \n'
[ ERROR ] b'Install the passlib library for continued encryption functionality. This \n'
[ ERROR ] b'feature will be removed in version 2.17. Deprecation warnings can be disabled \n'
[ ERROR ] b'by setting deprecation_warnings=False in ansible.cfg.\n'
[ ERROR ] Failed to execute stage 'Closing up': Failed executing ansible-playbook
7 months
Reminder: CentOS Stream 8 is now EOL
by Sandro Bonazzola
Hi, just a reminder that CentOS Stream 8 reached its end of life at the end
of last month on Friday, May 31, 2024.
As it has been announced by CentOS project[1], all the CentOS Stream 8
repositories are going to be archived at vault.centos.org .
Who didn't update yet to CentOS Stream 9 will probably hit several errors
related to this archiving: you'll need to manually adjust the repository
url to point to the new location at vault.centos.org.
The archiving is going to happen today [2] with the decommissioning of the
nodes used by the CentOS Community Build System used for oVirt builds for
Stream 8 within the CentOS Virtualization SIG.
At this point, the recommendation is to upgrade to CentOS Stream 9 (or
derived) as soon as practical.
For those who are pushing changes to the oVirt project, please note GitHub
actions may start to fail on CentOS Stream 8 (and with that, the builds for
oVirt Node and oVirt Appliance).
It's up to you to decide if you want to change the config there to use a
different el8 distribution for running the tests or just turn off el8 and
rely only on CentOS Stream 9 tests.
[1]
https://lists.centos.org/hyperkitty/list/announce@lists.centos.org/thread...
[2]
https://lists.centos.org/hyperkitty/list/devel@lists.centos.org/thread/P3...
--
Sandro Bonazzola
7 months
No valid authentication mechanism found
by Mathieu Valois
Hi everyone,
we've configured oVirt 4.5.5 with KeyCloak OIDC using an LDAP (FreeIPA)
backend.
When we wish to login on the portal, i.e
https://example.org/ovirt-engine, using the "Administration Portal" or
login directly with the button in the upper-right corner, it works (we
get redirected to keycloack and so on).
However, if we first try to login by clicking on the "VM portal", it
fails. We get redirected back to the portal having a "No valid
authentication mechanism found" error, as seen on the following screenshot.
Then, we're stuck until we clear the cache and cookies of the browser,
even when clicking on "Admin portal".
Backend logs only show this :
2024-06-04 11:56:24,319-04 ERROR
[org.ovirt.engine.core.sso.service.SsoService] (default task-86) []
Aucun mécanisme d'authentification valide trouvé.
which translates to the message seen on the screenshot.
Do you get any lead to resolve such an issue?
Thanks for your kind support,
Mathieu Valois
Ingénieur sécurité, systèmes et réseaux
Bureau Caen : Quartier Kœnig - 153, rue Géraldine MOCK - 14760 Bretteville-sur-Odon
Bureau Vitré : Zone de la baratière - 12, route de Domalain - 35500 Vitré
02 72 34 13 20 | https://teicee.com?pk_campaign=Email
https://www.facebook.com/teicee
https://www.linkedin.com/company/t-c-e
7 months
ovirt keycloak intergration user search not working
by g.vasilopoulos＠uoc.gr
Hello and thank you for all your efforts to provide such a quality software.
I have followd the instructions from the blog https://blogs.ovirt.org/2019/01/federate-ovirt-engine-authentication-to-o...
and I managed to intergrate ovirt with keycloak partialy. I say partialy because I cannot execute a user search from the admin portal. I can add the user if I know his username say do a search with the full username like gvas(a)test.domain. The thing is in the admin portal when I perform a user search using internalkeycloack-authz whatever I write in the search returns as a result. It does not seem to matter if it is an existing user or not. If the user exists, then the user cal login and is granted the appropriate rights, but user search does not work . What should I look for?
7 months
Backup bug in latest version
by Giulio Casella
Hi,
yesterday we upgraded engine:
ovirt-engine-4.5.7-0.master.20240506114300.git0a1ba8203f.el8.noarch ->
ovirt-engine-4.5.7-0.master.20240527152413.gited023e5e0a.el8.noarch
Since then our backups (made by Storware backup and recovery, vprotect)
are failing.
It seems that engine tries to add backup twice, and db primary key
constraint obviously fails. Find below a snippet from engine.log.
The snapshot part of backup process is executed correctly (but snapshot
named "Auto-generated for Backup VM" remains after failure).
Also script
/usr/share/doc/python3-ovirt-engine-sdk4/examples/backup_vm.py fails to
finalize/terminate backup.
Has anyone seen this and filed a bug on github?
------------------------------------------------------
2024-06-13 10:36:47,481+02 INFO
[org.ovirt.engine.core.bll.storage.backup.HybridBackupCommand] (default
task-8) [38c00ae1-a837-4758-85a9-ee9943395753] Lock Acquired to object
'EngineLock:{exclusiveLocks='[09db7fdc-c4d3-4fbd-a50e-1b04de2b1341=DISK,
32f9b481-8431-4cbc-ad3e-bb226374e693=DISK]', sharedLocks=''}'
2024-06-13 10:36:47,535+02 INFO
[org.ovirt.engine.core.bll.storage.backup.HybridBackupCommand] (default
task-8) [38c00ae1-a837-4758-85a9-ee9943395753] Running command:
HybridBackupCommand internal: false. Entities affected : ID:
dc6d9b23-e2f7-4744-a633-d4e532ef190f Type: VMAction group BACKUP_DISK
with role type ADMIN, ID: 09db7fdc-c4d3-4fbd-a50e-1b04de2b1341 Type:
DiskAction group BACKUP_DISK with role type ADMIN, ID:
32f9b481-8431-4cbc-ad3e-bb226374e693 Type: DiskAction group BACKUP_DISK
with role type ADMIN
2024-06-13 10:36:47,541+02 INFO
[org.ovirt.engine.core.bll.storage.backup.HybridBackupCommand] (default
task-8) [38c00ae1-a837-4758-85a9-ee9943395753] Created VmBackup entity
'd5bed8c5-f172-47c7-9827-5dda51490ee8' for VM
'dc6d9b23-e2f7-4744-a633-d4e532ef190f'
2024-06-13 10:36:47,596+02 INFO
[org.ovirt.engine.core.bll.snapshots.CreateSnapshotForVmCommand]
(default task-8) [38c00ae1-a837-4758-85a9-ee9943395753] Lock Acquired to
object
'EngineLock:{exclusiveLocks='[dc6d9b23-e2f7-4744-a633-d4e532ef190f=VM]',
sharedLocks=''}'
2024-06-13 10:36:47,640+02 INFO
[org.ovirt.engine.core.bll.snapshots.CreateSnapshotForVmCommand]
(default task-8) [38c00ae1-a837-4758-85a9-ee9943395753] Running command:
CreateSnapshotForVmCommand internal: true. Entities affected : ID:
dc6d9b23-e2f7-4744-a633-d4e532ef190f Type: VMAction group
MANIPULATE_VM_SNAPSHOTS with role type USER
2024-06-13 10:36:47,668+02 INFO
[org.ovirt.engine.core.bll.snapshots.CreateSnapshotDiskCommand] (default
task-8) [38c00ae1-a837-4758-85a9-ee9943395753] Running command:
CreateSnapshotDiskCommand internal: true. Entities affected : ID:
dc6d9b23-e2f7-4744-a633-d4e532ef190f Type: VMAction group
MANIPULATE_VM_SNAPSHOTS with role type USER
2024-06-13 10:36:47,731+02 INFO
[org.ovirt.engine.core.bll.snapshots.CreateSnapshotCommand] (default
task-8) [38c00ae1-a837-4758-85a9-ee9943395753] Running command:
CreateSnapshotCommand internal: true. Entities affected : ID:
00000000-0000-0000-0000-000000000000 Type: Storage
2024-06-13 10:36:47,767+02 INFO
[org.ovirt.engine.core.vdsbroker.irsbroker.CreateVolumeVDSCommand]
(default task-8) [38c00ae1-a837-4758-85a9-ee9943395753] START,
CreateVolumeVDSCommand(
CreateVolumeVDSCommandParameters:{storagePoolId='42135536-980b-4ea9-ab66-b850ed8c1f2b',
ignoreFailoverLimit='false',
storageDomainId='459011cf-ebb6-46ff-831d-8ccfafd82c8a',
imageGroupId='32f9b481-8431-4cbc-ad3e-bb226374e693',
imageSizeInBytes='107374182400', volumeFormat='COW',
newImageId='754b091f-eaa9-4fd8-afbf-1caa0e747eb6', imageType='Sparse',
newImageDescription='', imageInitialSizeInBytes='0',
imageId='06289dbc-fc0a-4d7b-bd13-92a2df199971',
sourceImageGroupId='32f9b481-8431-4cbc-ad3e-bb226374e693',
shouldAddBitmaps='false', legal='true', sequenceNumber='1',
bitmap='bf62fab5-fb82-4c03-ac60-ddb9943c9f0d'}), log id: 128fa930
2024-06-13 10:36:47,883+02 INFO
[org.ovirt.engine.core.vdsbroker.irsbroker.CreateVolumeVDSCommand]
(default task-8) [38c00ae1-a837-4758-85a9-ee9943395753] FINISH,
CreateVolumeVDSCommand, return: 754b091f-eaa9-4fd8-afbf-1caa0e747eb6,
log id: 128fa930
2024-06-13 10:36:47,895+02 INFO
[org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (default task-8)
[38c00ae1-a837-4758-85a9-ee9943395753] CommandAsyncTask::Adding
CommandMultiAsyncTasks object for command
'43b174d8-3b84-46a3-abe6-e825e9ce7c81'
2024-06-13 10:36:47,896+02 INFO
[org.ovirt.engine.core.bll.CommandMultiAsyncTasks] (default task-8)
[38c00ae1-a837-4758-85a9-ee9943395753]
CommandMultiAsyncTasks::attachTask: Attaching task
'86720608-b5bd-4a28-b7ee-b1a3507592aa' to command
'43b174d8-3b84-46a3-abe6-e825e9ce7c81'.
2024-06-13 10:36:47,918+02 INFO
[org.ovirt.engine.core.bll.tasks.AsyncTaskManager] (default task-8)
[38c00ae1-a837-4758-85a9-ee9943395753] Adding task
'86720608-b5bd-4a28-b7ee-b1a3507592aa' (Parent Command 'CreateSnapshot',
Parameters Type
'org.ovirt.engine.core.common.asynctasks.AsyncTaskParameters'), polling
hasn't started yet..
2024-06-13 10:36:47,947+02 INFO
[org.ovirt.engine.core.bll.snapshots.CreateSnapshotCommand] (default
task-8) [38c00ae1-a837-4758-85a9-ee9943395753] Running command:
CreateSnapshotCommand internal: true. Entities affected : ID:
00000000-0000-0000-0000-000000000000 Type: Storage
2024-06-13 10:36:47,963+02 INFO
[org.ovirt.engine.core.vdsbroker.irsbroker.CreateVolumeVDSCommand]
(default task-8) [38c00ae1-a837-4758-85a9-ee9943395753] START,
CreateVolumeVDSCommand(
CreateVolumeVDSCommandParameters:{storagePoolId='42135536-980b-4ea9-ab66-b850ed8c1f2b',
ignoreFailoverLimit='false',
storageDomainId='459011cf-ebb6-46ff-831d-8ccfafd82c8a',
imageGroupId='09db7fdc-c4d3-4fbd-a50e-1b04de2b1341',
imageSizeInBytes='53687091200', volumeFormat='COW',
newImageId='1407954a-6d41-4f01-928b-98afa8ef215f', imageType='Sparse',
newImageDescription='', imageInitialSizeInBytes='0',
imageId='5d65f77d-25fa-4879-8144-6147a16f3ae3',
sourceImageGroupId='09db7fdc-c4d3-4fbd-a50e-1b04de2b1341',
shouldAddBitmaps='false', legal='true', sequenceNumber='2',
bitmap='bf62fab5-fb82-4c03-ac60-ddb9943c9f0d'}), log id: 5ce87935
2024-06-13 10:36:48,055+02 INFO
[org.ovirt.engine.core.vdsbroker.irsbroker.CreateVolumeVDSCommand]
(default task-8) [38c00ae1-a837-4758-85a9-ee9943395753] FINISH,
CreateVolumeVDSCommand, return: 1407954a-6d41-4f01-928b-98afa8ef215f,
log id: 5ce87935
2024-06-13 10:36:48,058+02 INFO
[org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (default task-8)
[38c00ae1-a837-4758-85a9-ee9943395753] CommandAsyncTask::Adding
CommandMultiAsyncTasks object for command
'a3f817d8-ca15-4fff-a411-ac0294e2ea70'
2024-06-13 10:36:48,058+02 INFO
[org.ovirt.engine.core.bll.CommandMultiAsyncTasks] (default task-8)
[38c00ae1-a837-4758-85a9-ee9943395753]
CommandMultiAsyncTasks::attachTask: Attaching task
'60e6899b-f59f-404d-af8f-d2ef73e0c908' to command
'a3f817d8-ca15-4fff-a411-ac0294e2ea70'.
2024-06-13 10:36:48,067+02 INFO
[org.ovirt.engine.core.bll.tasks.AsyncTaskManager] (default task-8)
[38c00ae1-a837-4758-85a9-ee9943395753] Adding task
'60e6899b-f59f-404d-af8f-d2ef73e0c908' (Parent Command 'CreateSnapshot',
Parameters Type
'org.ovirt.engine.core.common.asynctasks.AsyncTaskParameters'), polling
hasn't started yet..
2024-06-13 10:36:48,080+02 INFO
[org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (default task-8)
[38c00ae1-a837-4758-85a9-ee9943395753] BaseAsyncTask::startPollingTask:
Starting to poll task '86720608-b5bd-4a28-b7ee-b1a3507592aa'.
2024-06-13 10:36:48,081+02 INFO
[org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (default task-8)
[38c00ae1-a837-4758-85a9-ee9943395753] BaseAsyncTask::startPollingTask:
Starting to poll t
ask '60e6899b-f59f-404d-af8f-d2ef73e0c908'.
2024-06-13 10:36:48,147+02 INFO
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(default task-8) [38c00ae1-a837-4758-85a9-ee9943395753] EVENT_ID:
USER_CREATE_SNAPS
HOT(45), Snapshot 'Auto-generated for Backup VM' creation for VM
'mercurio' was initiated by admin@internal.
2024-06-13 10:36:48,151+02 ERROR
[org.ovirt.engine.core.bll.storage.backup.HybridBackupCommand] (default
task-8) [38c00ae1-a837-4758-85a9-ee9943395753] Command
'org.ovirt.engine.core.bll.
storage.backup.HybridBackupCommand' failed: CallableStatementCallback;
SQL [{call insertvmbackup(?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)}]; ERROR:
duplicate key value violates unique constraint
"vm_backups_pkey"
Detail: Key (backup_id)=(d5bed8c5-f172-47c7-9827-5dda51490ee8)
already exists.
Where: SQL statement "INSERT INTO vm_backups (
backup_id,
from_checkpoint_id,
to_checkpoint_id,
vm_id,
host_id,
phase,
_create_date,
_update_date,
description,
backup_type,
snapshot_id
)
VALUES (
v_backup_id,
v_from_checkpoint_id,
v_to_checkpoint_id,
v_vm_id,
v_host_id,
v_phase,
v__create_date,
v__update_date,
v_description,
v_backup_type,
v_snapshot_id
)"
PL/pgSQL function insertvmbackup(uuid,uuid,uuid,uuid,uuid,text,timestamp
with time zone,timestamp with time zone,character varying,character
varying,uuid) line 3 at SQL statement; nested exception is
org.postgresql.util.PSQLException: ERROR: duplicate key value violates
unique constraint "vm_backups_pkey"
Detail: Key (backup_id)=(d5bed8c5-f172-47c7-9827-5dda51490ee8)
already exists.
Where: SQL statement "INSERT INTO vm_backups (
backup_id,
from_checkpoint_id,
to_checkpoint_id,
vm_id,
host_id,
phase,
_create_date,
_update_date,
description,
backup_type,
snapshot_id
)
VALUES (
v_backup_id,
v_from_checkpoint_id,
v_to_checkpoint_id,
v_vm_id,
v_host_id,
v_phase,
v__create_date,
v__update_date,
v_description,
v_backup_type,
v_snapshot_id
)"
PL/pgSQL function insertvmbackup(uuid,uuid,uuid,uuid,uuid,text,timestamp
with time zone,timestamp with time zone,character varying,character
varying,uuid) line 3 at SQL statement
------------------------------------------------------
Thanks in advance,
Giulio
7 months
VM Windows 2022 always been shutdown
by Kalil de A. Carvalho
Hello all.
Here, in my company, we have oVirt verson 4.5.4-1.el9 running with a lots
of VM's but all Windows 2022 and 11 has a strange behaviour, sometimes just
going down with this message:
"VM VM-NAME is down with error. Exit message: Lost connection with qemu
process."
Looking for any answer on logs I found out this message:
"Code=qemu-kvm: ../hw/core/cpu-sysemu.c:77: int
cpu_asidx_from_attrs(CPUState *, MemTxAttrs): Assertion `ret <
cpu->num_ases && ret >= 0' failed.
2024-06-03 13:59:46.809+0000: shutting down, reason=crashed"
We don't understand why it just has problems with Windwos 2022 and 11.
Windows 2019 run without problem.
Can any one have this kind of situation? Does it have any fixed action?
Best regars
--
Atenciosamente,
Kalil de A. Carvalho
7 months
New installation of oVirt 4.5.6: issues with bll.jar
by samu.paaso＠liberator.fi
Hello,
We are having issues with a brand new deployment of oVirt. After
installation, the users are unable to access the Administration or VM
portals, they'll face error 500. Other panels, like Keycloak and Grafana
work as expected. Digging deeper, there seems to be an issue with file
/var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar as
described in the log /var/log/ovirt-engine/server.log:
2024-06-11 22:18:12,459+03 INFO [org.jboss.weld.deployer] (MSC service
thread 1-8) WFLYWELD0003: Processing weld deployment restapi.war
2024-06-11 22:18:12,468+03 INFO [org.wildfly.security] (MSC service
thread 1-2) ELY00001: WildFly Elytron version 1.16.1.Final
2024-06-11 22:18:12,665+03 INFO
[org.hibernate.validator.internal.util.Version] (MSC service thread 1-8)
HV000001: Hibernate Validator 6.0.22.Final
2024-06-11 22:18:12,762+03 INFO [org.wildfly.extension.undertow]
(ServerService Thread Pool -- 47) WFLYUT0021: Registered web context:
'/ovirt-engine/web-ui' for server 'default-server'
2024-06-11 22:18:12,761+03 INFO [org.wildfly.extension.undertow]
(ServerService Thread Pool -- 49) WFLYUT0021: Registered web context:
'/ovirt-engine/apidoc' for server 'default-server'
2024-06-11 22:18:12,845+03 INFO [org.infinispan.CONTAINER]
(ServerService Thread Pool -- 44) ISPN000128: Infinispan version:
Infinispan 'Taedonggang' 12.1.4.Final
2024-06-11 22:18:13,041+03 INFO [org.infinispan.CONTAINER]
(ServerService Thread Pool -- 49) ISPN000556: Starting user marshaller
'org.wildfly.clustering.infinispan.marshalling.jboss.JBossMarshaller'
2024-06-11 22:18:13,061+03 INFO [org.jboss.as.server.deployment] (MSC
service thread 1-2) WFLYSRV0207: Starting subdeployment (runtime-name:
"enginesso.war")
2024-06-11 22:18:13,061+03 INFO [org.jboss.as.server.deployment] (MSC
service thread 1-5) WFLYSRV0207: Starting subdeployment (runtime-name:
"bll.jar")
2024-06-11 22:18:13,062+03 INFO [org.jboss.as.server.deployment] (MSC
service thread 1-1) WFLYSRV0207: Starting subdeployment (runtime-name:
"webadmin.war")
2024-06-11 22:18:13,062+03 INFO [org.jboss.as.server.deployment] (MSC
service thread 1-6) WFLYSRV0207: Starting subdeployment (runtime-name:
"docs.war")
2024-06-11 22:18:13,068+03 INFO [org.jboss.as.server.deployment] (MSC
service thread 1-3) WFLYSRV0207: Starting subdeployment (runtime-name:
"root.war")
2024-06-11 22:18:13,068+03 INFO [org.jboss.as.server.deployment] (MSC
service thread 1-8) WFLYSRV0207: Starting subdeployment (runtime-name:
"welcome.war")
2024-06-11 22:18:13,069+03 INFO [org.jboss.as.server.deployment] (MSC
service thread 1-7) WFLYSRV0207: Starting subdeployment (runtime-name:
"services.war")
2024-06-11 22:18:13,080+03 WARN [org.jboss.as.server.deployment] (MSC
service thread 1-5) WFLYSRV0059: Class Path entry lib/utils.jar in
/var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does
not point to a valid jar for a Class-Path reference.
2024-06-11 22:18:13,080+03 WARN [org.jboss.as.server.deployment] (MSC
service thread 1-5) WFLYSRV0059: Class Path entry lib/uutils.jar in
/var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does
not point to a valid jar for a Class-Path reference.
2024-06-11 22:18:13,093+03 WARN [org.jboss.as.server.deployment] (MSC
service thread 1-5) WFLYSRV0059: Class Path entry lib/sshd-core.jar in
/var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does
not point to a valid jar for a Class-Path reference.
2024-06-11 22:18:13,093+03 WARN [org.jboss.as.server.deployment] (MSC
service thread 1-5) WFLYSRV0059: Class Path entry lib/sshd-common.jar in
/var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does
not point to a valid jar for a Class-Path reference.
2024-06-11 22:18:13,093+03 WARN [org.jboss.as.server.deployment] (MSC
service thread 1-5) WFLYSRV0059: Class Path entry lib/jcl-over-slf4j.jar
in /var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar
does not point to a valid jar for a Class-Path reference.
2024-06-11 22:18:13,093+03 WARN [org.jboss.as.server.deployment] (MSC
service thread 1-5) WFLYSRV0059: Class Path entry
lib/commons-beanutils.jar in
/var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does
not point to a valid jar for a Class-Path reference.
2024-06-11 22:18:13,093+03 WARN [org.jboss.as.server.deployment] (MSC
service thread 1-5) WFLYSRV0059: Class Path entry
lib/commons-logging.jar in
/var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does
not point to a valid jar for a Class-Path reference.
2024-06-11 22:18:13,093+03 WARN [org.jboss.as.server.deployment] (MSC
service thread 1-5) WFLYSRV0059: Class Path entry
lib/commons-compress.jar in
/var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does
not point to a valid jar for a Class-Path reference.
2024-06-11 22:18:13,094+03 WARN [org.jboss.as.server.deployment] (MSC
service thread 1-5) WFLYSRV0059: Class Path entry lib/commons-lang.jar
in /var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar
does not point to a valid jar for a Class-Path reference.
2024-06-11 22:18:13,094+03 WARN [org.jboss.as.server.deployment] (MSC
service thread 1-5) WFLYSRV0059: Class Path entry lib/commons-codec.jar
in /var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar
does not point to a valid jar for a Class-Path reference.
2024-06-11 22:18:13,094+03 WARN [org.jboss.as.server.deployment] (MSC
service thread 1-5) WFLYSRV0059: Class Path entry lib/glance-client.jar
in /var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar
does not point to a valid jar for a Class-Path reference.
2024-06-11 22:18:13,094+03 WARN [org.jboss.as.server.deployment] (MSC
service thread 1-5) WFLYSRV0059: Class Path entry lib/glance-model.jar
in /var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar
does not point to a valid jar for a Class-Path reference.
2024-06-11 22:18:13,094+03 WARN [org.jboss.as.server.deployment] (MSC
service thread 1-5) WFLYSRV0059: Class Path entry lib/cinder-client.jar
in /var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar
does not point to a valid jar for a Class-Path reference.
2024-06-11 22:18:13,094+03 WARN [org.jboss.as.server.deployment] (MSC
service thread 1-5) WFLYSRV0059: Class Path entry lib/cinder-model.jar
in /var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar
does not point to a valid jar for a Class-Path reference.
2024-06-11 22:18:13,094+03 WARN [org.jboss.as.server.deployment] (MSC
service thread 1-5) WFLYSRV0059: Class Path entry lib/cors-filter.jar in
/var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does
not point to a valid jar for a Class-Path reference.
2024-06-11 22:18:13,094+03 WARN [org.jboss.as.server.deployment] (MSC
service thread 1-5) WFLYSRV0059: Class Path entry lib/compat.jar in
/var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does
not point to a valid jar for a Class-Path reference.
2024-06-11 22:18:13,095+03 WARN [org.jboss.as.server.deployment] (MSC
service thread 1-5) WFLYSRV0059: Class Path entry lib/common.jar in
/var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does
not point to a valid jar for a Class-Path reference.
2024-06-11 22:18:13,095+03 WARN [org.jboss.as.server.deployment] (MSC
service thread 1-5) WFLYSRV0059: Class Path entry
lib/hibernate-validator.jar in
/var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does
not point to a valid jar for a Class-Path reference.
2024-06-11 22:18:13,095+03 WARN [org.jboss.as.server.deployment] (MSC
service thread 1-5) WFLYSRV0059: Class Path entry lib/classmate.jar in
/var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does
not point to a valid jar for a Class-Path reference.
2024-06-11 22:18:13,095+03 WARN [org.jboss.as.server.deployment] (MSC
service thread 1-5) WFLYSRV0059: Class Path entry lib/jboss-modules.jar
in /var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar
does not point to a valid jar for a Class-Path reference.
2024-06-11 22:18:13,095+03 WARN [org.jboss.as.server.deployment] (MSC
service thread 1-5) WFLYSRV0059: Class Path entry lib/dal.jar in
/var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does
not point to a valid jar for a Class-Path reference.
2024-06-11 22:18:13,095+03 WARN [org.jboss.as.server.deployment] (MSC
service thread 1-5) WFLYSRV0059: Class Path entry lib/spring-jdbc.jar in
/var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does
not point to a valid jar for a Class-Path reference.
2024-06-11 22:18:13,095+03 WARN [org.jboss.as.server.deployment] (MSC
service thread 1-5) WFLYSRV0059: Class Path entry lib/spring-tx.jar in
/var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does
not point to a valid jar for a Class-Path reference.
2024-06-11 22:18:13,095+03 WARN [org.jboss.as.server.deployment] (MSC
service thread 1-5) WFLYSRV0059: Class Path entry
lib/java-client-kubevirt.jar in
/var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does
not point to a valid jar for a Class-Path reference.
2024-06-11 22:18:13,096+03 WARN [org.jboss.as.server.deployment] (MSC
service thread 1-5) WFLYSRV0059: Class Path entry
lib/vdsm-jsonrpc-java-client.jar in
/var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does
not point to a valid jar for a Class-Path reference.
2024-06-11 22:18:13,096+03 WARN [org.jboss.as.server.deployment] (MSC
service thread 1-5) WFLYSRV0059: Class Path entry lib/commons-lang3.jar
in /var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar
does not point to a valid jar for a Class-Path reference.
2024-06-11 22:18:13,096+03 WARN [org.jboss.as.server.deployment] (MSC
service thread 1-5) WFLYSRV0059: Class Path entry
lib/commons-collections.jar in
/var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does
not point to a valid jar for a Class-Path reference.
2024-06-11 22:18:13,096+03 WARN [org.jboss.as.server.deployment] (MSC
service thread 1-5) WFLYSRV0059: Class Path entry lib/snakeyaml.jar in
/var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does
not point to a valid jar for a Class-Path reference.
2024-06-11 22:18:13,096+03 WARN [org.jboss.as.server.deployment] (MSC
service thread 1-5) WFLYSRV0059: Class Path entry lib/aaa.jar in
/var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does
not point to a valid jar for a Class-Path reference.
2024-06-11 22:18:13,096+03 WARN [org.jboss.as.server.deployment] (MSC
service thread 1-5) WFLYSRV0059: Class Path entry lib/httpcore.jar in
/var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does
not point to a valid jar for a Class-Path reference.
2024-06-11 22:18:13,096+03 WARN [org.jboss.as.server.deployment] (MSC
service thread 1-5) WFLYSRV0059: Class Path entry lib/httpclient.jar in
/var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does
not point to a valid jar for a Class-Path reference.
2024-06-11 22:18:13,096+03 WARN [org.jboss.as.server.deployment] (MSC
service thread 1-5) WFLYSRV0059: Class Path entry
lib/extensions-manager.jar in
/var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does
not point to a valid jar for a Class-Path reference.
2024-06-11 22:18:13,096+03 WARN [org.jboss.as.server.deployment] (MSC
service thread 1-5) WFLYSRV0059: Class Path entry lib/builtin.jar in
/var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does
not point to a valid jar for a Class-Path reference.
2024-06-11 22:18:13,097+03 WARN [org.jboss.as.server.deployment] (MSC
service thread 1-5) WFLYSRV0059: Class Path entry lib/searchbackend.jar
in /var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar
does not point to a valid jar for a Class-Path reference.
2024-06-11 22:18:13,097+03 WARN [org.jboss.as.server.deployment] (MSC
service thread 1-5) WFLYSRV0059: Class Path entry lib/branding.jar in
/var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does
not point to a valid jar for a Class-Path reference.
2024-06-11 22:18:13,097+03 WARN [org.jboss.as.server.deployment] (MSC
service thread 1-5) WFLYSRV0059: Class Path entry
lib/ovirt-engine-extensions-api.jar in
/var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does
not point to a valid jar for a Class-Path reference.
2024-06-11 22:18:13,097+03 WARN [org.jboss.as.server.deployment] (MSC
service thread 1-5) WFLYSRV0059: Class Path entry
lib/keystone-client.jar in
/var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does
not point to a valid jar for a Class-Path reference.
2024-06-11 22:18:13,097+03 WARN [org.jboss.as.server.deployment] (MSC
service thread 1-5) WFLYSRV0059: Class Path entry
lib/openstack-client.jar in
/var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does
not point to a valid jar for a Class-Path reference.
2024-06-11 22:18:13,097+03 WARN [org.jboss.as.server.deployment] (MSC
service thread 1-5) WFLYSRV0059: Class Path entry lib/keystone-model.jar
in /var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar
does not point to a valid jar for a Class-Path reference.
2024-06-11 22:18:13,097+03 WARN [org.jboss.as.server.deployment] (MSC
service thread 1-5) WFLYSRV0059: Class Path entry lib/quantum-client.jar
in /var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar
does not point to a valid jar for a Class-Path reference.
2024-06-11 22:18:13,097+03 WARN [org.jboss.as.server.deployment] (MSC
service thread 1-5) WFLYSRV0059: Class Path entry lib/quantum-model.jar
in /var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar
does not point to a valid jar for a Class-Path reference.
2024-06-11 22:18:13,098+03 WARN [org.jboss.as.server.deployment] (MSC
service thread 1-5) WFLYSRV0059: Class Path entry
lib/resteasy-connector.jar in
/var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does
not point to a valid jar for a Class-Path reference.
2024-06-11 22:18:13,098+03 WARN [org.jboss.as.server.deployment] (MSC
service thread 1-5) WFLYSRV0059: Class Path entry lib/mail.jar in
/var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does
not point to a valid jar for a Class-Path reference.
2024-06-11 22:18:13,098+03 WARN [org.jboss.as.server.deployment] (MSC
service thread 1-5) WFLYSRV0059: Class Path entry
lib/jboss-interceptors-api_1.1_spec.jar in
/var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does
not point to a valid jar for a Class-Path reference.
2024-06-11 22:18:13,098+03 WARN [org.jboss.as.server.deployment] (MSC
service thread 1-5) WFLYSRV0059: Class Path entry lib/xmlrpc-client.jar
in /var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar
does not point to a valid jar for a Class-Path reference.
2024-06-11 22:18:13,098+03 WARN [org.jboss.as.server.deployment] (MSC
service thread 1-5) WFLYSRV0059: Class Path entry lib/xmlrpc-common.jar
in /var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar
does not point to a valid jar for a Class-Path reference.
2024-06-11 22:18:13,098+03 WARN [org.jboss.as.server.deployment] (MSC
service thread 1-5) WFLYSRV0059: Class Path entry
lib/ws-commons-util.jar in
/var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does
not point to a valid jar for a Class-Path reference.
2024-06-11 22:18:13,098+03 WARN [org.jboss.as.server.deployment] (MSC
service thread 1-5) WFLYSRV0059: Class Path entry lib/xml-apis.jar in
/var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does
not point to a valid jar for a Class-Path reference.
2024-06-11 22:18:13,098+03 WARN [org.jboss.as.server.deployment] (MSC
service thread 1-5) WFLYSRV0059: Class Path entry lib/spring-core.jar in
/var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does
not point to a valid jar for a Class-Path reference.
2024-06-11 22:18:13,099+03 WARN [org.jboss.as.server.deployment] (MSC
service thread 1-5) WFLYSRV0059: Class Path entry lib/spring-jcl.jar in
/var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does
not point to a valid jar for a Class-Path reference.
2024-06-11 22:18:13,099+03 WARN [org.jboss.as.server.deployment] (MSC
service thread 1-5) WFLYSRV0059: Class Path entry lib/spring-beans.jar
in /var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar
does not point to a valid jar for a Class-Path reference.
2024-06-11 22:18:13,099+03 WARN [org.jboss.as.server.deployment] (MSC
service thread 1-5) WFLYSRV0059: Class Path entry lib/spring-context.jar
in /var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar
does not point to a valid jar for a Class-Path reference.
2024-06-11 22:18:13,099+03 WARN [org.jboss.as.server.deployment] (MSC
service thread 1-5) WFLYSRV0059: Class Path entry lib/spring-aop.jar in
/var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does
not point to a valid jar for a Class-Path reference.
2024-06-11 22:18:13,099+03 WARN [org.jboss.as.server.deployment] (MSC
service thread 1-5) WFLYSRV0059: Class Path entry
lib/spring-expression.jar in
/var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar does
not point to a valid jar for a Class-Path reference.
2024-06-11 22:18:13,099+03 WARN [org.jboss.as.server.deployment] (MSC
service thread 1-5) WFLYSRV0059: Class Path entry lib/jboss-logging.jar
in /var/lib/ovirt-engine/jboss_runtime/deployments/engine.ear/bll.jar
does not point to a valid jar for a Class-Path reference.
2024-06-11 22:18:13,162+03 INFO [org.jboss.weld.Version] (MSC service
thread 1-4) WELD-000900: 3.1.7 (SP1)
2024-06-11 22:18:13,426+03 INFO [org.jboss.as.clustering.infinispan]
(ServerService Thread Pool -- 48) WFLYCLINF0002: Started
authenticationSessions cache from keycloak container
2024-06-11 22:18:13,426+03 INFO [org.jboss.as.clustering.infinispan]
(ServerService Thread Pool -- 54) WFLYCLINF0002: Started authorization
cache from keycloak container
2024-06-11 22:18:13,428+03 INFO [org.jboss.as.clustering.infinispan]
(ServerService Thread Pool -- 51) WFLYCLINF0002: Started work cache from
keycloak container
2024-06-11 22:18:13,428+03 INFO [org.jboss.as.clustering.infinispan]
(ServerService Thread Pool -- 45) WFLYCLINF0002: Started clientSessions
cache from keycloak container
2024-06-11 22:18:13,429+03 INFO [org.jboss.as.clustering.infinispan]
(ServerService Thread Pool -- 44) WFLYCLINF0002: Started
offlineClientSessions cache from keycloak container
2024-06-11 22:18:13,429+03 INFO [org.jboss.as.clustering.infinispan]
(ServerService Thread Pool -- 46) WFLYCLINF0002: Started sessions cache
from keycloak container
2024-06-11 22:18:13,429+03 INFO [org.jboss.as.clustering.infinispan]
(ServerService Thread Pool -- 47) WFLYCLINF0002: Started loginFailures
cache from keycloak container
2024-06-11 22:18:13,429+03 INFO [org.jboss.as.clustering.infinispan]
(ServerService Thread Pool -- 49) WFLYCLINF0002: Started offlineSessions
cache from keycloak container
2024-06-11 22:18:13,430+03 INFO [org.jboss.as.clustering.infinispan]
(ServerService Thread Pool -- 50) WFLYCLINF0002: Started keys cache from
keycloak container
2024-06-11 22:18:13,430+03 INFO [org.jboss.as.clustering.infinispan]
(ServerService Thread Pool -- 52) WFLYCLINF0002: Started realms cache
from keycloak container
2024-06-11 22:18:13,430+03 INFO [org.jboss.as.clustering.infinispan]
(ServerService Thread Pool -- 55) WFLYCLINF0002: Started users cache
from keycloak container
2024-06-11 22:18:13,430+03 INFO [org.jboss.as.clustering.infinispan]
(ServerService Thread Pool -- 53) WFLYCLINF0002: Started actionTokens
cache from keycloak container
2024-06-11 22:18:13,456+03 WARN [org.jboss.as.server.deployment] (MSC
service thread 1-7) WFLYSRV0273: Excluded subsystem webservices via
jboss-deployment-structure.xml does not exist.
2024-06-11 22:18:14,479+03 WARN [org.jboss.as.dependency.deprecated]
(MSC service thread 1-1) WFLYSRV0221: Deployment
"deployment.engine.ear.bll.jar" is using a deprecated module ("sun.jdk")
which may be removed in future versions without notice.
2024-06-11 22:18:14,499+03 INFO [org.jboss.weld.deployer] (MSC service
thread 1-5) WFLYWELD0003: Processing weld deployment engine.ear
2024-06-11 22:18:14,588+03 INFO [org.jboss.weld.deployer] (MSC service
thread 1-3) WFLYWELD0003: Processing weld deployment root.war
2024-06-11 22:18:14,665+03 INFO [org.jboss.weld.deployer] (MSC service
thread 1-2) WFLYWELD0003: Processing weld deployment services.war
2024-06-11 22:18:14,674+03 INFO [org.jboss.weld.deployer] (MSC service
thread 1-6) WFLYWELD0003: Processing weld deployment docs.war
2024-06-11 22:18:14,703+03 INFO [org.jboss.weld.deployer] (MSC service
thread 1-4) WFLYWELD0003: Processing weld deployment webadmin.war
2024-06-11 22:18:14,709+03 INFO [org.jboss.weld.deployer] (MSC service
thread 1-1) WFLYWELD0003: Processing weld deployment enginesso.war
2024-06-11 22:18:14,731+03 INFO [org.jboss.weld.deployer] (MSC service
thread 1-7) WFLYWELD0003: Processing weld deployment welcome.war
2024-06-11 22:18:14,783+03 INFO [org.jboss.weld.deployer] (MSC service
thread 1-8) WFLYWELD0003: Processing weld deployment bll.jar
2024-06-11 22:18:14,798+03 INFO [org.jboss.as.ejb3.deployment] (MSC
service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named
'LockManager' in deployment unit 'subdeployment "bll.jar" of deployment
"engine.ear"' are as follows:
java:global/engine/bll/LockManager!org.ovirt.engine.core.utils.lock.LockManager
java:app/bll/LockManager!org.ovirt.engine.core.utils.lock.LockManager
java:module/LockManager!org.ovirt.engine.core.utils.lock.LockManager
java:global/engine/bll/LockManager
java:app/bll/LockManager
java:module/LockManager
2024-06-11 22:18:14,798+03 INFO [org.jboss.as.ejb3.deployment] (MSC
service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named
'Backend' in deployment unit 'subdeployment "bll.jar" of deployment
"engine.ear"' are as follows:
java:global/engine/bll/Backend!org.ovirt.engine.core.bll.interfaces.BackendCommandObjectsHandler
java:app/bll/Backend!org.ovirt.engine.core.bll.interfaces.BackendCommandObjectsHandler
java:module/Backend!org.ovirt.engine.core.bll.interfaces.BackendCommandObjectsHandler
java:global/engine/bll/Backend!org.ovirt.engine.core.bll.interfaces.BackendInternal
java:app/bll/Backend!org.ovirt.engine.core.bll.interfaces.BackendInternal
java:module/Backend!org.ovirt.engine.core.bll.interfaces.BackendInternal
java:global/engine/bll/Backend!org.ovirt.engine.core.common.interfaces.BackendLocal
java:app/bll/Backend!org.ovirt.engine.core.common.interfaces.BackendLocal
java:module/Backend!org.ovirt.engine.core.common.interfaces.BackendLocal
2024-06-11 22:18:14,798+03 INFO [org.jboss.as.ejb3.deployment] (MSC
service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named
'OvirtGlusterSchedulingService' in deployment unit 'subdeployment
"bll.jar" of deployment "engine.ear"' are as follows:
java:global/engine/bll/OvirtGlusterSchedulingService!org.ovirt.engine.core.bll.scheduling.OvirtGlusterSchedulingService
java:app/bll/OvirtGlusterSchedulingService!org.ovirt.engine.core.bll.scheduling.OvirtGlusterSchedulingService
java:module/OvirtGlusterSchedulingService!org.ovirt.engine.core.bll.scheduling.OvirtGlusterSchedulingService
java:global/engine/bll/OvirtGlusterSchedulingService
java:app/bll/OvirtGlusterSchedulingService
java:module/OvirtGlusterSchedulingService
2024-06-11 22:18:14,799+03 INFO [org.jboss.as.ejb3.deployment] (MSC
service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named
'InitBackendServicesOnStartupBean' in deployment unit 'subdeployment
"bll.jar" of deployment "engine.ear"' are as follows:
java:global/engine/bll/InitBackendServicesOnStartupBean!org.ovirt.engine.core.bll.InitBackendServicesOnStartup
java:app/bll/InitBackendServicesOnStartupBean!org.ovirt.engine.core.bll.InitBackendServicesOnStartup
java:module/InitBackendServicesOnStartupBean!org.ovirt.engine.core.bll.InitBackendServicesOnStartup
java:global/engine/bll/InitBackendServicesOnStartupBean
java:app/bll/InitBackendServicesOnStartupBean
java:module/InitBackendServicesOnStartupBean
2024-06-11 22:18:14,799+03 INFO [org.jboss.as.ejb3.deployment] (MSC
service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named
'ManagedBlockStorageDiskUtil' in deployment unit 'subdeployment
"bll.jar" of deployment "engine.ear"' are as follows:
java:global/engine/bll/ManagedBlockStorageDiskUtil!org.ovirt.engine.core.bll.storage.disk.managedblock.util.ManagedBlockStorageDiskUtil
java:app/bll/ManagedBlockStorageDiskUtil!org.ovirt.engine.core.bll.storage.disk.managedblock.util.ManagedBlockStorageDiskUtil
java:module/ManagedBlockStorageDiskUtil!org.ovirt.engine.core.bll.storage.disk.managedblock.util.ManagedBlockStorageDiskUtil
java:global/engine/bll/ManagedBlockStorageDiskUtil
java:app/bll/ManagedBlockStorageDiskUtil
java:module/ManagedBlockStorageDiskUtil
2024-06-11 22:18:14,799+03 INFO [org.jboss.as.ejb3.deployment] (MSC
service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named
'MacPoolPerCluster' in deployment unit 'subdeployment "bll.jar" of
deployment "engine.ear"' are as follows:
java:global/engine/bll/MacPoolPerCluster!org.ovirt.engine.core.bll.network.macpool.MacPoolPerCluster
java:app/bll/MacPoolPerCluster!org.ovirt.engine.core.bll.network.macpool.MacPoolPerCluster
java:module/MacPoolPerCluster!org.ovirt.engine.core.bll.network.macpool.MacPoolPerCluster
java:global/engine/bll/MacPoolPerCluster
java:app/bll/MacPoolPerCluster
java:module/MacPoolPerCluster
2024-06-11 22:18:14,934+03 INFO [org.jboss.as.clustering.infinispan]
(ServerService Thread Pool -- 55) WFLYCLINF0002: Started realmRevisions
cache from keycloak container
2024-06-11 22:18:14,943+03 INFO [org.jboss.as.clustering.infinispan]
(ServerService Thread Pool -- 55) WFLYCLINF0002: Started userRevisions
cache from keycloak container
2024-06-11 22:18:14,950+03 INFO [org.jboss.as.clustering.infinispan]
(ServerService Thread Pool -- 55) WFLYCLINF0002: Started
authorizationRevisions cache from keycloak container
2024-06-11 22:18:15,074+03 INFO [org.infinispan.CONTAINER]
(ServerService Thread Pool -- 50) ISPN000556: Starting user marshaller
'org.wildfly.clustering.infinispan.marshalling.jboss.JBossMarshaller'
2024-06-11 22:18:15,095+03 INFO [org.jboss.as.clustering.infinispan]
(ServerService Thread Pool -- 50) WFLYCLINF0002: Started dashboard cache
from ovirt-engine container
2024-06-11 22:18:15,095+03 INFO [org.jboss.as.clustering.infinispan]
(ServerService Thread Pool -- 52) WFLYCLINF0002: Started inventory cache
from ovirt-engine container
2024-06-11 22:18:18,858+03 INFO
[org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool --
56) RESTEASY002225: Deploying javax.ws.rs.core.Application: class
org.ovirt.engine.api.restapi.BackendApplication
2024-06-11 22:18:18,859+03 INFO
[org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool --
56) RESTEASY002220: Adding singleton resource
org.ovirt.engine.api.restapi.resource.BackendApiResource from
Application class org.ovirt.engine.api.restapi.BackendApplication
2024-06-11 22:18:18,859+03 INFO
[org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool --
56) RESTEASY002210: Adding provider singleton
org.ovirt.engine.api.restapi.resource.validation.JsonExceptionMapper
from Application class org.ovirt.engine.api.restapi.BackendApplication
2024-06-11 22:18:18,859+03 INFO
[org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool --
56) RESTEASY002210: Adding provider singleton
org.ovirt.engine.api.restapi.resource.validation.IOExceptionMapper from
Application class org.ovirt.engine.api.restapi.BackendApplication
2024-06-11 22:18:18,859+03 INFO
[org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool --
56) RESTEASY002210: Adding provider singleton
org.ovirt.engine.api.restapi.resource.validation.MalformedIdExceptionMapper
from Application class org.ovirt.engine.api.restapi.BackendApplication
2024-06-11 22:18:18,859+03 INFO
[org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool --
56) RESTEASY002210: Adding provider singleton
org.ovirt.engine.api.restapi.resource.validation.ValidationExceptionMapper
from Application class org.ovirt.engine.api.restapi.BackendApplication
2024-06-11 22:18:18,860+03 INFO
[org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool --
56) RESTEASY002210: Adding provider singleton
org.ovirt.engine.api.restapi.resource.validation.MappingExceptionMapper
from Application class org.ovirt.engine.api.restapi.BackendApplication
2024-06-11 22:18:18,919+03 INFO [org.wildfly.extension.undertow]
(ServerService Thread Pool -- 56) WFLYUT0021: Registered web context:
'/ovirt-engine/api' for server 'default-server'
2024-06-11 22:18:19,391+03 INFO
[org.hibernate.jpa.internal.util.LogHelper] (ServerService Thread Pool
-- 55) HHH000204: Processing PersistenceUnitInfo [
name: keycloak-default
...]
2024-06-11 22:18:19,455+03 INFO [org.hibernate.Version] (ServerService
Thread Pool -- 55) HHH000412: Hibernate Core {5.3.20.Final}
2024-06-11 22:18:19,457+03 INFO [org.hibernate.cfg.Environment]
(ServerService Thread Pool -- 55) HHH000206: hibernate.properties not
found
2024-06-11 22:18:19,589+03 INFO
[org.hibernate.annotations.common.Version] (ServerService Thread Pool --
55) HCANN000001: Hibernate Commons Annotations {5.0.5.Final}
2024-06-11 22:18:19,778+03 INFO [org.hibernate.dialect.Dialect]
(ServerService Thread Pool -- 55) HHH000400: Using dialect:
org.hibernate.dialect.PostgreSQL95Dialect
2024-06-11 22:18:19,851+03 INFO
[org.hibernate.engine.jdbc.env.internal.LobCreatorBuilderImpl]
(ServerService Thread Pool -- 55) HHH000424: Disabling contextual LOB
creation as createClob() method threw error :
java.lang.reflect.InvocationTargetException
2024-06-11 22:18:19,856+03 INFO [org.hibernate.type.BasicTypeRegistry]
(ServerService Thread Pool -- 55) HHH000270: Type registration
[java.util.UUID] overrides previous :
org.hibernate.type.UUIDBinaryType@71c04561
2024-06-11 22:18:19,865+03 INFO
[org.hibernate.envers.boot.internal.EnversServiceImpl] (ServerService
Thread Pool -- 55) Envers integration enabled? : true
2024-06-11 22:18:20,282+03 INFO [org.hibernate.orm.beans]
(ServerService Thread Pool -- 55) HHH10005002: No explicit CDI
BeanManager reference was passed to Hibernate, but CDI is available on
the Hibernate ClassLoader.
2024-06-11 22:18:21,006+03 INFO [org.jboss.weld.Bootstrap] (Weld Thread
Pool -- 1) WELD-001125: Illegal bean type
org.ovirt.engine.core.dao.DefaultGenericDao<org.ovirt.engine.core.common.businessentities.Provider<?>,
org.ovirt.engine.core.compat.Guid> ignored on
[EnhancedAnnotatedTypeImpl] public @Named @Singleton class
org.ovirt.engine.core.dao.provider.ProviderDaoImpl
2024-06-11 22:18:21,016+03 INFO [org.jboss.weld.Bootstrap] (Weld Thread
Pool -- 1) WELD-001125: Illegal bean type interface
org.ovirt.engine.core.dao.ReadDao<org.ovirt.engine.core.common.businessentities.Provider<?>,class
org.ovirt.engine.core.compat.Guid> ignored on
[EnhancedAnnotatedTypeImpl] public @Named @Singleton class
org.ovirt.engine.core.dao.provider.ProviderDaoImpl
2024-06-11 22:18:21,016+03 INFO [org.jboss.weld.Bootstrap] (Weld Thread
Pool -- 1) WELD-001125: Illegal bean type class
org.ovirt.engine.core.dao.DefaultReadDao<org.ovirt.engine.core.common.businessentities.Provider<?>,class
org.ovirt.engine.core.compat.Guid> ignored on
[EnhancedAnnotatedTypeImpl] public @Named @Singleton class
org.ovirt.engine.core.dao.provider.ProviderDaoImpl
2024-06-11 22:18:21,016+03 INFO [org.jboss.weld.Bootstrap] (Weld Thread
Pool -- 1) WELD-001125: Illegal bean type
org.ovirt.engine.core.dao.GenericDao<org.ovirt.engine.core.common.businessentities.Provider<?>,
org.ovirt.engine.core.compat.Guid> ignored on
[EnhancedAnnotatedTypeImpl] public @Named @Singleton class
org.ovirt.engine.core.dao.provider.ProviderDaoImpl
2024-06-11 22:18:21,016+03 INFO [org.jboss.weld.Bootstrap] (Weld Thread
Pool -- 1) WELD-001125: Illegal bean type interface
org.ovirt.engine.core.dao.ModificationDao<org.ovirt.engine.core.common.businessentities.Provider<?>,class
org.ovirt.engine.core.compat.Guid> ignored on
[EnhancedAnnotatedTypeImpl] public @Named @Singleton class
org.ovirt.engine.core.dao.provider.ProviderDaoImpl
2024-06-11 22:18:21,016+03 INFO [org.jboss.weld.Bootstrap] (Weld Thread
Pool -- 1) WELD-001125: Illegal bean type
org.ovirt.engine.core.dao.SearchDao<org.ovirt.engine.core.common.businessentities.Provider<?>>
ignored on [EnhancedAnnotatedTypeImpl] public @Named @Singleton class
org.ovirt.engine.core.dao.provider.ProviderDaoImpl
2024-06-11 22:18:21,061+03 INFO [org.jboss.weld.Bootstrap] (Weld Thread
Pool -- 2) WELD-001125: Illegal bean type
org.springframework.jdbc.core.RowMapper<org.ovirt.engine.core.common.businessentities.Provider<?>>
ignored on [EnhancedAnnotatedTypeImpl] private static class
org.ovirt.engine.core.dao.provider.ProviderDaoImpl$ProviderRowMapper
2024-06-11 22:18:21,788+03 INFO
[org.hibernate.hql.internal.QueryTranslatorFactoryInitiator]
(ServerService Thread Pool -- 55) HHH000397: Using
ASTQueryTranslatorFactory
2024-06-11 22:18:22,098+03 INFO [org.wildfly.extension.undertow]
(ServerService Thread Pool -- 51) WFLYUT0021: Registered web context:
'/ovirt-engine/docs' for server 'default-server'
2024-06-11 22:18:22,103+03 INFO [org.wildfly.extension.undertow]
(ServerService Thread Pool -- 56) WFLYUT0021: Registered web context:
'/' for server 'default-server'
2024-06-11 22:18:22,113+03 INFO [org.wildfly.extension.undertow]
(ServerService Thread Pool -- 51) WFLYUT0021: Registered web context:
'/ovirt-engine/services' for server 'default-server'
2024-06-11 22:18:22,159+03 WARN
[org.jboss.jca.core.connectionmanager.pool.strategy.OnePool]
(ServerService Thread Pool -- 51) IJ000407: No lazy enlistment available
for ENGINEDataSource
2024-06-11 22:18:22,171+03 WARN
[org.jboss.jca.core.connectionmanager.pool.strategy.OnePool]
(ServerService Thread Pool -- 51) IJ000407: No lazy enlistment available
for DWHDataSource
2024-06-11 22:18:22,182+03 INFO [org.wildfly.extension.undertow]
(ServerService Thread Pool -- 49) WFLYUT0021: Registered web context:
'/ovirt-engine' for server 'default-server'
2024-06-11 22:18:22,201+03 INFO [org.wildfly.extension.undertow]
(ServerService Thread Pool -- 51) WFLYUT0021: Registered web context:
'/ovirt-engine/webadmin' for server 'default-server'
Per my understanding, this doesn't seem like an issue with the
PostgreSQL JDBC connector as referenced here
https://lists.ovirt.org/archives/list/users@ovirt.org/thread/SBCWNXLFLJBK...
, but I could be mistaken. What further steps could be taken to mitigate
this issue? This is a new deployment, so I'd assume there'd be issues if
upgrading older instances but not with new deployments.. The server is
running AlmaLinux 9.4 so maybe this would affect this?
Best regards,
Samu Paaso
7 months
