Bug #7226: service_ensure_started_at_boot does not work on non-systemd systems with upsteam CFEngine stdlib - Rudder - Issue Tracker

Actions

Copy link

Bug #7226

closed

service_ensure_started_at_boot does not work on non-systemd systems with upsteam CFEngine stdlib

Added by Tomas Corej about 9 years ago. Updated over 2 years ago.

Status:

Released

Priority:

N/A

Assignee:

Benoît PECCATTE

Category:

Generic methods

Target version:

ncf-0.x

Pull Request:

https://github.com/Normation/ncf/pull...

Severity:

UX impact:

User visibility:

Effort required:

Priority:

Name check:

Fix check:

Regression:

Description

It does not work because there is typo in variable name:

"command_to_register" string => "${paths.path[update_rcd]} ${service_name} defaults";

but paths.path[update_rcd] does not exists, paths.path[update_rc_d] does . There is also same error in linux knowledge bundle so class update_rcd_utility_present is never evaluated .

Actions

Copy link

Updated by Tomas Corej about 9 years ago

Now I see that paths.path[update_rcd] is in cfengine library that is distributed with ncf. I've used original cfengine std lib from masterfiles. But it seems that this typo is in ncf stdlib as well.

Actions

Copy link

Updated by Jonathan CLARKE about 9 years ago

Subject changed from service_ensure_started_at_boot does not work on non-systemd systems to service_ensure_started_at_boot does not work on non-systemd systems with upsteam CFEngine stdlib
Target version set to 0.x

Thanks for this bug report, Tomas. You're right, something fishy has obviously happened with this key in paths. However, it works OK with ncf's copy of the stdlib, so I've clarified the subject.

Actions

Copy link