Filed *Bug 1507214* <
https://bugzilla.redhat.com/show_bug.cgi?id=1507214>
for this issue
Alex
On Wed, Oct 18, 2017 at 3:36 PM, Nir Soffer <nsoffer(a)redhat.com> wrote:
On Wed, Oct 18, 2017 at 2:31 PM Alex K
<rightkicktech(a)gmail.com> wrote:
> For anyone that might be wondering, this errors disappeared after
> removing/adding the leases.
>
> The tasks were showing still the "Editing VM configuration" as not
> completed.
>
> I removed them by cleaning the tasks from the psql:
>
> Within engine:
>
> su - postgres
> psql
> \c engine
> select * from job order by start_time desc;
> select DeleteJob('<job id>');
>
> Alex
>
>
> On Wed, Oct 18, 2017 at 1:07 PM, Alex K <rightkicktech(a)gmail.com> wrote:
>
>> Hi all,
>>
>> While attempting to enable the VM leases for a specific VM I am
>> receiving the following error within the engine.log:
>>
>> 2017-10-18 07:56:03,186Z ERROR [org.ovirt.engine.core.dal.
>> dbbroker.auditloghandling.AuditLogDirector] (org.ovirt.thread.pool-6-thread-18)
>> [37c74b60] EVENT_ID: HOT_PLUG_LEASE_FAILED(1,220), Correlation ID:
>> 37c74b60, Job ID: fb7b0b47-3ca1-4588-99b6-2203337bcae5, Call Stack:
>> null, Custom ID: null, Custom Event ID: -1, Message: Failed to hot plug
>> lease to the VM Win-DC. The VM is running without a VM lease.
>> 2017-10-18 07:56:15,162Z ERROR
[org.ovirt.engine.core.bll.storage.lease.AddVmLeaseCommand]
>> (org.ovirt.thread.pool-6-thread-12) [37c74b60] Failure in hot plugging
>> a lease to VM 9f9a8be1-c4ed-4de8-a600-a751ae70a76b, message:
>> EngineException: org.ovirt.engine.core.vdsbroker.vdsbroker.VDSErrorException:
>> VDSGenericException: VDSErrorException: Failed to HotPlugLeaseVDS, error =
>> Virtual machine does not exist: {'vmId':
u'9f9a8be1-c4ed-4de8-a600-a751ae70a76b'},
>> code = 1 (Failed with error noVM and code 1)
>>
>> Also the tasks logs at dashboard is showing the "Editing VM
>> configuration" always as running, without the tasks completing.
>>
>
This smells like a bug, please file a bug.
Please include also vdsm log from the host the vm was running in.
>
>> The SPM host does nto lsit any running tasks:
>>
>> vdsClient -s 0 getAllTasksStatuses
>> {'status': {'message': 'OK', 'code': 0},
'allTasksStatus': {}}
>>
>
Hot plugging a lease does not involve the SPM, this is expected.
Nir