Project

General

Profile

Actions

Bug #14330

closed

By default, no group are supervised and new group are not supervised

Added by François ARMAND over 5 years ago. Updated about 1 year ago.

Status:
Released
Priority:
N/A
Category:
Web - Config management
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
I hate Rudder for that
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Small
Priority:
139
Name check:
Fix check:
Regression:
No

Description

When we install the change validation plugin no groups are selected as supervised so all modification are accepted without any change request.

Moreover, a new group is created as unsupervised which is a major authorization management problem.

By default, all groups and futur new group must be supervised, making them unsupervised must be a willing action.

To make that change without breaking compat, we need to store the "unsupervised-groups" and add a migration from the "supervised-groups" to unsupervised.

Actions #1

Updated by François ARMAND over 5 years ago

  • Project changed from Change validation to Rudder
  • Target version deleted (5.0-1.3)
Actions #2

Updated by François ARMAND over 5 years ago

  • Related to User story #14333: Remote run should optionnaly honor splay time in async mode added
Actions #3

Updated by François ARMAND over 5 years ago

  • Related to deleted (User story #14333: Remote run should optionnaly honor splay time in async mode)
Actions #4

Updated by Benoît PECCATTE over 5 years ago

  • Category set to Web - Config management
  • Severity set to Minor - inconvenience | misleading | easy workaround
  • User visibility set to Operational - other Techniques | Rudder settings | Plugins
  • Priority changed from 0 to 32
Actions #5

Updated by Nicolas CHARLES almost 5 years ago

  • Target version set to 5.0.13
  • Priority changed from 32 to 31
Actions #6

Updated by Vincent MEMBRÉ almost 5 years ago

  • Target version changed from 5.0.13 to 5.0.14
  • Priority changed from 31 to 30
Actions #7

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 5.0.14 to 5.0.15
  • Priority changed from 30 to 29
Actions #8

Updated by François ARMAND over 4 years ago

  • Effort required set to Very Small
  • Priority changed from 29 to 54
Actions #9

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 5.0.15 to 5.0.16
  • Priority changed from 54 to 53
Actions #10

Updated by Alexis Mousset over 4 years ago

  • Target version changed from 5.0.16 to 5.0.17
  • Priority changed from 53 to 51
Actions #11

Updated by Vincent MEMBRÉ about 4 years ago

  • Target version changed from 5.0.17 to 5.0.18
Actions #12

Updated by Vincent MEMBRÉ almost 4 years ago

  • Target version changed from 5.0.18 to 5.0.19
Actions #13

Updated by Vincent MEMBRÉ almost 4 years ago

  • Target version changed from 5.0.19 to 5.0.20
Actions #14

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 5.0.20 to 797
Actions #15

Updated by Benoît PECCATTE almost 3 years ago

  • Target version changed from 797 to 6.1.14
Actions #16

Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 6.1.14 to 6.1.15
Actions #17

Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 6.1.15 to 6.1.16
Actions #18

Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 6.1.16 to 6.1.17
Actions #19

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.1.17 to 6.1.18
Actions #20

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.1.18 to 6.1.19
Actions #21

Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 6.1.19 to 6.1.20
  • Priority changed from 51 to 52
Actions #22

Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 6.1.20 to 6.1.21
  • Priority changed from 52 to 53
Actions #23

Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 6.1.21 to old 6.1 issues to relocate
Actions #24

Updated by François ARMAND about 1 year ago

  • Subject changed from By default, no group is selected => it seems that change requests don't work to By default, no group are supervised and new group are not supervised
  • Description updated (diff)
  • Target version changed from old 6.1 issues to relocate to old 6.2 issues to relocate
  • Severity changed from Minor - inconvenience | misleading | easy workaround to Major - prevents use of part of Rudder | no simple workaround
  • UX impact set to I hate Rudder for that
  • Effort required changed from Very Small to Small
  • Priority changed from 53 to 137
  • Regression set to No
Actions #25

Updated by François ARMAND about 1 year ago

  • Status changed from New to In progress
  • Assignee set to François ARMAND
Actions #26

Updated by François ARMAND about 1 year ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from François ARMAND to Vincent MEMBRÉ
  • Pull Request set to https://github.com/Normation/rudder-plugins/pull/547
Actions #27

Updated by Anonymous about 1 year ago

  • Status changed from Pending technical review to Pending release
  • Priority changed from 137 to 138
Actions #28

Updated by Vincent MEMBRÉ about 1 year ago

  • Status changed from Pending release to Released
  • Priority changed from 138 to 139

This bug has been fixed in Rudder plugin change-validation v7.3.1-2.1

Actions #29

Updated by Vincent MEMBRÉ about 1 year ago

This bug has been fixed in Rudder plugin change-validation v7.2.6-2.1

Actions

Also available in: Atom PDF