Bug 1653575
| Summary: | [RHHI-V] Support single brick distribute volume for RHHI-V volumes | |||
|---|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | SATHEESARAN <sasundar> | |
| Component: | gluster-ansible | Assignee: | Sachidananda Urs <surs> | |
| Status: | CLOSED ERRATA | QA Contact: | SATHEESARAN <sasundar> | |
| Severity: | high | Docs Contact: | ||
| Priority: | high | |||
| Version: | rhgs-3.4 | CC: | rcyriac, rhs-bugs, sabose, sankarshan, sasundar, smali, surs | |
| Target Milestone: | --- | Keywords: | ZStream | |
| Target Release: | RHGS 3.4.z Batch Update 4 | |||
| Hardware: | x86_64 | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | gluster-ansible-features-1.0.4-2 | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1653576 (view as bug list) | Environment: | ||
| Last Closed: | 2019-03-27 03:44:39 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: | 1653576 | |||
|
Description
SATHEESARAN
2018-11-27 07:30:54 UTC
Make sure that the granular-entry-heal option is not turned on for the distribute volume. As this option is not relevant for the distribute volume. Does this item needs a separate bug to be tracked ? (In reply to SATHEESARAN from comment #2) > Make sure that the granular-entry-heal option is not turned on for the > distribute volume. As this option is not relevant for the distribute volume. > > Does this item needs a separate bug to be tracked ? No need, this bug is good enough. Thanks sas. Can this be targeted to 3.4 U3 or U4? (In reply to Sahina Bose from comment #4) > Can this be targeted to 3.4 U3 or U4? We can do this for U4. Commit: https://github.com/gluster/gluster-ansible-features/commit/99b688dcdd50 fixes the issue. Additional information here is that the new virt profile for distributed volume is now available with the name 'distributed-virt' The following way used to optimize the distribute volume for virt store usecase: # gluster volume set <vol> group distributed-virt (In reply to SATHEESARAN from comment #7) > Additional information here is that the new virt profile for distributed > volume is now available with the name 'distributed-virt' > The following way used to optimize the distribute volume for virt store > usecase: > # gluster volume set <vol> group distributed-virt sas, will this group be part of U4? (In reply to Sachidananda Urs from comment #8) > (In reply to SATHEESARAN from comment #7) > > Additional information here is that the new virt profile for distributed > > volume is now available with the name 'distributed-virt' > > The following way used to optimize the distribute volume for virt store > > usecase: > > # gluster volume set <vol> group distributed-virt > > sas, will this group be part of U4? If so, this can be set from the role by setting the: gluster_features_hci_volume_options variable. (In reply to Sachin P Mali from comment #12) > In release stakeholders meeting it was agreed to push this bug out of > proposed list of 3.4 BU4, and to be considered for a future batch update. This bug is needed for RHHI 1.6 as we move the deployment flow to be based on gluster-ansibles. Can this decision be re-evaluated as the verification of bug will be done by RHHI QE? Tested with gluster-ansible-features-1.0.4-3 distributed volume is created as part of single node deployment and required volume options are set on it 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/RHBA-2019:0661 |