Description of problem: UUID of the host is not generated(or deferred) till the time an another host is peer probed or a volume is created. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Through should be a gluster cli command to trigger the UUID generation when needeed. Additional info: In RHS-C, currently we are using IP/name(fqdn) of the host for all our operations and uniquely identify a particular host. But we are hitting lot issues due to the hosts having multiple interfaces and hence multiple ip addresses. More specifically when the hosts are peer probed through cli using different interface/bridge/ip and but added to engine with a different ip. So we have decided to go with the gluster UUID of the host for most of the operations and also to uniquely identify a particular host. The uuid will be fetched when the user adds the node to the rhsc and then stored in the database forever. In this case the vdsm reads the uuid file and returns the uuid to engine
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