Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1142705

Summary: [RFE]Option to specify a keyfile needed for Geo-replication create push-pem command.
Product: [Community] GlusterFS Reporter: Aravinda VK <avishwan>
Component: geo-replicationAssignee: Ajeet Jha <ajha>
Status: CLOSED DUPLICATE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: mainlineCC: aavati, ajha, avishwan, bugs, csaba, dnarayan, gluster-bugs, nlevinki, nsathyan, storage-qa-internal
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: 1139105 Environment:
Last Closed: 2014-09-17 09:04:33 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1136296, 1139105    
Bug Blocks:    

Description Aravinda VK 2014-09-17 08:55:58 UTC
+++ This bug was initially created as a clone of Bug #1139105 +++

+++ This bug was initially created as a clone of Bug #1136296 +++

Description of problem: 

    Currently geo-replication needs password-less ssh to be set up using the default key "~/.ssh/id_rsa" located at root users home directory. It should be possible to create password-less ssh using other keyfile, and an option to geo-replication create push-pem command to specify this keyfile. Geo-replication must use this key for further operations. 

    When setting geo-replication through RHSC, if the key file  "~/.ssh/id_rsa"  is not present . We will have to generate the key and use it. But since the location of keyfile is root users home directory. If root user runs ssh-keygen or deletes the keyfile at a later point of time the keyfile used for geo-replication will be gone and geo-replication stops functioning. So if we can specify a keyfile to geo-replication, we can have the keyfile stored in a safe location where it is not easily meddled by users. 

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

--- Additional comment from RHEL Product and Program Management on 2014-09-08 01:22:22 EDT ---

Since this issue was entered in bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

Comment 1 Aravinda VK 2014-09-17 09:04:33 UTC

*** This bug has been marked as a duplicate of bug 1136296 ***