Description of problem: As you can see at screenshot journal size is 5GB. But there is info about disk with journal with size 10GB in UI in section "Journal on osd.0". I think this is confusing. I think there are 2 options how to change it: 1) change UI and show info about partition with journal. In this case "Device Path:/dev/vdb1; Capacity: 5GB" or 2) change name of this section from "Journal on osd.0" to "Device dedicated for partitions with journal for osd.0". I know that this is long title, but current title is confusing. Version-Release number of selected component (if applicable): ceph-ansible-1.0.5-15.el7scon.noarch ceph-installer-1.0.11-1.el7scon.noarch perl-Scalar-List-Utils-1.27-248.el7.x86_64 rhscon-ceph-0.0.20-1.el7scon.x86_64 rhscon-core-0.0.21-1.el7scon.x86_64 rhscon-ui-0.0.35-1.el7scon.noarch How reproducible: 100% Steps to Reproduce: 1. create cluster 2. check osd section of cluster Actual results: Section "Journal on osd.x" contains confusing info. Expected results: Title will be changed or section content so user is clear about journal size and its location.
Need clarification from UXD team about the way to go.
Created attachment 1168764 [details] Cluster object details - osd tab
I agree that the label "Journal on osd.x" is confusing, as this is the related to journal for osd.x. Instead, I would suggest a different title/label, ie. "Journal for osd.x"
So this is basically a rephrasing... Or am I missing out on any technical change that is required?
@Deb - you are correct in that this is just rephrasing of the label. No other technical change needed beyond changing the text.
Checking with ============
I think that the issue here was not understood properly by the dev team and labeling it as a mere design issue is incorrect. There is no way I could declare this as resolved. See expanded explanation below. Checking with ============= On RHSC 2.0 server machine: rhscon-ui-0.0.48-1.el7scon.noarch rhscon-core-selinux-0.0.34-1.el7scon.noarch rhscon-ceph-0.0.33-1.el7scon.x86_64 rhscon-core-0.0.34-1.el7scon.x86_64 ceph-installer-1.0.14-1.el7scon.noarch ceph-ansible-1.0.5-28.el7scon.noarch On Ceph OSD machine: rhscon-core-selinux-0.0.34-1.el7scon.noarch rhscon-agent-0.0.15-1.el7scon.noarch ceph-selinux-10.2.2-22.el7cp.x86_64 ceph-common-10.2.2-22.el7cp.x86_64 ceph-base-10.2.2-22.el7cp.x86_64 ceph-osd-10.2.2-22.el7cp.x86_64 How reproducible ================ 100 % Steps to Reproduce ================== 1. Install RHSC 2.0 following the documentation. 2. Make sure future storage machines (OSD role) have a dedicated, at least 10 GB disk for ceph journal. 3. Accept few nodes for the ceph cluster. 4. Create new ceph cluster named 'alpha', selecting default journal size 5GB (the crucial detail here is that this 5GB default is smaller compared to the side of dedicated journal devices on OSD machines). 5. When the cluster is created, go to "OSDs" tab of the cluster page and select one osd from the list there. Actual results ============== Selecting osd.0 from the list, I see osd.0 details in the right sidebar. When I click on 'Journal for osd.0' link there, the details expand further and I see the following info: ~~~ Device Path: /var/lib/ceph/osd/alpha-0/journal Capacity: 10.0 GB Storage Profile: default ~~~ Which is not correct (checking on the machine hosting the osd): ~~~ # ceph-disk list /dev/vda : /dev/vda1 other, swap /dev/vda2 other, xfs, mounted on / /dev/vdb : /dev/vdb1 ceph journal, for /dev/vdc1 /dev/vdc : /dev/vdc1 ceph data, active, cluster alpha, osd.0, journal /dev/vdb1 # lsblk /dev/vdb NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT vdb 253:16 0 10G 0 disk └─vdb1 253:17 0 5G 0 part ~~~ As we can see here, the journal for osd.0 is hosted on 5GB partition. The confusion here seems to be caused by the fact that the 5GB journal partition is hosted on 10GB device. But the size of the device on which the journal partition is stored on should not be confused with the size of the journal itself. Expected results ================ The details of 'Journal for osd.0' is reported as follows: ~~~ Device Path: /var/lib/ceph/osd/alpha-0/journal Capacity: 5.0 GB Storage Profile: default ~~~ So that the size of journal of osd.0 reported here matches the size of the journal partition.
(In reply to Martin Kudlej from comment #0) > 2) change name of this section from "Journal on osd.0" to "Device dedicated > for partitions with journal for osd.0". I know that this is long title, but > current title is confusing. This would make only sense when the actual size of the journal partition is provided as well. Showing just the size of disk on which RHSC 2.0 have the journal partition created is absolutely pointless from the ceph admin point of view.
(In reply to :Deb from comment #5) > So this is basically a rephrasing... Or am I missing out on any technical > change that is required? See the description in comment 8.
Created attachment 1181959 [details] screenshot 3: journal details (failed qe screenshot)
*** Bug 1366006 has been marked as a duplicate of this bug. ***
JC Lopez: 1342969 Journal information must be accurate and journal related information must be amended (Cluster Configuration Window Default Journal Size element should be removed)
From reading this bug and issues mentioned, there are a couple things called out. Journal partition and the disk the journal partition is sitting on are not reporting size correctly in the OSD tabbed view. JC is asking for the default journal size not to be shown in the Cluster object details view > Configuration tab, which is showing the default Cluster journal size. One is incorrect reporting, and the latter is probably text that does not clearly explain what it is, hence why JC Lopez is asking for its removal.
1) the size of the symlink pointing to the journal is not relevant, we must display the actual journal size even in cases where we have colocation. In this case we show the size of the partition where the journal resides in GB with 1 decimal point ex. 2.5 2) we should remove the cluster config display of the default journal size - it's misleading
we should also disable auto-expansion of the cluster with new OSDs when we detect colocation
@Jeff, regarding journal size, say symlink direct to /dev/vdb1 partition of disk /dev/vdb, which is carved out of a 10GB disk (/dev/vdb) and journal size is 3.0 GB. Can we show the details something like Device Path: /dev/vdb1 Capacity: 3.0 GB Storage Profile: <name> I have a patch https://review.gerrithub.io/#/c/287136/ to get the actual partition name of the journal and size it can show as above. Is this as expected ??
Yes that is correct Shubhendu - perfect
The fix for https://bugzilla.redhat.com/show_bug.cgi?id=1365998 would take care correct display of journal details like path and size. Also the default journal size would be removed from cluster -> config list. Regarding comment#17 from Jeff, below are the points finalized post discussion with Ju and acked 1. Update documentation that auto expansion would be disabled for a cluster imported in RHS Console with co-located journals 2. During import cluster flow, there would be a step added saying "Disabling auto expand for the cluster", if co-located journals are discovered on the cluster getting imported 3. A highlighted text saying "auto expansion disabled" would be added next to Cluster Name in cluster object page as below "Clusters >> Ceph (*auto expansion disabled)"
+1 to Comment 20 (Shubhendu Tripathi has written above).
+1 to Comment 18 (Shubhendu Tripathi has written above).
@Rakesh, kindly add required documentation for point-1 in comment#20.
Created attachment 1203763 [details] Screenshot: Incorrect device path
Tested with Server: ceph-ansible-1.0.5-33.el7scon.noarch ceph-installer-1.0.15-2.el7scon.noarch graphite-web-0.9.12-8.1.el7.noarch rhscon-ceph-0.0.42-1.el7scon.x86_64 rhscon-core-selinux-0.0.43-1.el7scon.noarch rhscon-core-0.0.43-1.el7scon.x86_64 rhscon-ui-0.0.57-1.el7scon.noarch Node: calamari-server-1.4.8-1.el7cp.x86_64 ceph-base-10.2.2-41.el7cp.x86_64 ceph-common-10.2.2-41.el7cp.x86_64 ceph-mon-10.2.2-41.el7cp.x86_64 ceph-osd-10.2.2-41.el7cp.x86_64 ceph-selinux-10.2.2-41.el7cp.x86_64 libcephfs1-10.2.2-41.el7cp.x86_64 python-cephfs-10.2.2-41.el7cp.x86_64 rhscon-agent-0.0.19-1.el7scon.noarch rhscon-core-selinux-0.0.43-1.el7scon.noarch Capacity of Journal for osd.0 is shown as expected but Device Path is incorrect (/var/lib/ceph/osd/ceph-0/journal instead of /dev/vdb1 as seen on screenshot). --> Assigned
The BZ https://bugzilla.redhat.com/show_bug.cgi?id=1365998 is verified by Lubos and its same details. Please collaborate with Lubos and see if its actually an issue still..
I am not able to simulate this and works fine for me. Also as https://bugzilla.redhat.com/show_bug.cgi?id=1365998 is verified, ideally I dont an issue. Can you please verify with Lubos's setup and verify this BZ?
The issue was happening while pool creation and the latest patch takes care of syncing journal details properly now.
Tested with Server: ceph-ansible-1.0.5-34.el7scon.noarch ceph-installer-1.0.15-2.el7scon.noarch graphite-web-0.9.15-1.el7.noarch rhscon-ceph-0.0.43-1.el7scon.x86_64 rhscon-core-0.0.45-1.el7scon.x86_64 rhscon-core-selinux-0.0.45-1.el7scon.noarch rhscon-ui-0.0.59-1.el7scon.noarch Node: calamari-server-1.4.8-1.el7cp.x86_64 ceph-base-10.2.2-41.el7cp.x86_64 ceph-common-10.2.2-41.el7cp.x86_64 ceph-mon-10.2.2-41.el7cp.x86_64 ceph-osd-10.2.2-41.el7cp.x86_64 ceph-selinux-10.2.2-41.el7cp.x86_64 libcephfs1-10.2.2-41.el7cp.x86_64 python-cephfs-10.2.2-41.el7cp.x86_64 rhscon-agent-0.0.19-1.el7scon.noarch rhscon-core-selinux-0.0.45-1.el7scon.noarch and it works as it is expected. --> Verified
doc-text looks good.
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/RHSA-2016:2082