User story #14403
closed
When running Rudder through applyConfig API on the root server, tmp directory is not the system one
Added by Alexis Mousset over 5 years ago.
Updated over 4 years ago.
Category:
Relay server or API
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Very Small
Description
See https://www.maxoberberger.net/blog/2017/10/debian-9-private-tmp.html
When the apache daemon has a private /tmp dir (PrivateTmp systemd option), as the remote run is run by apache (which runs python, which runs the agent), the /tmp directory is a private directory (in /tmp/systemd-private-...
) and actions over /tmp do not affect system /tmp.
- Description updated (diff)
- Subject changed from When running Rudder through applyConfig API tmp directory is to When running Rudder through applyConfig API, tmp directory is not the system one
- Related to Bug #14391: Only one Node below a Rudder server can be run through remote run API added
- Subject changed from When running Rudder through applyConfig API, tmp directory is not the system one to When running Rudder through applyConfig API on the root server, tmp directory is not the system one
- Severity set to Minor - inconvenience | misleading | easy workaround
- User visibility set to Operational - other Techniques | Rudder settings | Plugins
- Priority changed from 0 to 32
This is very surprising, but it works as configured. I'm not sure we should do something.
- Target version changed from 4.3.11 to 4.3.12
- Target version changed from 4.3.12 to 4.3.13
- Target version changed from 4.3.13 to 4.3.14
- Target version changed from 4.3.14 to 587
- Priority changed from 32 to 31
- Category set to Relay server or API
- Target version changed from 587 to 5.0.13
- Target version changed from 5.0.13 to 5.0.14
- Priority changed from 31 to 30
- Target version changed from 5.0.14 to 5.0.15
- Priority changed from 30 to 29
- Effort required set to Very Small
- Priority changed from 29 to 54
very small => decide to either close that ticket and document it, or change the configuration.
- Tracker changed from Bug to User story
- Target version changed from 5.0.15 to 6.1.0~beta1
- Severity deleted (
Minor - inconvenience | misleading | easy workaround)
- Priority deleted (
54)
Still true in 6.0 as the relayd service may have PrivateTmp=True.
Let's document it!
- Status changed from New to In progress
- Assignee set to Alexis Mousset
- Status changed from In progress to Pending technical review
- Assignee changed from Alexis Mousset to François ARMAND
- Pull Request set to https://github.com/Normation/rudder-api-doc/pull/78
- Status changed from Pending technical review to Pending release
- Status changed from Pending release to Released
- Fix check changed from To do to Checked
Also available in: Atom
PDF