Project

General

Profile

Actions
Copy link

Bug #8739

closed

group management technique doesn't ensure optional user is in group

Added by Florian Heigl over 7 years ago. Updated almost 2 years ago.

Status:
Released
Priority:
N/A
Assignee:
Nicolas CHARLES
Category:
Techniques
Target version:
3.1.24
Pull Request:
https://github.com/Normation/rudder-t...
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Getting started - demo | first install | level 1 Techniques
Effort required:
Priority:
0
Name check:
Fix check:
Regression:

Description

if the group already exists
"option Users included in the group (optional)"
doesn't work UNLESS you also select enforce the content of the group

Files

groups.png (103 KB) groups.png Florian Heigl, 2016-07-21 22:47
Actions
Copy link
 #1

Updated by Alexis Mousset over 7 years ago

  • Target version set to 2.11.24

Indeed, the "Enforce the group content" boolean is used as a condition to edit the group content.

We should have:
  • an option to append the users list to the group
  • an option to enforce only these users.

We should also rename the body named "groups_file_append" that does not append users but set the whole content of the group.

Actions
Copy link
 #2

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 2.11.24 to 308
Actions
Copy link
 #3

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 308 to 3.1.14
Actions
Copy link
 #4

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.14 to 3.1.15
Actions
Copy link
 #5

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.15 to 3.1.16
Actions
Copy link
 #6

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.16 to 3.1.17
Actions
Copy link
 #7

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.17 to 3.1.18
Actions
Copy link
 #8

Updated by Vincent MEMBRÉ about 7 years ago

  • Target version changed from 3.1.18 to 3.1.19
Actions
Copy link
 #9

Updated by Benoît PECCATTE about 7 years ago

  • Severity set to Major - prevents use of part of Rudder | no simple workaround
  • User visibility set to Operational - other Techniques | Technique editor | Rudder settings
  • Priority set to 0
Actions
Copy link
 #10

Updated by François ARMAND about 7 years ago

  • Severity changed from Major - prevents use of part of Rudder | no simple workaround to Minor - inconvenience | misleading | easy workaround
  • User visibility changed from Operational - other Techniques | Technique editor | Rudder settings to Getting started - demo | first install | level 1 Techniques
  • Priority changed from 0 to 31

The behavior is the expected one, but the label for the checkbox must be explicit about what it does (obviously, it is not).

Actions
Copy link
 #11

Updated by Vincent MEMBRÉ about 7 years ago

  • Target version changed from 3.1.19 to 3.1.20
Actions
Copy link
 #12

Updated by Jonathan CLARKE almost 7 years ago

  • Priority changed from 31 to 30
Actions
Copy link
 #13

Updated by Vincent MEMBRÉ almost 7 years ago

  • Target version changed from 3.1.20 to 3.1.21
Actions
Copy link
 #14

Updated by Vincent MEMBRÉ almost 7 years ago

  • Target version changed from 3.1.21 to 3.1.22
Actions
Copy link
 #15

Updated by Benoît PECCATTE almost 7 years ago

  • Priority changed from 30 to 29
Actions
Copy link
 #16

Updated by Benoît PECCATTE almost 7 years ago

  • Priority changed from 29 to 43
Actions
Copy link
 #17

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 3.1.22 to 3.1.23
  • Priority changed from 43 to 42
Actions
Copy link
 #18

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 3.1.23 to 3.1.24
Actions
Copy link
 #19

Updated by François ARMAND over 6 years ago

  • Translation missing: en.field_tag_list set to Sponsored
  • Severity changed from Minor - inconvenience | misleading | easy workaround to Major - prevents use of part of Rudder | no simple workaround
  • Priority changed from 42 to 79

There is in fact no easy workaround to be able to ensure that an user is in a group.

Actions
Copy link
 #20

Updated by Alexis Mousset over 6 years ago

  • Status changed from New to In progress
  • Assignee set to Alexis Mousset
Actions
Copy link
 #21

Updated by Alexis Mousset over 6 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Alexis Mousset to Nicolas CHARLES
  • Pull Request set to https://github.com/Normation/rudder-techniques/pull/1205
Actions
Copy link
 #22

Updated by Alexis Mousset over 6 years ago

  • Status changed from Pending technical review to Pending release
Actions
Copy link
 #23

Updated by Vincent MEMBRÉ over 6 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 3.1.24, 4.1.8 and 4.2.1 which were released today.

Actions
Copy link
 #24

Updated by Alexis Mousset almost 2 years ago

  • Priority changed from 79 to 0
Actions
Copy link

Also available in: Atom PDF