Bug 1494062
| Summary: | Setting up lvmcache using gdeploy fails | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | SATHEESARAN <sasundar> |
| Component: | gdeploy | Assignee: | Sachidananda Urs <surs> |
| Status: | CLOSED ERRATA | QA Contact: | SATHEESARAN <sasundar> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rhgs-3.3 | CC: | amukherj, knarra, rcyriac, rhs-bugs, sabose, smohan, storage-qa-internal, surs |
| Target Milestone: | --- | Keywords: | ZStream |
| Target Release: | RHGS 3.3.1 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | gdeploy-2.0.2-16 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 1494041 | Environment: | |
| Last Closed: | 2017-11-29 03:27:19 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: | 1475688, 1494041 | ||
|
Description
SATHEESARAN
2017-09-21 12:21:16 UTC
This bug is actually cloned from the RHHI 1.1 bug which directly corresponds to the failure of gdeploy in creating lvmcache backed LVs Commit: https://github.com/gluster/gdeploy/commit/be2c9ddbecb47c fixes the issue. Verified with gdeploy-2.0.2-16.el7rhgs and this issue is not seen. The configuration file used is: [lv] action=setup-cache ssd=vde vgname=vg poolname=thinpool cache_lv=lvcache cache_lvsize=5GB cachemode=writeback This setup the lvmcache as required. Note: Not marking this bug as **VERIFIED** as the gdeploy errata is not yet available. Once the gdeploy errata is available with this specified build, I will move this bug to VERIFIED state. The build - gdeploy-2.0.2-16.el7rhgs is available with the errata and with comment3 marking this 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/RHBA-2017:3274 |