Project

General

Profile

Actions
Copy link

Bug #14560

closed

On error, rudder-upgrade stops without error message

Added by Nicolas CHARLES over 5 years ago. Updated almost 5 years ago.

Status:
Released
Priority:
N/A
Assignee:
Alexis Mousset
Category:
Packaging
Target version:
5.0.15
Pull Request:
https://github.com/Normation/rudder-p...
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Getting started - demo | first install | Technique editor and level 1 Techniques
Effort required:
Very Small
Priority:
70
Name check:
Reviewed
Fix check:
Checked
Regression:

Description

let's say there is a typo in rudder-upgrade (like what was in #14338) - then the script stops abruptly, without any error

it makes debugging really hard

Files

Capture du 2019-04-01 16-15-45.png (60.2 KB) Capture du 2019-04-01 16-15-45.png Nicolas CHARLES, 2019-04-01 16:15
Actions
Copy link
 #1

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 5.0.9 to 5.0.10
Actions
Copy link
 #2

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 5.0.10 to 5.0.11
Actions
Copy link
 #3

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 5.0.11 to 5.0.12
Actions
Copy link
 #4

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 5.0.12 to 5.0.13
Actions
Copy link
 #5

Updated by Vincent MEMBRÉ about 5 years ago

  • Target version changed from 5.0.13 to 5.0.14
Actions
Copy link
 #6

Updated by François ARMAND about 5 years ago

  • Subject changed from when there is an error in rudder-upgrade, the script stops, without complaining loudly to On error, rudder-upgrade stops without error message
  • Severity set to Minor - inconvenience | misleading | easy workaround
  • User visibility set to Getting started - demo | first install | Technique editor and level 1 Techniques
  • Effort required set to Very Small
  • Priority changed from 0 to 74
Actions
Copy link
 #7

Updated by Vincent MEMBRÉ about 5 years ago

  • Target version changed from 5.0.14 to 5.0.15
  • Priority changed from 74 to 73
Actions
Copy link
 #8

Updated by François ARMAND about 5 years ago

  • Assignee set to Benoît PECCATTE

We already have a trap but it is not called. So we would like to have a way to either actually make it catch the "set -e" error, or have a wrapper around the script that observe the error.

Actions
Copy link
 #9

Updated by Benoît PECCATTE about 5 years ago

  • Status changed from New to In progress
Actions
Copy link
 #10

Updated by Benoît PECCATTE about 5 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Benoît PECCATTE to Alexis Mousset
  • Pull Request set to https://github.com/Normation/rudder-packages/pull/2107
Actions
Copy link
 #11

Updated by Benoît PECCATTE about 5 years ago

  • Status changed from Pending technical review to Pending release
  • Priority changed from 73 to 71
Actions
Copy link
 #12

Updated by Vincent MEMBRÉ about 5 years ago

  • Fix check set to To do
Actions
Copy link
 #13

Updated by Vincent MEMBRÉ about 5 years ago

  • Name check set to To do
Actions
Copy link
 #14

Updated by Alexis Mousset about 5 years ago

  • Name check changed from To do to Reviewed
Actions
Copy link
 #15

Updated by Alexis Mousset about 5 years ago

  • Fix check changed from To do to Checked
Actions
Copy link
 #16

Updated by Vincent MEMBRÉ almost 5 years ago

  • Status changed from Pending release to Released
  • Priority changed from 71 to 70

This bug has been fixed in Rudder 5.0.15 which was released today.

Actions
Copy link

Also available in: Atom PDF