Project

General

Profile

Actions
Copy link

Bug #23001

open

Double error message for “Users” technique cause compliance status to display “unexpected”

Added by Michel BOUISSOU over 1 year ago. Updated 5 months ago.

Status:
New
Priority:
N/A
Assignee:
-
Category:
Techniques
Target version:
7.3.17
Pull Request:
Severity:
Trivial - no functional impact | cosmetic
UX impact:
I was bothered the first time
User visibility:
First impressions of Rudder
Effort required:
Priority:
92
Name check:
To do
Fix check:
To do
Regression:
No

Description

When creating a directive from the built-in “Users” technique,

Specifying a group name that is the same as the user name (which BTW would be Linux defaults if non specified).

The compliance report for “Users” (here in audit mode) will display 2 errors :

- “[Unexpected] The user john ( John Doe ) could not be added to the system because the custom group "john" does not exist”
- “[Unexpected] The user john ( John Doe ) is not present on the system, which violates the presence policy”

Only one error message should appear.

Files

Directive_user_double_error.png (73.9 KB) Directive_user_double_error.png Compliance display Michel BOUISSOU, 2023-07-04 15:54

Related issues 1 (1 open — 0 closed)

Related to Rudder - Bug #23002: “Users” technique : Creating a user speficying the same group name as the user causes an errorNewActions
Actions
Copy link
 #1

Updated by Michel BOUISSOU over 1 year ago

  • Related to Bug #23002: “Users” technique : Creating a user speficying the same group name as the user causes an error added
Actions
Copy link
 #2

Updated by Michel BOUISSOU over 1 year ago

  • Priority changed from 78 to 110
Actions
Copy link
 #3

Updated by Alexis Mousset over 1 year ago

  • Category changed from System techniques to Techniques
Actions
Copy link
 #4

Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 7.3.4 to 7.3.5
Actions
Copy link
 #5

Updated by Alexis Mousset over 1 year ago

  • Target version changed from 7.3.5 to 7.3.6
Actions
Copy link
 #6

Updated by Vincent MEMBRÉ about 1 year ago

  • Target version changed from 7.3.6 to 7.3.7
  • Priority changed from 110 to 108
Actions
Copy link
 #7

Updated by Vincent MEMBRÉ about 1 year ago

  • Target version changed from 7.3.7 to 7.3.8
Actions
Copy link
 #8

Updated by Vincent MEMBRÉ about 1 year ago

  • Target version changed from 7.3.8 to 7.3.9
  • Priority changed from 108 to 106
Actions
Copy link
 #9

Updated by Vincent MEMBRÉ about 1 year ago

  • Target version changed from 7.3.9 to 7.3.10
  • Priority changed from 106 to 105
Actions
Copy link
 #10

Updated by Vincent MEMBRÉ 12 months ago

  • Target version changed from 7.3.10 to 7.3.11
  • Priority changed from 105 to 103
Actions
Copy link
 #11

Updated by Vincent MEMBRÉ 10 months ago

  • Target version changed from 7.3.11 to 7.3.12
  • Priority changed from 103 to 100
Actions
Copy link
 #12

Updated by Vincent MEMBRÉ 9 months ago

  • Target version changed from 7.3.12 to 7.3.13
  • Priority changed from 100 to 99
Actions
Copy link
 #13

Updated by Vincent MEMBRÉ 9 months ago

  • Target version changed from 7.3.13 to 7.3.14
  • Priority changed from 99 to 98
Actions
Copy link
 #14

Updated by Vincent MEMBRÉ 7 months ago

  • Target version changed from 7.3.14 to 7.3.15
  • Priority changed from 98 to 96
Actions
Copy link
 #15

Updated by Vincent MEMBRÉ 6 months ago

  • Target version changed from 7.3.15 to 7.3.16
  • Priority changed from 96 to 94
Actions
Copy link
 #16

Updated by Vincent MEMBRÉ 5 months ago

  • Target version changed from 7.3.16 to 7.3.17
  • Priority changed from 94 to 92
Actions
Copy link

Also available in: Atom PDF