Bug 1230646
Summary: | Not able to create snapshots for geo-replicated volumes when session is created with root user | |||
---|---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Shubhendu Tripathi <shtripat> | |
Component: | geo-replication | Assignee: | Kotresh HR <khiremat> | |
Status: | CLOSED ERRATA | QA Contact: | Rahul Hinduja <rhinduja> | |
Severity: | high | Docs Contact: | ||
Priority: | high | |||
Version: | rhgs-3.1 | CC: | aavati, annair, avishwan, csaba, dpati, nlevinki, rhinduja, vagarwal | |
Target Milestone: | --- | |||
Target Release: | RHGS 3.1.0 | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | glusterfs-3.7.1-5 | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1231789 (view as bug list) | Environment: | ||
Last Closed: | 2015-07-29 05:02:18 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: | 1202842, 1224902, 1231789, 1233056 |
Description
Shubhendu Tripathi
2015-06-11 09:24:24 UTC
This happens only when "root@slavehost::slavevol" is used in Geo-rep create command instead of just "slavehost::slavevol". Upstream Master Patch: http://review.gluster.org/11233 Upstream 3.7 Patch: http://review.gluster.org/11310 Downstream Patch: https://code.engineering.redhat.com/gerrit/#/c/51070/ Verified with build: glusterfs-3.7.1-7.el6rhs.x86_64 (a) Created geo-rep session using root@slave-host::slave-vol (b) Started geo-rep session (c) Paused geo-rep session (d) Created Snapshot (e) Listed Snapshot (f) Activated snapshot (g) Resumed geo-rep session All above were successful. Moving the bug to verified state. The issues is surfaced only because of RHSC support of geo-replication. Hence giving Doc_text - 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/RHSA-2015-1495.html |