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

Bug 1934129

Summary: [Gluster] Unable to import existing gluster configuration into newly created cluster
Product: [oVirt] ovirt-engine Reporter: Artur Socha <asocha>
Component: BLL.GlusterAssignee: Artur Socha <asocha>
Status: CLOSED CURRENTRELEASE QA Contact: SATHEESARAN <sasundar>
Severity: high Docs Contact:
Priority: high    
Version: 4.4.5.6CC: bugs, dfodor, godas, mperina, rchikatw, sasundar
Target Milestone: ovirt-4.4.6Flags: pm-rhel: ovirt-4.4+
Target Release: 4.4.6.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-engine-4.4.6.1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-06-04 05:41:06 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Artur Socha 2021-03-02 14:57:05 UTC 
Description of problem:
Unable to create gluster cluster with imported host's configuration

Steps to Reproduce:
1.  Go to Clusters -> 'new' 
2.  Under 'General' tab select 'Enable Gluster Service' checkbox
3.  Select 'Import existing gluster configuration'
4.  Enter host's configuration to import existing gluster configuration from
5.  On multi host add popup panel enter passwords and hit OK
6.  Action fails with ssh authentication error message 

Additional info:
This issue was introduced as side effect of enabling the support for non-RSA keys for ssh communication between engine and its hosts.
https://bugzilla.redhat.com/1837221

For backward compatibility hosts with only fingerprints stored in db are treated as legacy hosts and public keys of RSA type are assumed. 
In the described gluster flow, the fingerprints are fetched from hosts and host's ssh is always providing the strongest available key ie ECDSA from which fingerprint is calculated therefore causing this issue.
Comment 1 SATHEESARAN 2021-05-18 04:50:18 UTC 
Verified with RHV 4.4.6.7-0.1.el8ev and when creating a new gluster enabled cluster,
the existing gluster cluster hosts can be imported in to the new cluster.