Actions
Bug #13174
closedcan't upgrade debian package if /bin/systemd exist but sysv is used
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:
Very Small
Priority:
78
Name check:
Fix check:
Regression:
Description
Hi,
During upgrade rudder-agent.postinst check if systemd is used. Code below is the part in question :
if type systemctl > /dev/null ; then CFRUDDER_USE_SYSTEMD="true"; fi
But it's possible to have the binary /bin/systemctl and used sysv instead of systemd, specially when you have upgraded your system from debian 7 to debian 8.
Proposed solution:
pidof systemd >/dev/null 2>&1 ; then CFRUDDER_USE_SYSTEMD="true"; fi
Workaround :
mv /bin/systemctl{,.bak}
upgrade...
mv /bin/systemctl.bak /bin/systemctl
Updated by François ARMAND about 6 years ago
- User visibility set to Operational - other Techniques | Technique editor | Rudder settings
- Priority changed from 0 to 51
Thanks for the proposition, it seems to be a good solution (and sorry for the delay!).
Updated by Benoît PECCATTE about 6 years ago
- Effort required set to Very Small
- Priority changed from 51 to 79
Updated by Alexis Mousset about 6 years ago
- Status changed from New to In progress
- Assignee set to Alexis Mousset
Updated by Alexis Mousset about 6 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Alexis Mousset to Benoît PECCATTE
- Pull Request set to https://github.com/Normation/rudder-packages/pull/1693
Updated by Vincent MEMBRÉ almost 6 years ago
- Target version changed from 4.3.5 to 4.3.6
Updated by Alexis Mousset almost 6 years ago
- Status changed from Pending technical review to Pending release
- Priority changed from 79 to 78
Applied in changeset rudder-packages|8b6acc6d087db208baf167bdf89ac06a62a9823a.
Updated by Vincent MEMBRÉ almost 6 years ago
- Status changed from Pending release to Released
Actions