August 2024 - Users - oVirt List Archives

SPM and Task error ...
by Enrico 22 Nov '24

22 Nov '24

Hi all, my ovirt cluster has got 3 Hypervisors runnig Centos 7.5.1804 vdsm is 4.20.39.1-1.el7, ovirt engine is 4.2.4.5-1.el7, the storage systems are HP MSA P2000 and 2050 (fibre channel). I need to stop one of the hypervisors for maintenance but this system is the storage pool manager. For this reason I decided to manually activate SPM in one of the other nodes but this operation is not successful. In the ovirt engine (engine.log) the error is this: 2019-07-25 12:39:16,744+02 INFO [org.ovirt.engine.core.bll.storage.pool.ForceSelectSPMCommand] (default task-30) [7c374384-f884-4dc9-87d0-7af27dce706b] Running command: ForceSelectSPMCommand internal: false. Entities affected : ID: 81c9bd3c-ae0a-467f-bf7f-63ab30cd8d9e Type: VDSAction group MANIPULATE_HOST with role type ADMIN 2019-07-25 12:39:16,745+02 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.SpmStopOnIrsVDSCommand] (default task-30) [7c374384-f884-4dc9-87d0-7af27dce706b] START, SpmStopOnIrsVDSCommand( SpmStopOnIrsVDSCommandParameters:{storagePoolId='18d57688-6ed4-43b8-bd7c-0665b55950b7', ignoreFailoverLimit='false'}), log id: 37bf4639 2019-07-25 12:39:16,747+02 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.ResetIrsVDSCommand] (default task-30) [7c374384-f884-4dc9-87d0-7af27dce706b] START, ResetIrsVDSCommand( ResetIrsVDSCommandParameters:{storagePoolId='18d57688-6ed4-43b8-bd7c-0665b55950b7', ignoreFailoverLimit='false', vdsId='751f3e99-b95e-4c31-bc38-77f5661a0bdc', ignoreStopFailed='false'}), log id: 2522686f 2019-07-25 12:39:16,749+02 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.SpmStopVDSCommand] (default task-30) [7c374384-f884-4dc9-87d0-7af27dce706b] START, SpmStopVDSCommand(HostName = infn-vm05.management, SpmStopVDSCommandParameters:{hostId='751f3e99-b95e-4c31-bc38-77f5661a0bdc', storagePoolId='18d57688-6ed4-43b8-bd7c-0665b55950b7'}), log id: 1810fd8b 2019-07-25 12:39:16,758+02 *ERROR* [org.ovirt.engine.core.vdsbroker.vdsbroker.SpmStopVDSCommand] (default task-30) [7c374384-f884-4dc9-87d0-7af27dce706b] SpmStopVDSCommand::Not stopping SPM on vds 'infn-vm05.management', pool id '18d57688-6ed4-43b8-bd7c-0665b55950b7' as there are uncleared tasks 'Task 'fdcf4d1b-82fe-49a6-b233-323ebe568f8e', status 'running'' 2019-07-25 12:39:16,758+02 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.SpmStopVDSCommand] (default task-30) [7c374384-f884-4dc9-87d0-7af27dce706b] FINISH, SpmStopVDSCommand, log id: 1810fd8b 2019-07-25 12:39:16,758+02 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.ResetIrsVDSCommand] (default task-30) [7c374384-f884-4dc9-87d0-7af27dce706b] FINISH, ResetIrsVDSCommand, log id: 2522686f 2019-07-25 12:39:16,758+02 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.SpmStopOnIrsVDSCommand] (default task-30) [7c374384-f884-4dc9-87d0-7af27dce706b] FINISH, SpmStopOnIrsVDSCommand, log id: 37bf4639 2019-07-25 12:39:16,760+02 *ERROR* [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-30) [7c374384-f884-4dc9-87d0-7af27dce706b] EVENT_ID: USER_FORCE_SELECTED_SPM_STOP_FAILED(4,096), Failed to force select infn-vm07.management as the SPM due to a failure to stop the current SPM. while in the hypervisor (SPM) vdsm.log: 2019-07-25 12:39:16,744+02 INFO [org.ovirt.engine.core.bll.storage.pool.ForceSelectSPMCommand] (default task-30) [7c374384-f884-4dc9-87d0-7af27dce706b] Running command: ForceSelectSPMCommand internal: false. Entities affected : ID: 81c9bd3c-ae0a-467f-bf7f-63ab30cd8d9e Type: VDSAction group MANIPULATE_HOST with role type ADMIN 2019-07-25 12:39:16,745+02 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.SpmStopOnIrsVDSCommand] (default task-30) [7c374384-f884-4dc9-87d0-7af27dce706b] START, SpmStopOnIrsVDSCommand( SpmStopOnIrsVDSCommandParameters:{storagePoolId='18d57688-6ed4-43b8-bd7c-0665b55950b7', ignoreFailoverLimit='false'}), log id: 37bf4639 2019-07-25 12:39:16,747+02 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.ResetIrsVDSCommand] (default task-30) [7c374384-f884-4dc9-87d0-7af27dce706b] START, ResetIrsVDSCommand( ResetIrsVDSCommandParameters:{storagePoolId='18d57688-6ed4-43b8-bd7c-0665b55950b7', ignoreFailoverLimit='false', vdsId='751f3e99-b95e-4c31-bc38-77f5661a0bdc', ignoreStopFailed='false'}), log id: 2522686f 2019-07-25 12:39:16,749+02 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.SpmStopVDSCommand] (default task-30) [7c374384-f884-4dc9-87d0-7af27dce706b] START, SpmStopVDSCommand(HostName = infn-vm05.management, SpmStopVDSCommandParameters:{hostId='751f3e99-b95e-4c31-bc38-77f5661a0bdc', storagePoolId='18d57688-6ed4-43b8-bd7c-0665b55950b7'}), log id: 1810fd8b 2019-07-25 12:39:16,758+02 *ERROR* [org.ovirt.engine.core.vdsbroker.vdsbroker.SpmStopVDSCommand] (default task-30) [7c374384-f884-4dc9-87d0-7af27dce706b] SpmStopVDSCommand::Not stopping SPM on vds 'infn-vm05.management', pool id '18d57688-6ed4-43b8-bd7c-0665b55950b7' as there are uncleared tasks 'Task 'fdcf4d1b-82fe-49a6-b233-323ebe568f8e', status 'running'' 2019-07-25 12:39:16,758+02 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.SpmStopVDSCommand] (default task-30) [7c374384-f884-4dc9-87d0-7af27dce706b] FINISH, SpmStopVDSCommand, log id: 1810fd8b 2019-07-25 12:39:16,758+02 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.ResetIrsVDSCommand] (default task-30) [7c374384-f884-4dc9-87d0-7af27dce706b] FINISH, ResetIrsVDSCommand, log id: 2522686f 2019-07-25 12:39:16,758+02 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.SpmStopOnIrsVDSCommand] (default task-30) [7c374384-f884-4dc9-87d0-7af27dce706b] FINISH, SpmStopOnIrsVDSCommand, log id: 37bf4639 2019-07-25 12:39:16,760+02 *ERROR* [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-30) [7c374384-f884-4dc9-87d0-7af27dce706b] EVENT_ID: USER_FORCE_SELECTED_SPM_STOP_FAILED(4,096), Failed to force select infn-vm07.management as the SPM due to a failure to stop the current SPM. 2019-07-25 12:39:18,660+02 INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] Task id 'fdcf4d1b-82fe-49a6-b233-323ebe568f8e' has passed pre-polling period time and should be polled. Pre-polling period is 60000 millis. 2019-07-25 12:39:18,660+02 INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] Task id 'fdcf4d1b-82fe-49a6-b233-323ebe568f8e' has passed pre-polling period time and should be polled. Pre-polling period is 60000 millis. 2019-07-25 12:39:18,750+02 INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] Task id 'fdcf4d1b-82fe-49a6-b233-323ebe568f8e' has passed pre-polling period time and should be polled. Pre-polling period is 60000 millis. 2019-07-25 12:39:18,750+02 *ERROR* [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] BaseAsyncTask::logEndTaskFailure: Task 'fdcf4d1b-82fe-49a6-b233-323ebe568f8e' (Parent Command 'Unknown', Parameters Type 'org.ovirt.engine.core.common.asynctasks.AsyncTaskParameters') ended with failure: 2019-07-25 12:39:18,750+02 INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] SPMAsyncTask::ClearAsyncTask: Attempting to clear task 'fdcf4d1b-82fe-49a6-b233-323ebe568f8e' 2019-07-25 12:39:18,751+02 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.SPMClearTaskVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] START, SPMClearTaskVDSCommand( SPMTaskGuidBaseVDSCommandParameters:{storagePoolId='18d57688-6ed4-43b8-bd7c-0665b55950b7', ignoreFailoverLimit='false', taskId='fdcf4d1b-82fe-49a6-b233-323ebe568f8e'}), log id: 34ae2b2f 2019-07-25 12:39:18,752+02 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMClearTaskVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] START, HSMClearTaskVDSCommand(HostName = infn-vm05.management, HSMTaskGuidBaseVDSCommandParameters:{hostId='751f3e99-b95e-4c31-bc38-77f5661a0bdc', taskId='fdcf4d1b-82fe-49a6-b233-323ebe568f8e'}), log id: d3a78ad 2019-07-25 12:39:18,757+02 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMClearTaskVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] FINISH, HSMClearTaskVDSCommand, log id: d3a78ad 2019-07-25 12:39:18,757+02 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.SPMClearTaskVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] FINISH, SPMClearTaskVDSCommand, log id: 34ae2b2f 2019-07-25 12:39:18,757+02 INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] SPMAsyncTask::ClearAsyncTask: At time of attempt to clear task 'fdcf4d1b-82fe-49a6-b233-323ebe568f8e' the response code was 'TaskStateError' and message was 'Operation is not allowed in this task state: ("can't clean in state running",)'. Task will not be cleaned 2019-07-25 12:39:18,757+02 INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] BaseAsyncTask::onTaskEndSuccess: Task 'fdcf4d1b-82fe-49a6-b233-323ebe568f8e' (Parent Command 'Unknown', Parameters Type 'org.ovirt.engine.core.common.asynctasks.AsyncTaskParameters') ended successfully. 2019-07-25 12:39:18,757+02 INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] SPMAsyncTask::ClearAsyncTask: Attempting to clear task 'fdcf4d1b-82fe-49a6-b233-323ebe568f8e' 2019-07-25 12:39:18,758+02 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.SPMClearTaskVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] START, SPMClearTaskVDSCommand( SPMTaskGuidBaseVDSCommandParameters:{storagePoolId='18d57688-6ed4-43b8-bd7c-0665b55950b7', ignoreFailoverLimit='false', taskId='fdcf4d1b-82fe-49a6-b233-323ebe568f8e'}), log id: 42de0c2b 2019-07-25 12:39:18,759+02 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMClearTaskVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] START, HSMClearTaskVDSCommand(HostName = infn-vm05.management, HSMTaskGuidBaseVDSCommandParameters:{hostId='751f3e99-b95e-4c31-bc38-77f5661a0bdc', taskId='fdcf4d1b-82fe-49a6-b233-323ebe568f8e'}), log id: 4895c79c 2019-07-25 12:39:18,764+02 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMClearTaskVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] FINISH, HSMClearTaskVDSCommand, log id: 4895c79c 2019-07-25 12:39:18,764+02 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.SPMClearTaskVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] FINISH, SPMClearTaskVDSCommand, log id: 42de0c2b 2019-07-25 12:39:18,764+02 INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] SPMAsyncTask::ClearAsyncTask: At time of attempt to clear task 'fdcf4d1b-82fe-49a6-b233-323ebe568f8e' the response code was 'TaskStateError' and message was 'Operation is not allowed in this task state: ("can't clean in state running",)'. Task will not be cleaned 2019-07-25 12:39:18,764+02 INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] Task id 'fdcf4d1b-82fe-49a6-b233-323ebe568f8e' has passed pre-polling period time and should be polled. Pre-polling period is 60000 millis. 2019-07-25 12:39:18,764+02 INFO [org.ovirt.engine.core.bll.tasks.AsyncTaskManager] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] Cleaning zombie tasks: Clearing async task 'Unknown' that started at 'Fri May 03 14:48:50 CEST 2019' 2019-07-25 12:39:18,764+02 INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] SPMAsyncTask::ClearAsyncTask: Attempting to clear task 'fdcf4d1b-82fe-49a6-b233-323ebe568f8e' 2019-07-25 12:39:18,765+02 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.SPMClearTaskVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] START, SPMClearTaskVDSCommand( SPMTaskGuidBaseVDSCommandParameters:{storagePoolId='18d57688-6ed4-43b8-bd7c-0665b55950b7', ignoreFailoverLimit='false', taskId='fdcf4d1b-82fe-49a6-b233-323ebe568f8e'}), log id: da77af2 2019-07-25 12:39:18,766+02 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMClearTaskVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] START, HSMClearTaskVDSCommand(HostName = infn-vm05.management, HSMTaskGuidBaseVDSCommandParameters:{hostId='751f3e99-b95e-4c31-bc38-77f5661a0bdc', taskId='fdcf4d1b-82fe-49a6-b233-323ebe568f8e'}), log id: 530694fb 2019-07-25 12:39:18,771+02 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMClearTaskVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] FINISH, HSMClearTaskVDSCommand, log id: 530694fb 2019-07-25 12:39:18,771+02 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.SPMClearTaskVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] FINISH, SPMClearTaskVDSCommand, log id: da77af2 2019-07-25 12:39:18,771+02 INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedThreadFactory-engineScheduled-Thread-67) [] SPMAsyncTask::ClearAsyncTask: At time of attempt to clear task 'fdcf4d1b-82fe-49a6-b233-323ebe568f8e' the response code was 'TaskStateError' and message was 'Operation is not allowed in this task state: ("can't clean in state running",)'. Task will not be cleaned there is some relation between this error and a task that has remained hanging, from SPM server: # vdsm-client Task getInfo taskID=fdcf4d1b-82fe-49a6-b233-323ebe568f8e { "verb": "prepareMerge", "id": "fdcf4d1b-82fe-49a6-b233-323ebe568f8e" } # vdsm-client Task getStatus taskID=fdcf4d1b-82fe-49a6-b233-323ebe568f8e { "message": "running job 1 of 1", "code": 0, "taskID": "fdcf4d1b-82fe-49a6-b233-323ebe568f8e", "taskResult": "", "taskState": "running" } How can I solve this problem ? Thanks a lot for your help !! Best Regards Enrico -- _______________________________________________________________________ Enrico Becchetti Servizio di Calcolo e Reti Istituto Nazionale di Fisica Nucleare - Sezione di Perugia Via Pascoli,c/o Dipartimento di Fisica 06123 Perugia (ITALY) Phone:+39 075 5852777 Mail: Enrico.Becchetti<at>pg.infn.it _______________________________________________________________________

5 15

oVirt CLI tool for automation tasks
by munnadawood＠gmail.com 14 Nov '24

14 Nov '24

We recently migrated from VMware to oVirt. I am looking for any CLI tool well suited for my automation tasks like VM create, clone, migrate 100s of Virtual machines in oVirt cluster. with VMware I was using govc (vSphere CLI built on top of govmomi). Another option I read is powercli, quite unsure if it works with oVirt. Any suggestions would be highly appreciated. Thanks!

5 6

Latest 4.5.5 centos node install username password not working.
by antonio.riggio＠mail.com 24 Oct '24

24 Oct '24

I been trying to install 4.5.5 testing and used the node installer iso. I cant login what is the username and password I have tried what others have done in the forums with no luck admin@ovirt . root admin . Also can the engine be installed from the node via the cockpit still? How can I get logged in to do this? I have used 4.3 and didnt have any of these problems. It was really simple to do. Any suggestions? grazie

4 8

Storage Domain Not synchronized, To synchronize them, please move them to maintenance and then activate.
by Arup Jyoti Thakuria 09 Sep '24

09 Sep '24

Dear All, In our Ovirt Engine Infrastructure, recently we have received an alert for one of our "Storage Domain" The alert is as mentioned below---- =================================== Storage domains with IDs [fb34e5b7-e850-4d66-ab47-3011d2000338] could not be synchronized. To synchronize them, please move them to maintenance and then activate. ========================================================== What is the consequence of this alert, if we ignore this what can happen to the infra, are we going to face any issue with the VMs, currently this infra is under production

2 1

cpu pinning validation failed - virtual cpu does not exist in vm
by parallax 05 Sep '24

05 Sep '24

server with two Gold 6346 this message appears when trying pin any cores after 14 core: 16#16_17#17_18#18_19#19_20#20_21#21_22#22 "cpu pinning validation failed - virtual cpu does not exist in vm" "Count Threads As Cores" is disabled pinning cores from 9 to 15 goes well 0#0_1#1_2#2_3#3_4#4_5#5_6#6_7#7_8#8_9#9_10#10_11#11

2 1

console certificate is not trusted
by suporte＠logicworks.pt 05 Sep '24

05 Sep '24

Hi, I just install last ovirt version ( Version 4.5.6-1.el9) using CentOS Stream 9. When trying to access the console get this error message: The certificate is not trusted. I'm using self signed certificate. Any idea? Thanks -- Jose Ferradeira http://www.logicworks.pt

5 5

Váltás a Centos Stream 9-re.
by tasnadi.peter＠kifu.gov.hu 04 Sep '24

04 Sep '24

Hello! We have a oVirt 4.5.6-1.el8 cluster. oVirt node Centos Stream 8 based. (5pcs) oVirt Hosted Engine Centos stream 8 based. We installed the hosts from an ISO image and the Hosted Engine we deployed from such a host. Link: https://resources.ovirt.org/pub/ovirt-4.5/iso/ovirt-node-ng-installer/4.5.5… How can we switch to Centos Stream 9 OS in the simplest way without downtime? Thanks in advance for the answer! Peter

2 1

Fallback Method to Start a VM if oVirt Engine is Offline
by Thomas Leitner 02 Sep '24

02 Sep '24

Hello, Is there a way to start a VM directly from the KVM host if the oVirt Engine is down or temporarily unavailable due to network issues or other reasons? thanks for any advice.

2 1

Import disk and ISO failed status "Paused by System"
by brancomrt＠gmail.com 02 Sep '24

02 Sep '24

OLVM version 8.5 OS Server OL8.10 I'm running ovirt-engine and ovirt-host on the same server. I'm having problems trying to import a qcow2 disk or an ISO to the OVLM 4.5 storage. The disk is in the status "Paused by System" and the following error is displayed: Transfer was stopped by system. Reason: failed to add host image ticket. VDSM pegasus.atech.com.br command AddImageTicketVDS failed: Image daemon is unsupported: () /var/log/vdsm/vdsm.log 2024-08-23 10:03:21,453+0000 ERROR (jsonrpc/2) [storage.taskmanager.task] (Task='483660c9-62ef-461e-903c-a62a6da2c0b3') Unexpected error (task:860) Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/vdsm/storage/task.py", line 867, in _run return fn(*args, **kargs) File "<decorator-gen-145>", line 2, in add_image_ticket File "/usr/lib/python3.6/site-packages/vdsm/common/api.py", line 33, in method ret = func(*args, **kwargs) File "/usr/lib/python3.6/site-packages/vdsm/storage/hsm.py", line 2716, in add_image_ticket imagetickets.add_ticket(ticket) File "/usr/lib/python3.6/site-packages/vdsm/storage/imagetickets.py", line 48, in wrapper raise se.ImageDaemonUnsupported() vdsm.storage.exception.ImageDaemonUnsupported: Image daemon is unsupported: () 2024-08-23 10:03:21,453+0000 INFO (jsonrpc/2) [storage.taskmanager.task] (Task='483660c9-62ef-461e-903c-a62a6da2c0b3') aborting: Task is aborted: 'value=Image daemon is unsupported: () abortedcode=483' (task:1165) 2024-08-23 10:03:21,454+0000 ERROR (jsonrpc/2) [storage.dispatcher] FINISH add_image_ticket error=Image daemon is unsupported: () (dispatcher:66) 2024-08-23 10:03:21,454+0000 INFO (jsonrpc/2) [jsonrpc.JsonRpcServer] RPC call Host.add_image_ticket failed (error 483) in 0.00 seconds (__init__:301) 2024-08-23 10:03:22,480+0000 INFO (jsonrpc/4) [vdsm.api] START getVolumeInfo(sdUUID='285dbac7-110f-439b-8904-0e7338c1d03c', spUUID='a6b1076b-2d25-436b-b715-e5a050086221', imgUUID='7367ebc3-7086-474f-8f50-0c6903de46e4', volUUID='aea06a98-3471-4bdb-a034-95614e4c2522') from=::ffff:192.168.1.2,42340, flow_id=f2eb55b2-1c95-42a1-a62e-cb827e1ed47e, task_id=6bf12ace-c722-4597-86ab-9401029e6d2f (api:31) 2024-08-23 10:03:22,485+0000 INFO (jsonrpc/4) [storage.volumemanifest] Info request: sdUUID=285dbac7-110f-439b-8904-0e7338c1d03c imgUUID=7367ebc3-7086-474f-8f50-0c6903de46e4 volUUID = aea06a98-3471-4bdb-a034-95614e4c2522 (volume:229) 2024-08-23 10:03:22,501+0000 INFO (jsonrpc/4) [storage.volumemanifest] 285dbac7-110f-439b-8904-0e7338c1d03c/7367ebc3-7086-474f-8f50-0c6903de46e4/aea06a98-3471-4bdb-a034-95614e4c2522 info is {'uuid': 'aea06a98-3471-4bdb-a034-95614e4c2522', 'type': 'SPARSE', 'format': 'RAW', 'disktype': 'ISOF', 'voltype': 'LEAF', 'capacity': '376832', 'parent': '00000000-0000-0000-0000-000000000000', 'description': '{"DiskAlias":"test.iso","DiskDescription":"test.iso"}', 'pool': '', 'domain': '285dbac7-110f-439b-8904-0e7338c1d03c', 'image': '7367ebc3-7086-474f-8f50-0c6903de46e4', 'ctime': '1724407386', 'mtime': '0', 'legality': 'ILLEGAL', 'generation': 0, 'sequence': 1, 'apparentsize': '376832', 'truesize': '4096', 'status': 'ILLEGAL', 'lease': {'path': '/rhev/data-center/mnt/pegasus.atech.com.br:_mnt_data/285dbac7-110f-439b-8904-0e7338c1d03c/images/7367ebc3-7086-474f-8f50-0c6903de46e4/aea06a98-3471-4bdb-a034-95614e4c2522.lease', 'offset': 0, 'owners': [], 'version': None}, 'children': []} (volume:268 )

2 1

What is the correct way to update Ovirt/Hosts from 4.5
by a_kagra＠jea.ca 02 Sep '24

02 Sep '24

Hello, I am currently sitting on oVirt 4.5 and I have 5 Linux hosts. I was hoping I could get some insight as to the correct way to get things updated. I am seeing the dashboard throw errors for each of my 5 hosts with the following error: Failed to check for available updates on host _______ with message 'Task Ensure Python3 is installed for CentOS/RHEL8 hosts failed to execute. Please check logs for more details: /var/log/ovirt-engine/host-deploy/ovirt-host-mgmt-ansible-check-20240822085114-10.100.50.14.log If I look at that log and grep the error I see: "fatal: [10.x.x.14]: FAILED! => {\"changed\": false, \"msg\": \"Failed to download metadata for repo 'ovirt-4.4-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]\" Here is details on my ovirt-engine host: ovirt-engine-4.5.4-1.el8.noarch yum.repos.d]# ls CentOS-Ceph-Pacific.repo epel-modular.repo CentOS-Gluster-10.repo epel-next.repo CentOS-NFV-OpenvSwitch.repo epel-next-testing.repo CentOS-OpsTools.repo epel.repo CentOS-oVirt-4.5.repo epel-testing-modular.repo CentOS-Storage-common.repo epel-testing.repo CentOS-Stream-Extras-common.repo ovirt-4.4-dependencies.repo CentOS-Stream-Extras.repo ovirt-4.4.repo elastic.repo redhat.repo And info on my hosts: OS: NAME="CentOS Stream" VERSION="8" ID="centos" ID_LIKE="rhel fedora" VERSION_ID="8" PLATFORM_ID="platform:el8" PRETTY_NAME="CentOS Stream 8" ANSI_COLOR="0;31" CPE_NAME="cpe:/o:centos:centos:8" HOME_URL="https://centos.org/" BUG_REPORT_URL="https://bugzilla.redhat.com/" REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux 8" REDHAT_SUPPORT_PRODUCT_VERSION="CentOS Stream" packages: ovirt-hosted-engine-ha-2.5.0-1.el8.noarch ovirt-vmconsole-1.0.9-1.el8.noarch ovirt-release44-4.4.10.3-1.el8.noarch python39-ovirt-imageio-common-2.4.7-1.el8.x86_64 ovirt-imageio-client-2.4.7-1.el8.x86_64 ovirt-host-4.5.0-3.el8.x86_64 ovirt-openvswitch-ovn-2.15-4.el8.noarch ovirt-imageio-common-2.4.7-1.el8.x86_64 ovirt-openvswitch-ipsec-2.15-4.el8.noarch ovirt-hosted-engine-setup-2.7.0-1.el8.noarch ovirt-engine-appliance-4.5-20221206133948.1.el8.x86_64 python3-ovirt-setup-lib-1.3.3-1.el8.noarch ovirt-host-dependencies-4.5.0-3.el8.x86_64 ovirt-vmconsole-host-1.0.9-1.el8.noarch python39-ovirt-imageio-client-2.4.7-1.el8.x86_64 ovirt-openvswitch-ovn-common-2.15-4.el8.noarch ovirt-ansible-collection-3.0.0-1.el8.noarch python39-ovirt-engine-sdk4-4.6.0-1.el8.x86_64 ovirt-provider-ovn-driver-1.2.36-1.el8.noarch ovirt-openvswitch-ovn-host-2.15-4.el8.noarch centos-release-ovirt45-8.9-1.el8s.noarch ovirt-openvswitch-2.15-4.el8.noarch cockpit-ovirt-dashboard-0.16.2-1.el8.noarch ovirt-imageio-daemon-2.4.7-1.el8.x86_64 python3-ovirt-engine-sdk4-4.6.0-1.el8.x86_64 ovirt-python-openvswitch-2.15-4.el8.noarch ovirt-hosted-engine-ha-2.5.0-1.el8.noarch Now on my ovirt-engine host, I can't run yum update _____ as it seems the mirrorlists are EOL So my question is below: What would be the best/safest way to update everything on my ovirt-engine and hosts, I am already on 4.5.4 but I know there is a current 4.5.6 release and would doing this update fix the packages on my machines?

2 1