Bug 1524356 - Volume deletion having snapshots gives unexpected error
Summary: Volume deletion having snapshots gives unexpected error
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.7.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: GA
: cfme-future
Assignee: Sam Lucidi
QA Contact: Nikhil Dhandre
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-12-11 10:28 UTC by Nikhil Dhandre
Modified: 2018-10-02 14:35 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Category: ---
Cloudforms Team: CFME Core
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
unexpected error: volume deletion having snapshot (75.62 KB, image/png)
2017-12-11 10:28 UTC, Nikhil Dhandre
no flags Details

Description Nikhil Dhandre 2017-12-11 10:28:22 UTC
Created attachment 1365905 [details]
unexpected error: volume deletion having snapshot

Description of problem:
----------------------

Volume having snapshots; without deleting those snapshots when try to delete volume gives me an unexpected error. 

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


How reproducible:
-----------------
always

Steps to Reproduce:
-------------------
1. create a new volume
2. create snapshots (with 2, I tested)
3. try to delete volume

Actual results:
-------------------
Unexpected error

Expected results:
------------------------
It should delete

Additional info:
---------------------
[0] attaching snapshot
[1] log :     http://pastebin.test.redhat.com/539474

Comment 2 Dave Johnson 2017-12-11 15:29:45 UTC
Nikhil, is this happening in 5.9.0 as well?  If so, please set blocker flag on it.

Comment 9 Josh Carter 2018-10-02 14:33:30 UTC
Dear customer, 

The CloudForms team is reviewing the current CloudForms Bug(defect) backlog in order to target engineering efforts. We are closing any bugs for versions that no longer have an active errata stream or that have hit their age limit. We are committing to better management of the backlog as we move forward. If you have an bug that you are still able to reproduce on a current version of CloudForms please open a new bug. 

If you have any concerns about this, please let us know.

Thanks and regards!

Comment 10 Josh Carter 2018-10-02 14:34:10 UTC
Dear customer, 

The CloudForms team is reviewing the current CloudForms Bug(defect) backlog in order to target engineering efforts. We are closing any bugs for versions that no longer have an active errata stream or that have hit their age limit. We are committing to better management of the backlog as we move forward. If you have an bug that you are still able to reproduce on a current version of CloudForms please open a new bug. 

If you have any concerns about this, please let us know.

Thanks and regards!

Comment 11 Josh Carter 2018-10-02 14:35:36 UTC
Dear customer, 

The CloudForms team is reviewing the current CloudForms Bug(defect) backlog in order to target engineering efforts. We are closing any bugs for versions that no longer have an active errata stream or that have hit their age limit. We are committing to better management of the backlog as we move forward. If you have an bug that you are still able to reproduce on a current version of CloudForms please open a new bug. 

If you have any concerns about this, please let us know.

Thanks and regards!


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