Bug #20792
closed
When upgrading from 6.2 to 7.0, the previous rudder logrotate configuration is not removed
Added by Nicolas CHARLES almost 3 years ago.
Updated over 2 years ago.
Description
7.0 introduce
rudder-apache
rudder-relay
rudder-slapd
while 6.x had
rudder
All nodes with a server role had this logrotate file, so we need to clean it on all servers
- Status changed from New to In progress
- Assignee set to Nicolas CHARLES
- Status changed from In progress to Pending technical review
- Assignee changed from Nicolas CHARLES to Félix DALLIDET
- Pull Request set to https://github.com/Normation/rudder-techniques/pull/1747
- Status changed from Pending technical review to Pending release
When I upgrade from 6.2 to 7.0.1 in debian 11 after an agent run, the file /etc/logrotate.d/rudder is still present on the server
- Fix check changed from To do to Error - Blocking
I updated from 6.2.13-nightly to 7.0.2-nightly and the content of /etc/logrotate.d/ did not changed at all:
Installing new version of config file /opt/rudder/etc/rudder-apache-webapp-ssl.conf ...
Installing new version of config file /opt/rudder/etc/rudder-apache-webapp-nossl.conf ...
Setting up rudder-server-root (7.0.2~git202203150234-debian11) ...
Processing triggers for rsyslog (8.2102.0-2) ...
Processing triggers for libc-bin (2.31-13+deb11u2) ...
root@server:/home/vagrant# ls /etc/logrotate.d/
alternatives apache2 apt btmp chrony dbconfig-common dpkg postgresql-common rsyslog rudder unattended-upgrades wtmp
- Fix check changed from Error - Blocking to Checked
Oups, it's converging after one more rudder agent run -u:
root@server:/home/vagrant# ls /etc/logrotate.d/
alternatives apache2 apt btmp chrony dbconfig-common dpkg postgresql-common rsyslog rudder-apache rudder-relay rudder-slapd unattended-upgrades wtmp
- Status changed from Pending release to Released
This bug has been fixed in Rudder 7.0.2 and 7.1.0~rc1 which were released today.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by