Bug 1319684 - Delete of a pool
Summary: Delete of a pool
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Storage Console
Classification: Red Hat
Component: core
Version: 2
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 2
Assignee: Nishanth Thomas
QA Contact: sds-qe-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-21 10:30 UTC by Lubos Trilety
Modified: 2018-11-19 05:33 UTC (History)
3 users (show)

Fixed In Version: rhscon-ceph-0.0.23-1.el7scon.x86_64, rhscon-core-0.0.24-1.el7scon.x86_64, rhscon-ui-0.0.39-1.el7scon.noarch
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-11-19 05:33:28 UTC
Target Upstream Version:

Attachments (Terms of Use)
delete task details (91.47 KB, image/png)
2016-03-21 10:30 UTC, Lubos Trilety 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Lubos Trilety 2016-03-21 10:30:35 UTC 
Created attachment 1138529 [details]
delete task details

Description of problem:
The delete task of any pool always ends with fail.
ERROR: Delete Storage: <ID> is timed out.
However the pool is deleted and sub tasks ends with success. The pool was removed from ceph and from skyring too.

Version-Release number of selected component (if applicable):
rhscon-core-0.0.8-14.el7.x86_64
rhscon-ui-0.0.23-1.el7.noarch
rhscon-ceph-0.0.6-14.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Try to delete some storage
2. Open details page for related task, wait till it finishes

Actual results:
Task fail with an timed-out error
Force Stop. Task: 66c1b95b-755f-4d75-b089-9274ea1d5138 explicitly stopped.

Expected results:
Task will fail only if delete is not successful.

Additional info:
Comment 1 Martin Kudlej 2016-07-08 12:30:38 UTC 
Tested with 
ceph-ansible-1.0.5-23.el7scon.noarch
ceph-installer-1.0.12-3.el7scon.noarch
rhscon-ceph-0.0.29-1.el7scon.x86_64
rhscon-core-0.0.29-1.el7scon.x86_64
rhscon-core-selinux-0.0.29-1.el7scon.noarch
rhscon-ui-0.0.43-1.el7scon.noarch
and it works. -->VERIFIED
Note You need to log in before you can comment on or make changes to this bug.