Actions
Bug #10834
closed
During upgrade from 3.1 to 4.1, rudder-server-relay install may fail
Pull Request:
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)
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
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 4.1.4 to 4.1.5
Updated by Alexis Mousset over 7 years ago
- Target version changed from 4.1.5 to 4.1.6
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.
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 4.1.6 to 4.1.7
Updated by Vincent MEMBRÉ about 7 years ago
- Target version changed from 4.1.7 to 4.1.8
- Priority changed from 51 to 50
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
Updated by Vincent MEMBRÉ almost 7 years ago
- Target version changed from 4.1.9 to 4.1.10
- Priority changed from 48 to 47
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
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
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
Updated by Benoît PECCATTE over 6 years ago
- Target version changed from 4.1.13 to 411
Updated by Benoît PECCATTE over 6 years ago
- Target version changed from 411 to 4.1.13
Updated by Vincent MEMBRÉ over 6 years ago
- Target version changed from 4.1.13 to 4.1.14
Updated by Benoît PECCATTE over 6 years ago
- Target version changed from 4.1.14 to 4.1.15
Updated by Vincent MEMBRÉ about 6 years ago
- Target version changed from 4.1.15 to 4.1.16
Updated by Vincent MEMBRÉ about 6 years ago
- Target version changed from 4.1.16 to 4.1.17
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