Bug 961250
Summary: | Able to trigger host UUID generation through gluster cli command | |||
---|---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Kanagaraj <kmayilsa> | |
Component: | glusterd | Assignee: | krishnan parthasarathi <kparthas> | |
Status: | CLOSED ERRATA | QA Contact: | Shruti Sampat <ssampat> | |
Severity: | high | Docs Contact: | ||
Priority: | medium | |||
Version: | 2.1 | CC: | amarts, avishwan, dtsang, knarra, mmahoney, nsathyan, pprakash, rhs-bugs, sabose, sankarshan, sdharane, shtripat, ssampat, vbellur | |
Target Milestone: | --- | |||
Target Release: | --- | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | glusterfs-3.4.0.10rhs | Doc Type: | Enhancement | |
Doc Text: |
Feature:
This feature allows the admin to get the uuid of the node (on which the command is executed).
Usage: gluster system:: uuid get
Reason:
This is required because we generate uuid of a node in a lazy manner. ie, we generate a uuid for the node, only on the first volume or peer operation, when the node requires an external identity.
Result (if any):
With this command, we can force[1] the uuid generation, without a volume or peer operation performed. The uuid is persisted at /var/lib/glusterd/glusterd.info
|
Story Points: | --- | |
Clone Of: | ||||
: | 971661 975684 (view as bug list) | Environment: | ||
Last Closed: | 2013-09-23 22:39:42 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: | 971661 |
Description
Kanagaraj
2013-05-09 08:53:37 UTC
Verified as fixed in glusterfs-3.4.0.10rhs. UUID being generated and persisted in /var/lib/glusterd/glusterd.info on running the command - # gluster system:: uuid get 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. http://rhn.redhat.com/errata/RHBA-2013-1262.html 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. http://rhn.redhat.com/errata/RHBA-2013-1262.html |