Bug #5209
closed
Bug #5172: ncf-api does not run as root and cannot use command to read/write promises
Bug #5194: correct permission on /var/rudder/configuration-repository so ncf-builder can write/delete techniques
Some issues on perms still persists even with shared repository
Added by Vincent MEMBRÉ over 10 years ago.
Updated over 10 years ago.
Category:
System integration
Description
even when setting configuration-repsoitory to be shared with the group (git init --shared=group) rudder, jetty still modify perms some files in .git/object, making making impossible for ncf-api user to commit in Rudder
setting umask in jetty to 007 instead of 027, would solve the issue.
We also need to harmonize umask in all script interacting with that git repository
- Status changed from New to Pending technical review
- Assignee changed from Vincent MEMBRÉ to Jonathan CLARKE
- Pull Request set to https://github.com/Normation/rudder-packages/pull/433
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset packages:commit:c24f70ada4df3ded8e9f0ffb8aec95446fd58d6e.
Applied in changeset packages:commit:e0dbfc41c3b13296d04cf316e29055f3a4503ded.
- Status changed from Pending release to In progress
- Assignee changed from Jonathan CLARKE to Vincent MEMBRÉ
The PR was on master ... reverting ....
- Status changed from In progress to Pending release
Applied in changeset packages:commit:45a03d24b6778258a88f54d38681d600d9af4fc8.
Applied in changeset packages:commit:c018e6beb7a2ea604ca87cd60c60b1ffd8b80837.
- Status changed from Pending release to Released
Also available in: Atom
PDF
Updated by 
Updated by Jonathan CLARKE