Bug 1082718
| Summary: | install.sh does not handle the case of "hadoop" group users in parsing "getent group hadoop" | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Jeff Vance <jvance> |
| Component: | rhs-hadoop-install | Assignee: | Jeff Vance <jvance> |
| Status: | CLOSED ERRATA | QA Contact: | Daniel Horák <dahorak> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | unspecified | CC: | bchilds, dahorak, eboyd, matt, mkudlej, nlevinki |
| Target Milestone: | Release Candidate | Keywords: | UpcomingRelease, ZStream |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | 0.82-1 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-11-24 11:54:23 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: | 1159155 | ||
|
Description
Jeff Vance
2014-03-31 16:58:57 UTC
Reproduced on rhs-hadoop-install-0_81-1.el6rhs.noarch with 4 nodes, with different users assigned to hadoop group on each node (the hadoop group has same gid 495 on all nodes):
NODE1:
# getent group hadoop
hadoop:x:495:
NODE1:
# getent group hadoop
hadoop:x:495:test1,test2
NODE1:
# getent group hadoop
hadoop:x:495:test1,test2
NODE1:
# getent group hadoop
hadoop:x:495:test1,test2,test3
# ./install.sh /dev/mapper/vg_brick-lv_brick
<<< truncated >>>
ERROR: "hadoop" group has inconsistent GIDs across the cluster. hadoop GIDs: 495 test1,test2 test1,test2,test3
Tested and verified on RHSS-2.1.bd-20140219.n.0 with rhs-hadoop-install-0_85-1.el6rhs.noarch accordingly to scenario described in comment 3. The gid is properly parsed from "getent group" command and verified across the cluster. >>> 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://rhn.redhat.com/errata/RHEA-2014-1275.html |