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

Bug 785956

Summary:	add openssh-clients to ovirt-engine spec file
Product:	[Retired] oVirt	Reporter:	Joey Boggs <jboggs>
Component:	ovirt-engine-core	Assignee:	Doron Fediuck <dfediuck>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	abaron, acathrow, bazulay, danken, iheim, robert, ykaul
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-02-08 22:33:55 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Joey Boggs 2012-01-31 02:32:46 UTC

If using a minimal Fedora install it will be missing openssh-clients. After approving nodes, the install will fail as it can not ssh to the node to setup keys and finish the remainder of the install

patch: http://gerrit.ovirt.org/#change,1368

Comment 1 Doron Fediuck 2012-01-31 08:59:35 UTC

Hi Joey,
It looks like a misunderstanding.
The Engine core does not need SSH client in order to create SSH session.
The core uses a Java library for client SSH connections.
The ovirt node should have an SSH server up & running, so the core could
create an SSH connection into it.

Please give us some more information on the error you hit so we'll try and
resolve the issue.

Comment 2 Joey Boggs 2012-01-31 14:02:27 UTC

Interesting, the engine was unable to connect to the node after approving it to finish the key exchange and setup. Once openssh-clients was installed it connected and finished without a problem


2005-02-09 20:39:26,989 INFO  [org.ovirt.engine.core.bll.CBCInstaller] (pool-5-thread-3) Installation of 192.168.1.81. Executing oVirt installation stage. (Stage: Starting Host installation)
2005-02-09 20:39:26,989 INFO  [org.ovirt.engine.core.bll.CBCInstaller] (pool-5-thread-3) Installation of 192.168.1.81. Executing oVirt installation stage. (Stage: Connecting to Host)
2005-02-09 20:39:27,095 ERROR [org.ovirt.engine.core.bll.VdsInstaller] (pool-5-thread-3) Installation of 192.168.1.81 has failed. Failure details: Failed connecting to 192.168.1.81 using Public-Key! Please verify that the host accepts public-key authentication. (Stage: Connecting to Host)
2005-02-09 20:39:27,095 INFO  [org.ovirt.engine.core.bll.InstallerMessages] (pool-5-thread-3) VDS message: Failed connecting to 192.168.1.81 using Public-Key! Please verify that the host accepts public-key authentication
2005-02-09 20:39:27,095 ERROR [org.ovirt.engine.core.utils.hostinstall.MinaInstallWrapper] (pool-5-thread-3) Could not connect to server 192.168.1.81: Failed connecting to 192.168.1.81 using Public-Key! Please verify that the host accepts public-key authentication

Comment 3 Doron Fediuck 2012-01-31 17:29:20 UTC

Joey,
This log snip shows that the engine opened an SSH session, and tried
to authenticate using public-key auth. The auth stage failed, and we
need more information to understand why. Installing ssh client has
no direct relevance to it. 
Is it possible to reproduce it?
If so, please contact me directly and we'll try to resolve it together.

Comment 4 Robert Middleswarth 2012-06-13 23:35:41 UTC

I was also just about to open the same bug.  Just had the same issue.

Thanks
Robert