Bug 1340916
| Summary: | cluster OSD expand is not working correctly | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Storage Console | Reporter: | Lubos Trilety <ltrilety> | ||||
| Component: | core | Assignee: | Nishanth Thomas <nthomas> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Lubos Trilety <ltrilety> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 2 | CC: | mkudlej, nthomas, sankarshan | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 2 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | rhscon-core-0.0.26-1.el7scon.x86_64 rhscon-ceph-0.0.26-1.el7scon.x86_64 | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2016-08-23 19:52:41 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: | 1344192, 1344195 | ||||||
| Attachments: |
|
||||||
*** Bug 1342069 has been marked as a duplicate of this bug. *** Tested on: rhscon-ceph-0.0.36-1.el7scon.x86_64 rhscon-core-selinux-0.0.36-1.el7scon.noarch rhscon-core-0.0.36-1.el7scon.x86_64 rhscon-ui-0.0.50-1.el7scon.noarch Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2016:1754 |
Created attachment 1162914 [details] cluster OSDs Description of problem: Cluster can be expanded but many times added hosts OSDs are down by UI while 'ceph status' is showing those OSDs as up. Moreover those OSDs have no storage profile or more precisely their storage profile has no name in UI. After skyring service restart the OSD, which was down, is missing in the list of OSDs. In mongodb in storage_nodes collection all disk are listed with correct storage profile, but in there's a bad info in storage_logical_units collection. Version-Release number of selected component (if applicable): rhscon-core-0.0.21-1.el7scon.x86_64 rhscon-ceph-0.0.20-1.el7scon.x86_64 rhscon-ui-0.0.34-1.el7scon.noarch How reproducible: 100% Steps to Reproduce: 1. Create cluster 2. Expand cluster with OSD host 3. Actual results: Some of OSDs on the host are down, all of them has no storage profile. Expected results: All expanded OSDs has correct state and storage profile. Additional info: attached screenshot is after skyring service restart