Bug #5464
closed
Make the rudder-upgrade script more verbose in case of failures
Added by Matthieu CERDA about 10 years ago.
Updated over 9 years ago.
Description
Currently, rudder-upgrade aborts when something fails during the upgrade (set -e)
This is a problem, as it makes debugging or simply interpreting the trouble harder to understand due to the lack of output ( lots of redirections to /dev/null)
We should provide a way to output at least the step that failed to be able to pinpoint the problem :)
- Project changed from Rudder to 34
- Status changed from In progress to Pending technical review
- Assignee changed from Matthieu CERDA to Jonathan CLARKE
- % Done changed from 0 to 100
- Pull Request set to https://github.com/Normation/rudder-packages/pull/469
- Status changed from Pending technical review to Pending release
Applied in changeset commit:41046f4762593529ad623b2dafeb65c102856faa.
Applied in changeset commit:bc388b481aa3a435fbe3e1344aa856ca7fa60316.
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.11.3, which was released on the 25/09/2014.
- Project changed from 34 to Rudder
- Category set to Packaging
Also available in: Atom
PDF