Bug 1838100 - Refresh LUN is showing UI error "Cannot sync Virtual Disk. Related operation is currently in progress"
Summary: Refresh LUN is showing UI error "Cannot sync Virtual Disk. Related operation ...
Keywords:
Status: CLOSED DUPLICATE of bug 1838051
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 4.3.9
Hardware: Unspecified
OS: All
unspecified
medium
Target Milestone: ovirt-4.4.2
: ---
Assignee: Fedor Gavrilov
QA Contact: Avihai
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-05-20 13:24 UTC by nijin ashok
Modified: 2020-11-02 15:04 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-06-29 12:09:16 UTC
oVirt Team: Storage
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 5101801 0 None None None 2020-05-25 11:18:32 UTC

Description nijin ashok 2020-05-20 13:24:18 UTC 
Description of problem:

While refreshing the direct LUN, the UI is showing below error.

===
Error while executing action: Cannot sync Virtual Disk. Related operation is currently in progress. Please try again later.
===

However, the action is successfully executed and the same can be seen in the engine logs.

===
2020-05-20 09:10:43,710-04 INFO  [org.ovirt.engine.core.bll.storage.pool.SyncDirectLunsCommand] (EE-ManagedThreadFactory-engine-Thread-176125) [cbe4c640-9e7c-4824-81d0-3f189e9e39fc] Lock Acquired to object 'EngineLock:{exclusiveLocks='[dbaf79e7-29d1-491a-be49-3a94bd91b7cc=DISK]', sharedLocks=''}'
2020-05-20 09:10:43,730-04 INFO  [org.ovirt.engine.core.bll.storage.pool.SyncDirectLunsCommand] (EE-ManagedThreadFactory-engine-Thread-176124) [cbe4c640-9e7c-4824-81d0-3f189e9e39fc] Failed to Acquire Lock to object 'EngineLock:{exclusiveLocks='[dbaf79e7-29d1-491a-be49-3a94bd91b7cc=DISK]', sharedLocks=''}'
2020-05-20 09:10:43,730-04 INFO  [org.ovirt.engine.core.bll.storage.pool.SyncDirectLunsCommand] (EE-ManagedThreadFactory-engine-Thread-176126) [cbe4c640-9e7c-4824-81d0-3f189e9e39fc] Failed to Acquire Lock to object 'EngineLock:{exclusiveLocks='[dbaf79e7-29d1-491a-be49-3a94bd91b7cc=DISK]', sharedLocks=''}'
2020-05-20 09:10:43,731-04 WARN  [org.ovirt.engine.core.bll.storage.pool.SyncDirectLunsCommand] (EE-ManagedThreadFactory-engine-Thread-176124) [cbe4c640-9e7c-4824-81d0-3f189e9e39fc] Validation of action 'SyncDirectLuns' failed for user admin@internal-authz. Reasons: VAR__ACTION__SYNC,VAR__TYPE__DISK,ACTION_TYPE_FAILED_OBJECT_LOCKED
2020-05-20 09:10:43,731-04 WARN  [org.ovirt.engine.core.bll.storage.pool.SyncDirectLunsCommand] (EE-ManagedThreadFactory-engine-Thread-176126) [cbe4c640-9e7c-4824-81d0-3f189e9e39fc] Validation of action 'SyncDirectLuns' failed for user admin@internal-authz. Reasons: VAR__ACTION__SYNC,VAR__TYPE__DISK,ACTION_TYPE_FAILED_OBJECT_LOCKED

2020-05-20 09:10:44,216-04 INFO  [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-120) [cbe4c640-9e7c-4824-81d0-3f189e9e39fc] EVENT_ID: SYNC_DIRECT_LUNS_STARTED(1,054), Direct LUN synchronization started.

2020-05-20 09:10:45,484-04 INFO  [org.ovirt.engine.core.bll.storage.pool.SyncDirectLunsCommand] (default task-120) [cbe4c640-9e7c-4824-81d0-3f189e9e39fc] LUNs with IDs: [3600140560f551776b614ebe9304fb651] were updated in the DB.
2020-05-20 09:10:45,512-04 INFO  [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-120) [cbe4c640-9e7c-4824-81d0-3f189e9e39fc] EVENT_ID: SYNC_DIRECT_LUNS_FINISHED(1,055), Direct LUN synchronization finished.
====

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

rhvm-4.3.9.4-11.el7.noarch


How reproducible:

100%

Steps to Reproduce:

1. Login to RHV-M => Disks => Run refresh LUN on any direct LUN.


Actual results:

Refresh LUN is showing UI error "Cannot sync Virtual Disk. Related operation is currently in progress"

Expected results:

Refresh LUN should not show any error.

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