- Users - oVirt List Archives

Re: CPU Shares
by Marcos Sungaila 03 Feb '23

03 Feb '23

Hi Nick, Setting CPU Shares only changes how the instance works. It does not affect the current workload unless the instance is under pressure. For example, if you are running an RDBMS, you may see a performance improvement when normalizing the database or generating a monthly report. Even that, the improvement may be minimum. Do not expect a sensible performance improvement for normal operation. Performance tuning is not magic. You will often perform many configurations to see a 1%, maybe 2% gain. Regards, Marcos From: Nick --- <jsmith1299(a)live.com> Sent: Wednesday, February 1, 2023 9:59 AM To: users(a)ovirt.org Subject: [External] : [ovirt-users] CPU Shares Hello, I would like some help understanding CPU shares. We have several VMs which are CPU pinned due to licensing. We would like to favor one VM since it is our application VM over the other VMs which it is pinned with. Would I set the CPU share on the one that needs to priority to high or low? In the documentation I see the following: Specify CPU Shares. Possible options are Low, Medium, High, Custom, and Disabled. Virtual machines set to High receive twice as many shares as Medium, and virtual machines set to Medium receive twice as many shares as virtual machines set to Low. Disabled instructs VDSM to use an older algorithm for determining share dispensation; usually the number of shares dispensed under these conditions is 1020. I currently have it set to high and I believe it is doing the opposite of what I want it to do as the CPU steal percentage appears to be 10-15% over the other VMs which show no CPU steal and are set to low. I'd like to confirm if I have this setup correctly or not. Thanks, Nick

1 0

Re: Self-hosted engine 4.5.0 deployment fails
by John 01 Feb '23

01 Feb '23

I would run the deploy again, wait until the engine is up and then from the server you are deploying the engine on # virsh list obtain the virtual machine number from the above command, in the example below we assume the number is 1 # virsh console 1 login as root wait for all packages to finish updating: tail -f /var/log/dnf.rpm.log then: # dnf downgrade postgresql-jdbc once that's done the deployment of the engine should get past the [ INFO ] TASK [ovirt.ovirt.engine_setup : Check if Engine health page is up] step. On 03/05/2022 17:03, Mohamed Roushdy wrote: > > Hello, > > I’m deploying on Ovirt nodes v4.5.0.1, but it fails to deploy the > self-hosted engine with the following errors in the web installer: > > [ INFO ] skipping: [localhost] > [ INFO ] TASK [ovirt.ovirt.engine_setup : Check if Engine health page > is up] > [ ERROR ] fatal: [localhost -> 192.168.222.197]: FAILED! => > {"attempts": 30, "changed": false, "connection": "close", > "content_encoding": "identity", "content_length": "86", > "content_type": "text/html; charset=UTF-8", "date": "Tue, 03 May 2022 > 15:57:20 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", "status": 500, "url": > http://localhost/ovirt-engine/services/health} > [ INFO ] TASK [ovirt.ovirt.engine_setup : Clean temporary files] > [ INFO ] changed: [localhost -> 192.168.222.197] > [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Sync on engine machine] > [ INFO ] changed: [localhost -> 192.168.222.197] > [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Set destination > directory path] > [ INFO ] ok: [localhost -> localhost] > [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Create destination > directory] > [ INFO ] changed: [localhost -> 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 -> localhost] > [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Set local_vm_disk_path] > [ INFO ] ok: [localhost -> 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 -> localhost] > [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Notify the user about > a failure] > [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": > "There was a failure deploying the engine on the local engine VM. 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"} > > Any idea if this is a bug or something? I tried to deploy for eight > times with different configuration > > Thank y9ou, > > > _______________________________________________ > Users mailing list --users(a)ovirt.org > To unsubscribe send an email tousers-leave(a)ovirt.org > Privacy Statement:https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct:https://www.ovirt.org/community/about/community-guidelines/ > List Archives:https://lists.ovirt.org/archives/list/users@ovirt.org/message/XL3Q…

2 1

CPU Shares
by Nick --- 01 Feb '23

01 Feb '23

Hello, I would like some help understanding CPU shares. We have several VMs which are CPU pinned due to licensing. We would like to favor one VM since it is our application VM over the other VMs which it is pinned with. Would I set the CPU share on the one that needs to priority to high or low? In the documentation I see the following: Specify CPU Shares. Possible options are Low, Medium, High, Custom, and Disabled. Virtual machines set to High receive twice as many shares as Medium, and virtual machines set to Medium receive twice as many shares as virtual machines set to Low. Disabled instructs VDSM to use an older algorithm for determining share dispensation; usually the number of shares dispensed under these conditions is 1020. I currently have it set to high and I believe it is doing the opposite of what I want it to do as the CPU steal percentage appears to be 10-15% over the other VMs which show no CPU steal and are set to low. I'd like to confirm if I have this setup correctly or not. Thanks, Nick

1 0

Cluster level upgrade (from 4.3 to 4.6) and Windows VM
by duparchy＠esrf.fr 01 Feb '23

01 Feb '23

Hi, When trying to upgrade the Cluster level to 4.6, a popup panel says "Due to the emulated machine change, some Windows virtual machines might lose static IP configuration" It is not clear if Windows VMs might be disconnected from the network right away when clicking OK or only when restarted... Bets regards

4 3

multiple disk snapshot_memory stay in locked state
by Nathanaël Blanchet 30 Jan '23

30 Jan '23

Hello, After many (failed) snapshot attempts, I find many disk snapshot_memory in locked state into the disks menu. unlock utility returns anything... how can I erase those disks, knowing that there is no listed snapshot for this vm

1 1

I need the deploy script to wait for fixing network configuration manually in oVirt 4.3.10
by lars.stolpe＠bvg.de 30 Jan '23

30 Jan '23

Hi, i'm planing to upgrade our production environment from oVirt 4.3 to 4.4. So i do need a fresh oVirt 4.3 installation to test the procedure before doing it in production. The command line deploy script can't handle network interfaces correctly. If i use either a single NIC oder a bond (active/passive) i get the error message "The selected network interface is not valid". If i predefine the management bridge to a running state, the deploy process goes on, but fails to activate the added host and removes the already running engine vm. The deploy process fails to synchronize the existing working network configuration with the engine configuration. I can already log in to the engine GUI and see, that the bridge "ovirtmgmt" needs to be assigned to the bonding IF, but i'm not fast enough to do so, because the deployment process ist already shutting down and erasing the vm. I do see the following ways to succeed: 1. make the depoyment process accept the given interfaces (maybe ignore errors) 2. make the deploy process wait for me to take necessary actions before checking the engine Do anyone know, how to achieve this? All i need is a running engine on hosted_storage... any other issues i can fix later. Another idea is to use one of the destined hosts as a bare metal engine, add hosts, backup the engine and use that backup for a hosted engine restore deploy, since the deploy script asks to wait after local vm is ready, but only if i do a recovery deploy. Any suggestions?

3 3

How to view multi ovirt-manager VM ?
by rak kim 27 Jan '23

27 Jan '23

Hello, I'm kim I have 7 ovirt-manager running on each service I want to manage 7 ovirt-manger on one platform Is there any program to view VMs at each ovirt-manager for one platform ? (like multi-cloud platform ?) I guess I just need to be able to control/view the VM.

2 2

Changing the Cluster Compatibility Version in hyperconverged environment
by lexxthefox＠gmail.com 25 Jan '23

25 Jan '23

Hi! I'm sorry if it is a noob question but it is very important for me. We are researching oVirt in our company and hope to use existing environment where there's no SAN/NAS solution. Just a bunch of servers. We were able to set up a hyperconverged installation with oVirt 4.4 a while ago and now I'm resuming research and trying to upgrade it to 4.5. I was able to upgrade HE and Hosts. What's left is to upgrade Cluster Compatibility Version from 4.5 to 4.7. I don't seem to find a way to do it as when I try to Edit cluster I get this error: "Cluster Compatibility Version". Upgrade Guide on https://www.ovirt.org/documentation/upgrade_guide/ does not have entries for hyperconverged set up. So I don't know where to look for information on this topic. Is it possible to achieve my goal at all? Can "frozen" Cluster Compatibility Version cause problems in the long run? I can rebuild the whole setup now when it is still being reviewed and planed. But if we start using it actively it won't be possible. I'm afraid that this could be a show-stopper in the long run. Thanks in advance!

3 6

New Ovirt installation on existing Ovirt
by yevhen.kyrylchenko＠gmail.com 25 Jan '23

25 Jan '23

Hi! I have a strange idea - I try to create a small Ovirt test lab on my existing Ovirt infrastructure. I have two real Ovirt hosts: host01 - 192.168.1.10/24, GW 192.168.1.1 host02 - 192.168.1.11/24, GW 192.168.1.1 I created VM on which I want to install new Ovirt instance: v_host01 - 192.168.1.100, checked Pass-Through Host CPU. During deployment hosted engine on v_host01 (lets say v_he - 192.168.1.110), Ovirt creates temporary bridge with random IP and hosted engine VM can comunicate through that bridge. After successful deployment this HE VM has assigned static IP 192.168.1.110. And now communication is possible only between v_host01 and v_he... I can't reach network from v_he further than v_host01 and can't reach v_he from hosts other than v_host01. Seems than bridge on v_host01, created during deployment doesn't want to forward traffik... Do you have any ideas what should I check? Regards!

1 0

Regenerate DWH ovirt_engine_history
by Diego Ercolani 24 Jan '23

24 Jan '23

Hello to all and happy new year. My question is "simple". I need to "reset" the ovirt_engine_history database. I tried to use: engine-setup --reconfigure-optional-components after removing: - ovirt_engine_history - set to "False" OVESETUP_DWH_CORE/enable=bool:True OVESETUP_GRAFANA_CORE/enable=bool:True in /etc/ovirt-engine-setup.conf.d/20-setup-ovirt-post.conf (obviously all in "Global Maintenance") currently I have a system where I have an initialized ovirt_engine_history but no engine is writing in it. I tried to follow (in some manner): https://www.ovirt.org/documentation/data_warehouse_guide/ In the ovirt engine's log there is no exception... so I cannot address the issue. I need help to reinitialize the db... I don't need the history.. only from now on. Thank you for your help but no one is

2 11

cluster level - features
by marek 24 Jan '23

24 Jan '23

hi, do you have tips where can i find information about new features in cluster levels? i found only https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/ht… there is only information "there are new features" hard way i tried check https://www.ovirt.org/release/4.5.0/ and found https://bugzilla.redhat.com/show_bug.cgi?id=2021545 - Detecting if scratch disks can be extended automatically - Detecting if host support disk format conversion - Maybe for using qcow2 format by default to enable incremental backup by https://bugzilla.redhat.com/show_bug.cgi?id=2033185 - e1000e is there some "central" place ? Marek

1 0

ovirt upgrade - Failed to execute stage 'Misc configuration' FATAL: Ident authentication failed for user "root"
by marek 24 Jan '23

24 Jan '23

upgrade from ovirt 4.4.4 to 4.5.5 engine-setup 2023-01-24 00:35:17,885+0100 DEBUG otopi.context context._executeMethod:145 method exception Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/otopi/context.py", line 132, in _executeMethod method['method']() File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine-grafana-dwh/db/default_privileges.py", line 51, in _misc_set_default_privileges user=self.environment[ogdwhcons.GrafanaDBEnv.USER], File "/usr/share/ovirt-engine/setup/ovirt_engine_setup/engine_common/database.py", line 1808, in setDefaultPrivilegesReadOnlyForUser ownConnection=True, File "/usr/share/ovirt-engine/setup/ovirt_engine_setup/engine_common/database.py", line 249, in execute database=database, File "/usr/share/ovirt-engine/setup/ovirt_engine_setup/engine_common/database.py", line 182, in connect sslmode=sslmode, File "/usr/lib64/python3.6/site-packages/psycopg2/__init__.py", line 127, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) psycopg2.OperationalError: FATAL: Ident authentication failed for user "root" FATAL: Ident authentication failed for user "root" 2023-01-24 00:35:17,886+0100 ERROR otopi.context context._executeMethod:154 Failed to execute stage 'Misc configuration': FATAL: Ident authentication failed for user "root" FATAL: Ident authentication failed for user "root" any tips? Marek

2 4

Disaster recovery failed with direct lun 4.4.10
by jaime luque 23 Jan '23

23 Jan '23

Good night I am configuring the disaster recovery with the following environment Ovirt 4.4.10 Site A An external manager A hypervisor server Site B An external manager A hypervisor server *Mons are being replicated from one storage to another with the conditions mentioned in the active passive guide. In the File disaster_recovery_vars.yml **** The mapping of the virtual machines is carried out, one of these has direct luns When I execute the failover the virtual machines are not importing in the secondary site. If I comment on the mapping of the direct luns, it is possible to import the virtual machines and they remain working correctly. NOTE: The direct lun that the vm has is without format or partition, since I am in the testing phase. Can you please give me ideas of what to check.

1 1

pass-through CPU
by duparchy＠esrf.fr 23 Jan '23

23 Jan '23

Hi, What are the pro and cons of enabling pass-through CPU ? It is a greyed option for a VM, unless specific host(s) is/are selected. That's the thing : it's possible to select all hosts..., so, it does not make difference w/ "Start on any host" option

3 3

VM backup issue on oVirt 4.4.7
by Don Dupuis 23 Jan '23

23 Jan '23

Hello, I am having an issue backing up vms using the backup_vm.py example script. The error I get is below: [ 0.0 ] Starting full backup for VM 'c656db00-065c-4fd0-b8b9-74a86dc864fc' Traceback (most recent call last): File "/opt/riva-config/backup_vm.py", line 547, in <module> main() File "/opt/riva-config/backup_vm.py", line 146, in main args.command(args) File "/opt/riva-config/backup_vm.py", line 160, in cmd_full backup = start_backup(connection, args) File "/opt/riva-config/backup_vm.py", line 348, in start_backup description=args.description File "/usr/lib64/python3.6/site-packages/ovirtsdk4/services.py", line 34151, in add return self._internal_add(backup, headers, query, wait) File "/usr/lib64/python3.6/site-packages/ovirtsdk4/service.py", line 232, in _internal_add return future.wait() if wait else future File "/usr/lib64/python3.6/site-packages/ovirtsdk4/service.py", line 55, in wait return self._code(response) File "/usr/lib64/python3.6/site-packages/ovirtsdk4/service.py", line 229, in callback self._check_fault(response) File "/usr/lib64/python3.6/site-packages/ovirtsdk4/service.py", line 132, in _check_fault self._raise_error(response, body) File "/usr/lib64/python3.6/site-packages/ovirtsdk4/service.py", line 118, in _raise_error raise error ovirtsdk4.Error: Fault reason is "Operation Failed". Fault detail is "[Cannot backup VM. Host (vsh001) is running on a version lower than 4.4.5. Please upgrade the host in order to use incremental backup.]". HTTP response code is 409. The strange this is that I am running oVirt 4.4.7. What component is it complaining about that is not up to version needed? Any help on this would be appreciated. oVirt rpm is ovirt-host-4.4.7-1.el8.x86_64. I plan on upgrading to version 4.4.10 but want to get this fixed first. I also can't got to 4.5.x because I have problems with Windows 10 vms and vGPUs. Thanks Don

3 7

Hosted-Engine Down VSDM Cert Expired
by jarredm＠ecboces.org 22 Jan '23

22 Jan '23

Hey all, I'm looking to get a bit of guidance here. As the subject suggests, we have a hosted-engine ovirt cluster. I ran into an issue trying to login to the web interface. I was seeing errors about certificate expiration, although I didn't know what cert it was referring to at the time. I ssh'd to the hosted-engine and restarted it. However, once it shutdown, it was unable to start again. What I've discovered so far is that the hosted-engine is currently residing on node 33 (storage is on a gluster volume) and the vdsm certificate for that node has expired. There are three nodes in total, and two of them have expired certs. However, one of them has a valid cert still. I'm able to run vdsm-client commands on that node. Although I haven't done anything with that yet other than to verify that I'm able to do some of the Host get* commands successfully. I'm wondering if it is possible to "pull" the hosted-engine onto this host and fire it back up there. Thanks in advance for your help! I'm gathering log info etc as described and it will be available here: https://drive.google.com/drive/folders/1cBPrN8SuIR-dgnpRKe1eKXRZZTPPshyJ?us… Version info: Installed Packages centos-release-gluster8.noarch 1.0-1.el8 @extras centos-release-storage-common.noarch 2-2.el8 @extras glusterfs.x86_64 8.6-2.el8 @centos-gluster8 ovirt-release44.noarch 4.4.8.3-1.el8 @@commandline vdsm.x86_64 4.40.80.6-1.el8 @ovirt-4.4

2 1

Re: Cannot prepare internal mirrorlist
by ahmad.hidayat＠singtel.com 22 Jan '23

22 Jan '23

Good day Nathan! Firstly, it's polite for me to thank the moderators for approving my post.. Thank you for guiding me on this. I have configured the /etc/environment and /etc/yum.conf with the proxy configurations then curl the mirrorlist site and it was successful. Our KVM is behind a firewall, do we need to allow the traffic for a specific range of IP addresses for this? Regards, Hidayat

1 0

ovirtsdk4 python - global maintenance
by yevhen.kyrylchenko＠gmail.com 20 Jan '23

20 Jan '23

Hi! I know how to set global maintenance mode using python SDK, something like vms_service.vm_service(vm.id).maintenance(maintenance_enabled=True) on HostedEngine. But now I try to find if global maintenance is enabled. And I'm going to give up - I can't find how to do it in documentation... Is there a way to get this info? Regards!

2 2

remote-viewer, vnc console, error certificate's owner does not match hostname
by Jiří Sléžka 20 Jan '23

20 Jan '23

Hello, I have recently enrolled new certificates on all hosts in our RHV (4.5.3.5-1.el8ev) cluster but now I cannot connect to VNC or SPICE+VNC console via remote-viewer (virt-viewer-11.0-2.fc36.x86_64) because of error The certificate's owner does not match hostname '10.224.102.72' 10.224.102.72 is host's ip address Connection through spice protocol works fine .vv file looks like [virt-viewer] type=vnc host=10.224.102.72 port=5910 password=******* # Password is valid for 120 seconds. delete-this-file=1 fullscreen=0 title=srv.example.com:%d toggle-fullscreen=shift+f11 release-cursor=shift+f12 secure-attention=ctrl+alt+end versions=rhev-win64:2.0-160;rhev-win32:2.0-160;rhel8:7.0-3;rhel7:2.0-6;rhel6:99.0-1 newer-version-url=https://rhv.example.com/ovirt-engine/rhv/client-resources [ovirt] host=rhv.example.com:443 vm-guid=d9f1e9f8-1111-2222-3333-1c1db6704f21 sso-token=K9r1tHadO7H8oB........JMCSwtcwyD0syaENFA admin=1 I also tried to copy oVirt's CA cert to ~/.pki/CA/cacert.pem as mentioned in https://access.redhat.com/solutions/6217601 but error persists. Debug log looks like remote-viewer --debug Downloads/console.vv --gtk-vnc-debug (remote-viewer:2445675): gtk-vnc-DEBUG: 14:36:54.160: ../src/vncdisplay.c Connected to VNC server (remote-viewer:2445675): gtk-vnc-DEBUG: 14:36:54.160: ../src/vncconnection.c Protocol initialization (remote-viewer:2445675): gtk-vnc-DEBUG: 14:36:54.160: ../src/vncconnection.c Schedule greeting timeout 0x5621f9d53478 (remote-viewer:2445675): gtk-vnc-DEBUG: 14:36:54.161: ../src/vncconnection.c Remove timeout 0x5621f9d53478 (remote-viewer:2445675): gtk-vnc-DEBUG: 14:36:54.161: ../src/vncconnection.c Server version: 3.8 (remote-viewer:2445675): gtk-vnc-DEBUG: 14:36:54.161: ../src/vncconnection.c Sending full greeting (remote-viewer:2445675): gtk-vnc-DEBUG: 14:36:54.161: ../src/vncconnection.c Using version: 3.8 (remote-viewer:2445675): gtk-vnc-DEBUG: 14:36:54.190: ../src/vncconnection.c Possible auth 19 (remote-viewer:2445675): virt-viewer-DEBUG: 14:36:54.191: Allocated 1024x768 (remote-viewer:2445675): virt-viewer-DEBUG: 14:36:54.191: Child allocate 1024x768 (remote-viewer:2445675): gtk-vnc-DEBUG: 14:36:54.192: ../src/vncconnection.c Emit main context 14 (remote-viewer:2445675): gtk-vnc-DEBUG: 14:36:54.192: ../src/vncconnection.c Thinking about auth type 19 (remote-viewer:2445675): gtk-vnc-DEBUG: 14:36:54.192: ../src/vncconnection.c Decided on auth type 19 (remote-viewer:2445675): gtk-vnc-DEBUG: 14:36:54.192: ../src/vncconnection.c Waiting for auth type (remote-viewer:2445675): gtk-vnc-DEBUG: 14:36:54.192: ../src/vncconnection.c Choose auth 19 (remote-viewer:2445675): gtk-vnc-DEBUG: 14:36:54.192: ../src/vncconnection.c Checking if credentials are needed (remote-viewer:2445675): gtk-vnc-DEBUG: 14:36:54.192: ../src/vncconnection.c No credentials required (remote-viewer:2445675): gtk-vnc-DEBUG: 14:36:54.194: ../src/vncconnection.c Possible VeNCrypt sub-auth 261 (remote-viewer:2445675): gtk-vnc-DEBUG: 14:36:54.194: ../src/vncconnection.c Emit main context 15 (remote-viewer:2445675): gtk-vnc-DEBUG: 14:36:54.194: ../src/vncconnection.c Requested auth subtype 261 (remote-viewer:2445675): gtk-vnc-DEBUG: 14:36:54.194: ../src/vncconnection.c Waiting for VeNCrypt auth subtype (remote-viewer:2445675): gtk-vnc-DEBUG: 14:36:54.194: ../src/vncconnection.c Choose auth subtype 261 (remote-viewer:2445675): gtk-vnc-DEBUG: 14:36:54.194: ../src/vncconnection.c Checking if credentials are needed (remote-viewer:2445675): gtk-vnc-DEBUG: 14:36:54.194: ../src/vncconnection.c No credentials required (remote-viewer:2445675): gtk-vnc-DEBUG: 14:36:54.194: ../src/vncconnection.c Do TLS handshake (remote-viewer:2445675): gtk-vnc-DEBUG: 14:36:54.195: ../src/vncconnection.c Checking if credentials are needed (remote-viewer:2445675): gtk-vnc-DEBUG: 14:36:54.195: ../src/vncconnection.c Want a TLS clientname (remote-viewer:2445675): gtk-vnc-DEBUG: 14:36:54.195: ../src/vncconnection.c Requesting missing credentials (remote-viewer:2445675): gtk-vnc-DEBUG: 14:36:54.195: ../src/vncconnection.c Emit main context 13 (remote-viewer:2445675): virt-viewer-DEBUG: 14:36:54.195: Got VNC credential request for 1 credential(s) (remote-viewer:2445675): gtk-vnc-DEBUG: 14:36:54.195: ../src/vncconnection.c Set credential 2 libvirt (remote-viewer:2445675): gtk-vnc-DEBUG: 14:36:54.195: ../src/vncconnection.c Searching for certs in /etc/pki (remote-viewer:2445675): gtk-vnc-DEBUG: 14:36:54.195: ../src/vncconnection.c Searching for certs in /home/user/.pki (remote-viewer:2445675): gtk-vnc-DEBUG: 14:36:54.195: ../src/vncconnection.c Failed to find certificate CA/cacrl.pem (remote-viewer:2445675): gtk-vnc-DEBUG: 14:36:54.195: ../src/vncconnection.c Failed to find certificate libvirt/private/clientkey.pem (remote-viewer:2445675): gtk-vnc-DEBUG: 14:36:54.195: ../src/vncconnection.c Failed to find certificate libvirt/clientcert.pem (remote-viewer:2445675): gtk-vnc-DEBUG: 14:36:54.195: ../src/vncconnection.c Waiting for missing credentials (remote-viewer:2445675): gtk-vnc-DEBUG: 14:36:54.195: ../src/vncconnection.c Got all credentials (remote-viewer:2445675): gtk-vnc-DEBUG: 14:36:54.195: ../src/vncconnection.c No client cert or key provided (remote-viewer:2445675): gtk-vnc-DEBUG: 14:36:54.195: ../src/vncconnection.c No CA revocation list provided (remote-viewer:2445675): gtk-vnc-DEBUG: 14:36:54.195: ../src/vncconnection.c Handshake was blocking (remote-viewer:2445675): gtk-vnc-DEBUG: 14:36:54.197: ../src/vncconnection.c Handshake was blocking (remote-viewer:2445675): gtk-vnc-DEBUG: 14:36:54.199: ../src/vncconnection.c Handshake was blocking (remote-viewer:2445675): gtk-vnc-DEBUG: 14:36:54.200: ../src/vncconnection.c Handshake was blocking (remote-viewer:2445675): gtk-vnc-DEBUG: 14:36:54.200: ../src/vncconnection.c Handshake done (remote-viewer:2445675): gtk-vnc-DEBUG: 14:36:54.200: ../src/vncconnection.c Validating (remote-viewer:2445675): gtk-vnc-DEBUG: 14:36:54.200: ../src/vncconnection.c Certificate is valid. (remote-viewer:2445675): gtk-vnc-DEBUG: 14:36:54.200: ../src/vncconnection.c Checking chain 0 (remote-viewer:2445675): gtk-vnc-DEBUG: 14:36:54.200: ../src/vncconnection.c Error: The certificate's owner does not match hostname '10.224.102.72' (remote-viewer:2445675): gtk-vnc-DEBUG: 14:36:54.200: ../src/vncconnection.c Emit main context 19 (remote-viewer:2445675): virt-viewer-WARNING **: 14:36:54.200: vnc-session: got vnc error The certificate's owner does not match hostname '10.224.102.72' (remote-viewer:2445675): gtk-vnc-DEBUG: 14:36:54.200: ../src/vncdisplay.c VNC server error (remote-viewer:2445675): gtk-vnc-DEBUG: 14:36:54.200: ../src/vncconnection.c Auth failed Also noVNC client throws "Something went wrong, connection is closed" Certificate on one of hosts looks like [root@rhev01 ~]# openssl x509 -in /etc/pki/vdsm/libvirt-vnc/server-cert.pem -text -noout Certificate: Data: Version: 3 (0x2) Serial Number: 165 (0xa5) Signature Algorithm: sha256WithRSAEncryption Issuer: C = US, O = SU Opava, CN = CA-rhv.example.com.51627 Validity Not Before: Jan 11 12:06:21 2023 GMT Not After : Jan 13 12:06:21 2028 GMT Subject: O = SU Opava, CN = rhev01.net.slu.cz ... X509v3 Subject Alternative Name: DNS:rhev01.net.slu.cz Yes, certificate has dns name of host inside, .vv file uses an ip address. Is it a bug? Can I disable hostname checking in remote-viewer somehow? Thanks in advance, Jiri

1 0

Updating the DNS configuration for the Hosted Engine
by nathan.english＠bt.com 20 Jan '23

20 Jan '23

Hi All, I've had a look through the documentation and not been able to find any up to date information on how to do this. We've now built a permanent DNS solution and need to update the Hosted Engine DNS server details. Luckily, I have managed to update the hosts configuration using the Data Center Settings so it's just the Hosted Engine to complete. Any advice on where should I update? I didn't want to update the if config file, as I assumed it's controlled by ansible somewhere! Kind Regards, Nathan

2 2

Cannot prepare internal mirrorlist
by ahmad.hidayat＠singtel.com 20 Jan '23

20 Jan '23

Hi Everyone, I am new here and hoping to get some advise on my issue that i'm encountering. I am setting up ovirt self hosting engine 4.5.4 and require proxy to access the internet. Below is the issue i encountered: [localhost -> 192.168.222.66]: FAILED! => {"changed": false, "msg": "Failed to download metadata for repo 'centos-ceph-pacific': Cannot prepare internal mirrorlist: Curl error (6): Couldn't resolve host name for http://mirrorlist.centos.org/?release=8-stream&arch=x86_64&repo=storage-cep… [Could not resolve host: mirrorlist.centos.org]", "rc": 1, "results": []} Hoping to gain some information to solve it. Thank you in advance!

2 1

Ovirt 4.4.10 AD Integration Error
by hemak88＠gmail.com 20 Jan '23

20 Jan '23

I am dong AD integration of the Ovirt 4.4 manager. The Insecure method with plain text password saved in /etc/ovirt-engine/aaa/uat.xxxx.com.properties works fine. I am using ovirt-engine-extension-aaa-ldap-setup utility However this is a hard coding method and insecure way. Hence I wanted to use starttls with PEM encoded certificate file. I obtained a root and intermediate CA from the Ad server and used with starttls I used below inputs for configuring AD auth with tool "ovirt-engine-extension-aaa-ldap-setup" Available LDAP implementations: 3 - Active Directory Please select: 3 Please enter Active Directory Forest name: uat.xxxx.com Please select protocol to use (startTLS, ldaps, plain) [startTLS]: startTLS Please select method to obtain PEM encoded CA certificate (File, URL, Inline, System, Insecure): file File path: /tmp/rootca.pem Enter search user DN (for example uid=username,dc=example,dc=com or leave empty for anonymous): myself(a)uat.xxxx.com Enter search user password: Are you going to use Single Sign-On for Virtual Machines (Yes, No) [Yes]: No Please specify profile name that will be visible to users [uat.xxxx.com] Please provide credentials to test login flow: Enter user name: myself(a)uat.xxxx.com Enter user password: But I am facing error. What could be the resolution WARNING: Error while connecting to 'adserver.uat.xxxx.com': LDAPException(resultCode=82 (local error), errorMessage='The connection reader was unable to successfully complete TLS negotiation: SSLHandshakeException(No trusted certificate found), ldapSDKVersion=4.0.14, revision=c0fb784eebf9d36a67c736d0428fb3577f2e25bb') I did verify the root and intemediate certificate: # openssl verify -verbose -CAfile uatrootca.pem uatca.pem uatca.pem: OK 1. What could be the reason for "No trusted certificate found" error? 2. Will this method also save the username and password of AD user as plain text in the file /etc/ovirt-engine/aaa/uat.xxxx.com.properties

2 1

oVirt + TrueNAS: Unable to create iSCSI domain - I am missing something obvious
by David Johnson 20 Jan '23

20 Jan '23

Good morning folks, and thank you in advance. I am working on migrating my oVirt backing store from NFS to iSCSI. *oVirt Environment:* oVirt Open Virtualization Manager Software Version:4.4.4.7-1.el8 *TrueNAS environment:* FreeBSD truenas.local 12.2-RELEASE-p11 75566f060d4(HEAD) TRUENAS amd64 The iSCSI share is on a TrueNAS server, exposed to user VDSM and group 36. oVirt sees the targeted share, but is unable to make use of it. The latest issue is "Error while executing action New SAN Storage Domain: Volume Group block size error, please check your Volume Group configuration, Supported block size is 512 bytes." As near as I can tell, oVirt does not support any block size other than 512 bytes, while TrueNAS's smallest OOB block size is 4k. I know that oVirt on TrueNAS is a common configuration, so I expect I am missing something really obvious here, probably a TrueNAS configuration needed to make TrueNAS work with 512 byte blocks. Any advice would be helpful. *David Johnson*

5 9

After Upgrade OVirt 4.4.9 > Version 4.4.10.7-1.el8 VM Kernel Crashes after migration
by Ralf Schenk 19 Jan '23

19 Jan '23

Dear List, we upgraded our OVirt 4.4.9 Infrastructure (engine and hosts) to latest available 4.4.10.x. Engine shows "4.4.10.7-1.el8" on Login Page Hosts are based on ovirt-node-ng (nodectl info outputs ovirt-node-ng-4.4.10.2-0.20220303.0) When we migrate VM's we see VM's dying short after migration with below errors also printed to console. We are only able to shutdown these VM's (PowerOff) and start them up again. Mostly they are started again on the Host that was target of migration and they run without issues then. All Servers are EPYC based, but different CPU Versions. All hosts are in a single "Cluster", CPU Type is "Secure AMD EPYC". With 4.4.8 and 4.4.9 we had no problems migrating VM's between hosts. Cluster is: 2 Hosts: AMD EPYC 7401P 24-Core Processor 1 Hosts: AMD EPYC 7402P 24-Core Processor 7 Hosts: AMD EPYC 7502P 32-Core Processor What can we do ? As said, we didn't see such problems for 1 year running 4.4.8.x and 4.4.9.x. Syslog showing crash and date/clock error or sudden offset: Jan 19 19:23:22 myvmXX kernel: [163933.218848] rcu: INFO: rcu_sched self-detected stall on CPU Jan 19 19:23:22 myvmXX kernel: [163933.218876] rcu: 1-...!: (8 GPs behind) idle=78a/0/0x1 softirq=4456350/4456351 fqs=0 Jan 19 19:23:22 myvmXX kernel: [163933.218901] (t=537752 jiffies g=9505317 q=22) Jan 19 19:23:22 myvmXX kernel: [163933.218903] rcu: rcu_sched kthread starved for 537752 jiffies! g9505317 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402 ->cpu=0 Jan 19 19:23:22 myvmXX kernel: [163933.218932] rcu: RCU grace-period kthread stack dump: Jan 19 19:23:22 myvmXX kernel: [163933.218949] rcu_sched I 0 10 2 0x80004000 Jan 19 19:23:22 myvmXX kernel: [163933.218951] Call Trace: Jan 19 19:23:22 myvmXX kernel: [163933.218957] __schedule+0x2e3/0x740 Jan 19 19:23:22 myvmXX kernel: [163933.218960] schedule+0x42/0xb0 Jan 19 19:23:22 myvmXX kernel: [163933.218961] schedule_timeout+0x8a/0x160 Jan 19 19:23:22 myvmXX kernel: [163933.218964] ? rcu_accelerate_cbs+0x28/0x190 Jan 19 19:23:22 myvmXX kernel: [163933.218967] ? __next_timer_interrupt+0xe0/0xe0 Jan 19 19:23:22 myvmXX kernel: [163933.218969] rcu_gp_kthread+0x48d/0x9a0 Jan 19 19:23:22 myvmXX kernel: [163933.218971] kthread+0x104/0x140 Jan 19 19:23:22 myvmXX kernel: [163933.218972] ? kfree_call_rcu+0x20/0x20 Jan 19 19:23:22 myvmXX kernel: [163933.218974] ? kthread_park+0x90/0x90 Jan 19 19:23:22 myvmXX kernel: [163933.218975] ret_from_fork+0x35/0x40 Jan 19 19:23:22 myvmXX kernel: [163933.218982] Sending NMI from CPU 1 to CPUs 0: Jan 19 19:23:22 myvmXX kernel: [163933.219978] NMI backtrace for cpu 0 Jan 19 19:23:22 myvmXX kernel: [163933.219978] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.4.0-137-generic #154-Ubuntu Jan 19 19:23:22 myvmXX kernel: [163933.219979] Hardware name: oVirt RHEL, BIOS 1.15.0-1.module_el8.6.0+1087+b42c8331 04/01/2014 Jan 19 19:23:22 myvmXX kernel: [163933.219979] RIP: 0010:timekeeping_advance+0x12f/0x5a0 Jan 19 19:23:22 myvmXX kernel: [163933.219980] Code: 00 48 8b 35 e3 a0 ec 01 bb 00 ca 9a 3b 49 29 c7 48 01 05 04 a0 ec 01 48 01 05 35 a0 ec 01 48 89 f2 48 d3 e2 8b 0d fd 9f ec 01 <48> 03 15 fa 9f ec 01 48 89 15 f3 9f ec 01 48 d3 e3 48 39 da 72 57 Jan 19 19:23:22 myvmXX kernel: [163933.219981] RSP: 0018:ffffb5a580003e40 EFLAGS: 00000016 Jan 19 19:23:22 myvmXX kernel: [163933.219981] RAX: 000000007a120000 RBX: 000000003b9aca00 RCX: 0000000000000017 Jan 19 19:23:22 myvmXX kernel: [163933.219982] RDX: 003d091a39de0000 RSI: 00001e848d1cef00 RDI: 00000000003d0900 Jan 19 19:23:22 myvmXX kernel: [163933.219982] RBP: ffffb5a580003e98 R08: 0000000000000000 R09: 666657f4d876bbc2 Jan 19 19:23:22 myvmXX kernel: [163933.219983] R10: ffff8d1ee8119618 R11: ffff8d1effa2ffb8 R12: 0000000000000000 Jan 19 19:23:22 myvmXX kernel: [163933.219983] R13: 0000000000000000 R14: 0000000000000009 R15: 6666232f185ebbc2 Jan 19 19:23:22 myvmXX kernel: [163933.219984] FS: 0000000000000000(0000) GS:ffff8d1effa00000(0000) knlGS:0000000000000000 Jan 19 19:23:22 myvmXX kernel: [163933.219984] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jan 19 19:23:22 myvmXX kernel: [163933.219984] CR2: 000055a093634da0 CR3: 00000001280d6000 CR4: 00000000003406f0 Jan 19 19:23:22 myvmXX kernel: [163933.219985] Call Trace: Jan 19 19:23:22 myvmXX kernel: [163933.219985] <IRQ> Jan 19 19:23:22 myvmXX kernel: [163933.219985] ? ttwu_do_activate+0x5b/0x70 Jan 19 19:23:22 myvmXX kernel: [163933.219985] update_wall_time+0x10/0x20 Jan 19 19:23:22 myvmXX kernel: [163933.219986] tick_do_update_jiffies64.part.0+0x88/0xd0 Jan 19 19:23:22 myvmXX kernel: [163933.219986] tick_sched_do_timer+0x58/0x60 Jan 19 19:23:22 myvmXX kernel: [163933.219986] tick_sched_timer+0x2d/0x80 Jan 19 19:23:22 myvmXX kernel: [163933.219987] __hrtimer_run_queues+0xf7/0x270 Jan 19 19:23:22 myvmXX kernel: [163933.219987] ? tick_sched_do_timer+0x60/0x60 Jan 19 19:23:22 myvmXX kernel: [163933.219987] hrtimer_interrupt+0x109/0x220 Jan 19 19:23:22 myvmXX kernel: [163933.219988] smp_apic_timer_interrupt+0x71/0x140 Jan 19 19:23:22 myvmXX kernel: [163933.219988] apic_timer_interrupt+0xf/0x20 Jan 19 19:23:22 myvmXX kernel: [163933.219988] </IRQ> Jan 19 19:23:22 myvmXX kernel: [163933.219988] RIP: 0010:native_safe_halt+0xe/0x10 Jan 19 19:23:22 myvmXX kernel: [163933.219989] Code: 7b ff ff ff eb bd 90 90 90 90 90 90 e9 07 00 00 00 0f 00 2d d6 39 51 00 f4 c3 66 90 e9 07 00 00 00 0f 00 2d c6 39 51 00 fb f4 <c3> 90 0f 1f 44 00 00 55 48 89 e5 41 55 41 54 53 e8 9d 5e 62 ff 65 Jan 19 19:23:22 myvmXX kernel: [163933.219990] RSP: 0018:ffffffff8be03e18 EFLAGS: 00000246 ORIG_RAX: ffffffffffffff13 Jan 19 19:23:22 myvmXX kernel: [163933.219990] RAX: ffffffff8aef7a20 RBX: 0000000000000000 RCX: 0000000000000001 Jan 19 19:23:22 myvmXX kernel: [163933.219991] RDX: 000000000bc48666 RSI: ffffffff8be03dd8 RDI: 00009519477dc7a5 Jan 19 19:23:22 myvmXX kernel: [163933.219991] RBP: ffffffff8be03e38 R08: 0000000000000001 R09: 0000000000000002 Jan 19 19:23:22 myvmXX kernel: [163933.219992] R10: 0000000000000000 R11: 0000000000000001 R12: 0000000000000000 Jan 19 19:23:22 myvmXX kernel: [163933.219992] R13: ffffffff8be13780 R14: 0000000000000000 R15: 0000000000000000 Jan 19 19:23:22 myvmXX kernel: [163933.219992] ? __cpuidle_text_start+0x8/0x8 Jan 19 19:23:22 myvmXX kernel: [163933.219993] ? tick_nohz_idle_stop_tick+0x164/0x290 Jan 19 19:23:22 myvmXX kernel: [163933.219993] ? default_idle+0x20/0x140 Jan 19 19:23:22 myvmXX kernel: [163933.219993] arch_cpu_idle+0x15/0x20 Jan 19 19:23:22 myvmXX kernel: [163933.219994] default_idle_call+0x23/0x30 Jan 19 19:23:22 myvmXX kernel: [163933.219994] do_idle+0x1fb/0x270 Jan 19 19:23:22 myvmXX kernel: [163933.219994] cpu_startup_entry+0x20/0x30 Jan 19 19:23:22 myvmXX kernel: [163933.219994] rest_init+0xae/0xb0 Jan 19 19:23:22 myvmXX kernel: [163933.219995] arch_call_rest_init+0xe/0x1b Jan 19 19:23:22 myvmXX kernel: [163933.219995] start_kernel+0x52f/0x550 Jan 19 19:23:22 myvmXX kernel: [163933.219995] x86_64_start_reservations+0x24/0x26 Jan 19 19:23:22 myvmXX kernel: [163933.219996] x86_64_start_kernel+0x8f/0x93 Jan 19 19:23:22 myvmXX kernel: [163933.219996] secondary_startup_64+0xa4/0xb0 Jan 19 19:23:22 myvmXX kernel: [163933.220000] NMI backtrace for cpu 1 Jan 19 19:23:22 myvmXX kernel: [163933.220002] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 5.4.0-137-generic #154-Ubuntu Jan 19 19:23:22 myvmXX kernel: [163933.220003] Hardware name: oVirt RHEL, BIOS 1.15.0-1.module_el8.6.0+1087+b42c8331 04/01/2014 Jan 19 19:23:22 myvmXX kernel: [163933.220003] Call Trace: Jan 19 19:23:22 myvmXX kernel: [163933.220004] <IRQ> Jan 19 19:23:22 myvmXX kernel: [163933.220006] dump_stack+0x6d/0x8b Jan 19 19:23:22 myvmXX kernel: [163933.220008] ? lapic_can_unplug_cpu+0x80/0x80 Jan 19 19:23:22 myvmXX kernel: [163933.220010] nmi_cpu_backtrace.cold+0x14/0x53 Jan 19 19:23:22 myvmXX kernel: [163933.220013] nmi_trigger_cpumask_backtrace+0xe8/0xf0 Jan 19 19:23:22 myvmXX kernel: [163933.220015] arch_trigger_cpumask_backtrace+0x19/0x20 Jan 19 19:23:22 myvmXX kernel: [163933.220016] rcu_dump_cpu_stacks+0x99/0xcb Jan 19 19:23:22 myvmXX kernel: [163933.220018] rcu_sched_clock_irq.cold+0x1b0/0x39c Jan 19 19:23:22 myvmXX kernel: [163933.220020] update_process_times+0x2c/0x60 Jan 19 19:23:22 myvmXX kernel: [163933.220021] tick_sched_handle+0x29/0x60 Jan 19 19:23:22 myvmXX kernel: [163933.220022] tick_sched_timer+0x3d/0x80 Jan 19 19:23:22 myvmXX kernel: [163933.220024] __hrtimer_run_queues+0xf7/0x270 Jan 19 19:23:22 myvmXX kernel: [163933.220026] ? tick_sched_do_timer+0x60/0x60 Jan 19 19:23:22 myvmXX kernel: [163933.220027] hrtimer_interrupt+0x109/0x220 Jan 19 19:23:22 myvmXX kernel: [163933.220029] smp_apic_timer_interrupt+0x71/0x140 Jan 19 19:23:22 myvmXX kernel: [163933.220030] apic_timer_interrupt+0xf/0x20 Jan 19 19:23:22 myvmXX kernel: [163933.220031] </IRQ> Jan 19 19:23:22 myvmXX kernel: [163933.220033] RIP: 0010:native_safe_halt+0xe/0x10 Jan 19 19:23:22 myvmXX kernel: [163933.220035] Code: 7b ff ff ff eb bd 90 90 90 90 90 90 e9 07 00 00 00 0f 00 2d d6 39 51 00 f4 c3 66 90 e9 07 00 00 00 0f 00 2d c6 39 51 00 fb f4 <c3> 90 0f 1f 44 00 00 55 48 89 e5 41 55 41 54 53 e8 9d 5e 62 ff 65 Jan 19 19:23:22 myvmXX kernel: [163933.220036] RSP: 0018:ffffb5a58007be70 EFLAGS: 00000246 ORIG_RAX: ffffffffffffff13 Jan 19 19:23:22 myvmXX kernel: [163933.220037] RAX: ffffffff8aef7a20 RBX: 0000000000000001 RCX: 0000000000000001 Jan 19 19:23:22 myvmXX kernel: [163933.220038] RDX: 000000000d1b7786 RSI: ffffb5a58007be30 RDI: 000095194740bea5 Jan 19 19:23:22 myvmXX kernel: [163933.220039] RBP: ffffb5a58007be90 R08: 0000000000000001 R09: 0000000000000000 Jan 19 19:23:22 myvmXX kernel: [163933.220040] R10: ffff8d1effa5c848 R11: 0000000000000000 R12: 0000000000000001 Jan 19 19:23:22 myvmXX kernel: [163933.220040] R13: ffff8d1eff25af00 R14: 0000000000000000 R15: 0000000000000000 Jan 19 19:23:22 myvmXX kernel: [163933.220042] ? __cpuidle_text_start+0x8/0x8 Jan 19 19:23:22 myvmXX kernel: [163933.220044] ? default_idle+0x20/0x140 Jan 19 19:23:22 myvmXX kernel: [163933.220046] arch_cpu_idle+0x15/0x20 Jan 19 19:23:22 myvmXX kernel: [163933.220047] default_idle_call+0x23/0x30 Jan 19 19:23:22 myvmXX kernel: [163933.220049] do_idle+0x1fb/0x270 Jan 19 19:23:22 myvmXX kernel: [163933.220051] cpu_startup_entry+0x20/0x30 Jan 19 19:23:22 myvmXX kernel: [163933.220053] start_secondary+0x167/0x1c0 Jan 19 19:23:22 myvmXX kernel: [163933.220054] secondary_startup_64+0xa4/0xb0 Jan 19 19:24:34 myvmXX systemd[1]: systemd-udevd.service: Watchdog timeout (limit 3min)! Jan 19 19:24:34 myvmXX systemd[1]: systemd-udevd.service: Killing process 421 (systemd-udevd) with signal SIGABRT. Nov 15 18:38:49 myvmXX kernel: [164024.594313] rcu: INFO: rcu_sched self-detected stall on CPU Nov 15 18:38:49 myvmXX kernel: [164024.594352] rcu: 0-...!: (2 ticks this GP) idle=66a/0/0x1 softirq=4017386/4017386 fqs=0 Nov 15 18:38:49 myvmXX kernel: [164024.594380] (t=1844682531753 jiffies g=9505317 q=675) Nov 15 18:38:49 myvmXX kernel: [164024.594382] rcu: rcu_sched kthread starved for 1844682531753 jiffies! g9505317 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x200 ->cpu=0 Nov 15 18:38:49 myvmXX kernel: [164024.594413] rcu: RCU grace-period kthread stack dump: Nov 15 18:38:49 myvmXX kernel: [164024.594432] rcu_sched R 0 10 2 0x80004000 Nov 15 18:38:49 myvmXX kernel: [164024.594435] Call Trace: Nov 15 18:38:49 myvmXX kernel: [164024.594445] __schedule+0x2e3/0x740 Nov 15 18:38:49 myvmXX kernel: [164024.594447] schedule+0x42/0xb0 Nov 15 18:38:49 myvmXX kernel: [164024.594449] schedule_timeout+0x8a/0x160 Nov 15 18:38:49 myvmXX kernel: [164024.594453] ? rcu_accelerate_cbs+0x28/0x190 Nov 15 18:38:49 myvmXX kernel: [164024.594456] ? __next_timer_interrupt+0xe0/0xe0 Nov 15 18:38:49 myvmXX kernel: [164024.594458] rcu_gp_kthread+0x48d/0x9a0 Nov 15 18:38:49 myvmXX kernel: [164024.594460] kthread+0x104/0x140 Nov 15 18:38:49 myvmXX kernel: [164024.594462] ? kfree_call_rcu+0x20/0x20 Nov 15 18:38:49 myvmXX kernel: [164024.594463] ? kthread_park+0x90/0x90 Nov 15 18:38:49 myvmXX kernel: [164024.594464] ret_from_fork+0x35/0x40 Nov 15 18:38:49 myvmXX kernel: [164024.594467] NMI backtrace for cpu 0 Nov 15 18:38:49 myvmXX kernel: [164024.594470] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.4.0-137-generic #154-Ubuntu Nov 15 18:38:49 myvmXX kernel: [164024.594471] Hardware name: oVirt RHEL, BIOS 1.15.0-1.module_el8.6.0+1087+b42c8331 04/01/2014 Nov 15 18:38:49 myvmXX kernel: [164024.594472] Call Trace: Nov 15 18:38:49 myvmXX kernel: [164024.594473] <IRQ> Nov 15 18:38:49 myvmXX kernel: [164024.594476] dump_stack+0x6d/0x8b Nov 15 18:38:49 myvmXX kernel: [164024.594479] ? lapic_can_unplug_cpu+0x80/0x80 Nov 15 18:38:49 myvmXX kernel: [164024.594480] nmi_cpu_backtrace.cold+0x14/0x53 Nov 15 18:38:49 myvmXX kernel: [164024.594484] nmi_trigger_cpumask_backtrace+0xe8/0xf0 Nov 15 18:38:49 myvmXX kernel: [164024.594485] arch_trigger_cpumask_backtrace+0x19/0x20 Nov 15 18:38:49 myvmXX kernel: [164024.594488] rcu_dump_cpu_stacks+0x99/0xcb Nov 15 18:38:49 myvmXX kernel: [164024.594489] rcu_sched_clock_irq.cold+0x1b0/0x39c Nov 15 18:38:49 myvmXX kernel: [164024.594491] update_process_times+0x2c/0x60 Nov 15 18:38:49 myvmXX kernel: [164024.594494] tick_sched_handle+0x29/0x60 Nov 15 18:38:49 myvmXX kernel: [164024.594495] tick_sched_timer+0x3d/0x80 Nov 15 18:38:49 myvmXX kernel: [164024.594497] __hrtimer_run_queues+0xf7/0x270 Nov 15 18:38:49 myvmXX kernel: [164024.594498] ? tick_sched_do_timer+0x60/0x60 Nov 15 18:38:49 myvmXX kernel: [164024.594500] hrtimer_interrupt+0x109/0x220 Nov 15 18:38:49 myvmXX kernel: [164024.594503] smp_apic_timer_interrupt+0x71/0x140 Nov 15 18:38:49 myvmXX kernel: [164024.594504] apic_timer_interrupt+0xf/0x20 Nov 15 18:38:49 myvmXX kernel: [164024.594505] </IRQ> Nov 15 18:38:49 myvmXX kernel: [164024.594507] RIP: 0010:native_safe_halt+0xe/0x10 Nov 15 18:38:49 myvmXX kernel: [164024.594510] Code: 7b ff ff ff eb bd 90 90 90 90 90 90 e9 07 00 00 00 0f 00 2d d6 39 51 00 f4 c3 66 90 e9 07 00 00 00 0f 00 2d c6 39 51 00 fb f4 <c3> 90 0f 1f 44 00 00 55 48 89 e5 41 55 41 54 53 e8 9d 5e 62 ff 65 Nov 15 18:38:49 myvmXX kernel: [164024.594511] RSP: 0018:ffffffff8be03e18 EFLAGS: 00000246 ORIG_RAX: ffffffffffffff13 Nov 15 18:38:49 myvmXX kernel: [164024.594513] RAX: ffffffff8aef7a20 RBX: 0000000000000000 RCX: 0000000000000001 Nov 15 18:38:49 myvmXX kernel: [164024.594513] RDX: 000000000bc48666 RSI: ffffffff8be03dd8 RDI: 00009519477dc7a5 Nov 15 18:38:49 myvmXX kernel: [164024.594514] RBP: ffffffff8be03e38 R08: 0000000000000001 R09: 0000000000000002 Nov 15 18:38:49 myvmXX kernel: [164024.594515] R10: 0000000000000000 R11: 0000000000000001 R12: 0000000000000000 Nov 15 18:38:49 myvmXX kernel: [164024.594515] R13: ffffffff8be13780 R14: 0000000000000000 R15: 0000000000000000 Nov 15 18:38:49 myvmXX kernel: [164024.594517] ? __cpuidle_text_start+0x8/0x8 Nov 15 18:38:49 myvmXX kernel: [164024.594519] ? tick_nohz_idle_stop_tick+0x164/0x290 Nov 15 18:38:49 myvmXX kernel: [164024.594521] ? default_idle+0x20/0x140 Nov 15 18:38:49 myvmXX kernel: [164024.594524] arch_cpu_idle+0x15/0x20 Nov 15 18:38:49 myvmXX kernel: [164024.594525] default_idle_call+0x23/0x30 Nov 15 18:38:49 myvmXX kernel: [164024.594528] do_idle+0x1fb/0x270 Nov 15 18:38:49 myvmXX kernel: [164024.594530] cpu_startup_entry+0x20/0x30 Nov 15 18:38:49 myvmXX kernel: [164024.594532] rest_init+0xae/0xb0 Nov 15 18:38:49 myvmXX kernel: [164024.594536] arch_call_rest_init+0xe/0x1b Nov 15 18:38:49 myvmXX kernel: [164024.594537] start_kernel+0x52f/0x550 Nov 15 18:38:49 myvmXX kernel: [164024.594539] x86_64_start_reservations+0x24/0x26 Nov 15 18:38:49 myvmXX kernel: [164024.594541] x86_64_start_kernel+0x8f/0x93 Nov 15 18:38:49 myvmXX kernel: [164024.594544] secondary_startup_64+0xa4/0xb0 ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@Jan 19 19:28:51 myvmXX systemd-sysctl[413]: Not setting net/ipv4/conf/all/promote_secondaries (explicit setting exists). -- Databay AG Logo *Ralf Schenk * fon: +49 2405 40837-0 mail: rs(a)databay.de web: www.databay.de <https://www.databay.de> Databay AG Jens-Otto-Krag-Str. 11 52146 Würselen Sitz/Amtsgericht Aachen • HRB: 8437 • USt-IdNr.: DE 210844202 Vorstand: Ralf Schenk, Dipl.-Ing. Jens Conze, Aresch Yavari, Dipl.-Kfm. Philipp Hermanns Aufsichtsratsvorsitzender: Dr. Jan Scholzen Datenschutzhinweise für Kunden: Hier nachlesen <https://www.databay.de/datenschutzhinweise-fuer-kunden>

1 0

unsynced after remove brick
by Dominique D 19 Jan '23

19 Jan '23

Hello, Yesterday I had to remove the brick of my first server (HCI with 3 servers) for maintenance and recover hard disks. 3 servers with 4 disks per server in raid5. 1 brick per server i did : gluster volume remove-brick data replica 2 ovnode1s.telecom.lan:/gluster_bricks/datassd/datassd force After deleting the brick, I had 8 unsynced entries present and this morning I have 6. What should I do to resolve my unsynced ? [root@ovnode2 ~]# gluster volume status Status of volume: datassd Gluster process TCP Port RDMA Port Online Pid ------------------------------------------------------------------------------ Brick ovnode2s.telecom.lan:/gluster_bricks/ datassd/datassd 49152 0 Y 2431 Brick ovnode3s.telecom.lan:/gluster_bricks/ datassd/datassd 49152 0 Y 2379 Self-heal Daemon on localhost N/A N/A Y 2442 Self-heal Daemon on ovnode3s.telecom.lan N/A N/A Y 2390 Task Status of Volume datassd ------------------------------------------------------------------------------ [root@ovnode2 ~]# gluster volume heal datassd info Brick ovnode2s.telecom.lan:/gluster_bricks/datassd/datassd /.shard/8d397a25-66d0-4f51-9358-5e1f70048103.18 /.shard/8d397a25-66d0-4f51-9358-5e1f70048103.7 /.shard/8d397a25-66d0-4f51-9358-5e1f70048103.150 /.shard/8d397a25-66d0-4f51-9358-5e1f70048103.241 /.shard/21907c8f-abe2-4501-b597-d1c2f9a0fa92.18 /.shard/8d397a25-66d0-4f51-9358-5e1f70048103.155 Status: Connected Number of entries: 6 Brick ovnode3s.telecom.lan:/gluster_bricks/datassd/datassd /.shard/8d397a25-66d0-4f51-9358-5e1f70048103.18 /.shard/8d397a25-66d0-4f51-9358-5e1f70048103.7 /.shard/8d397a25-66d0-4f51-9358-5e1f70048103.150 /.shard/8d397a25-66d0-4f51-9358-5e1f70048103.241 /.shard/21907c8f-abe2-4501-b597-d1c2f9a0fa92.18 /.shard/8d397a25-66d0-4f51-9358-5e1f70048103.155 Status: Connected Number of entries: 6 Thank you

2 1

Ovirt 4.4.10 running on RHEL 8.7
by James Wadsworth 19 Jan '23

19 Jan '23

Hi there, we currently have ovirt 4.4.9 running on RHEL 8.5. Can we upgrade the cluster to ovirt 4.4.10 on RHEL 8.7? Do we need to following these steps in this link? https://www.ovirt.org/download/install_on_rhel.html Many thanks, James

2 2

4.5.4 Hosted-Engine: change hosted-engine storage
by Diego Ercolani 19 Jan '23

19 Jan '23

ovirt-engine-appliance-4.5-20221206133948 Hello, I have some trouble with my Gluster instance where there is hosted-engine. I would like to copy data from that hosted engine and reverse to another hosted-engine storage (I will try NFS). I think the main method is to put ovirt in global-management mode, stop the hosted-engine instance, unmount the hosted-engine storage systemctl stop {vdsmd;supervdsmd;ovirt-ha-broker;ovirt-ha-agent}; hosted-engine --disconnect-storage umount /rhev/data-center/mnt/glusterSD/localhost:_glen/ and then redeploy the hosted engine with the current backup: method 1: [doesn't work; it fail the ansible script after the pause] ovirt-hosted-engine-setup --4 --config-append=/var/lib/ovirt-hosted-engine-setup/answers/answers-20230116184834.conf --restore-from-file=230116-backup.tar.gz --ansible-extra-vars=he_pause_before_engine_setup=true but it doesn't work method 2: [I cannot find the glitch] I saw in every node there is a configuration under /etc/ovirt-hosted-engine/hosted-engine.conf where there are some interessant entry: vm_disk_id=0a1a501c-fc45-430f-bfd3-076172cec406 vm_disk_vol_id=f65dab86-67f1-46fa-87c0-f9076f479741 storage=localhost:/glen domainType=glusterfs metadata_volume_UUID=4e64e155-ee11-4fdc-b9a0-a7cbee5e4181 metadata_image_UUID=20234090-ea40-4614-ae95-8f91b339ba3e lockspace_volume_UUID=6a975f46-4126-4c2a-b444-6e5a34872cf6 lockspace_image_UUID=893a1fc1-9a1d-44fc-a02f-8fdac19afc18 conf_volume_UUID=206e505f-1bb8-4cc4-abd9-942654c47612 conf_image_UUID=9871a483-8e7b-4f52-bf71-a6a8adc2309b so, the conf_volume under conf_image dir is a TAR archive: /rhev/data-center/mnt/glusterSD/localhost:_glen/3577c21e-f757-4405-97d1-0f827c9b4e22/images/9871a483-8e7b-4f52-bf71-a6a8adc2309b/206e505f-1bb8-4cc4-abd9-942654c47612: POSIX tar archive (GNU) That I think is the common configuration. I copied the structure (from 3577c21e-f757-4405-97d1-0f827c9b4e22 directory) in the new storage (nfs), changed the entries under local configuration and "shared configuration": from storage=localhost:/glen to storage=<server>:/directory (writable by vdsm user and kvm group) from domainType=glusterfs to domainType=nfs and issued: 1. hosted-engine --connect-storage <- work 2. hosted-engine --vm-start <- doesn't work because there is a complain about the not-starting ovirt-ha-agent What can I do? Is there any documentation somewhere? Diego

2 5

Bug in the engine-backup script when no attached TTY -- Easy fix
by eshwayri＠gmail.com 18 Jan '23

18 Jan '23

The output() function. This line: printf "%s\n" "${m}" It will fail if there is no attached TTY, which will set the exit code to 1, which in turn will trigger the cleanup() function notifying the engine that the backup failed. This ironically happens when it should be writing "Done." and exiting after a successful backup. Fix I used was to change it to: printf "%s\n" "${m}" >> "${LOG}" You can't assume attached TTY since a lot of people like me want to run this as part of a pre/post script to an automated backup program.

2 3

Hosted Engine No Longer Has IP Address - Help!
by Matthew J Black 17 Jan '23

17 Jan '23

Hi Guys, I've gone and shot myself in the foot - and I'm looking for some first-aid. I've managed to remove the IP Address of the oVirt Self-Hosted Engine and so have lost contact with it (don't ask how - let's just say I f*cked-up). I *think* its still running, I've got it set to DHCP, and I've got access to the Host its running on, so my question(s) is: - (The preferred method) How can I re-establish (console?) contact - I'm thinking via the Host Server and some kvm-commands, so I can issue a `dhclient` command - (The most drastic) How can I get it to reboot ie is there a command / command sequence to do this Any help would be appreciated. Cheers Dulux-Oz

2 2

update path from 4.4.4 to 4.5.4
by marek 16 Jan '23

16 Jan '23

hi, i have standalone ovirt-engine 4.4.4 (centos8 stream) few hosts (mix of old centos 8.2, centos 8 stream, rocky linux) can you confirm if this upgrade path is ok? first round - update engine to 4.4.10 - update OS on engine to last centos 8 stream (can i upgrade to some point in time recommended for 4.4.10?) - update hosts to ovirt 4.4.10 - update OS on hosts to last centos 8 stream and rocky linux 8.6 special case in first round - centos 8.2 - migrate OS on hosts from centos 8.2 to rocky linux 8.6 - update hosts to ovirt 4.4.10 second round - update engine to 4.5.4 - update hosts to ovirt 4.5.4 - update OS on hosts - centos 8 stream - is ALREADY on last update from first round - update OS on hosts - rocky linux - from 8.6 to 8.7 Marek

1 1

Preferred way to give customer access to VMs
by hanisirfan.work＠gmail.com 16 Jan '23

16 Jan '23

Hi. Just for an introduction, I'm a junior staff working on a way to deploy a KVM cluster to provision VMs to our customer. Before this, we're using VMware ESXi and connect it to OpenNebula as the console that we give to customers. We're moving to KVM due to VMware licensing cost. I've successfully deployed an oVirt cluster and currently able to access it remotely via a VPN that I've setup on a virtualized pfSense VM inside the cluster. My question is, what is the best way to give customer console access to the VMs that we provisioned for them? Surely we doesn't want to give them access to our VPN for security reasons. I can't seems to find a way to connect OpenNebula with oVirt and I do believe it isn't possible since both are basically virtualization manager, managing the KVM instances. Thanks for the responses and ideas given ☺️

2 1

I would like to inquire about doing DR solutions Active-Passive.
by natchawi28＠gmail.com 16 Jan '23

16 Jan '23

I would like to try a lab to test the DR solution, and would like to know how to provision resources. So what is storage replicate? Is it hardware storage?

2 1

Failed to import the Hosted Engine Storage Domain
by Frank Wall 14 Jan '23

14 Jan '23

Hi, the following error message is periodically logged to engine.log when oVirt tries to import the Hosted Engine Storage Domain (NFS): Validation of action 'AddExistingFileStorageDomain' failed for user SYSTEM. Reasons: VAR__TYPE__STORAGE__DOMAIN,VAR__ACTION__ADD,ERROR_CANNOT_ADD_EXISTING_STORAGE_DOMAIN_CONNECTION_DATA_ILLEGAL I've redeployed my Engine VM while upgrading to oVirt 4.5. Unfortunately, the Engine VM and Hosted Engine Storage Domain are both missing from the oVirt GUI and oVirt is unable to import them apparently. (FWIW, there are several other Storage Domains already configured that work perfectly fine.) Is there any way to manually add the Hosted Engine Storage Domain? I'm also fine with adding the entry manually to the PostgreSQL database if this would be feasible. (Just point me to the right direction so I don't mess up my oVirt setup.) Below are some log messages and errors I've collected from vdsm.log and engine.log. vdsm.log 2023-01-06 21:15:10,803+0100 INFO (jsonrpc/0) [vdsm.api] FINISH getStorageDomainInfo return={'info': {'uuid': '49d7aab9-1e45-4ef0-9657-1247983f129e', 'type': 'NFS', 'class': 'Data', 'name': 'hosted_storage', 'role': 'Master', 'pool': ['c87a1ad0-8dcd-11ed-b48a-00163e352102'], 'version': '5', 'block_size': 512, 'alignment': 1048576, 'remotePath': '10.1.2.3:/mnt/vol2/vm/engine'}} from=::ffff:192.168.0.30,43146, flow_id=4ba364c1, task_id=43840eb6-8b9e-4637-bd0f-261a899d374e (api:37) engine.log 2023-01-06 21:16:28,042+01 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMGetStorageDomainInfoVDSCommand] (EE-ManagedThreadFactory-engine-Thread-1342) [] FINISH, HSMGetStorageDomainInfoVDSCommand, return: <StorageDomainStatic:{name='hosted_storage', id='49d7aab9-1e45-4ef0-9657-1247983f129e'}, c87a1ad0-8dcd-11ed-b48a-00163e352102>, log id: 5344c976 2023-01-06 21:16:28,046+01 INFO [org.ovirt.engine.core.bll.storage.domain.ImportHostedEngineStorageDomainCommand] (EE-ManagedThreadFactory-engine-Thread-1342) [1728fc85] Running command: ImportHostedEngineStorageDomainCommand internal: true. 2023-01-06 21:16:28,086+01 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMGetStorageDomainInfoVDSCommand] (EE-ManagedThreadFactory-engine-Thread-1342) [1d6e287c] START, HSMGetStorageDomainInfoVDSCommand(HostName = hv05.example.com, HSMGetStorageDomainInfoVDSCommandParameters:{hostId='4fa6fe39-9254-4264-8a57-4b0a29c645e7', storageDomainId='49d7aab9-1e45-4ef0-9657-1247983f129e'}), log id: 759c4a73 2023-01-06 21:16:28,095+01 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMGetStorageDomainInfoVDSCommand] (EE-ManagedThreadFactory-engine-Thread-1342) [1d6e287c] FINISH, HSMGetStorageDomainInfoVDSCommand, return: <StorageDomainStatic:{name='hosted_storage', id='49d7aab9-1e45-4ef0-9657-1247983f129e'}, c87a1ad0-8dcd-11ed-b48a-00163e352102>, log id: 759c4a73 2023-01-06 21:16:28,095+01 WARN [org.ovirt.engine.core.bll.storage.domain.AddExistingFileStorageDomainCommand] (EE-ManagedThreadFactory-engine-Thread-1342) [1d6e287c] Validation of action 'AddExistingFileStorageDomain' failed for user SYSTEM. Reasons: VAR__TYPE__STORAGE__DOMAIN,VAR__ACTION__ADD,ERROR_CANNOT_ADD_EXISTING_STORAGE_DOMAIN_CONNECTION_DATA_ILLEGAL 2023-01-06 21:16:28,096+01 INFO [org.ovirt.engine.core.bll.storage.domain.AddExistingFileStorageDomainCommand] (EE-ManagedThreadFactory-engine-Thread-1342) [1d6e287c] Lock freed to object 'EngineLock:{exclusiveLocks='[49d7aab9-1e45-4ef0-9657-1247983f129e=STORAGE]', sharedLocks=''}' 2023-01-06 21:16:28,097+01 INFO [org.ovirt.engine.core.bll.CommandCompensator] (EE-ManagedThreadFactory-engine-Thread-1342) [1d6e287c] Command [id=b0a331fe-5ad5-40b0-b7ce-2d01d0276e4b]: Compensating DELETED_OR_UPDATED_ENTITY of org.ovirt.engine.core.common.businessentities.StorageServerConnections; snapshot: id=c346dafe-09db-4058-ae1c-9b609911a1af. 2023-01-06 21:16:28,100+01 ERROR [org.ovirt.engine.core.bll.storage.domain.ImportHostedEngineStorageDomainCommand] (EE-ManagedThreadFactory-engine-Thread-1342) [1d6e287c] Transaction rolled-back for command 'org.ovirt.engine.core.bll.storage.domain.ImportHostedEngineStorageDomainCommand'. The (new) Engine VM is running on CentOS Stream 8 (using the Engine Appliance from the rpm) and all oVirt nodes/hosts are running on CentOS Stream 9. Ciao - Frank

1 3

Re: aggregate multiple hosts
by Nathanaël Blanchet 13 Jan '23

13 Jan '23

Le 13/01/2023 à 10:57, Csókási István Lehel a écrit : > > I want to increase the performance of a virtual machine by connecting > 6 nodes. Windows 10 runs on the virtual machine, the nodes are HP > Compaq 7900 PCs with Intel E8400 3 GHz Dual core processor, Q45 > chipset, 4Gb RAM > > Thank you > If you want to aggregate hardware capabilities to an unique VM, i.e. vcpu from multiple hosts or RAM aggragation, I don't think it is possible, but I may be wrong... some other members of the community may confirm. > > > 2023. 01. 13. 10:18 keltezéssel, Nathanaël Blanchet írta: >> You should precise your intention to do so. >> Thank you >> >> Le 13 janv. 2023 08:52, csokasi.lehel(a)gmail.com a écrit : >> I would like to ask if it is possible to aggregate multiple hosts to >> a single virtual machine. >> _______________________________________________ >> Users mailing list -- users(a)ovirt.org >> To unsubscribe send an email to users-leave(a)ovirt.org >> Privacy Statement: https://www.ovirt.org/privacy-policy.html >> oVirt Code of Conduct: >> https://www.ovirt.org/community/about/community-guidelines/ >> List Archives: >> https://lists.ovirt.org/archives/list/users@ovirt.org/message/665K3Y7QSINUF…

2 1

interface http stuck
by remy.ressegaire＠unige.ch 13 Jan '23

13 Jan '23

Hello, When browsing our ovirtadmin web interface it never loads the resource. We are using a third party certificate authority (following this procedure https://myhomelab.gr/linux/2020/01/20/replacing_ovirt_ssl.html) but not sure this leads to the error we have. In the http logs I see : ssl_error_log : [proxy_ajp:error] [pid 23754] [client 10.25.64.40:57838] AH00992: ajp_read_header: ajp_ilink_receive failed [proxy_ajp:error] [pid 23754] (120006)APR does not understand this error code: [client 10.25.64.40:57838] AH00878: read response failed from 127.0.0.1:8702 (127.0.0.1) error.log : [proxy:error] [pid 20752] (111)Connection refused: AH00957: AJP: attempt to connect to 127.0.0.1:8702 (127.0.0.1) failed [proxy:error] [pid 20752] AH00959: ap_proxy_connect_backend disabling worker for (127.0.0.1) for 5s [proxy_ajp:error] [pid 20752] [client 10.25.64.44:50000] AH00896: failed to make connection to backend: 127.0.0.1 Any help will be welcomed. Thanks, Remo

1 0

Sparsifying VM disk not working
by andreas_nikiforou＠hotmail.com 13 Jan '23

13 Jan '23

Hello, i cannot get sparsifying to work in lastest oVirt 4.5.4 release (not that i have tried with a previous release) I have two Data domains connected to oVirt using iSCSI & NFS. I created 2 testvm's and 50GB thin provisioned qcow2 disks for each, made some temp files, remove them and tried to sparsify, but it does not work. Error i am getting is: Error while executing action: Cannot sparsify Virtual Disk. Sparsifying is not supported for QCOW2 disk testvm1_Disk1. In virtual disk options i have enable, Bootable, incremental back and for one of the images i enable discard for testing purposes. What am i doing wrong?

3 6

Failed to launch VM - Error unable to get volume size
by kushagra.gupta＠hsc.com 13 Jan '23

13 Jan '23

Hi, We're trying to launch the VM with PosixFS Storage and recently we've experienced an error while launching. We are successfully uploading the image with PosixFS storage in Storage -> Disks. After upload, we get the status of image upload as illegal, then we are executing the below command on management-engine, and the status changes to OK. `/usr/share/ovirt-engine/setup/dbutils/unlock_entity.sh -t all` Now, When we are creating VM with the same image. Then at the launch time, we got the below errors in /var/log/ovirt-engine/engine.log `ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-32) [539b710] EVENT_ID: VM_DOWN_ERROR(119), VM OS-22Dec is down with error. Exit message: Unable to get volume size for domain <domain_id> volume <volume_id>` All storage domains are PosixFS based. Thanks

2 1

Slightly confused by KeyCloak
by theo.pirkl＠hesge.ch 13 Jan '23

13 Jan '23

Hi there, We've decided to use oVirt for our school datacenter and I'm setting up a PoC to show it could work for our needs. So far, I've managed to deploy a single hosted engine to iSCSI by using the hosted-engine deploy script. So far, so good, I can create VMs, I've had a few problems, but nothing I couldn't figure out. What got me confused is the KeyCloak link with oVirt. My goal is to allow students to register to oVirt so that they can spin up VMs, images, and so on. I've created a group in KeyCloak named "ovirt-student" that is automatically assigned to new users. I have also linked oVirt to this group by going into the engine web UI and adding the group to oVirt's group list. I have given system permissions to the ovirt-student group such as VMCreator. I've then tried to connect to a dummy user called "test". My results are as follows : - The user does not seem to have the correct rights as it cannot create new VMs in the VM portal; - The admin interface does not suggest the user is a part of the ovirt-student group; However, when I add the test user to the ovirt-administrator group, no problem at all, the user is an admin, alright. My question is as follows : what do I need to do so that the groups in KeyCloak and oVirt are synced ? Thanks a lot, TP

2 1

VM disks & Logical Volume
by duparchy＠esrf.fr 13 Jan '23

13 Jan '23

Hi, Following the Daca Center and Cluster upgrade to 4.6 compatibility, LV volumes of VM disks are not there anymore. How VM disks are accessed / mounted ?

1 0

Storage Domain stuck in Maintainance mode
by kushagra.gupta＠hsc.com 13 Jan '23

13 Jan '23

Hi Team, I am new to oVirt. I have installed version 4.4.10 I am trying to create a new Storage domain of type POSIX compliant FS type. I have a ceph cluster configure on IPV6. I was able to create the domain using the following link: https://www.ovirt.org/documentation/administration_guide/#Understanding_Sto… Eventhough the domain was created, it's stuck in maintenance mode. On checking the engine.log ``` 2023-01-04 14:58:14,422+05 ERROR [org.ovirt.engine.core.vdsbroker.irsbroker.DetachStorageDomainVDSCommand] (EE-ManagedThreadFactory-engine-Thread-8455) [22bc 4e1c-115b-45e3-839e-e47f7786eb0a] Failed in 'DetachStorageDomainVDS' method 2023-01-04 14:58:14,452+05 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-8455) [22bc4e1 c-115b-45e3-839e-e47f7786eb0a] EVENT_ID: IRS_BROKER_COMMAND_FAILURE(10,803), VDSM command DetachStorageDomainVDS failed: Storage domain does not exist: ('738 57322-c523-46ec-9d90-5d5451d51e93',) 2023-01-04 14:58:14,453+05 ERROR [org.ovirt.engine.core.vdsbroker.irsbroker.DetachStorageDomainVDSCommand] (EE-ManagedThreadFactory-engine-Thread-8455) [22bc4e1c-115b-45e3-839e-e47f7786eb0a] Command 'DetachStorageDomainVDSCommand( DetachStorageDomainVDSCommandParameters:{storagePoolId='537e6452-8b7a-11ed-a21c-00163e750630', ignoreFailoverLimit='false', storageDomainId='73857322-c523-46ec-9d90-5d5451d51e93', masterDomainId='00000000-0000-0000-0000-000000000000', masterVersion='1', force='false'})' execution failed: IRSGenericException: IRSErrorException: Failed to DetachStorageDomainVDS, error = Storage domain does not exist: ('73857322-c523-46ec-9d90-5d5451d51e93',), code = 358 2023-01-04 14:58:14,453+05 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.DetachStorageDomainVDSCommand] (EE-ManagedThreadFactory-engine-Thread-8455) [22bc 4e1c-115b-45e3-839e-e47f7786eb0a] FINISH, DetachStorageDomainVDSCommand, return: , log id: fb86a82 2023-01-04 14:58:14,453+05 ERROR [org.ovirt.engine.core.bll.storage.domain.DetachStorageDomainFromPoolCommand] (EE-ManagedThreadFactory-engine-Thread-8455) [22bc4e1c-115b-45e3-839e-e47f7786eb0a] Command 'org.ovirt.engine.core.bll.storage.domain.DetachStorageDomainFromPoolCommand' failed: EngineException: org.ovirt.engine.core.vdsbroker.irsbroker.IrsOperationFailedNoFailoverException: IRSGenericException: IRSErrorException: Failed to DetachStorageDomainVDS, error = Storage domain does not exist: ('73857322-c523-46ec-9d90-5d5451d51e93',), code = 358 (Failed with error StorageDomainDoesNotExist and code 358) 2023-01-04 14:58:14,453+05 INFO [org.ovirt.engine.core.bll.CommandCompensator] (EE-ManagedThreadFactory-engine-Thread-8455) [22bc4e1c-115b-45e3-839e-e47f7786eb0a] Command [id=b2b2c6de-97b6-4e01-8589-fc4b22eeecb9]: Compensating CHANGED_STATUS_ONLY of org.ovirt.engine.core.common.businessentities.StoragePoolIsoMap; snapshot: EntityStatusSnapshot:{id='StoragePoolIsoMapId:{storagePoolId='537e6452-8b7a-11ed-a21c-00163e750630', storageId='73857322-c523-46ec-9d90-5d5451d51e93'}', status='Maintenance'}. 2023-01-04 14:58:14,555+05 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-8455) [22bc4e1c-115b-45e3-839e-e47f7786eb0a] EVENT_ID: USER_DETACH_STORAGE_DOMAIN_FROM_POOL_FAILED(965), Failed to detach Storage Domain POSIXDOMAIN from Data Center Default. (User: admin@internal-authz) ``` I tried the following link: https://lists.ovirt.org/pipermail/users/2012-August/009044.html But this also did not work. On the other hand on the same ceph node configured NFS server and created a storage domain for that on ovirt and it became active immidiately. Could anyone please help me out with this? Thanks and Regards Kushagra Gupta

2 1

can't add user in GUI of Version 4.4
by stephane.beausoleil＠cgi.com 12 Jan '23

12 Jan '23

hi, on previous version of the ovirt manager we could had simple local users now the gui interface Add button does nothing? What is going on. For day to day management it is faster and easier then using the cli.

1 0

aggregate multiple hosts
by csokasi.lehel＠gmail.com 12 Jan '23

12 Jan '23

I would like to ask if it is possible to aggregate multiple hosts to a single virtual machine.

1 0

user unlocked but remains locked on 4.4.10
by Gianluca Cecchi 12 Jan '23

12 Jan '23

Hello, I have a user that had validity until end of last year. He tried to access but now it gets locked. I tried to password reset and/or unlock but he continues to get the message that the account is locked. And in fact I see # ovirt-aaa-jdbc-tool user show myuser Picked up JAVA_TOOL_OPTIONS: -Dcom.redhat.fips=false -- User vale(485fc2a3-3faa-4e75-9965-b5a3067433e0) -- Namespace: * Name: myuser ID: 485fc2a3-3faa-4e75-9965-b5a3067433e0 Display Name: myuser Email: First Name: My Last Name: User Department: Title: Description: Account Disabled: false Account Locked: true Account Unlocked At: 2023-01-12 10:30:00Z Account Valid From: 2021-03-12 09:47:15Z Account Valid To: 2221-03-12 09:47:15Z Account Without Password: false Last successful Login At: 2022-12-31 23:06:06Z Last unsuccessful Login At: 2023-01-12 09:30:00Z Password Valid To: 2023-12-31 23:59:59Z # How to get "Account Locked: false"? Any other method? Tried sequence of commands: # ovirt-aaa-jdbc-tool user password-reset myuser --password-valid-to='2023-12-31 23:59:59Z' --force # ovirt-aaa-jdbc-tool user unlock myuser tried also to restart ovirt-engine service without luck Thanks in advance, Gianluca

1 0

java code example for vdsm rpc client call
by yongshengmaa＠126.com 12 Jan '23

12 Jan '23

Hello I have compiled vdsm-jsonrpc-java and got the jar files. Now I need to access the vdsm server on ovirt node. Where can I find the Java example for the rpc calls? Thanks!

1 0

ovirt migrate vm's
by Sam zz 11 Jan '23

11 Jan '23

Just curious to know, Is it possible to migrate vm's from ovirt to plain qemu/kvm? Also, Does engine-cleanup delete the guest VM's?

1 0

Virt-Viewer fullscreen multi-monitor dragging stops at edge
by jamie.briscoe＠johnstonnc.com 10 Jan '23

10 Jan '23

In linux, using virt-viewer to connect to a windows vm in fullscreen with multiple monitors I can not drag windows across monitors. The mouse stops at the edge. I have to release the mouse, then click and drag the window again. I don't have that issue using windows as the client to connect to the vm. Anybody else have this issue?

1 0

Floppy removed in Ovirt 4.4 and SysPrep not working
by raviteja 09 Jan '23

09 Jan '23

Hi Guys Happy New Year. We recently upgraded our oVirt version from 4.3 to 4.4. We have noticed floppy is removed in run once mode. So We are unable to proceed with Automated customisation(Assigning hostname, IP address and setting initial login creds) of Windows VM's. Anyone tried sysprep without floppy. We are using oVirt Ansible module for provisioning the VM and it uses a custom xml template(jinja2) for OS customization. Thanks in Advance.

1 0

Not able to create a disk.
by kushagra.gupta＠hsc.com 09 Jan '23

09 Jan '23

Hi team, I am new to ovirt. I have setup a self hosted ovirt engine with version 4.4. I am able to create a POSIX compliant FS storage domain type. While creating the Storage domain, at the path I am passing all the three nodes in the ceph cluster: eg. ``` [abcd:abcd:abcd::23],[abcd:abcd:abcd::22],[abcd:abcd:abcd::21]:6789:/volumes/kush/threetest/cb8a69c4-9c9a-4a2d-9a4a-7b9a5ff14c74 ``` When I am doing this, I am not able to create a disk in the domain. Following are the logs from the hosted engine. The log file I am reffering is /var/log/ovirt-engine/engine.log ``` 2023-01-09 12:40:13,815+05 INFO [org.ovirt.engine.core.bll.utils.ThreadPoolMonitoringService] (EE-ManagedScheduledExecutorService-engineThreadMonitoringThreadPool-Thread-1) [] Thread pool 'default' is using 0 threads out of 1, 5 threads waiting for tasks. 2023-01-09 12:40:13,815+05 INFO [org.ovirt.engine.core.bll.utils.ThreadPoolMonitoringService] (EE-ManagedScheduledExecutorService-engineThreadMonitoringThreadPool-Thread-1) [] Thread pool 'engine' is using 0 threads out of 500, 10 threads waiting for tasks and 0 tasks in queue. 2023-01-09 12:40:13,815+05 INFO [org.ovirt.engine.core.bll.utils.ThreadPoolMonitoringService] (EE-ManagedScheduledExecutorService-engineThreadMonitoringThreadPool-Thread-1) [] Thread pool 'engineScheduledThreadPool' is using 0 threads out of 1, 100 threads waiting for tasks. 2023-01-09 12:40:13,815+05 INFO [org.ovirt.engine.core.bll.utils.ThreadPoolMonitoringService] (EE-ManagedScheduledExecutorService-engineThreadMonitoringThreadPool-Thread-1) [] Thread pool 'engineThreadMonitoringThreadPool' is using 1 threads out of 1, 0 threads waiting for tasks. 2023-01-09 12:40:13,815+05 INFO [org.ovirt.engine.core.bll.utils.ThreadPoolMonitoringService] (EE-ManagedScheduledExecutorService-engineThreadMonitoringThreadPool-Thread-1) [] Thread pool 'hostUpdatesChecker' is using 0 threads out of 5, 4 threads waiting for tasks. 2023-01-09 12:40:17,706+05 INFO [org.ovirt.engine.core.bll.storage.disk.image.TransferDiskImageCommand] (default task-4) [e4ee0883-61f7-4940-9545-b2f36734df04] Lock Acquired to object 'EngineLock:{exclusiveLocks='[]', sharedLocks='[]'}' 2023-01-09 12:40:17,742+05 INFO [org.ovirt.engine.core.bll.storage.disk.image.TransferDiskImageCommand] (default task-4) [e4ee0883-61f7-4940-9545-b2f36734df04] Running command: TransferDiskImageCommand internal: false. Entities affected : ID: b0d10f22-f913-4c05-8d44-084f775ae87d Type: StorageAction group CREATE_DISK with role type USER 2023-01-09 12:40:17,742+05 INFO [org.ovirt.engine.core.bll.storage.disk.image.TransferDiskImageCommand] (default task-4) [e4ee0883-61f7-4940-9545-b2f36734df04] Creating ImageTransfer entity for command 'df2c9d30-e452-492d-b07c-b4b1232c9de0', proxyEnabled: true 2023-01-09 12:40:17,783+05 INFO [org.ovirt.engine.core.bll.storage.disk.image.TransferDiskImageCommand] (default task-4) [e4ee0883-61f7-4940-9545-b2f36734df04] Creating disk image 2023-01-09 12:40:17,909+05 INFO [org.ovirt.engine.core.bll.storage.disk.AddDiskCommand] (default task-4) [e4ee0883-61f7-4940-9545-b2f36734df04] Running command: AddDiskCommand internal: true. Entities affected : ID: b0d10f22-f913-4c05-8d44-084f775ae87d Type: StorageAction group CREATE_DISK with role type USER 2023-01-09 12:40:18,034+05 INFO [org.ovirt.engine.core.bll.storage.disk.image.AddImageFromScratchCommand] (default task-4) [e4ee0883-61f7-4940-9545-b2f36734df04] Running command: AddImageFromScratchCommand internal: true. Entities affected : ID: b0d10f22-f913-4c05-8d44-084f775ae87d Type: Storage 2023-01-09 12:40:18,201+05 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.CreateVolumeVDSCommand] (default task-4) [e4ee0883-61f7-4940-9545-b2f36734df04] START, CreateVolumeVDSCommand( CreateVolumeVDSCommandParameters:{storagePoolId='537e6452-8b7a-11ed-a21c-00163e750630', ignoreFailoverLimit='false', storageDomainId='b0d10f22-f913-4c05-8d44-084f775ae87d', imageGroupId='6f649bd6-2235-4ea8-822b-3b47308b3425', imageSizeInBytes='117440512', volumeFormat='COW', newImageId='032c711e-c488-4f2d-ae7c-363db5b6ffba', imageType='Sparse', newImageDescription='{"DiskAlias":"cirrorstrialpossix2","DiskDescription":"this is a trial for possix"}', imageInitialSizeInBytes='0', imageId='00000000-0000-0000-0000-000000000000', sourceImageGroupId='00000000-0000-0000-0000-000000000000', shouldAddBitmaps='false'}), log id: 6f257c25 2023-01-09 12:40:18,840+05 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.CreateVolumeVDSCommand] (default task-4) [e4ee0883-61f7-4940-9545-b2f36734df04] FINISH, CreateVolumeVDSCommand, return: 032c711e-c488-4f2d-ae7c-363db5b6ffba, log id: 6f257c25 2023-01-09 12:40:18,842+05 INFO [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (default task-4) [e4ee0883-61f7-4940-9545-b2f36734df04] CommandAsyncTask::Adding CommandMultiAsyncTasks object for command 'b0b78998-d71b-4dec-970d-0fbfa43d2e19' 2023-01-09 12:40:18,842+05 INFO [org.ovirt.engine.core.bll.CommandMultiAsyncTasks] (default task-4) [e4ee0883-61f7-4940-9545-b2f36734df04] CommandMultiAsyncTasks::attachTask: Attaching task '660f08b4-c380-4ece-86ee-41db40e6bb22' to command 'b0b78998-d71b-4dec-970d-0fbfa43d2e19'. 2023-01-09 12:40:19,034+05 INFO [org.ovirt.engine.core.bll.tasks.AsyncTaskManager] (default task-4) [e4ee0883-61f7-4940-9545-b2f36734df04] Adding task '660f08b4-c380-4ece-86ee-41db40e6bb22' (Parent Command 'AddImageFromScratch', Parameters Type 'org.ovirt.engine.core.common.asynctasks.AsyncTaskParameters'), polling hasn't started yet.. 2023-01-09 12:40:19,127+05 INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (default task-4) [e4ee0883-61f7-4940-9545-b2f36734df04] BaseAsyncTask::startPollingTask: Starting to poll task '660f08b4-c380-4ece-86ee-41db40e6bb22'. 2023-01-09 12:40:19,385+05 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-4) [e4ee0883-61f7-4940-9545-b2f36734df04] EVENT_ID: ADD_DISK_INTERNAL(2,036), Add-Disk operation of 'cirrorstrialpossix2' was initiated by the system. 2023-01-09 12:40:19,660+05 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-4) [e4ee0883-61f7-4940-9545-b2f36734df04] EVENT_ID: TRANSFER_IMAGE_INITIATED(1,031), Image Upload with disk cirrorstrialpossix2 was initiated by admin@internal-authz. 2023-01-09 12:40:20,378+05 INFO [org.ovirt.engine.core.bll.storage.disk.image.TransferDiskImageCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-24) [e4ee0883-61f7-4940-9545-b2f36734df04] Waiting for disk to be added for image transfer command 'df2c9d30-e452-492d-b07c-b4b1232c9de0' 2023-01-09 12:40:20,378+05 INFO [org.ovirt.engine.core.bll.storage.disk.AddDiskCommandCallback] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-24) [e4ee0883-61f7-4940-9545-b2f36734df04] Command 'AddDisk' (id: '674288b3-6da2-4458-9113-f64afc1e6685') waiting on child command id: 'b0b78998-d71b-4dec-970d-0fbfa43d2e19' type:'AddImageFromScratch' to complete 2023-01-09 12:40:20,497+05 INFO [org.ovirt.engine.core.bll.tasks.AsyncTaskManager] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-50) [] Setting new tasks map. The map contains now 1 tasks 2023-01-09 12:40:23,737+05 INFO [org.ovirt.engine.core.bll.storage.disk.image.TransferImageStatusCommand] (default task-4) [cd62aea8-2e37-4af1-9b0b-21a740436ca3] Running command: TransferImageStatusCommand internal: false. Entities affected : ID: b0d10f22-f913-4c05-8d44-084f775ae87d Type: SystemAction group CREATE_DISK with role type USER 2023-01-09 12:40:24,388+05 INFO [org.ovirt.engine.core.bll.storage.disk.image.TransferDiskImageCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-85) [e4ee0883-61f7-4940-9545-b2f36734df04] Waiting for disk to be added for image transfer command 'df2c9d30-e452-492d-b07c-b4b1232c9de0' 2023-01-09 12:40:24,389+05 INFO [org.ovirt.engine.core.bll.storage.disk.AddDiskCommandCallback] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-85) [e4ee0883-61f7-4940-9545-b2f36734df04] Command 'AddDisk' (id: '674288b3-6da2-4458-9113-f64afc1e6685') waiting on child command id: 'b0b78998-d71b-4dec-970d-0fbfa43d2e19' type:'AddImageFromScratch' to complete 2023-01-09 12:40:25,757+05 INFO [org.ovirt.engine.core.bll.tasks.AsyncTaskManager] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-89) [] Polling and updating Async Tasks: 1 tasks, 1 tasks to poll now 2023-01-09 12:40:25,917+05 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMGetAllTasksStatusesVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-89) [] Failed in 'HSMGetAllTasksStatusesVDS' method 2023-01-09 12:40:25,948+05 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-89) [] EVENT_ID: VDS_BROKER_COMMAND_FAILURE(10,802), VDSM ovirt-host command HSMGetAllTasksStatusesVDS failed: value=ParamsList: sep , in /rhev/data-center/mnt/[abcd:abcd:abcd::23],[abcd:abcd:abcd::22],[abcd:abcd:abcd::21]:6789:_volumes_kush_threetest_cb8a69c4-9c9a-4a2d-9a4a-7b9a5ff14c74/b0d10f22-f913-4c05-8d44-084f775ae87d/images/6f649bd6-2235-4ea8-822b-3b47308b3425 abortedcode=100 2023-01-09 12:40:25,948+05 INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-89) [] SPMAsyncTask::PollTask: Polling task '660f08b4-c380-4ece-86ee-41db40e6bb22' (Parent Command 'AddImageFromScratch', Parameters Type 'org.ovirt.engine.core.common.asynctasks.AsyncTaskParameters') returned status 'finished', result 'cleanSuccess'. 2023-01-09 12:40:25,948+05 ERROR [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-89) [] BaseAsyncTask::logEndTaskFailure: Task '660f08b4-c380-4ece-86ee-41db40e6bb22' (Parent Command 'AddImageFromScratch', Parameters Type 'org.ovirt.engine.core.common.asynctasks.AsyncTaskParameters') ended with failure: -- Result: 'cleanSuccess' -- Message: 'VDSGenericException: VDSErrorException: Failed to HSMGetAllTasksStatusesVDS, error = value=ParamsList: sep , in /rhev/data-center/mnt/[abcd:abcd:abcd::23],[abcd:abcd:abcd::22],[abcd:abcd:abcd::21]:6789:_volumes_kush_threetest_cb8a69c4-9c9a-4a2d-9a4a-7b9a5ff14c74/b0d10f22-f913-4c05-8d44-084f775ae87d/images/6f649bd6-2235-4ea8-822b-3b47308b3425 abortedcode=100, code = 100', -- Exception: 'VDSGenericException: VDSErrorException: Failed to HSMGetAllTasksStatusesVDS, error = value=ParamsList: sep , in /rhev/data-center/mnt/[abcd:abcd:abcd::23],[abcd:abcd:abcd::22],[abcd:abcd:abcd::21]:6789:_volumes_kush_threetest_cb8a69c4-9c9a-4a2d-9a4a-7b9a5ff14c74/b0d10f22-f913-4c05-8d44-084f775ae87d/images/6f649bd6-2235-4ea8-822b-3b47308b3425 abortedcode=100, code = 100' 2023-01-09 12:40:25,949+05 INFO [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-89) [] CommandAsyncTask::endActionIfNecessary: All tasks of command 'b0b78998-d71b-4dec-970d-0fbfa43d2e19' has ended -> executing 'endAction' 2023-01-09 12:40:25,949+05 INFO [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-89) [] CommandAsyncTask::endAction: Ending action for '1' tasks (command ID: 'b0b78998-d71b-4dec-970d-0fbfa43d2e19'): calling endAction '. 2023-01-09 12:40:25,950+05 INFO [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (EE-ManagedThreadFactory-engine-Thread-43674) [] CommandAsyncTask::endCommandAction [within thread] context: Attempting to endAction 'AddImageFromScratch', 2023-01-09 12:40:25,981+05 INFO [org.ovirt.engine.core.bll.storage.disk.image.AddImageFromScratchCommand] (EE-ManagedThreadFactory-engine-Thread-43674) [e4ee0883-61f7-4940-9545-b2f36734df04] Command [id=b0b78998-d71b-4dec-970d-0fbfa43d2e19]: Updating status to 'FAILED', The command end method logic will be executed by one of its parent commands. 2023-01-09 12:40:25,981+05 INFO [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (EE-ManagedThreadFactory-engine-Thread-43674) [e4ee0883-61f7-4940-9545-b2f36734df04] CommandAsyncTask::HandleEndActionResult [within thread]: endAction for action type 'AddImageFromScratch' completed, handling the result. 2023-01-09 12:40:25,981+05 INFO [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (EE-ManagedThreadFactory-engine-Thread-43674) [e4ee0883-61f7-4940-9545-b2f36734df04] CommandAsyncTask::HandleEndActionResult [within thread]: endAction for action type 'AddImageFromScratch' succeeded, clearing tasks. 2023-01-09 12:40:25,981+05 INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedThreadFactory-engine-Thread-43674) [e4ee0883-61f7-4940-9545-b2f36734df04] SPMAsyncTask::ClearAsyncTask: Attempting to clear task '660f08b4-c380-4ece-86ee-41db40e6bb22' 2023-01-09 12:40:25,982+05 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.SPMClearTaskVDSCommand] (EE-ManagedThreadFactory-engine-Thread-43674) [e4ee0883-61f7-4940-9545-b2f36734df04] START, SPMClearTaskVDSCommand( SPMTaskGuidBaseVDSCommandParameters:{storagePoolId='537e6452-8b7a-11ed-a21c-00163e750630', ignoreFailoverLimit='false', taskId='660f08b4-c380-4ece-86ee-41db40e6bb22'}), log id: 4a57fbda 2023-01-09 12:40:25,983+05 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMClearTaskVDSCommand] (EE-ManagedThreadFactory-engine-Thread-43674) [e4ee0883-61f7-4940-9545-b2f36734df04] START, HSMClearTaskVDSCommand(HostName = ovirt-host, HSMTaskGuidBaseVDSCommandParameters:{hostId='80024b36-7380-4cf6-936c-9ba01426316f', taskId='660f08b4-c380-4ece-86ee-41db40e6bb22'}), log id: 27ee199b 2023-01-09 12:40:26,036+05 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMClearTaskVDSCommand] (EE-ManagedThreadFactory-engine-Thread-43674) [e4ee0883-61f7-4940-9545-b2f36734df04] FINISH, HSMClearTaskVDSCommand, return: , log id: 27ee199b 2023-01-09 12:40:26,036+05 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.SPMClearTaskVDSCommand] (EE-ManagedThreadFactory-engine-Thread-43674) [e4ee0883-61f7-4940-9545-b2f36734df04] FINISH, SPMClearTaskVDSCommand, return: , log id: 4a57fbda 2023-01-09 12:40:26,065+05 INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedThreadFactory-engine-Thread-43674) [e4ee0883-61f7-4940-9545-b2f36734df04] BaseAsyncTask::removeTaskFromDB: Removed task '660f08b4-c380-4ece-86ee-41db40e6bb22' from DataBase 2023-01-09 12:40:26,065+05 INFO [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (EE-ManagedThreadFactory-engine-Thread-43674) [e4ee0883-61f7-4940-9545-b2f36734df04] CommandAsyncTask::HandleEndActionResult [within thread]: Removing CommandMultiAsyncTasks object for entity 'b0b78998-d71b-4dec-970d-0fbfa43d2e19' 2023-01-09 12:40:27,737+05 INFO [org.ovirt.engine.core.bll.storage.disk.image.TransferImageStatusCommand] (default task-4) [5deca7ba-3c4e-465c-b64d-853e622e01a4] Running command: TransferImageStatusCommand internal: false. Entities affected : ID: b0d10f22-f913-4c05-8d44-084f775ae87d Type: SystemAction group CREATE_DISK with role type USER 2023-01-09 12:40:31,739+05 INFO [org.ovirt.engine.core.bll.storage.disk.image.TransferImageStatusCommand] (default task-4) [83802d31-c7b5-4a80-bf64-af3f3a617d96] Running command: TransferImageStatusCommand internal: false. Entities affected : ID: b0d10f22-f913-4c05-8d44-084f775ae87d Type: SystemAction group CREATE_DISK with role type USER 2023-01-09 12:40:32,392+05 INFO [org.ovirt.engine.core.bll.storage.disk.image.TransferDiskImageCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-26) [e4ee0883-61f7-4940-9545-b2f36734df04] Waiting for disk to be added for image transfer command 'df2c9d30-e452-492d-b07c-b4b1232c9de0' 2023-01-09 12:40:32,393+05 INFO [org.ovirt.engine.core.bll.storage.disk.AddDiskCommandCallback] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-26) [e4ee0883-61f7-4940-9545-b2f36734df04] Command 'AddDisk' id: '674288b3-6da2-4458-9113-f64afc1e6685' child commands '[b0b78998-d71b-4dec-970d-0fbfa43d2e19]' executions were completed, status 'FAILED' 2023-01-09 12:40:33,418+05 ERROR [org.ovirt.engine.core.bll.storage.disk.AddDiskCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-55) [e4ee0883-61f7-4940-9545-b2f36734df04] Ending command 'org.ovirt.engine.core.bll.storage.disk.AddDiskCommand' with failure. 2023-01-09 12:40:33,451+05 ERROR [org.ovirt.engine.core.bll.storage.disk.image.AddImageFromScratchCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-55) [e4ee0883-61f7-4940-9545-b2f36734df04] Ending command 'org.ovirt.engine.core.bll.storage.disk.image.AddImageFromScratchCommand' with failure. 2023-01-09 12:40:33,493+05 WARN [org.ovirt.engine.core.bll.storage.disk.AddDiskCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-55) [] VM is null - no unlocking 2023-01-09 12:40:33,609+05 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-55) [] EVENT_ID: USER_ADD_DISK_FINISHED_FAILURE(2,022), Add-Disk operation failed to complete. 2023-01-09 12:40:34,644+05 ERROR [org.ovirt.engine.core.bll.storage.disk.image.TransferDiskImageCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-81) [e4ee0883-61f7-4940-9545-b2f36734df04] Failed to add disk for image transfer command 'df2c9d30-e452-492d-b07c-b4b1232c9de0' 2023-01-09 12:40:35,677+05 ERROR [org.ovirt.engine.core.bll.storage.disk.image.TransferDiskImageCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-20) [e4ee0883-61f7-4940-9545-b2f36734df04] Ending command 'org.ovirt.engine.core.bll.storage.disk.image.TransferDiskImageCommand' with failure. 2023-01-09 12:40:35,677+05 ERROR [org.ovirt.engine.core.bll.storage.disk.image.TransferDiskImageCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-20) [e4ee0883-61f7-4940-9545-b2f36734df04] Failed to transfer disk '00000000-0000-0000-0000-000000000000' (command id 'df2c9d30-e452-492d-b07c-b4b1232c9de0') 2023-01-09 12:40:35,684+05 WARN [org.ovirt.engine.core.bll.storage.disk.RemoveDiskCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-20) [78be2ab6] Validation of action 'RemoveDisk' failed for user admin@internal-authz. Reasons: VAR__ACTION__REMOVE,VAR__TYPE__DISK,ACTION_TYPE_FAILED_VM_IMAGE_DOES_NOT_EXIST 2023-01-09 12:40:35,684+05 INFO [org.ovirt.engine.core.bll.storage.disk.RemoveDiskCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-20) [78be2ab6] Lock freed to object 'EngineLock:{exclusiveLocks='[]', sharedLocks='[]'}' 2023-01-09 12:40:35,684+05 INFO [org.ovirt.engine.core.bll.storage.disk.image.TransferDiskImageCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-20) [78be2ab6] Lock freed to object 'EngineLock:{exclusiveLocks='[]', sharedLocks='[]'}' 2023-01-09 12:40:35,685+05 INFO [org.ovirt.engine.core.bll.storage.disk.image.ImageTransferUpdater] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-20) [78be2ab6] Updating image transfer df2c9d30-e452-492d-b07c-b4b1232c9de0 phase to Finished Failure 2023-01-09 12:40:35,743+05 INFO [org.ovirt.engine.core.bll.storage.disk.image.TransferImageStatusCommand] (default task-4) [f9eca38b-8cc4-4410-a653-ea091532302a] Running command: TransferImageStatusCommand internal: false. Entities affected : ID: b0d10f22-f913-4c05-8d44-084f775ae87d Type: SystemAction group CREATE_DISK with role type USER 2023-01-09 12:40:35,827+05 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-20) [78be2ab6] EVENT_ID: TRANSFER_IMAGE_FAILED(1,034), Image Upload with disk cirrorstrialpossix2 failed. 2023-01-09 12:40:39,744+05 INFO [org.ovirt.engine.core.bll.storage.disk.image.TransferImageStatusCommand] (default task-4) [727f4329-71fa-454b-923f-a84f2bfcc7e9] Running command: TransferImageStatusCommand internal: false. Entities affected : ID: b0d10f22-f913-4c05-8d44-084f775ae87d Type: SystemAction group CREATE_DISK with role type USER ``` Following are the VDSM logs: ``` 2023-01-09 12:40:20,050+0530 INFO (tasks/8) [storage.ThreadPool.WorkerThread] START task 660f08b4-c380-4ece-86ee-41db40e6bb22 (cmd=<bound method Task.commit of <vdsm.storage.task.Task object at 0x7f340c113940>>, args=None) (threadPool:146) 2023-01-09 12:40:20,612+0530 INFO (tasks/8) [storage.StorageDomain] Create placeholder /rhev/data-center/mnt/[abcd:abcd:abcd::23],[abcd:abcd:abcd::22],[abcd :abcd:abcd::21]:6789:_volumes_kush_threetest_cb8a69c4-9c9a-4a2d-9a4a-7b9a5ff14c74/b0d10f22-f913-4c05-8d44-084f775ae87d/images/6f649bd6-2235-4ea8-822b-3b47308 b3425 for image's volumes (sd:1718) 2023-01-09 12:40:20,612+0530 ERROR (tasks/8) [storage.TaskManager.Task] (Task='660f08b4-c380-4ece-86ee-41db40e6bb22') Unexpected error (task:877) Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/vdsm/storage/task.py", line 884, in _run return fn(*args, **kargs) File "/usr/lib/python3.6/site-packages/vdsm/storage/task.py", line 350, in run return self.cmd(*self.argslist, **self.argsdict) File "/usr/lib/python3.6/site-packages/vdsm/storage/securable.py", line 79, in wrapper return method(self, *args, **kwargs) File "/usr/lib/python3.6/site-packages/vdsm/storage/sp.py", line 1952, in createVolume initial_size=initialSize, add_bitmaps=addBitmaps) File "/usr/lib/python3.6/site-packages/vdsm/storage/sd.py", line 1216, in createVolume initial_size=initial_size, add_bitmaps=add_bitmaps) File "/usr/lib/python3.6/site-packages/vdsm/storage/volume.py", line 1174, in create imgPath = dom.create_image(imgUUID) File "/usr/lib/python3.6/site-packages/vdsm/storage/sd.py", line 1721, in create_image "create_image_rollback", [image_dir]) File "/usr/lib/python3.6/site-packages/vdsm/storage/task.py", line 385, in __init__ self.params = ParamList(argslist) File "/usr/lib/python3.6/site-packages/vdsm/storage/task.py", line 298, in __init__ raise ValueError("ParamsList: sep %s in %s" % (sep, i)) ValueError: ParamsList: sep , in /rhev/data-center/mnt/[abcd:abcd:abcd::23],[abcd:abcd:abcd::22],[abcd:abcd:abcd::21]:6789:_volumes_kush_threetest_cb8a69c4-9 c9a-4a2d-9a4a-7b9a5ff14c74/b0d10f22-f913-4c05-8d44-084f775ae87d/images/6f649bd6-2235-4ea8-822b-3b47308b3425 2023-01-09 12:40:21,530+0530 INFO (tasks/8) [storage.ThreadPool.WorkerThread] FINISH task 660f08b4-c380-4ece-86ee-41db40e6bb22 (threadPool:148) 2023-01-09 12:40:21,715+0530 INFO (jsonrpc/4) [api.host] START getAllVmStats() from=::1,52540 (api:48) 2023-01-09 12:40:21,715+0530 ``` Could anyone please help me out. Thanks and Regards Kushagra Gupta

1 0

VDSM myhost.example.local command Get Host Capabilities failed: Received fatal alert: certificate_expired
by PenguinWhispererThe 06 Jan '23

06 Jan '23

Hi, When starting my ovirt installation again ovirt was not working and after some troubleshooting it seemed that some certs where expired. So I basically did this redhat solution: https://access.redhat.com/solutions/6964632 And afterwards I had this in the UI: sun.security.validator.validatorexception: pkix path validation failed So tried this: https://lists.ovirt.org/archives/list/users@ovirt.org/thread/ZI5WNU6OB6FZMQ… Now I do get to the ovirt UI however the datacenter and storage is not coming up. I see in the events: VDSM myhost.example.local command Get Host Capabilities failed: Received fatal alert: certificate_expired On the vdsmd side on the host I see: ERROR ssl handshake: SSLError, address: ::ffff:192.168.1.109 I don't know to which service it tries to connect and so what certificate is expired or how to replace it. I just want to get the ovirt back up and running properly so I can start my VMs. Thanks in advance.

1 1

Tags in Ovirt
by Colin Coe 04 Jan '23

04 Jan '23

Hi all I'm trying to dump out a list of all tags and the VMs attached. I need to do this as I wrote an Ansible task to attach some VMs to some tags and ended up removing other VMs from these tags which caused some issues. I think I've fixed my problem but I want to take a backup of the tags and attached VMs but using ovirt.ovirt.ovirt_tag_info I can't see how to list all tags with the attached VMs. I've tried various incantations like: - ovirt.ovirt.ovirt_tag_info: auth: "{{ ovirt_auth}}" name: 'veeam-tier*' fetch_nested: true nested_attributes: - vm register: result but all I get is: ok: [localhost] => { "result": { "changed": false, "deprecations": [ { "msg": "The 'fetch_nested' and 'nested_attributes' are deprecated please use 'follow' parameter", "version": "3.0.0" } ], "failed": false, "ovirt_tags": [ { "description": "", "href": "/ovirt-engine/api/tags/4ebb9243-b133-40c9-b22e-03b3798415bf", "id": "4ebb9243-b133-40c9-b22e-03b3798415bf", "name": "veeam-tier3", "parent": { "href": "/ovirt-engine/api/tags/00000000-0000-0000-0000-000000000000", "id": "00000000-0000-0000-0000-000000000000" } }, { "description": "", "href": "/ovirt-engine/api/tags/0fd7a16a-82ca-4d13-a9ab-9646a41c58e6", "id": "0fd7a16a-82ca-4d13-a9ab-9646a41c58e6", "name": "veeam-tier1", "parent": { "href": "/ovirt-engine/api/tags/00000000-0000-0000-0000-000000000000", "id": "00000000-0000-0000-0000-000000000000" } }, { "description": "", "href": "/ovirt-engine/api/tags/4155338b-43f4-413c-bf41-4e46ee9472fa", "id": "4155338b-43f4-413c-bf41-4e46ee9472fa", "name": "veeam-tier2", "parent": { "href": "/ovirt-engine/api/tags/00000000-0000-0000-0000-000000000000", "id": "00000000-0000-0000-0000-000000000000" } } ] } } I'm using fetch_nested and nested_attributes as I couldn't get 'follow' to work. Any ideas? Thanks

1 0