- Users - oVirt List Archives

CPU support Xeon E5345
by Mikhail Po 11 Aug '23

11 Aug '23

Is it possible to install oVirt 4.3/4.4 on ProLiant BL460c G1 with Intel Xeon E5345 processor(a)2.33GHz ? In case of a setup failure, [ERROR] is fatal:[localhost]: FAILED!=>{"Changed":false,"message":"The host was inoperable, deployment errors: code 156:Host host1.test.com disabled because the host CPU type in this case is not supported by the cluster compatibility version or is not supported at all, code 9000: Failed to check the power management configuration for the host host1.test.com ., correct accordingly and re-deploy."

2 2

Trouble restoring + upgrading to ovirt 4.5 system after host crashed
by David Johnson 09 Aug '23

09 Aug '23

Good afternoon all, We had a confluence of events hit all at once and need help desperately. Our Ovirt engine system recently crashed and is unrecoverable. Due to a power maintenance event at the data center, 1/3 of our VM's are offline. I have recent backups from the engine created with engine-backup. I installed a clean Centos 9 and followed the directions to install the ovirt-engine . After I restore the backup, the engine-setup fails on the keycloak configuration. *From clean system:* *Install: **(Observe failed scriptlet during install, but rom install still succeeds)* [root@ovirt2 administrator]# dnf install -y ovirt-engine Last metadata expiration check: 2:08:15 ago on Tue 08 Aug 2023 10:11:31 AM CDT. Dependencies resolved. ============================================================================================================================================================= Package Architecture Version Repository Size ============================================================================================================================================================= Installing: ovirt-engine noarch 4.5.4-1.el9 centos-ovirt45 13 M Installing dependencies: SuperLU x86_64 5.3.0-2.el9 epel 182 k (Snip ...) * Running scriptlet: ovirt-vmconsole-1.0.9-1.el9.noarch 60/425Failed to resolve allow statement at /var/lib/selinux/targeted/tmp/modules/400/ovirt_vmconsole/cil:539Failed to resolve AST/usr/sbin/semodule: Failed!* (Snip ...) xmlrpc-common-3.1.3-1.1.el9.noarch xorg-x11-fonts-ISO8859-1-100dpi-7.5-33.el9.noarch zziplib-0.13.71-9.el9.x86_64 Complete! *Engine-restore (no visible issues):* [root@ovirt2 administrator]# engine-backup --mode=restore --log=restore1.log --file=Downloads/engine-2023-08-06.22.00.02.bak --provision-all-databases --restore-permissions Start of engine-backup with mode 'restore' scope: all archive file: Downloads/engine-2023-08-06.22.00.02.bak log file: restore1.log Preparing to restore: - Unpacking file 'Downloads/engine-2023-08-06.22.00.02.bak' Restoring: - Files ------------------------------------------------------------------------------ Please note: Operating system is different from the one used during backup. Current operating system: centos9 Operating system at backup: centos8 Apache httpd configuration will not be restored. You will be asked about it on the next engine-setup run. ------------------------------------------------------------------------------ Provisioning PostgreSQL users/databases: - user 'engine', database 'engine' - user 'ovirt_engine_history', database 'ovirt_engine_history' - user 'ovirt_engine_history_grafana' on 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 2023-08-06 22:00:19.000000000 -0500 . 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@ovirt2 administrator]# *Engine-setup :* [root@ovirt2 administrator]# 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-20230808124501-joveku.log Version: otopi-1.10.3 (otopi-1.10.3-1.el9) [ INFO ] The engine DB has been restored from a backup *[ ERROR ] Failed to execute stage 'Environment setup': Cannot connect to Keycloak database 'ovirt_engine_keycloak' using existing credentials: ovirt_engine_keycloak@localhost:5432*[ INFO ] Stage: Clean up Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20230808124501-joveku.log [ INFO ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20230808124504-setup.conf' [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination *[ ERROR ] Execution of setup failed[root@ovirt2 administrator]#* *Engine-cleanup results:* (snip) [ INFO ] Stage: Clean up Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-remove-20230808120445-mj4eef.log [ INFO ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20230808120508-cleanup.conf' [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ INFO ] Execution of cleanup completed successfully [root@cen-90-tmpl administrator]# *Engine backup (restore) results:* [root@ovirt2 administrator]# engine-backup --mode=restore --log=restore1.log --file=Downloads/engine-2023-08-06.22.00.02.bak --provision-all-databases --restore-permissions Start of engine-backup with mode 'restore' scope: all archive file: Downloads/engine-2023-08-06.22.00.02.bak log file: restore1.log Preparing to restore: - Unpacking file 'Downloads/engine-2023-08-06.22.00.02.bak' Restoring: - Files ------------------------------------------------------------------------------ Please note: Operating system is different from the one used during backup. Current operating system: centos9 Operating system at backup: centos8 Apache httpd configuration will not be restored. You will be asked about it on the next engine-setup run. ------------------------------------------------------------------------------ Provisioning PostgreSQL users/databases: - user 'engine', database 'engine' *FATAL: Existing database 'engine' or user 'engine' found and temporary ones created - Please clean up everything and try again* Any advice would be appreciated. *David Johnson*

2 2

Trouble restoring + upgrading to ovirt 4.5 system after host crashed
by David Johnson 09 Aug '23

09 Aug '23

Update: I have confirmed the original ovirt version has an ovirt_engine_keycloak database, but the database was not backed up by the engine-backup command *David Johnson* *Director of Development, Maxis Technology* 844.696.2947 ext 702 (o) | 479.531.3590 (c) <https://www.linkedin.com/in/pojoguy/> <https://maxistechnology.com/wp-content/uploads/vcards/vcard-David_Johnson.v…> <https://maxistechnology.com/> *Follow us:* <https://www.linkedin.com/company/maxis-tech-inc/>

1 1

ovirt node NonResponsive
by carlos.mendes＠mgo.cv 09 Aug '23

09 Aug '23

Hello, I have ovirt with two nodes and one that are NonResponsive and and cant manage them because they are in Unknown state. It seems that nodes lost connection for a while with their gateway. The node (ovirt2) however is having consistent problems. The follow sequence of events is reproducible and is causing the host to enter a "NonOperational" state on the cluster: What is the proper way of restoring management? I have a two-node cluster with the ovirt manager running standlone on the virtual maachine CentOS-Stream-9 and the ovirt node running the most recent oVirt Node 4.5.4 software. I can then re-activate ovirt2, which appears as green for approximately 5 minutes and then repeats all of the above issues. What can I do to troubleshoot this?

1 0

How restore nodes ovirt UP from NonResponsive and VMs executing
by José Pascual 08 Aug '23

08 Aug '23

Hello, I have ovirt with two nodes that are NonResponsive and all the VMs are properly executing but i cant manage them because are in Unknown state. It seems that nodes lost connection for a while with their gateway. I have thought of first restarting the node where the engine is not running and trying to put in UP. Then restart the engine from within de VM to see if it starts up on this node. What is the proper way of restoring management? I Thanks, Best Regards -- Saludos, José Pascual Gallud Martínez Nombre | Dpto. Ingeniería <http://telfy.com/>

3 2

Re: Some problems with ovirt
by אריה קלטר 07 Aug '23

07 Aug '23

Hi, Sorry for the late reply I tried now to get logs for the vm, for the scenario of stucked in the middle of the power up because of no disk. The vm id is 486cea97-ed56-47d4-930b-5f85c51ad3cf, the vm name is kc26-1 [image: image.png] About the second problem, with the migration, i also attached the logs here, both from the source and from the destination server. Any clue how to solve the problems? It is רeally annoying that a lot of times when I am trying to power on the vm it hangs like that, and when the system is doing live migration for the engine vm it is always not working and I need to power it off and on manually from the cli. For both scenarios i uploaded bot the /var/log/vdsm/vdsm.log and /var/log/libvirt/qemu/<vmname>.log

1 0

Certificates expired...
by Jason P. Thomas 07 Aug '23

07 Aug '23

We're moving to a new facility and pretty much building the infrastructure out from scratch. As such, the oVirt 4.4 cluster at our old location has floated under notice because it has just worked for years. In July it seems some of the certs expired (specifically the engine apache cert) and we just noticed it. I followed a post for changing the apache cert and that allowed us to login to the engine web interface, but nothing in the interface showed as connected. VMs are still running, I even rebooted one via ssh before realizing the certificate issues. In "Events" in the engine, it was complaining about certs being expired on the hosts. I found this post to this mailing list and followed the instructions possibly in error: https://lists.ovirt.org/archives/list/users@ovirt.org/thread/NHJNETOIMSHDXM… Now the engine won't start at all and I'm afraid I'm one power outage away from complete disaster. I need to keep the old location up and functioning for another 4-6 months, so any insights would be greatly appreciated. Sincerely, Jason P. Thomas

5 11

Problems running CentOS 9 Stream GenericCloud guests
by Gianluca Amato 04 Aug '23

04 Aug '23

Hello everyone, I'm trying to run CentOS 9 Stream GenericCloud as a guest in oVirt 4.5.4. While the images in the ovirt-image-repository seems to work fine (in particular, I've tried version 20211119.0), the latest version (20230727.1) does not start. After the initial boot messages, it gives the error: Starting dracut mount hook dracut-mount[413]: Warning: Can't mount root filesystem Starting dracut emergency shell and brings me to the emergency shell. Is this some known bug ? Note that if I start from the old image and then upgrade all the packages, I have no problems at all. Thanks in advance for any help. Gianluca

2 1

Installing oVirt as a self-hosted engine - big big problem :()
by Jorge Visentini 03 Aug '23

03 Aug '23

Hi guys, starting the weekend with a "cucumber" like that in my hands. I've been racking my brains for about 4 days to deploy a new engine. Turns out I already tested *4.4.10*, *4.5.4.x*, and *4.5.5(master)* (el8 and el9) and none is working. It seems to me to be ansible or a python problem, but I'm not sure. I've read several oVirt reddit and github threads, but they seem to have no effect anymore. I believe it's some package in the CentOS Stream repositories, *but unfortunately I don't have it frozen locally here*. Deploy hangs at *[ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Wait for the host to be up]* I already tried to update the version of *python netaddr* as I read in git and it still didn't work I also tried to *freeze the ansible update* in the engine and it didn't work. I updated the version of *ovirt-ansible-collection to ovirt-ansible-collection-3.1.3-0.1.master.20230420113738.el8.noarch.rpm* and it didn't work either... *The error seems to be on all oVirt builds*, but I don't know what I'm doing wrong anymore because I can't pinpoint where the error is. I appreciate any tips *Below are some log outputs:* [root@ksmmi1r02ovirt36 ~]# tail -f /var/log/vdsm/vdsm.log 2023-07-07 22:23:30,144-0300 INFO (vmrecovery) [vdsm.api] FINISH getConnectedStoragePoolsList return={'poollist': []} from=internal, task_id=6df1f5ed-0f41-4001-bb2e-e50fb0214ac7 (api:37) 2023-07-07 22:23:30,144-0300 INFO (vmrecovery) [vds] recovery: waiting for storage pool to go up (clientIF:723) 2023-07-07 22:23:35,146-0300 INFO (vmrecovery) [vdsm.api] START getConnectedStoragePoolsList() from=internal, task_id=bd2a755d-3488-4b43-8ca4-44717dd6b017 (api:31) 2023-07-07 22:23:35,146-0300 INFO (vmrecovery) [vdsm.api] FINISH getConnectedStoragePoolsList return={'poollist': []} from=internal, task_id=bd2a755d-3488-4b43-8ca4-44717dd6b017 (api:37) 2023-07-07 22:23:35,146-0300 INFO (vmrecovery) [vds] recovery: waiting for storage pool to go up (clientIF:723) 2023-07-07 22:23:39,320-0300 INFO (periodic/3) [vdsm.api] START repoStats(domains=()) from=internal, task_id=68567ce3-b579-469d-a46d-7bafc7b3e6bd (api:31) 2023-07-07 22:23:39,320-0300 INFO (periodic/3) [vdsm.api] FINISH repoStats return={} from=internal, task_id=68567ce3-b579-469d-a46d-7bafc7b3e6bd (api:37) 2023-07-07 22:23:40,151-0300 INFO (vmrecovery) [vdsm.api] START getConnectedStoragePoolsList() from=internal, task_id=fadcf734-9f7e-4681-8764-9d3863718644 (api:31) 2023-07-07 22:23:40,151-0300 INFO (vmrecovery) [vdsm.api] FINISH getConnectedStoragePoolsList return={'poollist': []} from=internal, task_id=fadcf734-9f7e-4681-8764-9d3863718644 (api:37) 2023-07-07 22:23:40,151-0300 INFO (vmrecovery) [vds] recovery: waiting for storage pool to go up (clientIF:723) 2023-07-07 22:23:44,183-0300 INFO (jsonrpc/1) [api.host] START getAllVmStats() from=::1,49920 (api:31) 2023-07-07 22:23:44,184-0300 INFO (jsonrpc/1) [api.host] FINISH getAllVmStats return={'status': {'code': 0, 'message': 'Done'}, 'statsList': (suppressed)} from=::1,49920 (api:37) 2023-07-07 22:23:45,157-0300 INFO (vmrecovery) [vdsm.api] START getConnectedStoragePoolsList() from=internal, task_id=504d8028-35be-45a3-b24d-4ec7cbc82f7e (api:31) 2023-07-07 22:23:45,157-0300 INFO (vmrecovery) [vdsm.api] FINISH getConnectedStoragePoolsList return={'poollist': []} from=internal, task_id=504d8028-35be-45a3-b24d-4ec7cbc82f7e (api:37) 2023-07-07 22:23:45,157-0300 INFO (vmrecovery) [vds] recovery: waiting for storage pool to go up (clientIF:723) 2023-07-07 22:23:50,162-0300 INFO (vmrecovery) [vdsm.api] START getConnectedStoragePoolsList() from=internal, task_id=297ad1df-c855-4fbb-a89f-dfbe7a1b60a2 (api:31) 2023-07-07 22:23:50,162-0300 INFO (vmrecovery) [vdsm.api] FINISH getConnectedStoragePoolsList return={'poollist': []} from=internal, task_id=297ad1df-c855-4fbb-a89f-dfbe7a1b60a2 (api:37) 2023-07-07 22:23:50,162-0300 INFO (vmrecovery) [vds] recovery: waiting for storage pool to go up (clientIF:723) [root@ksmmi1r02ovirt36 ~]# journalctl -f -- Logs begin at Fri 2023-07-07 21:57:13 -03. -- Jul 07 22:24:46 ksmmi1r02ovirt36.kosmo.cloud ansible-async_wrapper.py[13790]: 13791 still running (86045) Jul 07 22:24:50 ksmmi1r02ovirt36.kosmo.cloud platform-python[22812]: ansible-ovirt_host_info Invoked with pattern=name=ksmmi1r02ovirt36.kosmo.cloud auth={'token': 'eyJhbGciOiJSUzI1NiIsInR5cCIgOiAiSldUIiwia2lkIiA6ICIyZzVfWUdWX08wSFJoWnlVeFNkdGl4d0liRWV6Wkp5NTgwN3BaXzUxelBvIn0.eyJleHAiOjE2ODg3OTY0MzAsImlhdCI6MTY4ODc3OTE1MCwianRpIjoiOTBlOWE5ZTAtMmExNS00MzNiLWIxOGQtMmUwNmI4MTQ5NGE2IiwiaXNzIjoiaHR0cHM6Ly9rc21lbmdpbmUwMS5rb3Ntby5jbG91ZC9vdmlydC1lbmdpbmUtYXV0aC9yZWFsbXMvb3ZpcnQtaW50ZXJuYWwiLCJhdWQiOiJhY2NvdW50Iiwic3ViIjoiYWRkMWMyYzYtYzJjMy00N2M4LWI1ODUtNGI2MTU2ZDAxYTE3IiwidHlwIjoiQmVhcmVyIiwiYXpwIjoib3ZpcnQtZW5naW5lLWludGVybmFsIiwic2Vzc2lvbl9zdGF0ZSI6IjNhMWUzZTU2LWIyZTUtNGMyYi05YTIxLThjZjE1YzY4NzlmNiIsImFjciI6IjEiLCJhbGxvd2VkLW9yaWdpbnMiOlsiaHR0cHM6Ly9rc21lbmdpbmUwMS5rb3Ntby5jbG91ZCJdLCJyZWFsbV9hY2Nlc3MiOnsicm9sZXMiOlsiZGVmYXVsdC1yb2xlcy1vdmlydC1pbnRlcm5hbCIsIm9mZmxpbmVfYWNjZXNzIiwidW1hX2F1dGhvcml6YXRpb24iXX0sInJlc291cmNlX2FjY2VzcyI6eyJhY2NvdW50Ijp7InJvbGVzIjpbIm1hbmFnZS1hY2NvdW50IiwibWFuYWdlLWFjY291bnQtbGlua3MiLCJ2aWV3LXByb2ZpbGUiXX19LCJzY29wZSI6Im92aXJ0LWV4dD10b2tlbjpwYXNzd29yZC1hY2Nlc3Mgb3ZpcnQtZXh0PXRva2VuLWluZm86cHVibGljLWF1dGh6LXNlYXJjaCBvdmlydC1hcHAtYXBpIG92aXJ0LWV4dD10b2tlbi1pbmZvOnZhbGlkYXRlIHByb2ZpbGUgZW1haWwgb3ZpcnQtZXh0PXRva2VuLWluZm86YXV0aHotc2VhcmNoIiwic2lkIjoiM2ExZTNlNTYtYjJlNS00YzJiLTlhMjEtOGNmMTVjNjg3OWY2IiwiZW1haWxfdmVyaWZpZWQiOmZhbHNlLCJncm91cHMiOlsiL292aXJ0LWFkbWluaXN0cmF0b3IiXSwicHJlZmVycmVkX3VzZXJuYW1lIjoiYWRtaW5Ab3ZpcnQiLCJlbWFpbCI6ImFkbWluQGxvY2FsaG9zdCJ9.o9PsulNw0urPphWITcB6Y3wpHQiiQ0v00su6XorITcvNElzkfHqyYfJd8W-kIfgElh6BNnCmYyIwtX7t3T4-PiLgDdipH1J9uzuDBXkmNBNcVmFimfUAqyC8aUITK56CqZ5TyRyHqhOicPciqGSY8R98hQ8I8y11w2RiIFT0rQYnRev75gjKoqUH29uNyeCAdTyKvPSGHNm1pLLrtPUmk-JCGmsYytNRCMHAPoNIlZP3k94PbQ9pI4jZ5O7kcRSgJik8tUDOVglcL4g0MoAJwracek2MUTvK8pDpRghI9hSQVLFtAXCyGRxfHHzTko4EbHBbFlz5s3pfs2kbF6TFmw', 'url': 'https://ksmengine01.kosmo.cloud/ovirt-engine/api', 'ca_file': None, 'insecure': True, 'timeout': 0, 'compress': True, 'kerberos': False, 'headers': None, 'hostname': None, 'username': None, 'password': None} fetch_nested=False nested_attributes=[] follow=[] all_content=False cluster_version=None Jul 07 22:24:51 ksmmi1r02ovirt36.kosmo.cloud ansible-async_wrapper.py[13790]: 13791 still running (86040) Jul 07 22:24:56 ksmmi1r02ovirt36.kosmo.cloud ansible-async_wrapper.py[13790]: 13791 still running (86035) Jul 07 22:25:00 ksmmi1r02ovirt36.kosmo.cloud platform-python[22829]: ansible-ovirt_host_info Invoked with pattern=name=ksmmi1r02ovirt36.kosmo.cloud auth={'token': 'eyJhbGciOiJSUzI1NiIsInR5cCIgOiAiSldUIiwia2lkIiA6ICIyZzVfWUdWX08wSFJoWnlVeFNkdGl4d0liRWV6Wkp5NTgwN3BaXzUxelBvIn0.eyJleHAiOjE2ODg3OTY0MzAsImlhdCI6MTY4ODc3OTE1MCwianRpIjoiOTBlOWE5ZTAtMmExNS00MzNiLWIxOGQtMmUwNmI4MTQ5NGE2IiwiaXNzIjoiaHR0cHM6Ly9rc21lbmdpbmUwMS5rb3Ntby5jbG91ZC9vdmlydC1lbmdpbmUtYXV0aC9yZWFsbXMvb3ZpcnQtaW50ZXJuYWwiLCJhdWQiOiJhY2NvdW50Iiwic3ViIjoiYWRkMWMyYzYtYzJjMy00N2M4LWI1ODUtNGI2MTU2ZDAxYTE3IiwidHlwIjoiQmVhcmVyIiwiYXpwIjoib3ZpcnQtZW5naW5lLWludGVybmFsIiwic2Vzc2lvbl9zdGF0ZSI6IjNhMWUzZTU2LWIyZTUtNGMyYi05YTIxLThjZjE1YzY4NzlmNiIsImFjciI6IjEiLCJhbGxvd2VkLW9yaWdpbnMiOlsiaHR0cHM6Ly9rc21lbmdpbmUwMS5rb3Ntby5jbG91ZCJdLCJyZWFsbV9hY2Nlc3MiOnsicm9sZXMiOlsiZGVmYXVsdC1yb2xlcy1vdmlydC1pbnRlcm5hbCIsIm9mZmxpbmVfYWNjZXNzIiwidW1hX2F1dGhvcml6YXRpb24iXX0sInJlc291cmNlX2FjY2VzcyI6eyJhY2NvdW50Ijp7InJvbGVzIjpbIm1hbmFnZS1hY2NvdW50IiwibWFuYWdlLWFjY291bnQtbGlua3MiLCJ2aWV3LXByb2ZpbGUiXX19LCJzY29wZSI6Im92aXJ0LWV4dD10b2tlbjpwYXNzd29yZC1hY2Nlc3Mgb3ZpcnQtZXh0PXRva2VuLWluZm86cHVibGljLWF1dGh6LXNlYXJjaCBvdmlydC1hcHAtYXBpIG92aXJ0LWV4dD10b2tlbi1pbmZvOnZhbGlkYXRlIHByb2ZpbGUgZW1haWwgb3ZpcnQtZXh0PXRva2VuLWluZm86YXV0aHotc2VhcmNoIiwic2lkIjoiM2ExZTNlNTYtYjJlNS00YzJiLTlhMjEtOGNmMTVjNjg3OWY2IiwiZW1haWxfdmVyaWZpZWQiOmZhbHNlLCJncm91cHMiOlsiL292aXJ0LWFkbWluaXN0cmF0b3IiXSwicHJlZmVycmVkX3VzZXJuYW1lIjoiYWRtaW5Ab3ZpcnQiLCJlbWFpbCI6ImFkbWluQGxvY2FsaG9zdCJ9.o9PsulNw0urPphWITcB6Y3wpHQiiQ0v00su6XorITcvNElzkfHqyYfJd8W-kIfgElh6BNnCmYyIwtX7t3T4-PiLgDdipH1J9uzuDBXkmNBNcVmFimfUAqyC8aUITK56CqZ5TyRyHqhOicPciqGSY8R98hQ8I8y11w2RiIFT0rQYnRev75gjKoqUH29uNyeCAdTyKvPSGHNm1pLLrtPUmk-JCGmsYytNRCMHAPoNIlZP3k94PbQ9pI4jZ5O7kcRSgJik8tUDOVglcL4g0MoAJwracek2MUTvK8pDpRghI9hSQVLFtAXCyGRxfHHzTko4EbHBbFlz5s3pfs2kbF6TFmw', 'url': 'https://ksmengine01.kosmo.cloud/ovirt-engine/api', 'ca_file': None, 'insecure': True, 'timeout': 0, 'compress': True, 'kerberos': False, 'headers': None, 'hostname': None, 'username': None, 'password': None} fetch_nested=False nested_attributes=[] follow=[] all_content=False cluster_version=None cat /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20230707220613-2t8ze9.log 2023-07-07 22:19:11,816-0300 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 TASK [ovirt.ovirt.hosted_engine_setup : Wait for the host to be up] 2023-07-07 22:39:39,882-0300 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:109 {'changed': False, 'ovirt_hosts': [{'href': '/ovirt-engine/api/hosts/d1bf8fb2-74f4-4954-8c34-66eb99ba2bf3', 'comment': '', 'id': 'd1bf8fb2-74f4-4954-8c34-66eb99ba2bf3', 'name': 'ksmmi1r02ovirt36.kosmo.cloud', 'address': 'ksmmi1r02ovirt36.kosmo.cloud', 'affinity_labels': [], 'auto_numa_status': 'unknown', 'certificate': {'organization': 'kosmo.cloud', 'subject': 'O=kosmo.cloud,CN=ksmmi1r02ovirt36.kosmo.cloud'}, 'cluster': {'href': '/ovirt-engine/api/clusters/d8784faf-8b77-45c8-9fa4-b9b4b0404d95', 'id': 'd8784faf-8b77-45c8-9fa4-b9b4b0404d95'}, 'cpu': {'speed': 0.0, 'topology': {}}, 'cpu_units': [], 'device_passthrough': {'enabled': False}, 'devices': [], 'external_network_provider_configurations': [], 'external_status': 'ok', 'hardware_information': {'supported_rng_sources': []}, 'hooks': [], 'katello_errata': [], 'kdump_status': 'unknown', 'ksm': {'enabled': False}, 'max_scheduling_memory': 0, 'memory': 0, 'network_attachments': [], 'nics': [], 'numa_nodes': [], 'numa_supported': False, 'os': {'custom_kernel_cmdline': ''}, 'ovn_configured': False, 'permissions': [], 'port': 54321, 'power_management': {'automatic_pm_enabled': True, 'enabled': False, 'kdump_detection': True, 'pm_proxies': []}, 'protocol': 'stomp', 'reinstallation_required': False, 'se_**FILTERED**': {}, 'spm': {'priority': 5, 'status': 'none'}, 'ssh': {'fingerprint': 'SHA256:Nr04m1g0UxbpqxwMBr93DLHz2m2wzR8+xFJhBVNovHY', 'port': 22, 'public_key': 'ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBE2EdJn0vJiJUagEK3w2G2nHmziJJasailwapaL06qWU2+BkPwkokSvyK07APhwyynnz6lw8J4y/kWv12D7/r+s='}, 'statistics': [], 'status': 'install_failed', 'storage_connection_extensions': [], 'summary': {'total': 0}, 'tags': [], 'transparent_huge_pages': {'enabled': False}, 'type': 'rhel', 'unmanaged_networks': [], 'update_available': False, 'vgpu_placement': 'consolidated'}], 'invocation': {'module_args': {'pattern': 'name=ksmmi1r02ovirt36.kosmo.cloud', 'fetch_nested': False, 'nested_attributes': [], 'follow': [], 'all_content': False, 'cluster_version': None}}, '_ansible_no_log': None, 'attempts': 120} 2023-07-07 22:39:39,983-0300 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:109 ignored: [localhost]: FAILED! => {"attempts": 120, "changed": false, "ovirt_hosts": [{"address": "ksmmi1r02ovirt36.kosmo.cloud", "affinity_labels": [], "auto_numa_status": "unknown", "certificate": {"organization": "kosmo.cloud", "subject": "O=kosmo.cloud,CN=ksmmi1r02ovirt36.kosmo.cloud"}, "cluster": {"href": "/ovirt-engine/api/clusters/d8784faf-8b77-45c8-9fa4-b9b4b0404d95", "id": "d8784faf-8b77-45c8-9fa4-b9b4b0404d95"}, "comment": "", "cpu": {"speed": 0.0, "topology": {}}, "cpu_units": [], "device_passthrough": {"enabled": false}, "devices": [], "external_network_provider_configurations": [], "external_status": "ok", "hardware_information": {"supported_rng_sources": []}, "hooks": [], "href": "/ovirt-engine/api/hosts/d1bf8fb2-74f4-4954-8c34-66eb99ba2bf3", "id": "d1bf8fb2-74f4-4954-8c34-66eb99ba2bf3", "katello_errata": [], "kdump_status": "unknown", "ksm": {"enabled": false}, "max_scheduling_memory": 0, "memory": 0, "name": "ksmmi1r02ovirt36.kosmo.cloud", "network_attachments": [], "nics": [], "numa_nodes": [], "numa_supported": false, "os": {"custom_kernel_cmdline": ""}, "ovn_configured": false, "permissions": [], "port": 54321, "power_management": {"automatic_pm_enabled": true, "enabled": false, "kdump_detection": true, "pm_proxies": []}, "protocol": "stomp", "reinstallation_required": false, "se_**FILTERED**": {}, "spm": {"priority": 5, "status": "none"}, "ssh": {"fingerprint": "SHA256:Nr04m1g0UxbpqxwMBr93DLHz2m2wzR8+xFJhBVNovHY", "port": 22, "public_key": "ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBE2EdJn0vJiJUagEK3w2G2nHmziJJasailwapaL06qWU2+BkPwkokSvyK07APhwyynnz6lw8J4y/kWv12D7/r+s="}, "statistics": [], "status": "install_failed", "storage_connection_extensions": [], "summary": {"total": 0}, "tags": [], "transparent_huge_pages": {"enabled": false}, "type": "rhel", "unmanaged_networks": [], "update_available": false, "vgpu_placement": "consolidated"}]} 2023-07-07 22:39:40,284-0300 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 TASK [ovirt.ovirt.hosted_engine_setup : Notify the user about a failure] 2023-07-07 22:39:40,685-0300 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:109 {'msg': 'Host is not up, please check logs, perhaps also on the engine machine', '_ansible_no_log': None, 'changed': False} 2023-07-07 22:39:40,786-0300 ERROR otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:113 fatal: [localhost]: FAILED! => {"changed": false, "msg": "Host is not up, please check logs, perhaps also on the engine machine"} Have a nice weekend! -- Att, Jorge Visentini +55 55 98432-9868

2 2

Q: New node install failed
by Andrei Verovski 03 Aug '23

03 Aug '23

Hi, I’m trying to install new node same way as I did several times before, with oVirt 4.5.2.4-1el8. HP Proliant with clean install of CentOS Stream 9 (in previous installs some time ago I used Stream 8). Add new node failed with this error (at the bottom of this e-mail), ovirt-host-deploy-ansible-20230803161025-node15.starlett.lv-827b7fc4-68b6-410f-aa90-f33884923ee8.log (from /var/log/ovirt-engine/host-deploy/) I can attach the whole log but it looks it is not necessary. My engine runs on dedicated PC and is NOT hosted engine. Thanks in advance for any help. Andrei ———————————————— [root@node15 ~]# dnf repolist --enabled repo id repo name appstream CentOS Stream 9 - AppStream baseos CentOS Stream 9 - BaseOS extras-common CentOS Stream 9 - Extras packages ---------------------------------- 2023-08-03 16:10:44 EEST - TASK [ovirt-host-deploy-vdsm : Install ovirt-hosted-engine-setup package] ****** 2023-08-03 16:10:47 EEST - { "uuid" : "b1ffdae5-0679-40c3-8609-1a5b976edc0e", "counter" : 99, "stdout" : "fatal: [node15.starlett.lv]: FAILED! => {\"changed\": false, \"failures\": [\"No package ovirt-hosted-engine-setup available.\"], \"msg\": \"Failed to install some of the specified packages\", \"rc\": 1, \"results\": []}", "start_line" : 87, "end_line" : 88, "runner_ident" : "281cf22b-29e3-4b4f-adc4-a47028b1ba59", "event" : "runner_on_failed", "pid" : 3199, "created" : "2023-08-03T13:10:45.632672", "parent_uuid" : "525400a7-0063-c9c3-eaa2-00000000022c", "event_data" : { "playbook" : "ovirt-host-deploy.yml", "playbook_uuid" : "dcb4654e-2e81-4090-a60e-b007a715eda6", "play" : "all", "play_uuid" : "525400a7-0063-c9c3-eaa2-000000000006", "play_pattern" : "all", "task" : "Install ovirt-hosted-engine-setup package", "task_uuid" : "525400a7-0063-c9c3-eaa2-00000000022c", "task_action" : "yum", "task_args" : "", "task_path" : "/usr/share/ovirt-engine/ansible-runner-service-project/project/roles/ovirt-host-deploy-vdsm/tasks/packages.yml:6", "role" : "ovirt-host-deploy-vdsm", "host" : "node15.starlett.lv", "remote_addr" : "node15.starlett.lv", "res" : { "failures" : [ "No package ovirt-hosted-engine-setup available." ], "results" : [ ], "rc" : 1, "msg" : "Failed to install some of the specified packages", "invocation" : { "module_args" : { "name" : [ "ovirt-hosted-engine-setup" ], "state" : "present", "allow_downgrade" : false, "autoremove" : false, "bugfix" : false, "cacheonly" : false, "disable_gpg_check" : false, "disable_plugin" : [ ], "disablerepo" : [ ], "download_only" : false, "enable_plugin" : [ ], "enablerepo" : [ ], "exclude" : [ ], "installroot" : "/", "install_repoquery" : true, "install_weak_deps" : true, "security" : false, "skip_broken" : false, "update_cache" : false, "update_only" : false, "validate_certs" : true, "lock_timeout" : 30, "allowerasing" : false, "nobest" : false, "conf_file" : null, "disable_excludes" : null, "download_dir" : null, "list" : null, "releasever" : null } }, "_ansible_no_log" : false, "changed" : false }, "start" : "2023-08-03T13:10:43.563744", "end" : "2023-08-03T13:10:45.632205", "duration" : 2.068461, "ignore_errors" : null, "event_loop" : null, "uuid" : "b1ffdae5-0679-40c3-8609-1a5b976edc0e" } }

1 0

Ovirt engine after OS update doesn't start with WFLYEE0042: Failed t,o construct component instance
by Jirka Simon 29 Jul '23

29 Jul '23

Hello oVirt community. I just updated some OS packages (engine was up to date) and after restart engine doesn't start with error 500 and following error message in server.log I checked issue with postgres-jdbc (it has similar symptoms) and I downgraded it but it should be fixed now, but downgrade didn't help. here is part of server.log and list of all updated packages. thank you for any help. Jirka 023-07-29 12:01:51,382+02 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 42) MSC000001: Failed to start service jboss.deployment.subunit."engine.ear"."bll.jar".component. Backend.START: org.jboss.msc.service.StartException in service jboss.deployment.subunit."engine.ear"."bll.jar".component.Backend.START: java.lang.IllegalStateException: WFLYEE0042: Failed t o construct component instance at org.jboss.as.ee@24.0.1.Final//org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:57) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at org.jboss.threads@2.4.0.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990) at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377) at java.base/java.lang.Thread.run(Thread.java:829) at org.jboss.threads@2.4.0.Final//org.jboss.threads.JBossThread.run(JBossThread.java:513) Caused by: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance at org.jboss.as.ee@24.0.1.Final//org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:170) at org.jboss.as.ee@24.0.1.Final//org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:141) at org.jboss.as.ee@24.0.1.Final//org.jboss.as.ee.component.BasicComponent.createInstance(BasicComponent.java:88) at org.jboss.as.ejb3@24.0.1.Final//org.jboss.as.ejb3.component.singleton.SingletonComponent.getComponentInstance(SingletonComponent.java:127) at org.jboss.as.ejb3@24.0.1.Final//org.jboss.as.ejb3.component.singleton.SingletonComponent.start(SingletonComponent.java:141) at org.jboss.as.ee@24.0.1.Final//org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:54) ... 8 more Caused by: javax.ejb.EJBException: java.lang.RuntimeException: colliding os id 302 at node /os/centos_9x64/id at org.jboss.as.ejb3@24.0.1.Final//org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInNoTx(CMTTxInterceptor.java:239) at org.jboss.as.ejb3@24.0.1.Final//org.jboss.as.ejb3.tx.CMTTxInterceptor.supports(CMTTxInterceptor.java:446) at org.jboss.as.ejb3@24.0.1.Final//org.jboss.as.ejb3.tx.LifecycleCMTTxInterceptor.processInvocation(LifecycleCMTTxInterceptor.java:70) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.weld@24.0.1.Final//org.jboss.as.weld.injection.WeldInjectionContextInterceptor.processInvocation(WeldInjectionContextInterceptor.java:43) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3@24.0.1.Final//org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ee@24.0.1.Final//org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(ConcurrentContextInterceptor.java:45) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:60) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3@24.0.1.Final//org.jboss.as.ejb3.component.singleton.StartupCountDownInterceptor.processInvocation(StartupCountDownInterceptor.java:25) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:53) at org.jboss.as.ee@24.0.1.Final//org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:168) ... 13 more Caused by: java.lang.RuntimeException: colliding os id 302 at node /os/centos_9x64/id at org.ovirt.engine.core.utils//org.ovirt.engine.core.utils.OsRepositoryImpl.buildIdToUnameLookup(OsRepositoryImpl.java:105) at org.ovirt.engine.core.utils//org.ovirt.engine.core.utils.OsRepositoryImpl.init(OsRepositoryImpl.java:66) at deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.Backend.initOsRepository(Backend.java:674) at deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.Backend.initialize(Backend.java:242) at deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.Backend.create(Backend.java:178) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at org.jboss.as.ee@24.0.1.Final//org.jboss.as.ee.component.ManagedReferenceLifecycleMethodInterceptor.processInvocation(ManagedReferenceLifecycleMethodInterceptor.java:96) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:509) at org.jboss.as.weld.common@24.0.1.Final//org.jboss.as.weld.interceptors.Jsr299BindingsInterceptor.delegateInterception(Jsr299BindingsInterceptor.java:79) at org.jboss.as.weld.common@24.0.1.Final//org.jboss.as.weld.interceptors.Jsr299BindingsInterceptor.doLifecycleInterception(Jsr299BindingsInterceptor.java:126) at org.jboss.as.weld.common@24.0.1.Final//org.jboss.as.weld.interceptors.Jsr299BindingsInterceptor.processInvocation(Jsr299BindingsInterceptor.java:112) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:509) at org.jboss.weld.core@3.1.7.SP1//org.jboss.weld.module.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:81) at org.jboss.as.weld.common@24.0.1.Final//org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:89) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.weld@24.0.1.Final//org.jboss.as.weld.injection.WeldInjectionInterceptor.processInvocation(WeldInjectionInterceptor.java:53) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ee@24.0.1.Final//org.jboss.as.ee.component.AroundConstructInterceptorFactory$1.processInvocation(AroundConstructInterceptorFactory.java:28) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.weld@24.0.1.Final//org.jboss.as.weld.injection.WeldInterceptorInjectionInterceptor.processInvocation(WeldInterceptorInjectionInterceptor.java:56) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ee@24.0.1.Final//org.jboss.as.ee.component.ComponentInstantiatorInterceptor.processInvocation(ComponentInstantiatorInterceptor.java:74) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.weld@24.0.1.Final//org.jboss.as.weld.interceptors.Jsr299BindingsCreateInterceptor.processInvocation(Jsr299BindingsCreateInterceptor.java:111) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ee@24.0.1.Final//org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3@24.0.1.Final//org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInNoTx(CMTTxInterceptor.java:232) ... 28 more 2023-07-29 12:01:51,393+02 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: java.lang.RuntimeException: colliding os id 302 at node /os/centos_9x64/id Caused by: java.lang.RuntimeException: colliding os id 302 at node /os/centos_9x64/id"}} 2023-07-29 12:01:51,416+02 INFO [org.jboss.as.server] (ServerService Thread Pool -- 27) WFLYSRV0010: Deployed "ovirt-web-ui.war" (runtime-name : "ovirt-web-ui.war") 2023-07-29 12:01:51,417+02 INFO [org.jboss.as.server] (ServerService Thread Pool -- 27) WFLYSRV0010: Deployed "apidoc.war" (runtime-name : "apidoc.war") 2023-07-29 12:01:51,417+02 INFO [org.jboss.as.server] (ServerService Thread Pool -- 27) WFLYSRV0010: Deployed "restapi.war" (runtime-name : "restapi.war") 2023-07-29 12:01:51,417+02 INFO [org.jboss.as.server] (ServerService Thread Pool -- 27) WFLYSRV0010: Deployed "engine.ear" (runtime-name : "engine.ear") 2023-07-29 12:01:51,420+02 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 c onstruct component instance WFLYCTL0448: 2 additional services are down due to their dependencies being missing or failed 2023-07-29 12:01:51,462+02 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server 2023-07-29 12:01:51,466+02 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 24.0.1.Final (WildFly Core 16.0.1.Final) started (with errors) in 14577ms - Started 1670 o f 1890 services (6 services failed or missing dependencies, 393 services are lazy, passive or on-demand) 2023-07-29 12:01:51,468+02 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:8706/management 2023-07-29 12:01:51,469+02 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:8706 list of all updated packages: dnf history info 21 Transaction ID : 21 Begin time : Sat 29 Jul 2023 10:59:14 AM CEST Begin rpmdb : 1077:5e724adb5bc93f2e2930cf25e895ccb36798d23c End time : Sat 29 Jul 2023 11:07:20 AM CEST (8 minutes) End rpmdb : 1087:60820a34eb4d036ba2c19d49841036fae4209af5 User : root <root> Return-Code : Success Releasever : 8 Command Line : update Comment : Packages Altered: Install apr-util-bdb-1.6.1-9.el8.x86_64 @appstream Install apr-util-openssl-1.6.1-9.el8.x86_64 @appstream Install kernel-4.18.0-500.el8.x86_64 @baseos Install kernel-core-4.18.0-500.el8.x86_64 @baseos Install kernel-modules-4.18.0-500.el8.x86_64 @baseos Install ongres-stringprep-1.1-2.el8.noarch @centos-ovirt45 Install python3.11-jmespath-0.9.0-11.5.el8.noarch @centos-ovirt45 Install python3.11-ovirt-engine-sdk4-4.6.2-1.el8.x86_64 @centos-ovirt45 Install python3.11-ovirt-imageio-client-2.5.0-1.el8.x86_64 @centos-ovirt45 Install python3.11-ovirt-imageio-common-2.5.0-1.el8.x86_64 @centos-ovirt45 Install python3.11-passlib-1.7.4-3.3.el8.noarch @centos-ovirt45 Install python3.11-pycurl-7.45.2-2.2.el8.x86_64 @centos-ovirt45 Install velocity-1.7-36.2.el8s.noarch @centos-ovirt45 Upgrade ceph-common-2:16.2.13-1.el8s.x86_64 @centos-ceph-pacific Upgraded ceph-common-2:16.2.11-1.el8s.x86_64 @@System Upgrade libcephfs2-2:16.2.13-1.el8s.x86_64 @centos-ceph-pacific Upgraded libcephfs2-2:16.2.11-1.el8s.x86_64 @@System Upgrade librados2-2:16.2.13-1.el8s.x86_64 @centos-ceph-pacific Upgraded librados2-2:16.2.11-1.el8s.x86_64 @@System Upgrade libradosstriper1-2:16.2.13-1.el8s.x86_64 @centos-ceph-pacific Upgraded libradosstriper1-2:16.2.11-1.el8s.x86_64 @@System Upgrade librbd1-2:16.2.13-1.el8s.x86_64 @centos-ceph-pacific Upgraded librbd1-2:16.2.11-1.el8s.x86_64 @@System Upgrade librgw2-2:16.2.13-1.el8s.x86_64 @centos-ceph-pacific Upgraded librgw2-2:16.2.11-1.el8s.x86_64 @@System Upgrade python3-ceph-argparse-2:16.2.13-1.el8s.x86_64 @centos-ceph-pacific Upgraded python3-ceph-argparse-2:16.2.11-1.el8s.x86_64 @@System Upgrade python3-ceph-common-2:16.2.13-1.el8s.x86_64 @centos-ceph-pacific Upgraded python3-ceph-common-2:16.2.11-1.el8s.x86_64 @@System Upgrade python3-cephfs-2:16.2.13-1.el8s.x86_64 @centos-ceph-pacific Upgraded python3-cephfs-2:16.2.11-1.el8s.x86_64 @@System Upgrade python3-rados-2:16.2.13-1.el8s.x86_64 @centos-ceph-pacific Upgraded python3-rados-2:16.2.11-1.el8s.x86_64 @@System Upgrade python3-rbd-2:16.2.13-1.el8s.x86_64 @centos-ceph-pacific Upgraded python3-rbd-2:16.2.11-1.el8s.x86_64 @@System Upgrade python3-rgw-2:16.2.13-1.el8s.x86_64 @centos-ceph-pacific Upgraded python3-rgw-2:16.2.11-1.el8s.x86_64 @@System Upgrade openvswitch2.15-2.15.0-136.el8s.x86_64 @centos-nfv-openvswitch Upgraded openvswitch2.15-2.15.0-135.el8s.x86_64 @@System Upgrade python3-openvswitch2.15-2.15.0-136.el8s.x86_64 @centos-nfv-openvswitch Upgraded python3-openvswitch2.15-2.15.0-135.el8s.x86_64 @@System Upgrade PackageKit-1.1.12-7.el8.x86_64 @appstream Upgraded PackageKit-1.1.12-6.el8.x86_64 @@System Upgrade PackageKit-glib-1.1.12-7.el8.x86_64 @appstream Upgraded PackageKit-glib-1.1.12-6.el8.x86_64 @@System Upgrade alsa-lib-1.2.9-1.el8.x86_64 @appstream Upgraded alsa-lib-1.2.8-2.el8.x86_64 @@System Upgrade ansible-core-2.15.0-1.el8.x86_64 @appstream Upgraded ansible-core-2.14.2-3.el8.x86_64 @@System Upgrade apr-util-1.6.1-9.el8.x86_64 @appstream Upgraded apr-util-1.6.1-6.el8.x86_64 @@System Upgrade cjose-0.6.1-3.module_el8+302+abe4241d.x86_64 @appstream Upgraded cjose-0.6.1-2.module_el8.4.0+674+2c6c7264.x86_64 @@System Upgrade cockpit-packagekit-295-1.el8.noarch @appstream Upgraded cockpit-packagekit-284-1.el8.noarch @@System Upgrade gdb-headless-8.2-20.el8.x86_64 @appstream Upgraded gdb-headless-8.2-19.el8.x86_64 @@System Upgrade git-2.39.3-1.el8.x86_64 @appstream Upgraded git-2.39.1-1.el8.x86_64 @@System Upgrade git-core-2.39.3-1.el8.x86_64 @appstream Upgraded git-core-2.39.1-1.el8.x86_64 @@System Upgrade git-core-doc-2.39.3-1.el8.noarch @appstream Upgraded git-core-doc-2.39.1-1.el8.noarch @@System Upgrade grafana-9.2.10-4.el8.x86_64 @appstream Upgraded grafana-7.5.15-4.el8.x86_64 @@System Upgrade grafana-pcp-5.1.1-1.el8.x86_64 @appstream Upgraded grafana-pcp-3.2.0-3.el8.x86_64 @@System Upgrade jq-1.6-7.el8.x86_64 @appstream Upgraded jq-1.6-6.el8.x86_64 @@System Upgrade libfastjson-0.99.9-2.el8.x86_64 @appstream Upgraded libfastjson-0.99.9-1.el8.x86_64 @@System Upgrade librsvg2-2.42.7-5.el8.x86_64 @appstream Upgraded librsvg2-2.42.7-4.el8.x86_64 @@System Upgrade libtiff-4.0.9-28.el8.x86_64 @appstream Upgraded libtiff-4.0.9-27.el8.x86_64 @@System Upgrade libwebp-1.0.0-9.el8.x86_64 @appstream Upgraded libwebp-1.0.0-5.el8.x86_64 @@System Upgrade mod_auth_openidc-2.4.9.4-5.module_el8+319+bd773fd7.x86_64 @appstream Upgraded mod_auth_openidc-2.4.9.4-1.module_el8.7.0+1136+d8f380b8.x86_64 @@System Upgrade nspr-4.35.0-1.el8.x86_64 @appstream Upgraded nspr-4.34.0-3.el8.x86_64 @@System Upgrade perl-Git-2.39.3-1.el8.noarch @appstream Upgraded perl-Git-2.39.1-1.el8.noarch @@System Upgrade platform-python-devel-3.6.8-52.el8.x86_64 @appstream Upgraded platform-python-devel-3.6.8-51.el8.x86_64 @@System Upgrade protobuf-c-1.3.0-8.el8.x86_64 @appstream Upgraded protobuf-c-1.3.0-6.el8.x86_64 @@System Upgrade python3-tkinter-3.6.8-52.el8.x86_64 @appstream Upgraded python3-tkinter-3.6.8-51.el8.x86_64 @@System Upgrade python3.11-3.11.4-1.el8.x86_64 @appstream Upgraded python3.11-3.11.2-2.el8.x86_64 @@System Upgrade python3.11-libs-3.11.4-1.el8.x86_64 @appstream Upgraded python3.11-libs-3.11.2-2.el8.x86_64 @@System Upgrade python3.11-tkinter-3.11.4-1.el8.x86_64 @appstream Upgraded python3.11-tkinter-3.11.2-2.el8.x86_64 @@System Upgrade python38-3.8.16-1.module_el8.8.0+1242+93d6d191.x86_64 @appstream Upgraded python38-3.8.13-1.module_el8.7.0+1177+19c53253.x86_64 @@System Upgrade python38-libs-3.8.16-1.module_el8.8.0+1242+93d6d191.x86_64 @appstream Upgraded python38-libs-3.8.13-1.module_el8.7.0+1177+19c53253.x86_64 @@System Upgrade python38-tkinter-3.8.16-1.module_el8.8.0+1242+93d6d191.x86_64 @appstream Upgraded python38-tkinter-3.8.13-1.module_el8.7.0+1177+19c53253.x86_64 @@System Upgrade qemu-guest-agent-15:6.2.0-35.module_el8+466+00f6f2b0.x86_64 @appstream Upgraded qemu-guest-agent-15:6.2.0-28.module_el8.8.0+1257+0c3374ae.x86_64 @@System Upgrade qemu-img-15:6.2.0-35.module_el8+466+00f6f2b0.x86_64 @appstream Upgraded qemu-img-15:6.2.0-28.module_el8.8.0+1257+0c3374ae.x86_64 @@System Upgrade rhel-system-roles-1.22.0-0.13.el8.noarch @appstream Upgraded rhel-system-roles-1.21.0-2.el8.noarch @@System Upgrade rsyslog-8.2102.0-15.el8.x86_64 @appstream Upgraded rsyslog-8.2102.0-13.el8.x86_64 @@System Upgrade rsyslog-elasticsearch-8.2102.0-15.el8.x86_64 @appstream Upgraded rsyslog-elasticsearch-8.2102.0-13.el8.x86_64 @@System Upgrade rsyslog-gnutls-8.2102.0-15.el8.x86_64 @appstream Upgraded rsyslog-gnutls-8.2102.0-13.el8.x86_64 @@System Upgrade rsyslog-mmjsonparse-8.2102.0-15.el8.x86_64 @appstream Upgraded rsyslog-mmjsonparse-8.2102.0-13.el8.x86_64 @@System Upgrade rsyslog-mmnormalize-8.2102.0-15.el8.x86_64 @appstream Upgraded rsyslog-mmnormalize-8.2102.0-13.el8.x86_64 @@System Upgrade texlive-base-7:20180414-29.el8.noarch @appstream Upgraded texlive-base-7:20180414-28.el8.noarch @@System Upgrade texlive-dvipng-7:20180414-29.el8.x86_64 @appstream Upgraded texlive-dvipng-7:20180414-28.el8.x86_64 @@System Upgrade texlive-kpathsea-7:20180414-29.el8.x86_64 @appstream Upgraded texlive-kpathsea-7:20180414-28.el8.x86_64 @@System Upgrade texlive-lib-7:20180414-29.el8.x86_64 @appstream Upgraded texlive-lib-7:20180414-28.el8.x86_64 @@System Upgrade texlive-tetex-7:20180414-29.el8.noarch @appstream Upgraded texlive-tetex-7:20180414-28.el8.noarch @@System Upgrade texlive-texlive.infra-7:20180414-29.el8.noarch @appstream Upgraded texlive-texlive.infra-7:20180414-28.el8.noarch @@System Upgrade tzdata-java-2023c-1.el8.noarch @appstream Upgraded tzdata-java-2022g-2.el8.noarch @@System Upgrade NetworkManager-1:1.40.16-8.el8.x86_64 @baseos Upgraded NetworkManager-1:1.40.16-2.el8.x86_64 @@System Upgrade NetworkManager-libnm-1:1.40.16-8.el8.x86_64 @baseos Upgraded NetworkManager-libnm-1:1.40.16-2.el8.x86_64 @@System Upgrade NetworkManager-team-1:1.40.16-8.el8.x86_64 @baseos Upgraded NetworkManager-team-1:1.40.16-2.el8.x86_64 @@System Upgrade NetworkManager-tui-1:1.40.16-8.el8.x86_64 @baseos Upgraded NetworkManager-tui-1:1.40.16-2.el8.x86_64 @@System Upgrade audit-3.0.7-5.el8.x86_64 @baseos Upgraded audit-3.0.7-4.el8.x86_64 @@System Upgrade audit-libs-3.0.7-5.el8.x86_64 @baseos Upgraded audit-libs-3.0.7-4.el8.x86_64 @@System Upgrade binutils-2.30-121.el8.x86_64 @baseos Upgraded binutils-2.30-119.el8.x86_64 @@System Upgrade c-ares-1.13.0-8.el8.x86_64 @baseos Upgraded c-ares-1.13.0-6.el8.x86_64 @@System Upgrade chkconfig-1.19.2-1.el8.x86_64 @baseos Upgraded chkconfig-1.19.1-1.el8.x86_64 @@System Upgrade cockpit-295-1.el8.x86_64 @baseos Upgraded cockpit-288.2-1.el8.x86_64 @@System Upgrade cockpit-bridge-295-1.el8.x86_64 @baseos Upgraded cockpit-bridge-288.2-1.el8.x86_64 @@System Upgrade cockpit-system-295-1.el8.noarch @baseos Upgraded cockpit-system-288.2-1.el8.noarch @@System Upgrade cockpit-ws-295-1.el8.x86_64 @baseos Upgraded cockpit-ws-288.2-1.el8.x86_64 @@System Upgrade curl-7.61.1-31.el8.x86_64 @baseos Upgraded curl-7.61.1-30.el8.x86_64 @@System Upgrade dbus-1:1.12.8-25.el8.x86_64 @baseos Upgraded dbus-1:1.12.8-24.el8.x86_64 @@System Upgrade dbus-common-1:1.12.8-25.el8.noarch @baseos Upgraded dbus-common-1:1.12.8-24.el8.noarch @@System Upgrade dbus-daemon-1:1.12.8-25.el8.x86_64 @baseos Upgraded dbus-daemon-1:1.12.8-24.el8.x86_64 @@System Upgrade dbus-libs-1:1.12.8-25.el8.x86_64 @baseos Upgraded dbus-libs-1:1.12.8-24.el8.x86_64 @@System Upgrade dbus-tools-1:1.12.8-25.el8.x86_64 @baseos Upgraded dbus-tools-1:1.12.8-24.el8.x86_64 @@System Upgrade dnf-4.7.0-18.el8.noarch @baseos Upgraded dnf-4.7.0-15.el8.noarch @@System Upgrade dnf-data-4.7.0-18.el8.noarch @baseos Upgraded dnf-data-4.7.0-15.el8.noarch @@System Upgrade dnf-plugins-core-4.0.21-23.el8.noarch @baseos Upgraded dnf-plugins-core-4.0.21-18.el8.noarch @@System Upgrade dracut-049-225.git20230614.el8.x86_64 @baseos Upgraded dracut-049-223.git20230119.el8.x86_64 @@System Upgrade dracut-config-generic-049-225.git20230614.el8.x86_64 @baseos Upgraded dracut-config-generic-049-223.git20230119.el8.x86_64 @@System Upgrade dracut-config-rescue-049-225.git20230614.el8.x86_64 @baseos Upgraded dracut-config-rescue-049-223.git20230119.el8.x86_64 @@System Upgrade dracut-network-049-225.git20230614.el8.x86_64 @baseos Upgraded dracut-network-049-223.git20230119.el8.x86_64 @@System Upgrade dracut-squash-049-225.git20230614.el8.x86_64 @baseos Upgraded dracut-squash-049-223.git20230119.el8.x86_64 @@System Upgrade elfutils-0.189-2.el8.x86_64 @baseos Upgraded elfutils-0.188-3.el8.x86_64 @@System Upgrade elfutils-debuginfod-client-0.189-2.el8.x86_64 @baseos Upgraded elfutils-debuginfod-client-0.188-3.el8.x86_64 @@System Upgrade elfutils-default-yama-scope-0.189-2.el8.noarch @baseos Upgraded elfutils-default-yama-scope-0.188-3.el8.noarch @@System Upgrade elfutils-libelf-0.189-2.el8.x86_64 @baseos Upgraded elfutils-libelf-0.188-3.el8.x86_64 @@System Upgrade elfutils-libs-0.189-2.el8.x86_64 @baseos Upgraded elfutils-libs-0.188-3.el8.x86_64 @@System Upgrade emacs-filesystem-1:26.1-11.el8.noarch @baseos Upgraded emacs-filesystem-1:26.1-9.el8.noarch @@System Upgrade file-5.33-25.el8.x86_64 @baseos Upgraded file-5.33-24.el8.x86_64 @@System Upgrade file-libs-5.33-25.el8.x86_64 @baseos Upgraded file-libs-5.33-24.el8.x86_64 @@System Upgrade fuse-libs-2.9.7-17.el8.x86_64 @baseos Upgraded fuse-libs-2.9.7-16.el8.x86_64 @@System Upgrade fuse3-libs-3.3.0-17.el8.x86_64 @baseos Upgraded fuse3-libs-3.3.0-16.el8.x86_64 @@System Upgrade glibc-2.28-228.el8.x86_64 @baseos Upgraded glibc-2.28-225.el8.x86_64 @@System Upgrade glibc-common-2.28-228.el8.x86_64 @baseos Upgraded glibc-common-2.28-225.el8.x86_64 @@System Upgrade glibc-gconv-extra-2.28-228.el8.x86_64 @baseos Upgraded glibc-gconv-extra-2.28-225.el8.x86_64 @@System Upgrade glibc-langpack-en-2.28-228.el8.x86_64 @baseos Upgraded glibc-langpack-en-2.28-225.el8.x86_64 @@System Upgrade gnutls-3.6.16-7.el8.x86_64 @baseos Upgraded gnutls-3.6.16-6.el8.x86_64 @@System Upgrade grubby-8.40-48.el8.x86_64 @baseos Upgraded grubby-8.40-47.el8.x86_64 @@System Upgrade hwdata-0.314-8.18.el8.noarch @baseos Upgraded hwdata-0.314-8.16.el8.noarch @@System Upgrade iproute-6.2.0-2.el8.x86_64 @baseos Upgraded iproute-5.18.0-1.el8.x86_64 @@System Upgrade iscsi-initiator-utils-6.2.1.4-8.git095f59c.el8.x86_64 @baseos Upgraded iscsi-initiator-utils-6.2.1.4-4.git095f59c.el8.x86_64 @@System Upgrade iscsi-initiator-utils-iscsiuio-6.2.1.4-8.git095f59c.el8.x86_64 @baseos Upgraded iscsi-initiator-utils-iscsiuio-6.2.1.4-4.git095f59c.el8.x86_64 @@System Upgrade kbd-2.0.4-11.el8.x86_64 @baseos Upgraded kbd-2.0.4-10.el8.x86_64 @@System Upgrade kbd-legacy-2.0.4-11.el8.noarch @baseos Upgraded kbd-legacy-2.0.4-10.el8.noarch @@System Upgrade kbd-misc-2.0.4-11.el8.noarch @baseos Upgraded kbd-misc-2.0.4-10.el8.noarch @@System Upgrade kernel-tools-4.18.0-500.el8.x86_64 @baseos Upgraded kernel-tools-4.18.0-481.el8.x86_64 @@System Upgrade kernel-tools-libs-4.18.0-500.el8.x86_64 @baseos Upgraded kernel-tools-libs-4.18.0-481.el8.x86_64 @@System Upgrade libblkid-2.32.1-42.el8.x86_64 @baseos Upgraded libblkid-2.32.1-41.el8.x86_64 @@System Upgrade libcurl-7.61.1-31.el8.x86_64 @baseos Upgraded libcurl-7.61.1-30.el8.x86_64 @@System Upgrade libdnf-0.63.0-16.el8.x86_64 @baseos Upgraded libdnf-0.63.0-13.el8.x86_64 @@System Upgrade libfdisk-2.32.1-42.el8.x86_64 @baseos Upgraded libfdisk-2.32.1-41.el8.x86_64 @@System Upgrade libgcc-8.5.0-20.el8.x86_64 @baseos Upgraded libgcc-8.5.0-18.el8.x86_64 @@System Upgrade libgfortran-8.5.0-20.el8.x86_64 @baseos Upgraded libgfortran-8.5.0-18.el8.x86_64 @@System Upgrade libgomp-8.5.0-20.el8.x86_64 @baseos Upgraded libgomp-8.5.0-18.el8.x86_64 @@System Upgrade libibverbs-46.0-1.el8.1.x86_64 @baseos Upgraded libibverbs-44.0-2.el8.1.x86_64 @@System Upgrade libldb-2.7.2-3.el8.x86_64 @baseos Upgraded libldb-2.6.1-1.el8.x86_64 @@System Upgrade libmount-2.32.1-42.el8.x86_64 @baseos Upgraded libmount-2.32.1-41.el8.x86_64 @@System Upgrade libnftnl-1.2.2-3.el8.x86_64 @baseos Upgraded libnftnl-1.1.5-5.el8.x86_64 @@System Upgrade libquadmath-8.5.0-20.el8.x86_64 @baseos Upgraded libquadmath-8.5.0-18.el8.x86_64 @@System Upgrade librabbitmq-0.9.0-4.el8.x86_64 @baseos Upgraded librabbitmq-0.9.0-3.el8.x86_64 @@System Upgrade librdmacm-46.0-1.el8.1.x86_64 @baseos Upgraded librdmacm-44.0-2.el8.1.x86_64 @@System Upgrade libsmartcols-2.32.1-42.el8.x86_64 @baseos Upgraded libsmartcols-2.32.1-41.el8.x86_64 @@System Upgrade libsolv-0.7.20-6.el8.x86_64 @baseos Upgraded libsolv-0.7.20-4.el8.x86_64 @@System Upgrade libsoup-2.62.3-4.el8.x86_64 @baseos Upgraded libsoup-2.62.3-3.el8.x86_64 @@System Upgrade libsss_autofs-2.9.1-1.el8.x86_64 @baseos Upgraded libsss_autofs-2.8.2-1.el8.x86_64 @@System Upgrade libsss_certmap-2.9.1-1.el8.x86_64 @baseos Upgraded libsss_certmap-2.8.2-1.el8.x86_64 @@System Upgrade libsss_idmap-2.9.1-1.el8.x86_64 @baseos Upgraded libsss_idmap-2.8.2-1.el8.x86_64 @@System Upgrade libsss_nss_idmap-2.9.1-1.el8.x86_64 @baseos Upgraded libsss_nss_idmap-2.8.2-1.el8.x86_64 @@System Upgrade libsss_sudo-2.9.1-1.el8.x86_64 @baseos Upgraded libsss_sudo-2.8.2-1.el8.x86_64 @@System Upgrade libstdc++-8.5.0-20.el8.x86_64 @baseos Upgraded libstdc++-8.5.0-18.el8.x86_64 @@System Upgrade libtalloc-2.4.0-3.el8.x86_64 @baseos Upgraded libtalloc-2.3.4-1.el8.x86_64 @@System Upgrade libtdb-1.4.8-3.el8.x86_64 @baseos Upgraded libtdb-1.4.7-1.el8.x86_64 @@System Upgrade libtevent-0.14.1-3.el8.x86_64 @baseos Upgraded libtevent-0.13.0-1.el8.x86_64 @@System Upgrade libuuid-2.32.1-42.el8.x86_64 @baseos Upgraded libuuid-2.32.1-41.el8.x86_64 @@System Upgrade linux-firmware-20230515-115.gitd1962891.el8.noarch @baseos Upgraded linux-firmware-20230217-113.git83f1d778.el8.noarch @@System Upgrade memstrack-0.2.5-2.el8.x86_64 @baseos Upgraded memstrack-0.2.4-2.el8.x86_64 @@System Upgrade microcode_ctl-4:20230214-2.el8.x86_64 @baseos Upgraded microcode_ctl-4:20220809-2.el8.x86_64 @@System Upgrade nvme-cli-1.16-9.el8.x86_64 @baseos Upgraded nvme-cli-1.16-7.el8.x86_64 @@System Upgrade nvmetcli-0.7-5.el8.noarch @baseos Upgraded nvmetcli-0.7-3.el8.noarch @@System Upgrade pam-1.3.1-27.el8.x86_64 @baseos Upgraded pam-1.3.1-25.el8.x86_64 @@System Upgrade platform-python-3.6.8-52.el8.x86_64 @baseos Upgraded platform-python-3.6.8-51.el8.x86_64 @@System Upgrade python-rpm-macros-3-45.el8.noarch @baseos Upgraded python-rpm-macros-3-44.el8.noarch @@System Upgrade python-srpm-macros-3-45.el8.noarch @baseos Upgraded python-srpm-macros-3-44.el8.noarch @@System Upgrade python3-audit-3.0.7-5.el8.x86_64 @baseos Upgraded python3-audit-3.0.7-4.el8.x86_64 @@System Upgrade python3-cryptography-3.2.1-6.el8.x86_64 @baseos Upgraded python3-cryptography-3.2.1-5.el8.x86_64 @@System Upgrade python3-dnf-4.7.0-18.el8.noarch @baseos Upgraded python3-dnf-4.7.0-15.el8.noarch @@System Upgrade python3-dnf-plugin-versionlock-4.0.21-23.el8.noarch @baseos Upgraded python3-dnf-plugin-versionlock-4.0.21-18.el8.noarch @@System Upgrade python3-dnf-plugins-core-4.0.21-23.el8.noarch @baseos Upgraded python3-dnf-plugins-core-4.0.21-18.el8.noarch @@System Upgrade python3-hawkey-0.63.0-16.el8.x86_64 @baseos Upgraded python3-hawkey-0.63.0-13.el8.x86_64 @@System Upgrade python3-libdnf-0.63.0-16.el8.x86_64 @baseos Upgraded python3-libdnf-0.63.0-13.el8.x86_64 @@System Upgrade python3-libs-3.6.8-52.el8.x86_64 @baseos Upgraded python3-libs-3.6.8-51.el8.x86_64 @@System Upgrade python3-magic-5.33-25.el8.noarch @baseos Upgraded python3-magic-5.33-24.el8.noarch @@System Upgrade python3-perf-4.18.0-500.el8.x86_64 @baseos Upgraded python3-perf-4.18.0-481.el8.x86_64 @@System Upgrade python3-rpm-macros-3-45.el8.noarch @baseos Upgraded python3-rpm-macros-3-44.el8.noarch @@System Upgrade python3-syspurpose-1.28.38-1.el8.x86_64 @baseos Upgraded python3-syspurpose-1.28.35-1.el8.x86_64 @@System Upgrade selinux-policy-3.14.3-123.el8.noarch @baseos Upgraded selinux-policy-3.14.3-117.el8.noarch @@System Upgrade selinux-policy-targeted-3.14.3-123.el8.noarch @baseos Upgraded selinux-policy-targeted-3.14.3-117.el8.noarch @@System Upgrade shadow-utils-2:4.6-18.el8.x86_64 @baseos Upgraded shadow-utils-2:4.6-17.el8.x86_64 @@System Upgrade sos-4.5.4-1.el8.noarch @baseos Upgraded sos-4.5.0-1.el8.noarch @@System Upgrade sqlite-3.26.0-18.el8.x86_64 @baseos Upgraded sqlite-3.26.0-17.el8.x86_64 @@System Upgrade sqlite-libs-3.26.0-18.el8.x86_64 @baseos Upgraded sqlite-libs-3.26.0-17.el8.x86_64 @@System Upgrade sssd-client-2.9.1-1.el8.x86_64 @baseos Upgraded sssd-client-2.8.2-1.el8.x86_64 @@System Upgrade sssd-common-2.9.1-1.el8.x86_64 @baseos Upgraded sssd-common-2.8.2-1.el8.x86_64 @@System Upgrade sssd-kcm-2.9.1-1.el8.x86_64 @baseos Upgraded sssd-kcm-2.8.2-1.el8.x86_64 @@System Upgrade sssd-nfs-idmap-2.9.1-1.el8.x86_64 @baseos Upgraded sssd-nfs-idmap-2.8.2-1.el8.x86_64 @@System Upgrade systemd-239-76.el8.x86_64 @baseos Upgraded systemd-239-73.el8.x86_64 @@System Upgrade systemd-libs-239-76.el8.x86_64 @baseos Upgraded systemd-libs-239-73.el8.x86_64 @@System Upgrade systemd-pam-239-76.el8.x86_64 @baseos Upgraded systemd-pam-239-73.el8.x86_64 @@System Upgrade systemd-udev-239-76.el8.x86_64 @baseos Upgraded systemd-udev-239-73.el8.x86_64 @@System Upgrade tmux-2.7-3.el8.x86_64 @baseos Upgraded tmux-2.7-1.el8.x86_64 @@System Upgrade tzdata-2023c-1.el8.noarch @baseos Upgraded tzdata-2022g-2.el8.noarch @@System Upgrade util-linux-2.32.1-42.el8.x86_64 @baseos Upgraded util-linux-2.32.1-41.el8.x86_64 @@System Upgrade which-2.21-20.el8.x86_64 @baseos Upgraded which-2.21-18.el8.x86_64 @@System Upgrade xfsprogs-5.0.0-12.el8.x86_64 @baseos Upgraded xfsprogs-5.0.0-10.el8.x86_64 @@System Upgrade yum-4.7.0-18.el8.noarch @baseos Upgraded yum-4.7.0-15.el8.noarch @@System Upgrade yum-utils-4.0.21-23.el8.noarch @baseos Upgraded yum-utils-4.0.21-18.el8.noarch @@System Upgrade zlib-1.2.11-25.el8.x86_64 @baseos Upgraded zlib-1.2.11-21.el8.x86_64 @@System Upgrade centos-release-ovirt45-8.9-1.el8s.noarch @extras-common Upgraded centos-release-ovirt45-8.7-3.el8s.noarch @@System Upgrade ongres-scram-2.1-3.el8.noarch @centos-ovirt45 Upgraded ongres-scram-1.0.0~beta.2-5.el8.noarch @@System Upgrade ongres-scram-client-2.1-3.el8.noarch @centos-ovirt45 Upgraded ongres-scram-client-1.0.0~beta.2-5.el8.noarch @@System Upgrade ovirt-ansible-collection-3.1.2-1.el8.noarch @centos-ovirt45 Upgraded ovirt-ansible-collection-3.0.0-1.el8.noarch @@System Upgrade ovirt-dependencies-4.5.3-1.el8.noarch @centos-ovirt45 Upgraded ovirt-dependencies-4.5.2-1.el8.noarch @@System Upgrade ovirt-imageio-client-2.5.0-1.el8.x86_64 @centos-ovirt45 Upgraded ovirt-imageio-client-2.4.7-1.el8.x86_64 @@System Upgrade ovirt-imageio-common-2.5.0-1.el8.x86_64 @centos-ovirt45 Upgraded ovirt-imageio-common-2.4.7-1.el8.x86_64 @@System Upgrade ovirt-imageio-daemon-2.5.0-1.el8.x86_64 @centos-ovirt45 Upgraded ovirt-imageio-daemon-2.4.7-1.el8.x86_64 @@System Upgrade postgresql-jdbc-42.2.27-1.el8.noarch @centos-ovirt45 Upgraded postgresql-jdbc-42.2.14-2.el8.noarch @@System Upgrade python3-jmespath-0.9.0-11.5.el8.noarch @centos-ovirt45 Upgraded python3-jmespath-0.9.0-11.2.el8.noarch @@System Upgrade python3-netaddr-0.8.0-12.3.el8.noarch @centos-ovirt45 Upgraded python3-netaddr-0.7.19-8.1.2.el8.noarch @@System Upgrade python3-ovirt-engine-sdk4-4.6.2-1.el8.x86_64 @centos-ovirt45 Upgraded python3-ovirt-engine-sdk4-4.6.0-1.el8.x86_64 @@System Upgrade python3-passlib-1.7.4-3.3.el8.noarch @centos-ovirt45 Upgraded python3-passlib-1.7.4-1.el8.noarch @@System Upgrade python3-pycurl-7.45.2-2.2.el8.x86_64 @centos-ovirt45 Upgraded python3-pycurl-7.43.0.2-4.2.el8.x86_64 @@System Upgrade python3-cinder-common-1:20.3.0-1.el8.noarch @ovirt-45-centos-stream-openstack-yoga Upgraded python3-cinder-common-1:20.1.0-1.el8.noarch @@System Upgrade python3-os-brick-5.2.3-1.el8.noarch @ovirt-45-centos-stream-openstack-yoga Upgraded python3-os-brick-5.2.2-1.el8.noarch @@System Upgrade python3-oslo-messaging-12.13.1-1.el8.noarch @ovirt-45-centos-stream-openstack-yoga Upgraded python3-oslo-messaging-12.13.0-1.el8.noarch @@System Reason ChangeGConf2-3.2.6-22.el8.x86_64 @appstream Removed kernel-4.18.0-383.el8.x86_64 @@System Removed kernel-core-4.18.0-383.el8.x86_64 @@System Removed kernel-modules-4.18.0-383.el8.x86_64 @@System

1 1

CPU Compatibility with 4.5.4-1.el8 (4.7)
by mark.williams＠nist.gov 27 Jul '23

27 Jul '23

Having issue adding oVirt host using AlmaLinux 8/9 with systems using the sandybridge CPU Intel(R) Xeon(R) CPU E5-2690 0 @ 2.90GHz. Error give CPU not compatible with Ovirt "compatibility type 4.7". Works with creating another Cluster at "compatibility type 4.3", but not 4.7. These host were re-purposed from RHV 4.3 Cluster. Any thoughts?

1 0

Connection to ovirt-imageio has failed
by masth.ganesh＠gmail.com 26 Jul '23

26 Jul '23

I am trying to upload an ISO onto the OLVM and I get the "connection to ovirt-imageio has failed" message when I test the connection. I have uploaded the certificates onto the web browser but for some reason I am unable to test the connection successfully. I have tried it on other browsers like Edge and Firefox as well.

1 0

Problema VM with Disk blocked creating snapshot wrong
by José Pascual 25 Jul '23

25 Jul '23

Hi, I have a Virtual Machine Bloqued by the disk and i cant delete for restoreing de VM and i cant do anything. This is a error with the snapshot and never ends (the virtual machine now is shutdown). What can i do for deleteting de virtual machine from my engine and the disk? -- Saludos, José Pascual Gallud Martínez Nombre | Dpto. Ingeniería <http://telfy.com/>

1 0

Ovirt_Provider_Citrix-Xen
by rj.indramaya＠gmail.com 23 Jul '23

23 Jul '23

Hi All, First of all apology If i'm doing it wrong way. I could not find any solution so I hoped I'll get some answers here. In my Organization I started exploring the Ovirt-Engine, While I have created multiple VMs and all working fine I started facing one issue as in my organization we had Citrix Xen server which is out of date so I started working on migrating them directly to Ovirt-enigne. so I tried to add my Xen-server as a provider but its failing to load or connect with the Citrix-Xen. Let me know how should I move forward, Thanks in advance, people are amazing.

3 2

Obtain SSO token using username/password credentials] fails Error during SSO authentication access_denied : Cannot authenticate user Invalid user credentials.
by antonio.riggio＠mail.com 22 Jul '23

22 Jul '23

can anyone tell how I can fix this I have not been able to install ovirt. Im using the same password when I login to ovirt too. thanks INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Obtain SSO token using username/password credentials] [ ERROR ] ovirtsdk4.AuthError: Error during SSO authentication access_denied : Cannot authenticate user Invalid user credentials. [ ERROR ] fatal: [localhost]: FAILED! => {"attempts": 50, "changed": false, "msg": "Error during SSO authentication access_denied : Cannot authenticate user Invalid user credentials."} [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Sync on engine machine] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Fetch logs from the engine VM] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Set destination directory path] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Create destination directory] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : include_tasks] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Find the local appliance image] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Set local_vm_disk_path] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Give the vm time to flush dirty buffers] [ INFO ] ok: [localhost -> localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Copy engine logs] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Change ownership of copied engine logs] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : include_tasks] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Remove local vm dir] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Remove temporary entry in /etc/hosts for the local VM] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : include_tasks] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Destroy local storage-pool localvmxfo24vb0] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Undefine local storage-pool localvmxfo24vb0] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Destroy local storage-pool 9df88328-fb97-4230-a679-a9ab4cc59562] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Undefine local storage-pool 9df88328-fb97-4230-a679-a9ab4cc59562] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Notify the user about a failure] [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "The system may not be provisioned according to the playbook results: please check the logs for the issue, fix accordingly or re-deploy from scratch.\n"}

1 0

oVirt Host EL9 with UEFI Secure Boot
by Jorge Visentini 21 Jul '23

21 Jul '23

Hi there! Is this information still valid? To use Enterprise Linux 9 on virtualization hosts, the UEFI Secure Boot option must be disabled due to *Bug 2081648 - dmidecode module fails to decode DMI data <https://bugzilla.redhat.com/show_bug.cgi?id=2081648>*. I read that it was fixed in *python-dmidecode-3.12.3-1.el9* but we still use *python-3.11*. Is this bug only for hosted-engine or for standalone too? BR. -- Att, Jorge Visentini +55 55 98432-9868

2 4

Processors compatibility matrix oVirt
by Jorge Visentini 21 Jul '23

21 Jul '23

Do you have any documentation or compatibility matrix between oVirt and processors? How can I know if a processor is compatible? I ask because in the *lscpu* command I see 2 sockets, but in the *engine* I only see 1 socket. BR. -- Att, Jorge Visentini +55 55 98432-9868

5 9

ovirt with rocky linux kvm
by cynthiaberbery＠outlook.com 21 Jul '23

21 Jul '23

Hello, after installing multiple machines as rocky linux, Ovirt was chosen to be used to manage this infra. But adding these machines as "hosts" on ovirt always give: Error while executing action: Cannot add Host. Connecting to host via SSH has failed, verify that the host is reachable (IP address, routable address etc.) You may refer to the engine.log file for further details. Is rocky kvm supported on ovirt 4.3.10.4-1.el7? Do you have any contact with a supporting company/team for ovirt to check their support plan?

4 3

How to re-enroll a host with an active workload whose certificate expired
by David Johnson 20 Jul '23

20 Jul '23

Good evening all, I have a three host installation with a separate dedicated bare metal system for the engine, running Ovirt 4.5.2.4-1.el8. This afternoon, the engine lost communication with one of the hosts. The engine log says the certificate is expired. The official solution appears to be to put the host into maintenance mode then re-enroll it. Unfortunately, because the certificate is expired, the engine cannot switch to maintenance mode or control the VM's to shut them down. Error while executing action: Cannot switch Host to Maintenance mode. Host still has running VMs on it and is in Non Responsive state. See log excerpt below What is the correct way to update/reinstate a certificate in a running cluster when the engine does not acknowledge the host is operational due to an expired certificate? Thank you. *David Johnson* Log excerpt: 2023-07-20 16:27:46,904-05 INFO [org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp Reactor) [] Connecting to /192.168.2.18 2023-07-20 16:27:46,904-05 INFO [org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp Reactor) [] *Connected to /192.168.2.18:54321 <http://192.168.2.18:54321>* 2023-07-20 16:27:46,912-05 ERROR [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor) [] *Unable to process messages Received fatal alert: certificate_expired* 2023-07-20 16:27:46,914-05 ERROR [org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-52) [] Unable to RefreshCapabilities: VDSNetworkException: VDSGenericException: VDSNetworkException: Received fatal alert: certificate_expired 2023-07-20 16:27:47,356-05 ERROR [org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-34) [] Unable to RefreshCapabilities: ClientConnectionException: SSL session is invalid 2023-07-20 16:27:47,356-05 WARN [org.ovirt.engine.core.bll.lock.InMemoryLockManager] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-34) [] Trying to release exclusive lock which does not exist, lock key: 'f69d35b2-7666-4ac6-8645-2f119cf2ce1cVDS_INIT' 2023-07-20 16:27:47,356-05 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesAsyncVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-34) [] Command 'org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesAsyncVDSCommand' return value 'org.ovirt.engine.core.vdsbroker.vdsbroker.VDSInfoReturn@7d03f4f0' 2023-07-20 16:27:47,356-05 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesAsyncVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-34) [] HostName = ovirt-host-03 2023-07-20 16:27:47,356-05 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesAsyncVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-34) [] Command 'GetCapabilitiesAsyncVDSCommand(HostName = ovirt-host-03, VdsIdAndVdsVDSCommandParametersBase:{hostId='f69d35b2-7666-4ac6-8645-2f119cf2ce1c', vds='Host[ovirt-host-03,f69d35b2-7666-4ac6-8645-2f119cf2ce1c]'})' execution failed: org.ovirt.vdsm.jsonrpc.client.ClientConnectionException: *SSL session is invalid*

1 0

First time user/setup
by jmred88＠gmail.com 20 Jul '23

20 Jul '23

Could someone explain to me the proper documentation I should be using for a standalone setup? I have one host with local storage/resources and would like that to both host and manage my VMs but I keep getting into the weeds with which documentation to follow.

2 1

ovirt node 4.5 is not working on esxi8 on my lab
by poper＠windowslive.com 20 Jul '23

20 Jul '23

Hello there, May I ask why I have installed ovirt node 4.5 latest from iso on my esxi8 after I logged in to the web interface to manage this host I cannot find menu virtualization but when I tested on 4.4.6 everything is work. Do you have any idea? Thanks.

2 1

Commit or release history
by Jorge Visentini 20 Jul '23

20 Jul '23

Hi. I'm following the release of the 4.5.5 isos and I see that new isos are coming out almost every day. Is there any place where I can keep track of the changes that were made from one iso to another? Is it open for us to follow? Cheers! -- Att, Jorge Visentini +55 55 98432-9868

2 2

python sdk4 ovirt 4.5.5.0 master
by Jorge Visentini 19 Jul '23

19 Jul '23

Hi. I am testing oVirt 4.5.5-0.master.20230712143502.git07e865d650.el8. I missed the python scripts to download and upload discs and images... Will it still be possible to use them or should I consider using Ansible? BR. -- Att, Jorge Visentini +55 55 98432-9868

2 2

oVirt 4.4. Engine Deployment: Problems with Gluster Storage Domain
by Thyen, Niko 18 Jul '23

18 Jul '23

Hi everybody! I am having a hard time getting oVirt 4.4 to work. We want to update our 4.3 Cluster and i am trying to set up a fresh 4.4 Cluster (and restore the backup later on) in order to update to 4.5. It fails at the end of the engine deloyment, when the Gluster Storage Domain should be added. I installed oVirt Node 4.4.10 on an old PC and made the following modifications to the engine deployment process: - altered defaults in /usr/share/ansible/collections/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/defaults/main.yml: - "he_pause_before_engine_setup: true" (in this pause before engine setup, i ssh into the engine and exclude the package postgresql-jdbc from update, which otherwise breaks the deployment [1]) - "he_remove_appliance_rpm: false" (to avoid the large download every single try, i tried a lot) - "he_force_ip4: true" (to avoid problems with IPv6, see below) - in /usr/share/ansible/collections/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/fetch_host_ip.yml i added after "- name: Get host address resolution:" the following lines (to avoid a problem with an "invalid" IPv6-Adress, which otherwise breaks the deployment [2]): - name: Get host IP addresses ansible.builtin.command: hostname -I register: hostname_addresses_output changed_when: true Most times, i started deployment via shell but tried via webinterface of the node as well. It fails at the task "Add glusterfs storage domain" with the following message: "[ ERROR ] ovirtsdk4.Error: Fault reason is "Operation Failed". Fault detail is "[Failed to fetch Gluster Volume List]". HTTP response code is 400." (See also [3]) When the setup asks for storage, i tried different answers (gluster.local:/volume, gluster.local:/path/to/brick/volume, 192.168.8.51:/volume ...), no mount options. I added firewall rules for glusterfs at node and engine. Even tried disabling the firewall. No firewall on the gluster servers running. On the Node, i also tested setting SELinux to permissive. Recorded the traffic at different interfaces ("ovirtmgmt" and "virbr0" on the node and "eth0" on the engine) and i can see the node and the gluster server talking: Node gets the volume with options (which are, btw, compliant to the docs, "storage.owner-gid: 36" "storage.owner-uid: 36" etc) but thats it, no further packets to mount the volume. I noticed some ARP packets as well, the node asks the IP from the engine (the configured static IP, which is not yet active). And the engine sends a dns request for the gluster server to the node (via interface virbr0), but doesnt connect to the gluster server. At least, thats what i can see, most of the traffic is TLS, which i couldnt decrypt yet. I appreciate any hint where to find the right keys. Anyway, i can ssh from the engine to the gluster server and mount the gluster volume manually on the node (mount -t glusterfs gluster.local:/volume /local/path), so there seem no connectivity issues. Since the engine deployment log is around 30MB i attached a log summary with findings i found relevant. I'll provide more logs if needed. I really wanna put this huge timesink to an end. Can anyone help me or point me in the right direction? Many thanks in advance :) Regards, Niko [1] This was the error message i got: "[ ERROR ] fatal: [localhost -> 192.168.222.195]: FAILED! => {"attempts": 30, "changed": false, "connection": "close", "content": "Error500 - Internal Server Error", "content_encoding": "identity", "content_length": "86", "content_type": "text/html; charset=UTF-8", "date": "Wed, 17 May 2023 22:42:27 GMT", "elapsed": 0, "msg": "Status code was 500 and not [200]: HTTP Error 500: Internal Server Error", "redirected": false, "server": "Apache/2.4.37 (centos) OpenSSL/1.1.1k mod_auth_gssapi/1.6.1 mod_wsgi/4.6.4 Python/3.6", "status": 500, "url": "http://localhost/ovirt-engine/services/health"}" [2] This was the error message i got: "VDSM ovirt.martinwi.local command HostSetupNetworksVDS failed: Internal JSON-RPC error: {'reason': "Invalid IP address: 'fe80::ea3f:67ff:fe7f:a029%ovirtmgmt' does not appear to be an IPv4 or IPv6 address"}" [3] /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20230718140628-rryscj.log: 2023-07-18 16:32:35,877+0200 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:106 {'msg': 'Fault reason is "Operation Failed". Fault detail is "[Failed to fetch Gluster Volume List]". HTTP response code is 400.', 'exception': 'Traceback (most recent call last):\n File "/tmp/ansible_ovirt_storage_domain_payload_b4ofbzxa/ansible_ovirt_storage_domain_payload.zip/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_storage_domain.py", line 804, in main\n File "/tmp/ansible_ovirt_storage_domain_payload_b4ofbzxa/ansible_ovirt_storage_domain_payload.zip/ansible_collections/ovirt/ovirt/plugins/module_utils/ovirt.py", line 674, in create\n **kwargs\n File "/usr/lib64/python3.6/site-packages/ovirtsdk4/services.py", line 26258, in add\n return self._internal_add(storage_domain, headers, query, wait)\n File "/usr/lib64/python3.6/site-packages/ovirtsdk4/service.py", line 232, in _internal_add\n return future.wait() if wait else future\n File "/usr/lib64/python3.6/site-packages/ovirtsdk4/service.py", line 55, in wait\n return self._code(response)\n File "/usr/lib64/python3.6/site-packages/ovirtsdk4/service.py", line 229, in callback\n self._check_fault(response)\n File "/usr/lib64/python3.6/site-packages/ovirtsdk4/service.py", line 132, in _check_fault\n self._raise_error(response, body)\n File "/usr/lib64/python3.6/site-packages/ovirtsdk4/service.py", line 118, in _raise_error\n raise error\novirtsdk4.Error: Fault reason is "Operation Failed". Fault detail is "[Failed to fetch Gluster Volume List]". HTTP response code is 400.\n', 'invocation': {'module_args': {'state': 'unattached', 'name': 'hosted_storage', 'host': 'ovirt.martinwi.local', 'data_center': 'Default', 'wait': True, 'glusterfs': {'address': 'gluster1.martinwi.local', 'path': '/gv3', 'mount_options': ''}, 'timeout': 180, 'poll_interval': 3, 'fetch_nested': False, 'nested_attributes': [], 'domain_function': 'data', 'id': None, 'description': None, 'comment': None, 'localfs': None, 'nfs': None, 'iscsi': None, 'managed_block_storage': None, 'posixfs': None, 'fcp': None, 'wipe_after_delete': None, 'backup': None, 'critical_space_action_blocker': None, 'warning_low_space': None, 'destroy': None, 'format': None, 'discard_after_delete': None}}, '_ansible_no_log': False, 'changed': False}

1 0