Bug 1632144
| Summary: | [Test] Support volume expansion | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | SATHEESARAN <sasundar> |
| Component: | rhhi | Assignee: | Sahina Bose <sabose> |
| Status: | CLOSED ERRATA | QA Contact: | bipin <bshetty> |
| Severity: | medium | Docs Contact: | |
| Priority: | high | ||
| Version: | rhhiv-1.5 | CC: | asriram, godas, jcall, kdhananj, rcyriac, rhs-bugs, sabose, sankarshan, sasundar, storage-doc |
| Target Milestone: | --- | Keywords: | TestOnly |
| Target Release: | RHHI-V 1.6 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: |
Gluster volumes can now be expanded across more than three nodes on Red Hat Hyperconverged Infrastructure for Virtualization.
|
Story Points: | --- |
| Clone Of: | 1591397 | Environment: | |
| Last Closed: | 2019-05-09 06:09:23 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: | 1591397, 1679109 | ||
| Bug Blocks: | 1672931, 1679113 | ||
|
Description
SATHEESARAN
2018-09-24 08:24:18 UTC
Bipin is carrying out the test related to expansion and reduction of gluster volume. Assigning QA_contact to him Tested the support volume expansion and the flow works fine. Found 2 issues during the test's Bug 1679863 and Bug 1684350 but dont see it blocking this RFE. Component versions: ================== rhv 4.3 glusterfs-3.12.2-47.el7rhgs.x86_64 glusterfs-3.12.2-45.el7rhgs.x86_64 glusterfs-3.12.2-43.el7rhgs.x86_64 Scenarios covered: ================= 1. 1*3 --> 2*3 -->3*3 2. 1*3 --> 2*3 Also, covered few negative path like killing of a brick while re-balance is in progress etc. So based on all these results marking the bug as verified 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 |