Description of problem: If the user is created without primary group in mount-broker setup, geo-rep fails to set proper ownership of .ssh and authorized keys. which consequently fails mount-broker setup. Version-Release number of selected component (if applicable): glusterfs-3.6.0.8-1 How reproducible: Happens everytime. Steps to Reproduce: 1. create and start a master and slave volumes. 2. Create a new group on the slave nodes. For example, geogroup 3. Create a unprivileged account on the slave nodes without the primary group. For example, geoaccount. Make it a member of geogroup on all the slave nodes. CMD : "useradd geoaccount -N -G geogroup" 4. Create a new directory on all the slave nodes owned by root and with permissions 0711. Ensure that the location where this directory is created is writable only by root but geoaccount is able to access it. For example, create a mountbroker-root directory at /var/mountbroker-root. 5. Add the following options to the glusterd volfile on the slave nodes, (which you can find in /etc/glusterfs/glusterd.vol) assuming the name of the slave volume as slavevol: option mountbroker-root /var/mountbroker-root option mountbroker-geo-replication.geoaccount slavevol option geo-replication-log-group geogroup option rpc-auth-allow-insecure on 6. Restart glusterd on all the slave nodes. 7. Setup a passwdless ssh from one of the master node, to user on one of the slave node. For ex: to geoaccount 8. Create geo-rep relationship between master and slave to the user from master one of the master node. for ex: gluster volume geo-rep MASTERNODE geoaccount@SLAVENODE::slavevol create push-pem 9. In the slavenode which is used to create relationship, run /usr/libexec/glusterfs/set_geo_rep_pem_keys.sh as a root with user name as argument. Ex: # /usr/libexec/glusterfs/set_geo_rep_pem_keys.sh geoaccount Start the geo-rep with slave user Ex: gluster volume geo-rep MASTERNODE geoaccount@SLAVENODE::slavevol start Actual results: set_geo_rep_pem_keys.sh actually fails to setup proper ownership of authorized keys Expected results: It shouldn't be able to set proper ownership. Additional info:
Fix at https://code.engineering.redhat.com/gerrit/26327
verified on the build glusterfs-3.6.0.25-1
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/RHEA-2014-1278.html