- Users - oVirt List Archives

Reminder: oVirt conference in Milan next week
by Sandro Bonazzola 07 Nov '18

07 Nov '18

Just a reminder we'll have an oVirt conference (presentation will be in Italian) in Milan next week, a good chance for meeting developers and users, exchange experiences, and learn about oVirt. More info at: http://www.ovirt-italia.it/2018/10/ovirt-conference-2018.html Thanks, -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig>

1 0

Import VM from VMware fails
by Markus Schaufler 07 Nov '18

07 Nov '18

Hi, I configured a VMware Provider (Test success) and tried to import a VM which fails shortly after starting. Failed to import Vm SK-Test-VSAN to Data Center Default, Cluster Default from engine.log: "HSMGetAllTasksStatusesVDS failed: Error creating a new volume: (u"Volume creation 9909f715-cd8a-452a-bb2a-73341b77f8af failed: Invalid parameter: 'initial size=107175936'" any ideas on that? # engine.log 2018-11-07 06:26:06,071+01 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-15) [cf1eb385-cbe4-4e73-a5f2-a307bd39fa0a] Command 'ImportVmFromExternalProvider' (id: 'c8d4cf1b-8465-4501-9930-0b06262477a4') waiting on child command id: '02112e67-8dd5-4ef8-95ac-eeb9a4b39d0a' type:'ConvertVm' to complete 2018-11-07 06:26:09,979+01 INFO [org.ovirt.engine.core.bll.exportimport.ImportVmFromExternalProviderCommand] (default task-292) [bd9e622c-574f-4cc6-a6b3-284a7a6dbdbc] Lock Acquired to object 'EngineLock:{exclusiveLocks='[42205902-f5d8-fd29-fcb3-926dbf8935e9=VM, SK-Test-VSAN=VM_NAME]', sharedLocks=''}' 2018-11-07 06:26:10,183+01 INFO [org.ovirt.engine.core.bll.exportimport.ImportVmFromExternalProviderCommand] (EE-ManagedThreadFactory-engine-Thread-39664) [bd9e622c-574f-4cc6-a6b3-284a7a6dbdbc] Running command: ImportVmFromExternalProviderCommand internal: false. Entities affected : ID: 5e6850cd-5e72-47b3-a19d-8c748c884c42 Type: StorageAction group IMPORT_EXPORT_VM with role type ADMIN 2018-11-07 06:26:10,196+01 WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-39664) [bd9e622c-574f-4cc6-a6b3-284a7a6dbdbc] EVENT_ID: MAC_ADDRESS_IS_EXTERNAL(925), VM SK-Test-VSAN has MAC address(es) 00:50:56:a0:1b:18, which is/are out of its MAC pool definitions. 2018-11-07 06:26:10,369+01 INFO [org.ovirt.engine.core.bll.storage.disk.AddDiskCommand] (EE-ManagedThreadFactory-engine-Thread-39664) [bd9e622c-574f-4cc6-a6b3-284a7a6dbdbc] Running command: AddDiskCommand internal: true. Entities affected : ID: 42205902-f5d8-fd29-fcb3-926dbf8935e9 Type: VMAction group CONFIGURE_VM_STORAGE with role type USER, ID: 5e6850cd-5e72-47b3-a19d-8c748c884c42 Type: StorageAction group CREATE_DISK with role type USER 2018-11-07 06:26:10,383+01 INFO [org.ovirt.engine.core.bll.storage.disk.image.AddImageFromScratchCommand] (EE-ManagedThreadFactory-engine-Thread-39664) [bd9e622c-574f-4cc6-a6b3-284a7a6dbdbc] Running command: AddImageFromScratchCommand internal: true. Entities affected : ID: 5e6850cd-5e72-47b3-a19d-8c748c884c42 Type: Storage 2018-11-07 06:26:10,402+01 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.CreateImageVDSCommand] (EE-ManagedThreadFactory-engine-Thread-39664) [bd9e622c-574f-4cc6-a6b3-284a7a6dbdbc] START, CreateImageVDSCommand( CreateImageVDSCommandParameters:{storagePoolId='6d4eea22-c7cb-11e8-a006-00163e699560', ignoreFailoverLimit='false', storageDomainId='5e6850cd-5e72-47b3-a19d-8c748c884c42', imageGroupId='9703780a-ff5d-48e1-929c-6526d63fddb0', imageSizeInBytes='26843545600', volumeFormat='COW', newImageId='9909f715-cd8a-452a-bb2a-73341b77f8af', imageType='Sparse', newImageDescription='{"DiskAlias":"SK-Test_VSAN","DiskDescription":""}', imageInitialSizeInBytes='54874079232'}), log id: 44235172 2018-11-07 06:26:10,402+01 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.CreateImageVDSCommand] (EE-ManagedThreadFactory-engine-Thread-39664) [bd9e622c-574f-4cc6-a6b3-284a7a6dbdbc] -- executeIrsBrokerCommand: calling 'createVolume' with two new parameters: description and UUID 2018-11-07 06:26:10,457+01 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.CreateImageVDSCommand] (EE-ManagedThreadFactory-engine-Thread-39664) [bd9e622c-574f-4cc6-a6b3-284a7a6dbdbc] FINISH, CreateImageVDSCommand, return: 9909f715-cd8a-452a-bb2a-73341b77f8af, log id: 44235172 2018-11-07 06:26:10,460+01 INFO [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (EE-ManagedThreadFactory-engine-Thread-39664) [bd9e622c-574f-4cc6-a6b3-284a7a6dbdbc] CommandAsyncTask::Adding CommandMultiAsyncTasks object for command 'e05cf461-111a-47d3-8bb1-1455dde5be3c' 2018-11-07 06:26:10,460+01 INFO [org.ovirt.engine.core.bll.CommandMultiAsyncTasks] (EE-ManagedThreadFactory-engine-Thread-39664) [bd9e622c-574f-4cc6-a6b3-284a7a6dbdbc] CommandMultiAsyncTasks::attachTask: Attaching task '6dbfe14e-1ce5-4a77-aff9-58da486a458c' to command 'e05cf461-111a-47d3-8bb1-1455dde5be3c'. 2018-11-07 06:26:10,471+01 INFO [org.ovirt.engine.core.bll.tasks.AsyncTaskManager] (EE-ManagedThreadFactory-engine-Thread-39664) [bd9e622c-574f-4cc6-a6b3-284a7a6dbdbc] Adding task '6dbfe14e-1ce5-4a77-aff9-58da486a458c' (Parent Command 'AddImageFromScratch', Parameters Type 'org.ovirt.engine.core.common.asynctasks.AsyncTaskParameters'), polling hasn't started yet.. 2018-11-07 06:26:10,478+01 INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedThreadFactory-engine-Thread-39664) [bd9e622c-574f-4cc6-a6b3-284a7a6dbdbc] BaseAsyncTask::startPollingTask: Starting to poll task '6dbfe14e-1ce5-4a77-aff9-58da486a458c'. 2018-11-07 06:26:10,498+01 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-39664) [bd9e622c-574f-4cc6-a6b3-284a7a6dbdbc] EVENT_ID: ADD_DISK_INTERNAL(2,036), Add-Disk operation of 'SK-Test_VSAN' was initiated by the system. 2018-11-07 06:26:10,544+01 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-39664) [bd9e622c-574f-4cc6-a6b3-284a7a6dbdbc] EVENT_ID: IMPORTEXPORT_STARTING_IMPORT_VM(1,165), Starting to import Vm SK-Test-VSAN to Data Center Default, Cluster Default 2018-11-07 06:26:11,079+01 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-65) [bd9e622c-574f-4cc6-a6b3-284a7a6dbdbc] Command 'ImportVmFromExternalProvider' (id: '7a8529e5-d463-45fd-9f1c-2a261c84e458') waiting on child command id: '578ed27c-f891-4279-b0f4-84b63b53db34' type:'AddDisk' to complete 2018-11-07 06:26:11,081+01 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-65) [bd9e622c-574f-4cc6-a6b3-284a7a6dbdbc] Command 'AddDisk' (id: '578ed27c-f891-4279-b0f4-84b63b53db34') waiting on child command id: 'e05cf461-111a-47d3-8bb1-1455dde5be3c' type:'AddImageFromScratch' to complete 2018-11-07 06:26:13,085+01 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-48) [bd9e622c-574f-4cc6-a6b3-284a7a6dbdbc] Command 'ImportVmFromExternalProvider' (id: '7a8529e5-d463-45fd-9f1c-2a261c84e458') waiting on child command id: '578ed27c-f891-4279-b0f4-84b63b53db34' type:'AddDisk' to complete 2018-11-07 06:26:13,086+01 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-48) [bd9e622c-574f-4cc6-a6b3-284a7a6dbdbc] Command 'AddDisk' (id: '578ed27c-f891-4279-b0f4-84b63b53db34') waiting on child command id: 'e05cf461-111a-47d3-8bb1-1455dde5be3c' type:'AddImageFromScratch' to complete 2018-11-07 06:26:15,894+01 INFO [org.ovirt.engine.core.bll.tasks.AsyncTaskManager] (EE-ManagedThreadFactory-engineScheduled-Thread-83) [] Polling and updating Async Tasks: 1 tasks, 1 tasks to poll now 2018-11-07 06:26:15,898+01 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMGetAllTasksStatusesVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-83) [] Failed in 'HSMGetAllTasksStatusesVDS' method 2018-11-07 06:26:15,901+01 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-83) [] EVENT_ID: VDS_BROKER_COMMAND_FAILURE(10,802), VDSM VIRZ01-101 command HSMGetAllTasksStatusesVDS failed: Error creating a new volume: (u"Volume creation 9909f715-cd8a-452a-bb2a-73341b77f8af failed: Invalid parameter: 'initial size=107175936'",) 2018-11-07 06:26:15,901+01 INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedThreadFactory-engineScheduled-Thread-83) [] SPMAsyncTask::PollTask: Polling task '6dbfe14e-1ce5-4a77-aff9-58da486a458c' (Parent Command 'AddImageFromScratch', Parameters Type 'org.ovirt.engine.core.common.asynctasks.AsyncTaskParameters') returned status 'finished', result 'cleanSuccess'. 2018-11-07 06:26:15,903+01 ERROR [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedThreadFactory-engineScheduled-Thread-83) [] BaseAsyncTask::logEndTaskFailure: Task '6dbfe14e-1ce5-4a77-aff9-58da486a458c' (Parent Command 'AddImageFromScratch', Parameters Type 'org.ovirt.engine.core.common.asynctasks.AsyncTaskParameters') ended with failure: -- Result: 'cleanSuccess' -- Message: 'VDSGenericException: VDSErrorException: Failed to HSMGetAllTasksStatusesVDS, error = Error creating a new volume: (u"Volume creation 9909f715-cd8a-452a-bb2a-73341b77f8af failed: Invalid parameter: 'initial size=107175936'",), code = 205', -- Exception: 'VDSGenericException: VDSErrorException: Failed to HSMGetAllTasksStatusesVDS, error = Error creating a new volume: (u"Volume creation 9909f715-cd8a-452a-bb2a-73341b77f8af failed: Invalid parameter: 'initial size=107175936'",), code = 205' 2018-11-07 06:26:15,905+01 INFO [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (EE-ManagedThreadFactory-engineScheduled-Thread-83) [] CommandAsyncTask::endActionIfNecessary: All tasks of command 'e05cf461-111a-47d3-8bb1-1455dde5be3c' has ended -> executing 'endAction' 2018-11-07 06:26:15,905+01 INFO [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (EE-ManagedThreadFactory-engineScheduled-Thread-83) [] CommandAsyncTask::endAction: Ending action for '1' tasks (command ID: 'e05cf461-111a-47d3-8bb1-1455dde5be3c'): calling endAction '. 2018-11-07 06:26:15,905+01 INFO [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (EE-ManagedThreadFactory-engine-Thread-39669) [] CommandAsyncTask::endCommandAction [within thread] context: Attempting to endAction 'AddImageFromScratch', 2018-11-07 06:26:15,911+01 INFO [org.ovirt.engine.core.bll.storage.disk.image.AddImageFromScratchCommand] (EE-ManagedThreadFactory-engine-Thread-39669) [bd9e622c-574f-4cc6-a6b3-284a7a6dbdbc] Command [id=e05cf461-111a-47d3-8bb1-1455dde5be3c]: Updating status to 'FAILED', The command end method logic will be executed by one of its parent commands. 2018-11-07 06:26:15,911+01 INFO [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (EE-ManagedThreadFactory-engine-Thread-39669) [bd9e622c-574f-4cc6-a6b3-284a7a6dbdbc] CommandAsyncTask::HandleEndActionResult [within thread]: endAction for action type 'AddImageFromScratch' completed, handling the result. 2018-11-07 06:26:15,911+01 INFO [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (EE-ManagedThreadFactory-engine-Thread-39669) [bd9e622c-574f-4cc6-a6b3-284a7a6dbdbc] CommandAsyncTask::HandleEndActionResult [within thread]: endAction for action type 'AddImageFromScratch' succeeded, clearing tasks. 2018-11-07 06:26:15,911+01 INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedThreadFactory-engine-Thread-39669) [bd9e622c-574f-4cc6-a6b3-284a7a6dbdbc] SPMAsyncTask::ClearAsyncTask: Attempting to clear task '6dbfe14e-1ce5-4a77-aff9-58da486a458c' 2018-11-07 06:26:15,911+01 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.SPMClearTaskVDSCommand] (EE-ManagedThreadFactory-engine-Thread-39669) [bd9e622c-574f-4cc6-a6b3-284a7a6dbdbc] START, SPMClearTaskVDSCommand( SPMTaskGuidBaseVDSCommandParameters:{storagePoolId='6d4eea22-c7cb-11e8-a006-00163e699560', ignoreFailoverLimit='false', taskId='6dbfe14e-1ce5-4a77-aff9-58da486a458c'}), log id: adf17a1 2018-11-07 06:26:15,912+01 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMClearTaskVDSCommand] (EE-ManagedThreadFactory-engine-Thread-39669) [bd9e622c-574f-4cc6-a6b3-284a7a6dbdbc] START, HSMClearTaskVDSCommand(HostName = VIRZ01-101, HSMTaskGuidBaseVDSCommandParameters:{hostId='9edfd1cd-261b-4b4f-832c-baa96e229ea7', taskId='6dbfe14e-1ce5-4a77-aff9-58da486a458c'}), log id: 60cae22f 2018-11-07 06:26:15,916+01 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMClearTaskVDSCommand] (EE-ManagedThreadFactory-engine-Thread-39669) [bd9e622c-574f-4cc6-a6b3-284a7a6dbdbc] FINISH, HSMClearTaskVDSCommand, log id: 60cae22f 2018-11-07 06:26:15,916+01 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.SPMClearTaskVDSCommand] (EE-ManagedThreadFactory-engine-Thread-39669) [bd9e622c-574f-4cc6-a6b3-284a7a6dbdbc] FINISH, SPMClearTaskVDSCommand, log id: adf17a1 2018-11-07 06:26:15,919+01 INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedThreadFactory-engine-Thread-39669) [bd9e622c-574f-4cc6-a6b3-284a7a6dbdbc] BaseAsyncTask::removeTaskFromDB: Removed task '6dbfe14e-1ce5-4a77-aff9-58da486a458c' from DataBase 2018-11-07 06:26:15,919+01 INFO [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (EE-ManagedThreadFactory-engine-Thread-39669) [bd9e622c-574f-4cc6-a6b3-284a7a6dbdbc] CommandAsyncTask::HandleEndActionResult [within thread]: Removing CommandMultiAsyncTasks object for entity 'e05cf461-111a-47d3-8bb1-1455dde5be3c' 2018-11-07 06:26:16,092+01 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-37) [cf1eb385-cbe4-4e73-a5f2-a307bd39fa0a] Command 'ImportVmFromExternalProvider' (id: 'c8d4cf1b-8465-4501-9930-0b06262477a4') waiting on child command id: '02112e67-8dd5-4ef8-95ac-eeb9a4b39d0a' type:'ConvertVm' to complete 2018-11-07 06:26:17,097+01 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-39) [bd9e622c-574f-4cc6-a6b3-284a7a6dbdbc] Command 'ImportVmFromExternalProvider' (id: '7a8529e5-d463-45fd-9f1c-2a261c84e458') waiting on child command id: '578ed27c-f891-4279-b0f4-84b63b53db34' type:'AddDisk' to complete 2018-11-07 06:26:17,099+01 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-39) [bd9e622c-574f-4cc6-a6b3-284a7a6dbdbc] Command 'AddDisk' id: '578ed27c-f891-4279-b0f4-84b63b53db34' child commands '[e05cf461-111a-47d3-8bb1-1455dde5be3c]' executions were completed, status 'FAILED' 2018-11-07 06:26:18,104+01 ERROR [org.ovirt.engine.core.bll.storage.disk.AddDiskCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-81) [bd9e622c-574f-4cc6-a6b3-284a7a6dbdbc] Ending command 'org.ovirt.engine.core.bll.storage.disk.AddDiskCommand' with failure. 2018-11-07 06:26:18,109+01 ERROR [org.ovirt.engine.core.bll.storage.disk.image.AddImageFromScratchCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-81) [bd9e622c-574f-4cc6-a6b3-284a7a6dbdbc] Ending command 'org.ovirt.engine.core.bll.storage.disk.image.AddImageFromScratchCommand' with failure. 2018-11-07 06:26:18,359+01 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-81) [] EVENT_ID: USER_ADD_DISK_FINISHED_FAILURE(2,022), Add-Disk operation failed to complete. 2018-11-07 06:26:19,368+01 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-34) [bd9e622c-574f-4cc6-a6b3-284a7a6dbdbc] Command 'ImportVmFromExternalProvider' id: '7a8529e5-d463-45fd-9f1c-2a261c84e458' child commands '[578ed27c-f891-4279-b0f4-84b63b53db34]' executions were completed, status 'FAILED' 2018-11-07 06:26:20,394+01 ERROR [org.ovirt.engine.core.bll.exportimport.ImportVmFromExternalProviderCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-90) [bd9e622c-574f-4cc6-a6b3-284a7a6dbdbc] Ending command 'org.ovirt.engine.core.bll.exportimport.ImportVmFromExternalProviderCommand' with failure. 2018-11-07 06:26:20,534+01 INFO [org.ovirt.engine.core.bll.storage.disk.image.RemoveAllVmImagesCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-90) [7a1c5fb3] Running command: RemoveAllVmImagesCommand internal: true. Entities affected : ID: 42205902-f5d8-fd29-fcb3-926dbf8935e9 Type: VM 2018-11-07 06:26:20,545+01 INFO [org.ovirt.engine.core.bll.storage.disk.image.RemoveImageCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-90) [7a1c5fb3] Running command: RemoveImageCommand internal: true. Entities affected : ID: 00000000-0000-0000-0000-000000000000 Type: Storage 2018-11-07 06:26:20,570+01 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-90) [7a1c5fb3] START, DeleteImageGroupVDSCommand( DeleteImageGroupVDSCommandParameters:{storagePoolId='6d4eea22-c7cb-11e8-a006-00163e699560', ignoreFailoverLimit='false', storageDomainId='5e6850cd-5e72-47b3-a19d-8c748c884c42', imageGroupId='9703780a-ff5d-48e1-929c-6526d63fddb0', postZeros='false', discard='false', forceDelete='false'}), log id: 7de025db 2018-11-07 06:26:20,694+01 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-90) [7a1c5fb3] EVENT_ID: IRS_BROKER_COMMAND_FAILURE(10,803), VDSM command DeleteImageGroupVDS failed: Image does not exist in domain: u'image=9703780a-ff5d-48e1-929c-6526d63fddb0, domain=5e6850cd-5e72-47b3-a19d-8c748c884c42' 2018-11-07 06:26:20,694+01 ERROR [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-90) [7a1c5fb3] Command 'DeleteImageGroupVDSCommand( DeleteImageGroupVDSCommandParameters:{storagePoolId='6d4eea22-c7cb-11e8-a006-00163e699560', ignoreFailoverLimit='false', storageDomainId='5e6850cd-5e72-47b3-a19d-8c748c884c42', imageGroupId='9703780a-ff5d-48e1-929c-6526d63fddb0', postZeros='false', discard='false', forceDelete='false'})' execution failed: IRSGenericException: IRSErrorException: Image does not exist in domain: u'image=9703780a-ff5d-48e1-929c-6526d63fddb0, domain=5e6850cd-5e72-47b3-a19d-8c748c884c42' 2018-11-07 06:26:20,694+01 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-90) [7a1c5fb3] FINISH, DeleteImageGroupVDSCommand, log id: 7de025db 2018-11-07 06:26:20,694+01 INFO [org.ovirt.engine.core.bll.storage.disk.image.RemoveImageCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-90) [7a1c5fb3] Disk '9703780a-ff5d-48e1-929c-6526d63fddb0' doesn't exist on storage domain '5e6850cd-5e72-47b3-a19d-8c748c884c42', rolling forward 2018-11-07 06:26:20,858+01 INFO [org.ovirt.engine.core.bll.tasks.AsyncTaskManager] (EE-ManagedThreadFactory-engineScheduled-Thread-90) [7a1c5fb3] Removed task '90cd47dc-1b40-45c2-8991-9eca1ff1d63a' from DataBase 2018-11-07 06:26:20,861+01 INFO [org.ovirt.engine.core.bll.CommandCompensator] (EE-ManagedThreadFactory-engineScheduled-Thread-90) [7a1c5fb3] Command [id=7a8529e5-d463-45fd-9f1c-2a261c84e458]: Compensating NEW_ENTITY_ID of org.ovirt.engine.core.common.businessentities.network.VmNetworkStatistics; snapshot: 8b933069-ccb8-4752-b936-63d6a37f49a8. 2018-11-07 06:26:20,862+01 INFO [org.ovirt.engine.core.bll.CommandCompensator] (EE-ManagedThreadFactory-engineScheduled-Thread-90) [7a1c5fb3] Command [id=7a8529e5-d463-45fd-9f1c-2a261c84e458]: Compensating NEW_ENTITY_ID of org.ovirt.engine.core.common.businessentities.network.VmNetworkInterface; snapshot: 8b933069-ccb8-4752-b936-63d6a37f49a8. 2018-11-07 06:26:20,863+01 INFO [org.ovirt.engine.core.bll.CommandCompensator] (EE-ManagedThreadFactory-engineScheduled-Thread-90) [7a1c5fb3] Command [id=7a8529e5-d463-45fd-9f1c-2a261c84e458]: Compensating TRANSIENT_ENTITY of org.ovirt.engine.core.common.businessentities.ReleaseMacsTransientCompensation; snapshot: org.ovirt.engine.core.common.businessentities.ReleaseMacsTransientCompensation@23fd0e49. 2018-11-07 06:26:20,863+01 INFO [org.ovirt.engine.core.bll.CommandCompensator] (EE-ManagedThreadFactory-engineScheduled-Thread-90) [7a1c5fb3] Command [id=7a8529e5-d463-45fd-9f1c-2a261c84e458]: Compensating NEW_ENTITY_ID of org.ovirt.engine.core.common.businessentities.VmStatistics; snapshot: 42205902-f5d8-fd29-fcb3-926dbf8935e9. 2018-11-07 06:26:20,864+01 INFO [org.ovirt.engine.core.bll.CommandCompensator] (EE-ManagedThreadFactory-engineScheduled-Thread-90) [7a1c5fb3] Command [id=7a8529e5-d463-45fd-9f1c-2a261c84e458]: Compensating NEW_ENTITY_ID of org.ovirt.engine.core.common.businessentities.VmDynamic; snapshot: 42205902-f5d8-fd29-fcb3-926dbf8935e9. 2018-11-07 06:26:20,865+01 INFO [org.ovirt.engine.core.bll.CommandCompensator] (EE-ManagedThreadFactory-engineScheduled-Thread-90) [7a1c5fb3] Command [id=7a8529e5-d463-45fd-9f1c-2a261c84e458]: Compensating NEW_ENTITY_ID of org.ovirt.engine.core.common.businessentities.Snapshot; snapshot: b1551a3a-ecb7-4031-ad7b-0c47a97d341a. 2018-11-07 06:26:20,866+01 INFO [org.ovirt.engine.core.bll.CommandCompensator] (EE-ManagedThreadFactory-engineScheduled-Thread-90) [7a1c5fb3] Command [id=7a8529e5-d463-45fd-9f1c-2a261c84e458]: Compensating NEW_ENTITY_ID of org.ovirt.engine.core.common.businessentities.VmStatic; snapshot: 42205902-f5d8-fd29-fcb3-926dbf8935e9. 2018-11-07 06:26:20,872+01 INFO [org.ovirt.engine.core.bll.exportimport.ImportVmFromExternalProviderCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-90) [7a1c5fb3] Lock freed to object 'EngineLock:{exclusiveLocks='[42205902-f5d8-fd29-fcb3-926dbf8935e9=VM, SK-Test-VSAN=VM_NAME]', sharedLocks=''}' 2018-11-07 06:26:20,882+01 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-90) [7a1c5fb3] EVENT_ID: IMPORTEXPORT_IMPORT_VM_FAILED(1,153), Failed to import Vm SK-Test-VSAN to Data Center Default, Cluster Default

1 0

Hardware for oVirt
by p.staniforth＠leedsbeckett.ac.uk 06 Nov '18

06 Nov '18

Hello, we are looking to expand our oVirt system, at present we use HPE ProLiant DL360 Gen9 servers but are considering using Broadberry TN200B7108-X4L Multi Node Servers. I was wondering if anyone had experience of using them, they are quad-node systems and I assume we can use them as 4 oVirt nodes. Thanks, Paul S.

1 0

Configuring Ovirt + ACPI
by David Johnson 06 Nov '18

06 Nov '18

Good day all, Is there a simple step-by-step instruction to give my cluster controller the ability to turn the power for my compute nodes on and off? I am running ovirt 4.7.2 on Centos 7. My compute nodes are on Supermicro X7QC3 hosts. I know it is supposed to be there since every time I look at the dashbaord it complains that "Host has disabled power management". I imagine it is supposed to be trivial to configure. What I keep running into with the documents is the assumption that you already know what to do before you read the documents. This makes for a dizzy cycle of digging through various feature documents, manuals, etc, to end up back where I started. Any assistance would be appreciated. Regards, David Johnson Director of Development, Maxis Technology 844.696.2947 ext 702 (o) | 479.531.3590 (c) djohnson(a)maxistechnology.com [image: Maxis Techncology] <http://www.maxistechnology.com> www.maxistechnology.com *stay connected <http://www.linkedin.com/in/pojoguy>*

4 3

Foreman integration / CDRom boot ?
by jeanbaptiste＠nfrance.com 06 Nov '18

06 Nov '18

Hello everybody, Is there a way to make work Foreman/OVirt provisioning integration without use of DHCP ? I explain: On some of my networks, I don't want to use DHCP for provisioning, so I want to provision Foreman / OVirt VM with CDRom tool, After some research, bootdisk plugin seem mandatory: https://github.com/theforeman/foreman_bootdisk. I've install it succesfully, but I can't provision VM with Boot disk based Provisioning Method ( UI > Create Host > Operating System). Is it possible to boot a Foreman / OVirt VM to CDRom ? (or Network Based with DHCP is mandatory for provisioning ?) Regards,

1 0

Involuntary emergency upgrade from 4.1 to 4.2
by djohnson＠maxistechnology.com 05 Nov '18

05 Nov '18

I'm looking for a hand in recovering my ovirt cluster from a hardware failure. The hard drive on my cluster controller failed, and I would like to recover from backup. The problem is, the cluster was 4.1, which is less than a year old, but was nevertheless removed from the active repositories back in May. 4.2 will not recover from 4.1 backups. The storage domains are all intact (I think), and the hosts are still running (unmanaged). I've tried to manually restore the engine from backups, but either the upgrade is reinitializing or I am missing something. Any ideas?

6 13

[ANN] oVirt 4.2.7 is now generally available
by Sandro Bonazzola 05 Nov '18

05 Nov '18

The oVirt Project is pleased to announce the general availability of oVirt 4.2.7, as of November 2nd, 2018. This update is the seventh in a series of stabilization updates to the 4.2 series. This release is available now for: * Red Hat Enterprise Linux 7.5 or later (7.6 recommended) * CentOS Linux (or similar) 7.5 or later This release supports Hypervisor Hosts running: * Red Hat Enterprise Linux 7.5 or later (7.6 recommended) * CentOS Linux (or similar) 7.5 or later * oVirt Node 4.2 See the release notes [1] for installation / upgrade instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is available - oVirt Node update is available, ISO will be available soon [2] - oVirt Tools Setup ISO is available[2] oVirt Node has been updated including: - oVirt 4.2.7: http://www.ovirt.org/release/4.2.7/ - Ansible 2.7.0: https://github.com/ansible/ansible/blob/stable-2.7/changelogs/CHANGELOG-v2.… - GlusterFS 3.12.15: https://docs.gluster.org/en/latest/release-notes/3.12.15/ CentOS Errata included: - CEBA-2018:3013 CentOS 7 tzdata BugFix Update <https://lists.centos.org/pipermail/centos-announce/2018-October/023074.html> - centos-release-7-5.1804.5.el7.centos update <https://lists.centos.org/pipermail/centos-announce/2018-October/023050.html> Updated packages: +ansible-2.7.0-1.el7.noarch +centos-release-7-5.1804.5.el7.centos.x86_64 +cockpit-ovirt-dashboard-0.11.37-1.el7.noarch +glusterfs-3.12.15-1.el7.x86_64 +glusterfs-api-3.12.15-1.el7.x86_64 +glusterfs-cli-3.12.15-1.el7.x86_64 +glusterfs-client-xlators-3.12.15-1.el7.x86_64 +glusterfs-events-3.12.15-1.el7.x86_64 +glusterfs-fuse-3.12.15-1.el7.x86_64 +glusterfs-geo-replication-3.12.15-1.el7.x86_64 +glusterfs-gnfs-3.12.15-1.el7.x86_64 +glusterfs-libs-3.12.15-1.el7.x86_64 +glusterfs-rdma-3.12.15-1.el7.x86_64 +glusterfs-server-3.12.15-1.el7.x86_64 +imgbased-1.0.29-1.el7.noarch +ovirt-hosted-engine-ha-2.2.18-1.el7.noarch +ovirt-hosted-engine-setup-2.2.30-1.el7.noarch +ovirt-imageio-common-1.4.5-0.el7.x86_64 +ovirt-imageio-daemon-1.4.5-0.el7.noarch +ovirt-node-ng-image-update-placeholder-4.2.7-1.el7.noarch +ovirt-provider-ovn-driver-1.2.16-1.el7.noarch +ovirt-release-host-node-4.2.7-1.el7.noarch +ovirt-release42-4.2.7-1.el7.noarch +pulp-rpm-handlers-2.13.4.9-1.el7.noarch +python-imgbased-1.0.29-1.el7.noarch +python-ovirt-engine-sdk4-4.2.9-2.el7.x86_64 +python-pulp-agent-lib-2.13.4.14-1.el7.noarch +python-pulp-common-2.13.4.14-1.el7.noarch +python-pulp-rpm-common-2.13.4.9-1.el7.noarch +python2-gluster-3.12.15-1.el7.x86_64 +python2-pyOpenSSL-17.3.0-3.el7.noarch +qemu-img-ev-2.10.0-21.el7_5.7.1.x86_64 +qemu-kvm-common-ev-2.10.0-21.el7_5.7.1.x86_64 +qemu-kvm-ev-2.10.0-21.el7_5.7.1.x86_64 +tzdata-2018f-2.el7.noarch +vdsm-4.20.43-1.el7.x86_64 +vdsm-api-4.20.43-1.el7.noarch +vdsm-client-4.20.43-1.el7.noarch +vdsm-common-4.20.43-1.el7.noarch +vdsm-gluster-4.20.43-1.el7.x86_64 +vdsm-hook-ethtool-options-4.20.43-1.el7.noarch +vdsm-hook-fcoe-4.20.43-1.el7.noarch +vdsm-hook-openstacknet-4.20.43-1.el7.noarch +vdsm-hook-vhostmd-4.20.43-1.el7.noarch +vdsm-hook-vmfex-dev-4.20.43-1.el7.noarch +vdsm-http-4.20.43-1.el7.noarch +vdsm-jsonrpc-4.20.43-1.el7.noarch +vdsm-network-4.20.43-1.el7.x86_64 +vdsm-python-4.20.43-1.el7.noarch +vdsm-yajsonrpc-4.20.43-1.el7.noarch Additional Resources: * Read more about the oVirt 4.2.7 release highlights: http://www.ovirt.org/release/4.2.7/ * Get more oVirt Project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] http://www.ovirt.org/release/4.2.7/ [2] http://resources.ovirt.org/pub/ovirt-4.2/iso/ -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig>

2 2

Ignore disabled users (AD)
by Colin Coe 04 Nov '18

04 Nov '18

Hi all Running RHV 4.1.10 with AD integration (ovirt-engine-extension-aaa-ldap), I'd like to prevent disabled users from appearing in the Users or Permissions tab. In addition, I'd like to exclude "example.com/PROD/Users/Admin" from being searched for the above, is that possible? My current config file is "/etc/ovirt-engine/aaa/example.com.properties": --- include = <ad.properties> vars.domain = example.com vars.user = CN=user,OU=Restricted,OU=Users,OU=PROD,DC=example,DC=com vars.password = passsword pool.default.auth.simple.bindDN = ${global:vars.user} pool.default.auth.simple.password = ${global:vars.password} pool.default.serverset.type = srvrecord pool.default.serverset.srvrecord.domain = ${global:vars.domain} pool.default.serverset.srvrecord.domain-conversion.type = regex pool.default.serverset.srvrecord.domain-conversion.regex.pattern = ^(?<domain>.*)$ pool.default.serverset.srvrecord.domain-conversion.regex.replacement = DefaultSite._sites.${domain} --- Thanks CC

1 1

oVirt deployment with GlusterFS with replica 3 arbiter 1
by hunter86_bg＠yahoo.com 04 Nov '18

04 Nov '18

Hello community, I am planing to deploy a lab with oVirt and I would like to know if the design in my mind has any flaws. Current plan is to deploy oVirt on 2 workstations with 24GB of RAM and 8 threads each while the 3rd machine will be a VM in a public Cloud and will be used for GlusterFS arbiter. Is it a problem if the arbiter is a vanilla CentOS 7 . I am affraid that oVirt will require all GlusterFS nodes to be also oVirt Hosts, but the VM will lack the necessary resources and I would like to not use that 3rd system. Is this idea possible ? Thanks for reading this confusing post and I hope I managed to explain my idea. Best Regards, Strahil

2 2

iSCSI Boot from SAN
by Alan G 03 Nov '18

03 Nov '18

Hi, I'm setting up a lab with oVirt 4.2. All hosts are disk-less and boot from a NetApp using iSCSI. All storage domains are also iSCSI, to the same NetApp as BFS. Whenever I put a host into maintenance vdsm seems to try to un-mount all iSCSI partitions including the OS partition, causing the host fail. Is this a supported configuration? Thanks, Alan

2 3