Description of problem: Dist-geo-rep: If .ssh directory not present(on slave cluster) then 'create push-pem force' is unable to put required keys and as a result geo-rep session is in faluty state Version-Release number of selected component (if applicable): 3.4.0.12rhs.beta1-1.el6rhs.x86_64 How reproducible: always Steps to Reproduce: 1.have a slave cluster which do not have .ssh directory 2. from master copy ssh-copy-id 3. from master - gluster system:: execute gsec_create 4. gluster volume geo-replication master_vol <slaveip::slave_vol> create push-pem force 5.gluster volume geo-replication master_vol <slaveip::slave_vol> start 6.gluster volume geo-replication master_vol <slaveip::slave_vol> status Actual results: [root@baratheon ~]# gluster volume geo-replication master1 10.70.43.110::slave status NODE MASTER SLAVE HEALTH UPTIME ------------------------------------------------------------------------------------- baratheon.blr.redhat.com master1 10.70.43.110::slave faulty N/A flash.blr.redhat.com master1 10.70.43.110::slave faulty N/A batman.blr.redhat.com master1 10.70.43.110::slave faulty N/A dragon.blr.redhat.com master1 10.70.43.110::slave faulty N/A Expected results: If .ssh Directory is not present, it should be created. Additional info:
It is working fine in the build, glusterfs-3.4.0.12rhs.beta3-1.el6rhs.x86_64.
verified with -3.4.0.18rhs-1.el6rhs.x86_64 working as per expected result , hence moving to verified
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