Bug 1949512 - [Ceph-Dashboard] - All Size specification options are not implemented in the dashboard
Summary: [Ceph-Dashboard] - All Size specification options are not implemented in t...
Keywords:
Status: CLOSED DUPLICATE of bug 1945054
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: Ceph-Dashboard
Version: 5.0
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: ---
: 6.0
Assignee: avan
QA Contact: skanta
Anjana Suparna Sriram
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-04-14 13:08 UTC by skanta
Modified: 2022-06-14 20:10 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-06-14 20:10:34 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHCSDASH-369 0 None None None 2021-11-04 09:40:10 UTC

Description skanta 2021-04-14 13:08:39 UTC 
Description of problem:

As per the OSD creation doc, the following Size specification options are provided to create the OSD's

1.LOW:HIGH
2.:HIGH
3.LOW:
4.EXACT

In Dashboard, we can see the option for an exact(EXACT) size.The remaining three options are not provided.

Doc Link: https://docs.ceph.com/en/latest/cephadm/osd/#size-specs 

 

Version-Release number of selected component (if applicable):
ceph: root@depressa009 /]# ceph -v
ceph version 16.2.0-1.el8cp (a330ff4fed793ca0b5d3b248c395a06e432b51c4) pacific (stable)
[ceph: root@depressa009 /]# 


How reproducible:


Steps to Reproduce:
1.Configure the cluster with cephadm
2.Login to the Dashboard
3.Navigate to clusters -> OSDs
4.In create OSDs window click Add 
5.click the filter option and select the size option
6.You can notice the exact size, not the other options


Actual results:
 The other above three options are not exist. There is discrepancy between CLI and Dashboard.

Expected results:

   The options should exist in the dashboard for the customers.


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