Project

General

Profile

Bug #14560

On error, rudder-upgrade stops without error message

Added by Nicolas CHARLES 10 months ago. Updated about 2 months ago.

Status:
Released
Priority:
N/A
Category:
Packaging
Target version:
Severity:
Minor - inconvenience | misleading | easy workaround
User visibility:
Getting started - demo | first install | Technique editor and level 1 Techniques
Effort required:
Very Small
Priority:
70

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

Associated revisions

Revision 63a9e44a (diff)
Added by Benoît PECCATTE 4 months ago

Fixes #14560: On error, rudder-upgrade stops without error message

History

#1

Updated by Vincent MEMBRÉ 10 months ago

  • Target version changed from 5.0.9 to 5.0.10
#2

Updated by Vincent MEMBRÉ 9 months ago

  • Target version changed from 5.0.10 to 5.0.11
#3

Updated by Vincent MEMBRÉ 8 months ago

  • Target version changed from 5.0.11 to 5.0.12
#4

Updated by Vincent MEMBRÉ 7 months ago

  • Target version changed from 5.0.12 to 5.0.13
#5

Updated by Vincent MEMBRÉ 5 months ago

  • Target version changed from 5.0.13 to 5.0.14
#6

Updated by François ARMAND 5 months 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
#7

Updated by Vincent MEMBRÉ 4 months ago

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

Updated by François ARMAND 4 months 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.

#9

Updated by Benoît PECCATTE 4 months ago

  • Status changed from New to In progress
#10

Updated by Benoît PECCATTE 4 months 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
#11

Updated by Benoît PECCATTE 3 months ago

  • Status changed from Pending technical review to Pending release
  • Priority changed from 73 to 71
#16

Updated by Vincent MEMBRÉ about 2 months 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.

Also available in: Atom PDF