Description of problem: ------------------------ when we deploy gluster using colonizer from a node , the domain name is not being suffixed to the localnode. Atleast that is what shows up in peer status when seen from other nodes. However, I don't see any impact, at the outset, as I am still able to create volumes using either g1-1 or g1-1.exam.com as the hostname (hostname does show as g1-1.exam.com) Version-Release number of selected component (if applicable): --------------- colonizer-1.1.2 [root@g1-2 test]# gluster peer status Number of Peers: 3 Hostname: g1-1 ----->colonizer was run from this node Uuid: 7b5ec962-9ca2-41f1-a0e0-8be3715df816 State: Peer in Cluster (Connected) Hostname: g1-3.exam.com Uuid: cb51b44e-b447-46a0-b5b4-92dc5aefd1d0 State: Peer in Cluster (Connected) Hostname: g1-4.exam.com Uuid: 27ebf41c-c727-4792-95eb-42d52be9bb52 State: Peer in Cluster (Connected) [root@g1-2 test]# exam.com was the domain name Steps to Reproduce: 1.deploy colonizer from one of the nodes 2.enter a domain name say example.com 3.let deployment pass 4. issue gluster peer status from other nodes Actual results: ============
This is actually a gdeploy bug with the peer module: BZ1552750
Closing all Colonizer BZs (as DEFERRED) as we do not intend to work on them for the time being.