Bug #4644
closed
Cannot upgrade from 2.9.2 to 2.9.4 due to an error on '/etc/logrotate.d/rudder'
Added by Vincent MEMBRÉ about 10 years ago.
Updated about 9 years ago.
Description
I tried upgrading a Rudder server (debian squeeze) from 2.9.2 to 2.9.4 but at the end (seems rudder-server-root postinst)
I get that error (sorry about the french in error ...) :
Paramétrage de rudder-server-root (2.9.4-squeeze0) ...
Installation de la nouvelle version du fichier de configuration /etc/init.d/rudder-server-root ...
Preserving user changes to /etc/logrotate.d/rudder (renamed from /etc/logrotate.d/rudder-server-root)...
mv: impossible d'évaluer « /etc/logrotate.d/rudder »: Aucun fichier ou dossier de ce type
dpkg : erreur de traitement de rudder-server-root (--configure) :
le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1
configured to not write apport reports
Des erreurs ont été rencontrées pendant l'exécution :
rudder-server-root
E: Sub-process /usr/bin/dpkg returned an error code (1)
Saying that '/etc/logrotate.d/rudder' is missing, but this file is actually present ...
The server seems to work fine but the installation is not complete...
- Status changed from New to 8
- Assignee set to Matthieu CERDA
- Priority changed from 2 to 1
- Target version changed from 2.9.5 to 2.9.6
- Target version changed from 2.9.6 to 2.9.7
- Target version changed from 2.9.7 to 150
- Target version changed from 150 to 2.10.4
- Target version changed from 2.10.4 to 2.10.5
- Status changed from 8 to Pending technical review
- Assignee changed from Matthieu CERDA to Benoît PECCATTE
- Pull Request set to https://github.com/Normation/rudder-packages/pull/461
This is a bit of a weird one. We use the "dpkg-maintscript-helper mv_conffile" helper to move the old config file (/etc/logrotate.d/rudder-server-root) to it's new name (/etc/logrotate.d/rudder). However, this helper tries to mv the new file to /etc/logrotate.d/rudder.dpkg-new, without checking if it exists. This seems weird to me, and at least some other people, as shown in https://code.launchpad.net/~neil-aldur/ubuntu/precise/iptables-persistent/fix-for-967018-905517/+merge/100652.
However, the workaround is simple: we touch the new file if it doesn't exist, so that "dpkg-maintscript-helper mv_conffile" always succeeds.
- Target version changed from 2.10.5 to 2.10.6
- Status changed from Pending technical review to In progress
- Assignee changed from Benoît PECCATTE to Jonathan CLARKE
- Status changed from In progress to Pending technical review
- Assignee changed from Jonathan CLARKE to Benoît PECCATTE
- Pull Request changed from https://github.com/Normation/rudder-packages/pull/461 to https://github.com/Normation/rudder-packages/pull/485
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset commit:a5fec0d5941792e6b583d0e462e65a1bbd672f0c.
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.10.6, which was released today.
Check out:
This bug has been fixed in Rudder 2.10.6, which was released today.
Check out:
- Project changed from 34 to Rudder
- Category set to Packaging
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by Nicolas PERRON 
Updated by 
Updated by Matthieu CERDA