Project

General

Profile

Actions

Bug #5658

closed

User story #5293: Add a 'changes only' compliance mode, only reporting changes on systems

User story #5296: Create the logic to get execution reports for "error only" mode

full-compliance default value is wrong

Bug #5658: full-compliance default value is wrong

Added by Vincent MEMBRÉ about 11 years ago. Updated about 11 years ago.

Status:
Released
Priority:
N/A
Category:
Web - Maintenance
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

compliance mode default value is wrong.

default value is "fullCompliance", but accepted values are "full-compliance" and "error-only" It works fine since we fall back to full-compliance but there is an error message

Updated by Vincent MEMBRÉ about 11 years ago Actions #1

  • Parent task set to #5293

Updated by Vincent MEMBRÉ about 11 years ago Actions #2

  • Status changed from New to Pending technical review
  • Assignee changed from Vincent MEMBRÉ to François ARMAND
  • Pull Request set to https://github.com/Normation/rudder/pull/642

Updated by François ARMAND about 11 years ago Actions #3

Ah. that's that to do convergente state, we are missing when the starting point is not OK...

Thanks !

Updated by Vincent MEMBRÉ about 11 years ago Actions #4

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100

Updated by François ARMAND about 11 years ago Actions #6

  • Parent task changed from #5293 to #5296

Updated by Matthieu CERDA about 11 years ago Actions #7

  • Target version changed from 140 to 3.0.0~beta1

Updated by Vincent MEMBRÉ about 11 years ago Actions #8

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 3.0.0~beta1 which was release on 01/12/2014.

Actions

Also available in: PDF Atom