Bug 1079522

Summary: [RFE] Improve help for password-based ssh auth when collecting logs from hypervisors
Product: [Retired] oVirt Reporter: Vojtech Szocs <vszocs>
Component: ovirt-engine-logcollectorAssignee: Simone Tiraboschi <stirabos>
Status: CLOSED WONTFIX QA Contact: Pavel Stehlik <pstehlik>
Severity: low Docs Contact:
Priority: low    
Version: unspecifiedCC: bugs, dfediuck, didi, gklein, iheim, lveyde, rbalakri, sbonazzo, s.kieske, stirabos, yeylon
Target Milestone: ---Keywords: FutureFeature
Target Release: 3.6.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: integration
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-29 09:06:27 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:

Description Vojtech Szocs 2014-03-21 18:24:27 UTC
To enforce password-based ssh auth (fallback from key-based ssh auth) when collecting logs from hypervisors, user needs to do following:

  $ engine-log-collector -k ""

Note that -k option always requires some value (empty string in this case), otherwise it fails with following message:

  error: -k option requires an argument

Current help text for -k option says:

  If a identity file is not supplied the program will prompt for a password.

From above help text, it's not really obvious that user needs to specify empty string to enforce password-based ssh auth.

I suggest one of following (just ideas):

a, improve --help and man page documentation for -k option, for example:
   Provide empty string to make program prompt for a password.

b, introduce new option as shorthand for -k "", for example:
   $ engine-log-collector --use-pw-auth

Comment 1 Sandro Bonazzola 2014-06-11 06:50:56 UTC
This is an automated message:
This bug has been re-targeted from 3.4.2 to 3.5.0 since neither priority nor severity were high or urgent. Please re-target to 3.4.3 if relevant.

Comment 2 Itamar Heim 2015-03-29 09:06:27 UTC
Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug.