Bug #2471
closed
PT filePermissions has Owner and Group values mandatory even if our choice is to not modify them
Added by Nicolas PERRON over 12 years ago.
Updated over 9 years ago.
Description
This happen in Rudder 2.3 with filePermissions 1.0
Files
1.png (216 KB)
1.png |
|
Jonathan CLARKE, 2012-07-05 17:37
|
|
- Project changed from Rudder to 24
- Category deleted (
Techniques)
- Assignee changed from Jonathan CLARKE to Matthieu CERDA
- Status changed from New to Discussion
- Assignee changed from Matthieu CERDA to Nicolas PERRON
I'm sorry, but when I try to create a Policy Instance with this PT without ticking the "Should the owner of the file be modified ?" box by example, everything goes fine.
Can you please elaborate more on what you saw ?
This bug is no more repetable. We should reject it
- Category set to Policy Templates
And it concerns Policy Templates
- File 1.png 1.png added
- Assignee changed from Nicolas PERRON to Matthieu CERDA
Nicolas PERRON wrote:
This bug is no more repetable. We should reject it
I disagree, the problem is still present.
To elaborate on it: this Technique (PT) has a checkbox "Should the owner of the file be modified ?". If you don't select it, you still have to put a value in the field "Owner of the file", which is not optional.
See the screenshot of an attempt to save a new Directive based on this Technique without specifying a user:
- Description updated (diff)
Oh, yes. There is a error on the description. It's the PT filePermissions, not the fileManagement one.
- Target version changed from 2.3.8 to 2.3.9
- Status changed from Discussion to Pending technical review
- % Done changed from 0 to 100
Applied in changeset commit:7f40d1e572d8e19d404db27ddcc629ff828a7697.
This has been hanging around too long, it's a quick fix, I'm doing it.
- Status changed from Pending technical review to Released
- Project changed from 24 to Rudder
- Category changed from Policy Templates to Techniques
Also available in: Atom
PDF