| Summary: | object-storage: mutiple "auth" volumes across cluster | ||
|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Saurabh <saurabh> |
| Component: | object-storage | Assignee: | Junaid <junaid> |
| Status: | CLOSED NOTABUG | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | mainline | CC: | gluster-bugs, junaid, vagarwal |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-04-18 07:03:11 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Gaurav
2011-08-16 06:20:12 UTC
I have a set up where I have different "auth" volumes on different nodes of the cluster, on nodeA: fs.conf points to "auth" on nodeB: fs.conf points to "auth1" hence i can have same user namely "tester" on both the volumes and the token generation will be separate. this effectively is not consistent information considering cluster. This bug is no more valid as we have moved away from swauth. |