Bug 1332085

Summary: Expand cluster with existing node in the cluster by adding new disks, should utilize existing journal disks if available and they hace space left
Product: Red Hat Storage Console Reporter: Shubhendu Tripathi <shtripat>
Component: coreAssignee: Shubhendu Tripathi <shtripat>
core sub component: provisioning QA Contact: sds-qe-bugs
Status: CLOSED CURRENTRELEASE Docs Contact:
Severity: unspecified    
Priority: unspecified CC: nthomas
Version: 2   
Target Milestone: ---   
Target Release: 2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
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:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-11-19 05:34:52 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:

Description Shubhendu Tripathi 2016-05-02 07:26:36 UTC 
Description of problem:
Currently as part of disk addition to a node which is already participating in a cluster, the expand cluster happens automatically through event framework.

In this flow, we should try to utilize the existing journal disks if they are available and have space available with them.

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


How reproducible:


Steps to Reproduce:
1. Create a cluster with set of OSDs (say odd no of rotational disks or SSD as jorunal disk such a way that they are fully consumed as journal and still space available)
2. Add a new disk to one of the OSD node
3.

Actual results:
The expand cluster does not consider existing and unused journal disks

Expected results:
The flow should consider existing and available journal disks while expansion of the cluster.

Additional info: