Bug 1301340 - Error on removing Cinder disk snapshots
Summary: Error on removing Cinder disk snapshots
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Storage
Version: 3.6.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ovirt-3.6.3
: 3.6.3.1
Assignee: Daniel Erez
QA Contact: Natalie Gavrielov
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-24 11:20 UTC by Daniel Erez
Modified: 2016-02-23 13:31 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-02-23 13:31:47 UTC
oVirt Team: Storage
Embargoed:
tnisan: ovirt-3.6.z?
rule-engine: planning_ack+
tnisan: devel_ack+
rule-engine: testing_ack?

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 52654 0 master MERGED core: fix remove disk snapshots for cinder 2016-01-26 14:31:53 UTC
oVirt gerrit 52762 0 ovirt-engine-3.6 MERGED core: fix remove disk snapshots for cinder 2016-01-27 14:06:29 UTC
oVirt gerrit 52808 0 ovirt-engine-3.6.3 MERGED core: fix remove disk snapshots for cinder 2016-01-27 15:05:36 UTC

Description Daniel Erez 2016-01-24 11:20:16 UTC 
Description of problem:
Failure on removing a disk snapshot from Cinder storage domain
(see 'Additional info' for thrown error in the log).

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

How reproducible:
100%

Steps to Reproduce:
1. Navigate to Storage main-tab
2. Select a Cinder Storage domain
3. Navigate to 'Disk Snapshots' sub-tab
4. Remove a disk snapshot

Actual results:
Operation fails.

Expected results:
Operation succeeds.

Additional info:
From engine.log - ERROR [org.ovirt.engine.core.bll.CommandsFactory] (org.ovirt.thread.pool-9-thread-40) [2393929d] Error in invocating CTOR of command 'RemoveDiskSnapshots': null
Comment 1 Red Hat Bugzilla Rules Engine 2016-01-24 11:20:19 UTC 
Bug tickets must have version flags set prior to targeting them to a release. Please ask maintainer to set the correct version flags and only then set the target milestone.
Comment 2 Red Hat Bugzilla Rules Engine 2016-01-24 11:20:19 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 3 Red Hat Bugzilla Rules Engine 2016-01-24 11:22:43 UTC 
Bug tickets must have version flags set prior to targeting them to a release. Please ask maintainer to set the correct version flags and only then set the target milestone.
Comment 4 Red Hat Bugzilla Rules Engine 2016-01-24 11:33:11 UTC 
Bug tickets must have version flags set prior to targeting them to a release. Please ask maintainer to set the correct version flags and only then set the target milestone.
Comment 5 Red Hat Bugzilla Rules Engine 2016-01-28 12:10:45 UTC 
Bug tickets that are moved to testing must have target release set to make sure tester knows what to test. Please set the correct target release before moving to ON_QA.
Comment 6 Red Hat Bugzilla Rules Engine 2016-01-28 12:14:15 UTC 
Bug tickets that are moved to testing must have target release set to make sure tester knows what to test. Please set the correct target release before moving to ON_QA.
Comment 7 Red Hat Bugzilla Rules Engine 2016-01-28 12:18:38 UTC 
Bug tickets that are moved to testing must have target release set to make sure tester knows what to test. Please set the correct target release before moving to ON_QA.
Comment 8 Red Hat Bugzilla Rules Engine 2016-01-28 12:24:19 UTC 
Bug tickets that are moved to testing must have target release set to make sure tester knows what to test. Please set the correct target release before moving to ON_QA.
Comment 9 Red Hat Bugzilla Rules Engine 2016-01-28 12:29:20 UTC 
Bug tickets that are moved to testing must have target release set to make sure tester knows what to test. Please set the correct target release before moving to ON_QA.
Note You need to log in before you can comment on or make changes to this bug.