Bug 856279 - Beaker Transfer rsync errors not scary enough
Summary: Beaker Transfer rsync errors not scary enough
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Beaker
Classification: Retired
Component: lab controller
Version: 0.9
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: 0.15.3
Assignee: Dan Callaghan
QA Contact:
URL:
Whiteboard: LogStorage
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-09-11 15:43 UTC by Sean Waite
Modified: 2018-02-06 00:41 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-02-03 04:51:38 UTC
Embargoed:


Attachments (Terms of Use)

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


Note You need to log in before you can comment on or make changes to this bug.