Bug 1653230 - Starting the HA VMs with lease is failing when using ovirt-ansible-disaster-recovery role
Summary: Starting the HA VMs with lease is failing when using ovirt-ansible-disaster-r...
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-ansible-roles
Version: 4.2.7
Hardware: All
OS: Linux
Target Milestone: ovirt-4.3.0
: ---
Assignee: Eyal Shenitzky
QA Contact: Yosi Ben Shimon
Depends On:
Blocks: 1676427
TreeView+ depends on / blocked
Reported: 2018-11-26 10:34 UTC by nijin ashok
Modified: 2020-08-03 15:37 UTC (History)
7 users (show)

Fixed In Version: ovirt-engine-4.3.0_rc2
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1676427 (view as bug list)
Last Closed: 2019-05-08 12:34:23 UTC
oVirt Team: Storage
Target Upstream Version:
lsvaty: testing_plan_complete-

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 3736931 0 None None None 2018-12-05 09:10:34 UTC
Red Hat Product Errata RHEA-2019:1064 0 None None None 2019-05-08 12:34:37 UTC
oVirt gerrit 96627 0 master MERGED core: validate VM lease exists on storage before adding it 2020-02-25 13:19:44 UTC

Description nijin ashok 2018-11-26 10:34:34 UTC
Description of problem:

While importing the VM from the storage domain in the DR site and starting the same using ovirt-ansible-disaster-recovery role, the VM may fail to start with the error below. 

2018-11-26 02:02:53,670-05 WARN  [org.ovirt.engine.core.bll.RunVmCommand] (default task-38) [05a1b0c9-a098-413f-9a93-9d086096c345] Validation of action 'RunVm' failed for user admin@internal-authz. Reasons: VAR__ACTION__RUN,VAR__TYPE__VM,ACTION_TYPE_FAILED_INVALID_VM_LEASE
2018-11-26 02:02:53,670-05 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-38) [05a1b0c9-a098-413f-9a93-9d086096c345] EVENT_ID: USER_FAILED_RUN_VM(54), Failed to run VM ha_vm due to a failed validation: [Cannot run VM. Invalid VM lease. Please note that it may take few minutes to create the lease.] (User: admin@internal-authz).

The ansible is trying to start the VMs immediately after registering the same. However, by this time, the storage lease addition operation will be still going on for the VM and it will fail with the mentioned error.

Version-Release number of selected component (if applicable):

RHV 4.2.7

How reproducible:

100 %

Steps to Reproduce:

1. Test the failover using ovirt-ansible-disaster-recovery role which is having HA VMs with the lease.
2. We can observe that these VMs will fail to start with the mentioned error.

Actual results:

HA VMs with the lease is failing to start during Active Passive DR failover.

Expected results:

HA VMs should start.

Additional info:

Comment 2 Yosi Ben Shimon 2019-02-06 16:05:47 UTC
Tested using:

A running HA VM on the primary site failover (and start) successfully on the secondary site.
Same result for failback.

Moving to VERIFIED

Comment 3 Yosi Ben Shimon 2019-02-06 16:10:00 UTC
In addition to comment #2:
Tested using:

Comment 7 errata-xmlrpc 2019-05-08 12:34:23 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Comment 8 Daniel Gur 2019-08-28 13:14:05 UTC

Comment 9 Daniel Gur 2019-08-28 13:18:20 UTC

Note You need to log in before you can comment on or make changes to this bug.