Project

General

Profile

Actions

Bug #10834

closed

During upgrade from 3.1 to 4.1, rudder-server-relay install may fail

Added by Vincent MEMBRÉ over 7 years ago. Updated about 6 years ago.

Status:
Rejected
Priority:
N/A
Assignee:
-
Category:
Packaging
Target version:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Operational - other Techniques | Technique editor | Rudder settings
Effort required:
Priority:
0
Name check:
Fix check:
Regression:

Description

During upgrade from 4.0.2 to 4.1.3, rudder-server-relay install may fail, because we transfered ownership of /opt/rudder/etc/rudder-networks.conf from rudder-webapp to rudder-server-relay

dpkg: error processing archive /var/cache/apt/archives/rudder-server-relay_4.1.3-jessie0_amd64.deb (--unpack): trying to overwrite '/opt/rudder/etc/rudder-networks.conf', which is also in 
                       package rudder-webapp 4.0.2-jessie0
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Actions #1

Updated by François ARMAND over 7 years ago

  • Severity set to Major - prevents use of part of Rudder | no simple workaround
  • User visibility set to Operational - other Techniques | Technique editor | Rudder settings
  • Priority changed from 0 to 36
Actions #2

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 4.1.4 to 4.1.5
Actions #3

Updated by Alexis Mousset over 7 years ago

  • Target version changed from 4.1.5 to 4.1.6
Actions #4

Updated by Benoît PECCATTE over 7 years ago

  • Priority changed from 36 to 52
Actions #5

Updated by Alexis Mousset over 7 years ago

  • Subject changed from During upgrade from 4.0.2 to 4.1.3, rudder-server-relay install may fail to During upgrade from 3.1 to 4.1, rudder-server-relay install may fail
  • Priority changed from 52 to 51

Changing version as it likely also happens on 3.1.

Actions #6

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 4.1.6 to 4.1.7
Actions #7

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 4.1.7 to 4.1.8
  • Priority changed from 51 to 50
Actions #8

Updated by Vincent MEMBRÉ about 7 years ago

  • Target version changed from 4.1.8 to 4.1.9
  • Priority changed from 50 to 49
Actions #9

Updated by Benoît PECCATTE about 7 years ago

  • Priority changed from 49 to 48
Actions #10

Updated by Vincent MEMBRÉ about 7 years ago

  • Target version changed from 4.1.9 to 4.1.10
  • Priority changed from 48 to 47
Actions #11

Updated by Vincent MEMBRÉ almost 7 years ago

  • Target version changed from 4.1.10 to 4.1.11
  • Priority changed from 47 to 45
Actions #12

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 4.1.11 to 4.1.12
  • Priority changed from 45 to 44
Actions #13

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 4.1.12 to 4.1.13
  • Priority changed from 44 to 43
Actions #14

Updated by Benoît PECCATTE over 6 years ago

  • Target version changed from 4.1.13 to 411
Actions #15

Updated by Benoît PECCATTE over 6 years ago

  • Target version changed from 411 to 4.1.13
Actions #16

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 4.1.13 to 4.1.14
Actions #17

Updated by Benoît PECCATTE over 6 years ago

  • Target version changed from 4.1.14 to 4.1.15
Actions #18

Updated by Vincent MEMBRÉ about 6 years ago

  • Target version changed from 4.1.15 to 4.1.16
Actions #19

Updated by Vincent MEMBRÉ about 6 years ago

  • Target version changed from 4.1.16 to 4.1.17
Actions #20

Updated by Alexis Mousset about 6 years ago

  • Status changed from New to Rejected
  • Priority changed from 43 to 0

The file was moved in 4.1, so the problem cannot occur anymore on supported versions. Closing.

Actions

Also available in: Atom PDF