Bug 1339520 - wrong number of OSDs in pool summary
Summary: wrong number of OSDs in pool summary
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Storage Console
Classification: Red Hat Storage
Component: UI
Version: 2
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: 2
Assignee: sankarshan
QA Contact: sds-qe-bugs
URL:
Whiteboard:
Depends On:
Blocks: Console-2-Feature-Freeze
TreeView+ depends on / blocked
 
Reported: 2016-05-25 08:52 UTC by Lubos Trilety
Modified: 2018-11-19 05:31 UTC (History)
2 users (show)

Fixed In Version: rhscon-core-0.0.34-1.el7scon.x86_64 rhscon-ceph-0.0.33-1.el7scon.x86_64 rhscon-ui-0.0.47-1.el7scon.noarch
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-11-19 05:31:20 UTC
Embargoed:

Attachments (Terms of Use)
pool summary (109.03 KB, image/png)
2016-05-25 08:52 UTC, Lubos Trilety 		no flags Details
View All

Description Lubos Trilety 2016-05-25 08:52:42 UTC 
Created attachment 1161352 [details]
pool summary

Description of problem:
In pool summary there's always number of all OSDs in a cluster as OSDs number not the number of OSDs related to the chosen storage profile.

Version-Release number of selected component (if applicable):
rhscon-core-0.0.19-1.el7scon.x86_64
rhscon-ceph-0.0.18-1.el7scon.x86_64
rhscon-ui-0.0.34-1.el7scon.noarch

How reproducible:
100%

Steps to Reproduce:
1. Start to create a pool, look on pool summary
2.
3.

Actual results:
As number of OSDs for pool there;s number of all OSDs in a cluster.

Expected results:
Only those OSDs in chosen storage profile should be counted.

Additional info:
There's number of OSDs per pool 3 OSDs on attached screenshot, however a chosen storage profile 'test' had only 1 OSD.
Comment 1 Lubos Trilety 2016-07-15 13:25:12 UTC 
Tested on:
rhscon-ceph-0.0.31-1.el7scon.x86_64
rhscon-core-selinux-0.0.32-1.el7scon.noarch
rhscon-ui-0.0.46-1.el7scon.noarch
rhscon-core-0.0.32-1.el7scon.x86_64

There's correct number of OSDs on pool summary page.
Note You need to log in before you can comment on or make changes to this bug.