Cloning the bug to RHHI for tracking purpose. +++ This bug was initially created as a clone of Bug #1679109 +++ Description of problem: ----------------------- With RHHI 1.6, gluster volumes of type distributed replicate and arbiter volumes will be supported. When user tries to expand the volume, provide the appropriate warning. Version-Release number of selected component (if applicable): ------------------------------------------------------------- Not applicable How reproducible: ----------------- Always Steps to Reproduce: -------------------- Not applicable Expected results: ------------------- Rephrase the warning message, such a way the drawback is explained but do not prevent them from adding brick by choosing words as 'not recommended' Additional info: --- Additional comment from Sahina Bose on 2018-10-08 10:12:20 UTC --- Is this a Test Only requirement - or are there changes needed for initial deployment as well? --- Additional comment from SATHEESARAN on 2019-01-07 11:39:53 UTC --- (In reply to Sahina Bose from comment #1) > Is this a Test Only requirement - or are there changes needed for initial > deployment as well? While adding the set of bricks to the volume, there is a additional info pops up, stating, its advised to have new volume created. This is misleading. The exact statement goes like this: "Expanding gluster volume in a hyper-converged setup is not recommended as it could lead to degraded performance. To expand storage for cluster, it is advised to add additional gluster volumes. Are you sure you want to continue?" We should remove such warning note. --- Additional comment from Sahina Bose on 2019-03-04 11:07:42 UTC --- https://gerrit.ovirt.org/#/c/72883/ is the patch that added this warning. Kaustav, can you remove this?
This bug can be added in document as known issue for RFE 1632144
The dependent bug is ON_QA and also placing this bug ON_QA
Tested with ovirt-engine-4.3.3 When adding brick from RHV Manager UI, there are no warnings pops up
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-2019:1121