Bug 1301602 - new disks stay locked
Summary: new disks stay locked
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Storage
Version: 3.5.6.2
Hardware: Unspecified
OS: Unspecified
unspecified
high vote
Target Milestone: ovirt-3.6.5
: ---
Assignee: Daniel Erez
QA Contact: Aharon Canan
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-25 13:46 UTC by movciari
Modified: 2016-03-21 12:44 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-03 14:53:18 UTC
oVirt Team: Storage
amureini: ovirt-3.6.z?
ylavi: planning_ack+
rule-engine: devel_ack?
rule-engine: testing_ack?


Attachments (Terms of Use)

Description movciari 2016-01-25 13:46:45 UTC
Description of problem:
New disks created when creating new VMs from template or when creating new snapshots stay in status locked.
Some of them already exist for a few days and they're still locked.
There should at lest be some timeout for this, and then it should stop the task and throw an error in webadmin alerts
I don't know how to reproduce this, but it happened old hosted-engine setup with lots of VMs, maybe there will be some clue in logs - I will add links to them in a comment because they're over bugzilla attachment size limit

Version-Release number of selected component (if applicable):
3.5.6.2-0.1.el6ev

Comment 2 Allon Mureinik 2016-01-25 14:01:33 UTC
(In reply to movciari from comment #0)
> Version-Release number of selected component (if applicable):
> 3.5.6.2-0.1.el6ev
I'm assuming this is the engine version, right?

Comment 3 Red Hat Bugzilla Rules Engine 2016-01-25 14:01:36 UTC
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.

Comment 4 Allon Mureinik 2016-01-25 14:02:30 UTC
Daniel, as QE contact, please take a look?

Comment 5 movciari 2016-01-25 16:18:36 UTC
yes, it's engine version

Comment 6 movciari 2016-01-26 13:41:01 UTC
For some reason those images are not locked anymore (it took ~5 days)
I didn't do anything special that could affect this, so I don't have any clue why, except some extremely long timeout

Comment 7 Daniel Erez 2016-01-27 05:59:52 UTC
Hi Michal,

In order to analyze the issue can you please attach the engine and vdsm logs from the aforementioned ~5 days time period.

Thanks!

Comment 9 Daniel Erez 2016-01-31 13:20:34 UTC
Hi Michal,

Is it possible to reproduce the issue and provide 'cleaner' logs. I can't find any 'createVolume' tasks in the given logs that were running for a few days.
Perhaps you remember the specific volume or the time you started the operation? 

Thanks!

Comment 10 Allon Mureinik 2016-03-03 14:53:18 UTC
We're unable to reproduce this or gain any insights from the logs, unfortunately.
If you have a reproducer, plesae reopen with the exact steps to rerproduce.
Thanks!

Comment 11 movciari 2016-03-21 12:44:11 UTC
can't reproduce this right now, clearing needinfo


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