Merge lp:~javier.collado/utah/bug1161855 into lp:utah
Proposed by
Javier Collado
Status: | Merged | ||||
---|---|---|---|---|---|
Approved by: | Javier Collado | ||||
Approved revision: | 851 | ||||
Merged at revision: | 848 | ||||
Proposed branch: | lp:~javier.collado/utah/bug1161855 | ||||
Merge into: | lp:utah | ||||
Diff against target: |
250 lines (+103/-23) 5 files modified
debian/changelog (+1/-0) docs/source/reference.rst (+6/-3) tests/test_rsyslog.py (+22/-0) utah/config.py (+9/-1) utah/provisioning/rsyslog.py (+65/-19) |
||||
To merge this branch: | bzr merge lp:~javier.collado/utah/bug1161855 | ||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Andy Doan (community) | Approve | ||
Javier Collado (community) | Needs Resubmitting | ||
Review via email: mp+156139@code.launchpad.net |
Description of the change
This branch adds the ability to set failure patterns in the syslog
implementation so that the server stops if one of those patterns is found (not
only on timeout).
This is good not only to stop as soon as possible, but also to make sure that
an error code is return by the server process when a problem happens.
I've tested this with both desktop/server images and also introducing a problem
in the late/success_
To post a comment you must log in.
Looks good to me, but I haven't tested it yet. I guess maybe a latecommand designed to fail would be the best thing for that?