RDO tickets are now tracked in Jira https://issues.redhat.com/projects/RDO/issues/
Bug 1272970 - glusterfs_native: cannot connect via SSH using password authentication to multiple gluster clusters with different passwords
Summary: glusterfs_native: cannot connect via SSH using password authentication to mul...
Keywords:
Status: CLOSED EOL
Alias: None
Product: RDO
Classification: Community
Component: openstack-manila
Version: Liberty
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: Kilo
Assignee: Pete Zaitcev
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-19 10:22 UTC by krishnaram Karthick
Modified: 2016-05-19 15:49 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-19 15:49:01 UTC
Embargoed:


Attachments (Terms of Use)

Description krishnaram Karthick 2015-10-19 10:22:22 UTC
Description of problem:

glusterfs_native driver picks a volume from among different Gluster clusters and serves it as a share. The host node running Manila services connects via SSH to remote Gluster clusters. There's a config option, 'glusterfs_native_server_password', provided to connect to a remote server by password based authentication.

But this config option holds only one password, and it's used to connect to different remote backends.

https://github.com/openstack/manila/commit/ca294a7449601d6f4763fccdb0022fb03a2c82f6#diff-b3aecadf35ea04da97e8c26fd719a28bR53

So if the different remote backends do not have the same password, then connection cannot be established with the remote backends.

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

# rpm -qa | grep 'manila'
python-manila-1.0.0.0-rc2.dev24.el7.centos.noarch
python-manilaclient-1.4.1-dev3.el7.centos.noarch
openstack-manila-1.0.0.0-rc2.dev24.el7.centos.noarch
openstack-manila-share-1.0.0.0-rc2.dev24.el7.centos.noarch

How reproducible:
Always

Comment 1 Chandan Kumar 2016-05-19 15:49:01 UTC
This bug is against a Version which has reached End of Life.
If it's still present in supported release (http://releases.openstack.org), please update Version and reopen.


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