Bug 1172058 - push-pem does not distribute common_secret.pem.pub
Summary: push-pem does not distribute common_secret.pem.pub
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: geo-replication
Version: 3.6.1
Hardware: Unspecified
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Aravinda VK
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-12-09 10:19 UTC by zsarosi
Modified: 2016-08-19 11:33 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-08-19 11:33:52 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description zsarosi 2014-12-09 10:19:03 UTC
Description of problem:
gluster volume geo-replication ... create push-pem  command reports success, but the keys are not distributed to the slaves.

Version-Release number of selected component (if applicable):
3.6.1


How reproducible:
almost always

Steps to Reproduce:
1. create and start 2 x 2 gluster replicas (2 x replicas on master side, 2 x replicas on slave side)
2. generate ssh key for the root on master1 server (/root/.ssh/id_rsa), add the public key (/root/.ssh/id_rsa.pub) to the slave1 and slave2 to (/root/.ssh/authorized_keys)
3. generate common_keys on master1 using: gluster system:: execute gsec_create
4. create geo-replication: gluster volume geo-replication volume_master slave1::volume_slave create push-pem
5. on slaves: cat /root/.ssh/authorized_keys

Actual results:
on the slave1 and slave2 /root/.ssh/authorized_keys file contains only the public keys of the root@master1 (the one from step 2) and not the common_secret.pem.pub keys from step 3, hence starting the gluster geo-replication fails.

Expected results:
on both slave1 and slave2 /root/.ssh/authorized_keys should contain the common_secret.pem.pub public keys generated in step 3

Additional info:

Comment 1 Aravinda VK 2016-08-19 11:33:52 UTC
This bug is being closed as GlusterFS-3.6 is nearing its End-Of-Life and only important security bugs will be fixed. This bug has been fixed in more recent GlusterFS releases. If you still face this bug with the newer GlusterFS versions, please open a new bug.


Note You need to log in before you can comment on or make changes to this bug.