Actions
Bug #19498
closed
Uninstalling rudder-agent and re-installing ends with malfunctioning rudder services
Status:
Rejected
Priority:
N/A
Assignee:
Category:
Packaging
Target version:
Pull Request:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Small
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
No
Description
At least on debian 11, Reinstalling rudder-agent after removing it ends with malfunctioning rudder services
apt-get remove rudder-agent
apt-get install rudder-agent
service rudder-cf-execd status
● rudder-cf-execd.service - CFEngine Execution Scheduler
Loaded: loaded (/lib/systemd/system/rudder-cf-execd.service; disabled; vendor preset: enabled)
Active: inactive (dead)
~# service rudder-cf-serverd status
● rudder-cf-serverd.service - CFEngine file server
Loaded: (/lib/systemd/system/rudder-cf-serverd.service; disabled; vendor preset: enabled)
Active: inactive (dead)
running the following command fix the agent:
systemctl enable rudder-cf-execd systemctl enable rudder-cf-serverd systemctl enable rudder-agent systemctl start rudder-cf-execd systemctl start rudder-cf-serverd systemctl start rudder-agent
Updated by Vincent MEMBRÉ over 3 years ago
- Target version changed from 6.2.8 to 6.2.9
Updated by Vincent MEMBRÉ over 3 years ago
- Target version changed from 6.2.9 to 6.2.10
Updated by Vincent MEMBRÉ over 3 years ago
- Target version changed from 6.2.10 to 6.2.11
Updated by Vincent MEMBRÉ about 3 years ago
- Target version changed from 6.2.11 to 6.2.12
Updated by Vincent MEMBRÉ about 3 years ago
- Target version changed from 6.2.12 to 6.2.13
Updated by Alexis Mousset about 3 years ago
- Severity set to Major - prevents use of part of Rudder | no simple workaround
- User visibility set to Operational - other Techniques | Rudder settings | Plugins
- Effort required set to Small
- Priority changed from 0 to 62
Still happens regularly.
Updated by Alexis Mousset about 3 years ago
This happens because the postinst script detects the previous install and consider the situation as:
- an upgrade
- with currently disabled cf-server and cf-execd services
so we don't enable them. We need a better detection logic.
Updated by Alexis Mousset about 3 years ago
- Status changed from New to In progress
- Assignee set to Alexis Mousset
Updated by Alexis Mousset almost 3 years ago
- Status changed from In progress to New
- Priority changed from 62 to 61
Updated by Vincent MEMBRÉ over 2 years ago
- Target version changed from 6.2.13 to 6.2.14
- Priority changed from 61 to 59
Updated by Vincent MEMBRÉ over 2 years ago
- Target version changed from 6.2.14 to 6.2.15
- Priority changed from 59 to 57
Updated by Vincent MEMBRÉ over 2 years ago
- Target version changed from 6.2.15 to 6.2.16
- Priority changed from 57 to 56
Updated by Alexis Mousset over 2 years ago
- Target version changed from 6.2.16 to 6.2.17
Updated by Vincent MEMBRÉ over 2 years ago
- Target version changed from 6.2.17 to 997
- Priority changed from 56 to 0
Updated by Vincent MEMBRÉ over 2 years ago
- Target version changed from 997 to 6.2.18
Updated by Vincent MEMBRÉ over 2 years ago
- Target version changed from 6.2.18 to 6.2.19
Updated by Vincent MEMBRÉ over 2 years ago
- Target version changed from 6.2.19 to 6.2.20
Updated by Vincent MEMBRÉ about 2 years ago
- Target version changed from 6.2.20 to old 6.2 issues to relocate
Updated by Alexis Mousset over 1 year ago
- Status changed from New to Rejected
- Regression set to No
Updated by Alexis Mousset over 1 year ago
- Is duplicate of Bug #22413: When we uninstall and reinstall an agent, the agent is not correctly activated added
Actions