Bug 1301602
Summary: | new disks stay locked | ||
---|---|---|---|
Product: | [oVirt] ovirt-engine | Reporter: | movciari |
Component: | BLL.Storage | Assignee: | Daniel Erez <derez> |
Status: | CLOSED WORKSFORME | QA Contact: | Aharon Canan <acanan> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.5.6.2 | CC: | amureini, bugs, derez, movciari, tnisan |
Target Milestone: | ovirt-3.6.5 | Flags: | amureini:
ovirt-3.6.z?
ylavi: planning_ack+ rule-engine: devel_ack? rule-engine: testing_ack? |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-03-03 14:53:18 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | Storage | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
movciari
2016-01-25 13:46:45 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? 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. Daniel, as QE contact, please take a look? yes, it's engine version 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 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! 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! 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! can't reproduce this right now, clearing needinfo |