Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
This project is now read‑only. Starting Monday, February 2, please use https://ibm-ceph.atlassian.net/ for all bug tracking management.

Bug 1563009

Summary: Install and configure ceph-dashboard with ceph-ansible
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Christina Meno <gmeno>
Component: Ceph-AnsibleAssignee: Boris Ranto <branto>
Status: CLOSED DUPLICATE QA Contact: ceph-qe-bugs <ceph-qe-bugs>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.0CC: adeza, aschoen, branto, ceph-eng-bugs, epuertat, flucifre, gabrioux, gfidente, gmeno, nthomas, sankarshan, shan, tnielsen, yrabl, zcerza
Target Milestone: rc   
Target Release: 4.*   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-02-27 23:26:59 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1475556    

Description Christina Meno 2018-04-02 22:21:12 UTC 
Description of problem:


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 4 Travis Nielsen 2018-09-25 15:36:12 UTC 
Moving out of 3.2 since dashboard is not in 3.2.
Comment 6 Ernesto Puerta 2018-12-18 19:44:01 UTC 
Related/Possible duplicate of Bug #1656591
Comment 7 John Fulton 2019-01-02 15:29:17 UTC 
*** Bug 1526398 has been marked as a duplicate of this bug. ***
Comment 8 Boris Ranto 2019-01-10 11:36:55 UTC 
There is an upstream PR for this, here:

https://github.com/ceph/ceph-ansible/pull/3426

We (me and Zack) are working on this feature there.
Comment 11 Christina Meno 2019-02-27 23:26:59 UTC 

*** This bug has been marked as a duplicate of bug 1656591 ***