Bug 879336

Summary:	often time-out during some wallaby commands
Product:	Red Hat Enterprise MRG	Reporter:	Lubos Trilety <ltrilety>
Component:	wallaby-utils	Assignee:	grid-maint-list <grid-maint-list>
Status:	CLOSED WONTFIX	QA Contact:	MRG Quality Engineering <mrgqe-bugs>
Severity:	medium	Docs Contact:
Priority:	low
Version:	Development	CC:	matt, willb
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:	2016-05-26 20:23:01 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:	879339
Bug Blocks:

Description Lubos Trilety 2012-11-22 16:05:08 UTC

Description of problem:
On slower machines some wallaby commands very often ends with time-out. In some cases they always end with time-out.

e.g.
# wallaby make-snapshot some
Console Connection Established...
fatal:  Timed out waiting for response

There should be some way how to change the time when the command should end.

Version-Release number of selected component (if applicable):
wallaby-utils-0.16.1-2

How reproducible:
80%

Steps to Reproduce:
1. load wallaby base database

# wallaby load /var/lib/condor-wallaby-base-db/condor-base-db.snapshot

2. try to make snapshot

# wallaby make-snapshot empty
Console Connection Established...
fatal:  Timed out waiting for response

  
Actual results:
timed out, no means how to edit default time-out

Expected results:
user can change default time-out (possibly per operation)

Additional info:

Comment 2 Anne-Louise Tangring 2016-05-26 20:23:01 UTC

MRG-Grid is in maintenance and only customer escalations will be considered. This issue can be reopened if a customer escalation associated with it occurs.