Bug #16837
closed
userManagement produces missing reports when used in "check only" mode
Added by Félix DALLIDET over 4 years ago.
Updated over 1 year ago.
Severity:
Major - prevents use of part of Rudder | no simple workaround
User visibility:
Getting started - demo | first install | Technique editor and level 1 Techniques
Fix check:
Error - Blocking
Description
When setting the "Policy to apply on this account" to "Check Only" and setting the shell on an already existing user with the wrong shell,
it does not report.
Still, I believe we should not fix it. This option is very old and most likely come from a time where the audit mode wasn't available.
- Target version changed from 6.0.4 to 6.0.5
- Target version changed from 6.0.5 to 6.0.6
- Target version changed from 6.0.6 to 6.0.7
- Target version changed from 6.0.7 to 6.0.8
- Severity set to Major - prevents use of part of Rudder | no simple workaround
- User visibility set to Getting started - demo | first install | Technique editor and level 1 Techniques
- Priority changed from 0 to 66
- Target version changed from 6.0.8 to 6.0.9
- Priority changed from 66 to 65
- Target version changed from 6.0.9 to 6.0.10
- Priority changed from 65 to 64
- Status changed from New to In progress
- Assignee set to Nicolas CHARLES
- Status changed from In progress to Pending technical review
- Assignee changed from Nicolas CHARLES to Félix DALLIDET
- Pull Request set to https://github.com/Normation/rudder-techniques/pull/1620
- Status changed from Pending technical review to Pending release
- Subject changed from userManagement produce missing reports when used in Check only mode to userManagement produces missing reports when used in "check only" mode
- Priority changed from 64 to 63
- Fix check changed from To do to Error - Blocking
The correction seems to have worsen the problem: no I get "change detected in audit mode, abort"
=> see #18294
- Status changed from Pending release to New
- Target version changed from 6.0.10 to 798
- Priority changed from 63 to 62
- Target version changed from 798 to 6.1.14
- Priority changed from 62 to 58
- Target version changed from 6.1.14 to 6.1.15
- Target version changed from 6.1.15 to 6.1.16
- Target version changed from 6.1.16 to 6.1.17
- Target version changed from 6.1.17 to 6.1.18
- Target version changed from 6.1.18 to 6.1.19
- Target version changed from 6.1.19 to 6.1.20
- Target version changed from 6.1.20 to 6.1.21
- Target version changed from 6.1.21 to old 6.1 issues to relocate
- Status changed from New to Rejected
- Priority changed from 58 to 0
- Regression set to No
Could not reproduce in 7.2.0. The reporting was ok. Closing the ticket, feel free to re-open it and add more details to reproduce.
- Target version changed from old 6.1 issues to relocate to old 6.2 issues to relocate
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by