Project

General

Profile

Actions
Copy link

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.

Status:
Released
Priority:
1 (highest)
Assignee:
Jonathan CLARKE
Category:
Packaging
Target version:
2.11.3
Pull Request:
https://github.com/Normation/rudder-p...
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

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 :)

Actions
Copy link
 #1

Updated by Matthieu CERDA about 10 years ago

  • 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

PR is ready !

Actions
Copy link
 #2

Updated by Matthieu CERDA about 10 years ago

PR updated.

Actions
Copy link
 #3

Updated by Matthieu CERDA about 10 years ago

  • Status changed from Pending technical review to Pending release

Applied in changeset commit:41046f4762593529ad623b2dafeb65c102856faa.

Actions
Copy link
 #4

Updated by Benoît PECCATTE about 10 years ago

Applied in changeset commit:bc388b481aa3a435fbe3e1344aa856ca7fa60316.

Actions
Copy link
 #5

Updated by Vincent MEMBRÉ about 10 years ago

  • 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.

Actions
Copy link
 #6

Updated by Benoît PECCATTE over 9 years ago

  • Project changed from 34 to Rudder
  • Category set to Packaging
Actions
Copy link

Also available in: Atom PDF