Bug 856279

Summary: Beaker Transfer rsync errors not scary enough
Product: [Retired] Beaker Reporter: Sean Waite <swaite>
Component: lab controllerAssignee: Dan Callaghan <dcallagh>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 0.9CC: asaha, bpeck, dcallagh, jnicolet, kbaker, llim, rmancy, xjia
Target Milestone: 0.15.3   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: LogStorage
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-03 04:51:38 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 Sean Waite 2012-09-11 15:43:15 UTC 
Description of problem:
When the transfer rsync passes, it has the quiet little rc=0 to indicate this. When it fails, it has the equally quiet little rc=5, rc=12, or whatever the error code happens to be. 

If you know what you are looking for, you can sort it out, but it'd be helpful to have a more obvious error message letting us know when something broke. Something simple like RSYNC FAILED WITH ERROR CODE 5 or something could be enough, or maybe a little more information if it's possible without cluttering up the logs (as in, we don't want -v set by default on the rsync).
Comment 1 Nick Coghlan 2012-10-17 04:37:42 UTC 
Bulk reassignment of issues as Bill has moved to another team.
Comment 4 Dan Callaghan 2014-01-21 02:42:32 UTC 
On Gerrit: http://gerrit.beaker-project.org/2706
Comment 7 Nick Coghlan 2014-02-03 04:51:38 UTC 
This change is included in the Beaker 0.15.3 maintenance release:

http://beaker-project.org/docs/whats-new/release-0.15.html#beaker-0-15-3