Description of problem: Enumerated host names like g1, g2, g3, etc can cause entries in /etc/hosts to get overwritten when numbers are in double digits and the order of assignment in the ansible play puts a smaller number after a bigger number. For instance, if g12 is populated in the hosts file first, then g1 would overwrite that entry because of a bad regex match. Version-Release number of selected component (if applicable): v1.0.2 How reproducible: Mostly consistently, but could vary with random-ish order of play operations Steps to Reproduce: 1. Deploy colonizer to 12 nodes 2. Enumerate hostnames g{1..12} Actual results: Colonizer fails, possibly at variable plays after the hosts file is populated. Expected results: Colonizer populates the hosts file correctly and completes Additional info:
Upstream merge commit corrects this problem: https://github.com/gluster/gluster-colonizer/commit/cb9f5a36b7471af95857c4af8debc73185a934a8
Dustin, How do i verify this as I have only 6 nodes?
Try manually naming the nodes: node1 node10 node100 node1000 node10000 node100000 Prior to the fix, this will almost definitely trigger the problem.
i see that colonizer is able to take names bigger than 2 letters. However , for some reason i am seeing failures in deployment not completing. I guess the last entry is not getting peer probed
i see hostnames being taken with as big as even 10 letters and /etc/hosts not having any descrepencies , hence moving to verified however raised a new bz#1553011 - Colonizer seems to be failing when hostnames are entered manuall
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://access.redhat.com/errata/RHEA-2018:0477