Project

General

Profile

Actions
Copy link

Bug #3004

closed

(ex PT/ Technique)ManageFileAndFolder: Try to set permissions on folder with action set to "do nothing" result in unknow state in reporting

Added by Nicolas PERRON about 12 years ago. Updated over 11 years ago.

Status:
Rejected
Priority:
1 (highest)
Assignee:
Matthieu CERDA
Category:
Techniques
Target version:
2.3.13
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

On Rudder 2.4~beta4, trying to use ManageFileAndFolder permission to ensure permissions on an existing folder with "Do nothing" in action lead to a bug in reporting.
The reporting will returns two succes: "No action on..." and "The element [...] was not set to be created" which result in unkown state.

To reproduce, point to a folder:
  • set "Set action on a file or folder" to "Do nothing"
  • set "Set permissions" to "Yes, enforce permissions"
  • Set "File mode" to User => Read, Write, Exec Group => Read, Exec Other => Read, Exec
  • Set "File Owner (optional)" to "root"
  • Set "File Group (optional)" to "root"
  • Set "Set these permissions" to "On this path only"

Related issues 1 (0 open — 1 closed)

Is duplicate of Rudder - Bug #3131: Manage files and folders Technique has improper reporting when dealing with non existent file we don't wish to createReleasedMatthieu CERDA2013-01-02Actions
Actions
Copy link

Also available in: Atom PDF