Bug #8004
closedTechnique "Cron job v3.0" does not use the "user" setting with predefined scheduled
Description
I had set up a cron job v3 in this technique and defined a certain user to be used.
The interval I set to "hourly" since that was fine.
It seems (at least) when using a predefined interval rudder drops the cron file in the /etc/cron.<interval> folder, forgetting about the run-as setting three lines above.
Of course this has some security implications, not to mention messed up permissions.
At least the rule configuration needs to be clear and direct about this.
I'd also bed you to have a dozen unit tests on this that test all the different code paths since they seem to be pretty independent.
[root@rudder cron.hourly]# cat /etc/cron.hourly/job-myuser
echo "id ; hallo" > /tmp/hallo
after the next cron hourly run we end up with this file:
[root@rudder cron.hourly]# ls -ltr /tmp/hallo
-rw-r--r-- 1 root root 11 Feb 29 22:01 /tmp/hallo
Reproduced in a clean env, same result.
Updated by Jonathan CLARKE over 7 years ago
- Severity set to Major - prevents use of part of Rudder | no simple workaround
- User visibility set to Getting started - demo | first install | level 1 Techniques
Updated by Nicolas CHARLES about 6 years ago
- Target version set to 4.1.17
- Priority changed from 58 to 0
Updated by Nicolas CHARLES about 6 years ago
- Status changed from New to In progress
- Assignee set to Nicolas CHARLES
Updated by Nicolas CHARLES about 6 years ago
- 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/1368
Updated by Rudder Quality Assistant about 6 years ago
- Assignee changed from Félix DALLIDET to Nicolas CHARLES
Updated by Nicolas CHARLES about 6 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder-techniques|d22a96c9b7d026ead15947d7c94c78007bd91bd8.
Updated by François ARMAND about 6 years ago
- Subject changed from Cron daemon configuration (3.0) does not actually handle the user setting to Technique "Cron job v3.0" does not use the "user" setting with predefined scheduled
- Description updated (diff)
Updated by Vincent MEMBRÉ about 6 years ago
- Status changed from Pending release to Released