Multiple hosts stuck in Connecting state waiting for storage pool to go up.
by ivan.lezhnjov.iv＠gmail.com
Hi!
We have a problem with multiple hosts stuck in Connecting state, which I hoped somebody here could help us wrap our heads around.
All hosts, except one, seem to have very similar symptoms but I'll focus on one host that represents the rest.
So, the host is stuck in Connecting state and this what we see in oVirt log files.
/var/log/ovirt-engine/engine.log:
2023-04-20 09:51:53,021+03 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesAsyncVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-37) [] Command 'GetCapabilitiesAsyncVDSCommand(HostName = ABC010-176-XYZ, VdsIdAndVdsVDSCommandParametersBase:{hostId='2c458562-3d4d-4408-afc9-9a9484984a91', vds='Host[ABC010-176-XYZ,2c458562-3d4d-4408-afc9-9a9484984a91]'})' execution failed: org.ovirt.vdsm.jsonrpc.client.ClientConnectionException: SSL session is invalid
2023-04-20 09:55:16,556+03 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-67) [] EVENT_ID: VDS_BROKER_COMMAND_FAILURE(10,802), VDSM ABC010-176-XYZ command Get Host Capabilities failed: Message timeout which can be caused by communication issues
/var/log/vdsm/vdsm.log:
2023-04-20 17:48:51,977+0300 INFO (vmrecovery) [vdsm.api] START getConnectedStoragePoolsList() from=internal, task_id=ebce7c8c-6ded-454e-9aee-86edf72764ef (api:31)
2023-04-20 17:48:51,977+0300 INFO (vmrecovery) [vdsm.api] FINISH getConnectedStoragePoolsList return={'poollist': []} from=internal, task_id=ebce7c8c-6ded-454e-9aee-86edf72764ef (api:37)
2023-04-20 17:48:51,978+0300 INFO (vmrecovery) [vds] recovery: waiting for storage pool to go up (clientIF:723)
Both engine.log and vdsm.log are flooded with these messages. They are repeated at regular intervals ad infinitum. This is one common symptom shared by multiple hosts in our deployment. They all have these message loops in engine.log and vdsm.log files. On all
Running vdsm-client Host getConnectedStoragePools also returns an empty list represented by [] on all hosts (but interestingly there is one that showed Storage Pool UUID and yet it was still stuck in Connecting state).
This particular host (ABC010-176-XYZ) is connected to 3 CEPH iSCSI Storage Domains and lsblk shows 3 block devices with matching UUIDs in their device components. So, the storage seems to be connected but the Storage Pool is not? How is that even possible?
Now, what's even more weird is that we tried rebooting the host (via Administrator Portal) and it didn't help. We even tried removing and re-adding the host in Administrator Portal but to no avail.
Additionally, the host refused to go into Maintenance mode so we had to enforce it by manually updating Engine DB.
We also tried reinstalling the host via Administrator Portal and ran into another weird problem, which I'm not sure if it's a related one or a problem that deserves a dedicated discussion thread but, basically, the underlying Ansible playbook exited with the following error message:
"stdout" : "fatal: [10.10.10.176]: UNREACHABLE! => {\"changed\": false, \"msg\": \"Data could not be sent to remote host \\\"10.10.10.176\\\". Make sure this host can be reached over ssh: \", \"unreachable\": true}",
Counterintuitively, just before running Reinstall via Administrator Portal we had been able to reboot the same host (which as you know oVirt does via Ansible as well). So, no changes on the host in between just different Ansible playbooks. To confirm that we actually had access to the host over ssh we successfully ran ssh -p $PORT root(a)10.10.10.176 -i /etc/pki/ovirt-engine/keys/engine_id_rsa and it worked.
That made us scratch our heads for a while but what seems to had fixed Ansible's ssh access problems was manual full stop of all VDSM-related systemd services on the host. It was just a wild guess but as soon as we stopped all VDSM services Ansible stopped complaining about not being able to reach the target host and successfully did its job.
I'm sure you'd like to see more logs but I'm not certain what exactly is relevant. There are a ton of logs as this deployment is comprised of nearly 80 hosts. So, I guess it's best if you just request to see specific logs, messages or configuration details and I'll cherry-pick what's relevant.
We don't really understand what's going on and would appreciate any help. We tried just about anything we could think of to resolve this issue and are running out of ideas what to do next.
If you have any questions just ask and I'll do my best to answer them.
6 months
- 2
- 4
Re: Failed to synchronize networks of Provider ovirt-provider-ovn
by Mail SET Inc. Group
Yes, i use same manual to change WebUI SSL.
ovirt-ca-file= is a same SSL file which use WebUI.
Yes, i restart ovirt-provider-ovn, i restart engine, i restart all what i can restart. Nothing...
> 12 сент. 2018 г., в 16:11, Dominik Holler <dholler(a)redhat.com> написал(а):
>
> On Wed, 12 Sep 2018 14:23:54 +0300
> "Mail SET Inc. Group" <mail(a)set-pro.net> wrote:
>
>> Ok!
>
> Not exactly, please use users(a)ovirt.org for such questions.
> Other should benefit from this questions, too.
> Please write the next mail to users(a)ovirt.org and keep me in CC.
>
>> What i did:
>>
>> 1) install oVirt «from box» (4.2.5.2-1.el7);
>> 2) generate own ssl for my engine using my FreeIPA CA, Install it and
>
> What means "Install it"? You can use the doc from the following link
> https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2/...
>
> Ensure that ovirt-ca-file= in
> /etc/ovirt-provider-ovn/conf.d/10-setup-ovirt-provider-ovn.conf
> points to the correct file and ovirt-provider-ovn is restarted.
>
>> get tis issue;
>>
>>
>> [root@engine ~]# tail -n 50 /var/log/ovirt-provider-ovn.log
>> 2018-09-12 14:10:23,828 root [SSL: CERTIFICATE_VERIFY_FAILED]
>> certificate verify failed (_ssl.c:579) Traceback (most recent call
>> last): File "/usr/share/ovirt-provider-ovn/handlers/base_handler.py",
>> line 133, in _handle_request method, path_parts, content
>> File "/usr/share/ovirt-provider-ovn/handlers/selecting_handler.py",
>> line 175, in handle_request return
>> self.call_response_handler(handler, content, parameters) File
>> "/usr/share/ovirt-provider-ovn/handlers/keystone.py", line 33, in
>> call_response_handler return response_handler(content, parameters)
>> File "/usr/share/ovirt-provider-ovn/handlers/keystone_responses.py",
>> line 62, in post_tokens user_password=user_password) File
>> "/usr/share/ovirt-provider-ovn/auth/plugin_facade.py", line 26, in
>> create_token return auth.core.plugin.create_token(user_at_domain,
>> user_password) File
>> "/usr/share/ovirt-provider-ovn/auth/plugins/ovirt/plugin.py", line
>> 48, in create_token timeout=self._timeout()) File
>> "/usr/share/ovirt-provider-ovn/auth/plugins/ovirt/sso.py", line 75,
>> in create_token username, password, engine_url, ca_file, timeout)
>> File "/usr/share/ovirt-provider-ovn/auth/plugins/ovirt/sso.py", line
>> 91, in _get_sso_token timeout=timeout File
>> "/usr/share/ovirt-provider-ovn/auth/plugins/ovirt/sso.py", line 54,
>> in wrapper response = func(*args, **kwargs) File
>> "/usr/share/ovirt-provider-ovn/auth/plugins/ovirt/sso.py", line 47,
>> in wrapper raise BadGateway(e) BadGateway: [SSL:
>> CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:579)
>>
>>
>> [root@engine ~]# tail -n 20 /var/log/ovirt-engine/engine.log
>> 2018-09-12 14:10:23,773+03 INFO
>> [org.ovirt.engine.core.bll.provider.network.SyncNetworkProviderCommand]
>> (EE-ManagedThreadFactory-engineScheduled-Thread-47) [316db685] Lock
>> Acquired to object
>> 'EngineLock:{exclusiveLocks='[14e4fb72-9764-4757-b37d-4d487995571a=PROVIDER]',
>> sharedLocks=''}' 2018-09-12 14:10:23,778+03 INFO
>> [org.ovirt.engine.core.bll.provider.network.SyncNetworkProviderCommand]
>> (EE-ManagedThreadFactory-engineScheduled-Thread-47) [316db685]
>> Running command: SyncNetworkProviderCommand internal: true.
>> 2018-09-12 14:10:23,836+03 ERROR
>> [org.ovirt.engine.core.bll.provider.network.SyncNetworkProviderCommand]
>> (EE-ManagedThreadFactory-engineScheduled-Thread-47) [316db685]
>> Command
>> 'org.ovirt.engine.core.bll.provider.network.SyncNetworkProviderCommand'
>> failed: EngineException: (Failed with error Bad Gateway and code
>> 5050) 2018-09-12 14:10:23,837+03 INFO
>> [org.ovirt.engine.core.bll.provider.network.SyncNetworkProviderCommand]
>> (EE-ManagedThreadFactory-engineScheduled-Thread-47) [316db685] Lock
>> freed to object
>> 'EngineLock:{exclusiveLocks='[14e4fb72-9764-4757-b37d-4d487995571a=PROVIDER]',
>> sharedLocks=''}' 2018-09-12 14:14:12,477+03 INFO
>> [org.ovirt.engine.core.sso.utils.AuthenticationUtils] (default
>> task-6) [] User admin@internal successfully logged in with scopes:
>> ovirt-app-admin ovirt-app-api ovirt-app-portal
>> ovirt-ext=auth:sequence-priority=~ ovirt-ext=revoke:revoke-all
>> ovirt-ext=token-info:authz-search
>> ovirt-ext=token-info:public-authz-search
>> ovirt-ext=token-info:validate ovirt-ext=token:password-access
>> 2018-09-12 14:14:12,587+03 INFO
>> [org.ovirt.engine.core.bll.aaa.CreateUserSessionCommand] (default
>> task-6) [1bf1b763] Running command: CreateUserSessionCommand
>> internal: false. 2018-09-12 14:14:12,628+03 INFO
>> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
>> (default task-6) [1bf1b763] EVENT_ID: USER_VDC_LOGIN(30), User
>> admin@internal-authz connecting from '10.0.3.61' using session
>> 's8jAm7BUJGlicthm6yZBA3CUM8QpRdtwFaK3M/IppfhB3fHFB9gmNf0cAlbl1xIhcJ2WX+ww7e71Ri+MxJSsIg=='
>> logged in. 2018-09-12 14:14:30,972+03 INFO
>> [org.ovirt.engine.core.bll.provider.ImportProviderCertificateCommand]
>> (default task-6) [ee3cc8a7-4485-4fdf-a0c2-e9d67b5cfcd3] Running
>> command: ImportProviderCertificateCommand internal: false. Entities
>> affected : ID: aaa00000-0000-0000-0000-123456789aaa Type:
>> SystemAction group CREATE_STORAGE_POOL with role type ADMIN
>> 2018-09-12 14:14:30,982+03 INFO
>> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
>> (default task-6) [ee3cc8a7-4485-4fdf-a0c2-e9d67b5cfcd3] EVENT_ID:
>> PROVIDER_CERTIFICATE_IMPORTED(213), Certificate for provider
>> ovirt-provider-ovn was imported. (User: admin@internal-authz)
>> 2018-09-12 14:14:31,006+03 INFO
>> [org.ovirt.engine.core.bll.provider.TestProviderConnectivityCommand]
>> (default task-6) [a48d94ab-b0b2-42a2-a667-0525b4c652ea] Running
>> command: TestProviderConnectivityCommand internal: false. Entities
>> affected : ID: aaa00000-0000-0000-0000-123456789aaa Type:
>> SystemAction group CREATE_STORAGE_POOL with role type ADMIN
>> 2018-09-12 14:14:31,058+03 ERROR
>> [org.ovirt.engine.core.bll.provider.TestProviderConnectivityCommand]
>> (default task-6) [a48d94ab-b0b2-42a2-a667-0525b4c652ea] Command
>> 'org.ovirt.engine.core.bll.provider.TestProviderConnectivityCommand'
>> failed: EngineException: (Failed with error Bad Gateway and code
>> 5050) 2018-09-12 14:15:10,954+03 INFO
>> [org.ovirt.engine.core.bll.utils.ThreadPoolMonitoringService]
>> (EE-ManagedThreadFactory-engineThreadMonitoring-Thread-1) [] Thread
>> pool 'default' is using 0 threads out of 1, 5 threads waiting for
>> tasks. 2018-09-12 14:15:10,954+03 INFO
>> [org.ovirt.engine.core.bll.utils.ThreadPoolMonitoringService]
>> (EE-ManagedThreadFactory-engineThreadMonitoring-Thread-1) [] Thread
>> pool 'engine' is using 0 threads out of 500, 16 threads waiting for
>> tasks and 0 tasks in queue. 2018-09-12 14:15:10,954+03 INFO
>> [org.ovirt.engine.core.bll.utils.ThreadPoolMonitoringService]
>> (EE-ManagedThreadFactory-engineThreadMonitoring-Thread-1) [] Thread
>> pool 'engineScheduled' is using 0 threads out of 100, 100 threads
>> waiting for tasks. 2018-09-12 14:15:10,954+03 INFO
>> [org.ovirt.engine.core.bll.utils.ThreadPoolMonitoringService]
>> (EE-ManagedThreadFactory-engineThreadMonitoring-Thread-1) [] Thread
>> pool 'engineThreadMonitoring' is using 1 threads out of 1, 0 threads
>> waiting for tasks. 2018-09-12 14:15:10,954+03 INFO
>> [org.ovirt.engine.core.bll.utils.ThreadPoolMonitoringService]
>> (EE-ManagedThreadFactory-engineThreadMonitoring-Thread-1) [] Thread
>> pool 'hostUpdatesChecker' is using 0 threads out of 5, 2 threads
>> waiting for tasks. 2018-09-12 14:15:23,843+03 INFO
>> [org.ovirt.engine.core.bll.provider.network.SyncNetworkProviderCommand]
>> (EE-ManagedThreadFactory-engineScheduled-Thread-61) [2455041f] Lock
>> Acquired to object
>> 'EngineLock:{exclusiveLocks='[14e4fb72-9764-4757-b37d-4d487995571a=PROVIDER]',
>> sharedLocks=''}' 2018-09-12 14:15:23,849+03 INFO
>> [org.ovirt.engine.core.bll.provider.network.SyncNetworkProviderCommand]
>> (EE-ManagedThreadFactory-engineScheduled-Thread-61) [2455041f]
>> Running command: SyncNetworkProviderCommand internal: true.
>> 2018-09-12 14:15:23,900+03 ERROR
>> [org.ovirt.engine.core.bll.provider.network.SyncNetworkProviderCommand]
>> (EE-ManagedThreadFactory-engineScheduled-Thread-61) [2455041f]
>> Command
>> 'org.ovirt.engine.core.bll.provider.network.SyncNetworkProviderCommand'
>> failed: EngineException: (Failed with error Bad Gateway and code
>> 5050) 2018-09-12 14:15:23,901+03 INFO
>> [org.ovirt.engine.core.bll.provider.network.SyncNetworkProviderCommand]
>> (EE-ManagedThreadFactory-engineScheduled-Thread-61) [2455041f] Lock
>> freed to object
>> 'EngineLock:{exclusiveLocks='[14e4fb72-9764-4757-b37d-4d487995571a=PROVIDER]',
>> sharedLocks=''}'
>>
>>
>> [root@engine ~]#
>> cat /etc/ovirt-provider-ovn/conf.d/10-setup-ovirt-provider-ovn.conf #
>> This file is automatically generated by engine-setup. Please do not
>> edit manually [OVN REMOTE] ovn-remote=ssl:127.0.0.1:6641
>> [SSL]
>> https-enabled=true
>> ssl-cacert-file=/etc/pki/ovirt-engine/ca.pem
>> ssl-cert-file=/etc/pki/ovirt-engine/certs/ovirt-provider-ovn.cer
>> ssl-key-file=/etc/pki/ovirt-engine/keys/ovirt-provider-ovn.key.nopass
>> [OVIRT]
>> ovirt-sso-client-secret=Ms7Gw9qNT6IkXu7oA54tDmxaZDIukABV
>> ovirt-host=https://engine.set.local:443
>> ovirt-sso-client-id=ovirt-provider-ovn
>> ovirt-ca-file=/etc/pki/ovirt-engine/apache-ca.pem
>> [PROVIDER]
>> provider-host=engine.set.local
>>
>>
>>> 12 сент. 2018 г., в 13:59, Dominik Holler <dholler(a)redhat.com>
>>> написал(а):
>>>
>>> On Wed, 12 Sep 2018 13:04:53 +0300
>>> "Mail SET Inc. Group" <mail(a)set-pro.net> wrote:
>>>
>>>> Hello Dominik!
>>>> I have a same issue with OVN provider and SSL
>>>> https://www.mail-archive.com/users@ovirt.org/msg47020.html
>>>> <https://www.mail-archive.com/users@ovirt.org/msg47020.html> But
>>>> certificate changes not helps to resolve it. Maybe you can help me
>>>> with this?
>>>
>>> Sure. Can you please share the relevant lines of
>>> ovirt-provider-ovn.log and engine.log, and the information if you
>>> are using the certificates generated by engine-setup with
>>> users(a)ovirt.org ? Thanks,
>>> Dominik
>>>
>>
>
>
6 months, 2 weeks
- 5
- 13
Unable to enable HPET component of an specific VM in oVirt 4.7
by ricardoot＠gmail.com
Hello community members,
I'm currently using oVirt 4.7 as my virtualization environment, and I'm facing an issue with enabling the HPET (High Precision Event Timer) component in the XML configuration file of virtual machine (VM).
Upon inspecting the XML file, I noticed that the `<timer name='hpet' present='no'/>` line is missing, indicating that the HPET component is disabled.
Here are the steps I have taken so far:
1. I verified that the VM's XML configuration file does not include the `<timer name='hpet' present='yes'/>` line.
2. While the VM was powered on, I used the following command to edit the XML configuration file:
```
virsh edit VM_NAME
```
I added the `<timer name='hpet' present='yes'/>` line to the XML file. However, the changes did not persist after restarting the VM.
To provide additional information, on the host where oVirt is running, the available clock sources can be viewed by executing the following command:
```
cat /sys/devices/system/clocksource/clocksource0/available_clocksource
```
The output shows the available clock sources, such as `tsc`, `hpet`, and `acpi_pm`.
To resolve the authentication issue with the `virsh` command, I created a user with appropriate privileges using the following command:
```
sudo saslpasswd2 -a libvirt USERNAME
```
After creating the user, I was able to authenticate successfully with the `virsh` command using the newly created credentials.
However, I'm unable to find an option to add the HPET parameter in the web console of oVirt. It seems that the option to configure HPET is not available in the web console.
Has anyone else encountered a similar issue in oVirt 4.7? Could you please provide guidance or suggest a solution to enable the HPET component in the XML configuration file of a powered-off VM in oVirt 4.7? Any insights, experiences, or suggestions would be greatly appreciated.
Thank you in advance for your assistance!
Best regards,
6 months, 2 weeks
- 2
- 4
What is the status of the whole Ovirt Project?
by Arman Khalatyan
Hello everybody,
What is the status of the ovirt project, would be continued it in the
Rocky Linunx9?
the last message is so sad:
https://lists.ovirt.org/archives/list/users@ovirt.org/thread/HEKKBM6MZEKB...
Any good news/progress there?
As a happy ovirt user since 2016 should we move to an another system?
Thank you beforehand,
Arman.
6 months, 3 weeks
- 9
- 14
engine-config -s UserSessionTimeOutInterval=X problem
by marek
ovirt 4.5.4, standalone engine, centos 8 stream
[root@ovirt ~]# engine-config -g UserSessionTimeOutInterval
Picked up JAVA_TOOL_OPTIONS: -Dcom.redhat.fips=false
UserSessionTimeOutInterval: 30 version: general
[root@ovirt ~]# engine-config -s UserSessionTimeOutInterval=60
Picked up JAVA_TOOL_OPTIONS: -Dcom.redhat.fips=false
Cannot set value 60 to key UserSessionTimeOutInterval.
any ideas where is the problem?
Marek
8 months, 2 weeks
- 5
- 6
Unable to upload or download iso via admin portal
by Igor Filipovic
Hi, I'm having a trouble on fresh 4.4.10.7 installation (on oracle linux), I'm not able to upload or download any file using storage domain upload image function. I've imported CA certificate and have tried on several browsers (firefow, chrome,edge), on different computers (and browsers are green - claiming that I'm securely connected), but I'm always getting error regarding CA certificate when I test connection, or when I try to upload ISO image. I've tried to upload ISO image via cli commands (upload_disk.py), and that scenario was successful, however this method It is not very convenient for my co-workers.
I have 5 physical hosts, one is dedicated to run ovirt-engine, and other 4 are kvm hypervisors. When I try to upload ISO this is what engine.log logs:
2023-04-08 11:00:28,339+02 INFO [org.ovirt.engine.core.bll.storage.disk.image.TransferImageStatusCommand] (default task-2) [f6b62add-0a0c-45ee-a985-a76171843382] Running command: TransferImageStatusCommand internal: false. Entities affected : ID: 1eb97088-b805-4616-af55-0ac9d1d7dfbe Type: SystemAction group CREATE_DISK with role type USER
2023-04-08 11:00:28,340+02 INFO [org.ovirt.engine.core.bll.storage.disk.image.ImageTransferUpdater] (default task-2) [f6b62add-0a0c-45ee-a985-a76171843382] Updating image transfer a78b18c5-e395-4c29-aa5c-15ffff8a1cb6 (image 4f758325-ac11-4071-a9fa-d180425e8604) phase to Paused by System (message: 'Sent 0MB')
2023-04-08 11:00:28,363+02 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-2) [f6b62add-0a0c-45ee-a985-a76171843382] EVENT_ID: UPLOAD_IMAGE_NETWORK_ERROR(1,062), Unable to upload image to disk 4f758325-ac11-4071-a9fa-d180425e8604 due to a network error. Ensure ovirt-engine's CA certificate is registered as a trusted CA in the browser. The certificate can be fetched from https://engine-dr.somedomain/ovirt-engine/services/pki-resource?resource=...
2023-04-08 11:00:28,363+02 INFO [org.ovirt.engine.core.bll.storage.disk.image.TransferImageStatusCommand] (default task-2) [f6b62add-0a0c-45ee-a985-a76171843382] Running command: TransferImageStatusCommand internal: false. Entities affected : ID: 1eb97088-b805-4616-af55-0ac9d1d7dfbe Type: SystemAction group CREATE_DISK with role type USER
Can you please point me in some direction to try to fix this?
Thanks, and best regards
Igor
8 months, 2 weeks
- 4
- 4
ovirt.hosted_engine_setup : Obtain SSO token using username/password credentials
by cmicarelli＠fdmservices.it
Hi Guys,
I'm tried to install ovirt 4.5 on centos 8 stream and everytime file with this error
ovirt.hosted_engine_setup : Obtain SSO token using username/password credentials
Someone could help me?
Regrards
8 months, 3 weeks
- 2
- 2
How restore nodes ovirt UP from NonResponsive and VMs executing
by José Pascual
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/>
9 months
- 3
- 2
Installing oVirt as a self-hosted engine - big big problem :()
by Jorge Visentini
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
9 months, 1 week
- 2
- 2
Ovirt engine after OS update doesn't start with WFLYEE0042: Failed t,o construct component instance
by Jirka Simon
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
9 months, 2 weeks
- 1
- 1