User story #14403: When running Rudder through applyConfig API on the root server, tmp directory is not the system one - Rudder - Issue Tracker

Actions

Copy link

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 almost 6 years ago. Updated over 4 years ago.

Status:

Released

Priority:

N/A

Assignee:

François ARMAND

Category:

Relay server or API

Target version:

6.1.0~beta1

Pull Request:

https://github.com/Normation/rudder-a...

UX impact:

Suggestion strength:

User visibility:

Operational - other Techniques | Rudder settings | Plugins

Effort required:

Very Small

Name check:

Fix check:

Checked

Regression:

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.

Related issues 1 (0 open — 1 closed)

Actions

Copy link

Updated by Alexis Mousset almost 6 years ago

Description updated (diff)

Actions

Copy link

Updated by Alexis Mousset almost 6 years ago

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

Actions

Copy link

Updated by Alexis Mousset almost 6 years ago

Related to Bug #14391: Only one Node below a Rudder server can be run through remote run API added

Actions

Copy link

Updated by Alexis Mousset almost 6 years ago

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

Actions

Copy link

Updated by François ARMAND almost 6 years ago

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.

Actions

Copy link

Updated by Vincent MEMBRÉ over 5 years ago

Target version changed from 4.3.11 to 4.3.12

Actions

Copy link

Updated by Vincent MEMBRÉ over 5 years ago

Target version changed from 4.3.12 to 4.3.13

Actions

Copy link

Updated by Vincent MEMBRÉ over 5 years ago

Target version changed from 4.3.13 to 4.3.14

Actions

Copy link

Updated by Vincent MEMBRÉ over 5 years ago

Target version changed from 4.3.14 to 587
Priority changed from 32 to 31

Actions

Copy link

#10

Updated by Alexis Mousset over 5 years ago

Category set to Relay server or API

Actions

Copy link

#11

Updated by Alexis Mousset over 5 years ago

Target version changed from 587 to 5.0.13

Actions

Copy link

#12

Updated by Vincent MEMBRÉ over 5 years ago

Target version changed from 5.0.13 to 5.0.14
Priority changed from 31 to 30

Actions

Copy link

#13

Updated by Vincent MEMBRÉ about 5 years ago

Target version changed from 5.0.14 to 5.0.15
Priority changed from 30 to 29

Actions

Copy link

#14

Updated by François ARMAND about 5 years ago

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.

Actions

Copy link

#15

Updated by Alexis Mousset about 5 years ago

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)