Bug 1224902
Summary: | [New] - cannot create snapshot while geo-replication session is running on the volume. | ||||||
---|---|---|---|---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | RamaKasturi <knarra> | ||||
Component: | rhsc | Assignee: | Shubhendu Tripathi <shtripat> | ||||
Status: | CLOSED ERRATA | QA Contact: | Stanislav Graf <sgraf> | ||||
Severity: | high | Docs Contact: | |||||
Priority: | high | ||||||
Version: | rhgs-3.1 | CC: | aloganat, asrivast, dpati, khiremat, nlevinki, rhs-bugs, sabose, sgraf, shtripat | ||||
Target Milestone: | --- | ||||||
Target Release: | RHGS 3.1.0 | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | rhsc-3.1.0-61 | Doc Type: | Bug Fix | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2015-07-29 05:30:04 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: | 1230646, 1231789, 1233056 | ||||||
Bug Blocks: | 1202842, 1224288 | ||||||
Attachments: |
|
Description
RamaKasturi
2015-05-26 07:31:28 UTC
Engine and vdsm logs can be found in the link below. http://rhsqe-repo.lab.eng.blr.redhat.com/sosreports/rhsc/1224902/ Created attachment 1045990 [details]
screenshot for snapshot creation
Unable to create snapshot for volume when geo rep session is running in build rhsc-3.1.0-0.62.el6.noarch.(screenshot attached). Hence moving this bug to assigned state. The error is from Gluster itself. The geo-replication session pause is failing. Kotresh, can you please check this out? Verified the fix in build, rhsc-3.1.0-0.62.el6.noarch Separate bug 1240196 has been raised for the issue mentioned in comment 7 and 8. Snapshot creation works fine when all the nodes in cluster is part of master volume. Refer comment 10 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://rhn.redhat.com/errata/RHEA-2015-1494.html |