Bug #3997: /etc/{init.d,default}/rudder-agent is removed if the package rudder-agent is upgraded from 2.4.8 on SuSE or RHEL/CentOS - Rudder - Issue Tracker

Actions

Copy link

Bug #3997

closed

/etc/{init.d,default}/rudder-agent is removed if the package rudder-agent is upgraded from 2.4.8 on SuSE or RHEL/CentOS

Added by Nicolas PERRON over 10 years ago. Updated about 9 years ago.

Status:

Released

Priority:

Assignee:

Jonathan CLARKE

Category:

Packaging

Target version:

2.4.10

Pull Request:

https://github.com/Normation/rudder-p...

Severity:

UX impact:

User visibility:

Effort required:

Priority:

Name check:

Fix check:

Regression:

Description

The upgrade of rudder-agent from the versions 2.4.8 on SuSE or RHEL/CentOS will lead to a serious bug which is the removal of /etc/{init.d,default}/rudder-agent

Related issues 2 (0 open — 2 closed)

Actions

Copy link

Updated by Nicolas PERRON over 10 years ago

Status changed from New to Pending technical review
Assignee changed from Nicolas PERRON to Jonathan CLARKE
% Done changed from 0 to 100
Pull Request set to https://github.com/Normation/rudder-packages/pull/137

Pull Reques URL added: https://github.com/Normation/rudder-packages/pull/137

Actions

Copy link

Updated by Nicolas PERRON over 10 years ago

#3995 originally added the code of the actual PR but on the branch 2.4, the cron file was not yet /etc/cron.d/rudder-agent but /etc/crontab. The consequence was that upgrade of rudder-agent failed at the preinst stage (backup of a file which does not exist) and the script check-rudder-agent too.

Actions

Copy link

Updated by Nicolas PERRON over 10 years ago

Status changed from Pending technical review to Pending release

Applied in changeset commit:912682bdf67099c8b2432bf2585132c581f448fa.

Actions

Copy link

Updated by Nicolas PERRON over 10 years ago

Applied in changeset commit:796dc6817970ff88471818d079190c6980001067.

Actions

Copy link

Updated by Nicolas PERRON over 10 years ago

Status changed from Pending release to Released

This bug has been fixed in Rudder 2.4.10 but was not publicly annouced as it unfortunately did not meet our quality and assurance requirements. It has also been fixed in Rudder 2.4.11, which was released today.
Check out: