Bug 765149 (GLUSTER-3417) - object-storage: mutiple "auth" volumes across cluster
Summary: object-storage: mutiple "auth" volumes across cluster
Keywords:
Status: CLOSED NOTABUG
Alias: GLUSTER-3417
Product: GlusterFS
Classification: Community
Component: object-storage
Version: mainline
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Junaid
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-08-16 07:35 UTC by Saurabh
Modified: 2015-12-01 16:45 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-04-18 07:03:11 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Gaurav 2011-08-16 06:20:12 UTC 
At the cluster level there should be only single auth account, so fs.conf should have the same entry for auth_account on all the nodes.
Comment 1 Saurabh 2011-08-16 07:35:07 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.
Comment 2 Junaid 2012-04-18 07:03:11 UTC 
This bug is no more valid as we have moved away from swauth.
Note You need to log in before you can comment on or make changes to this bug.