Project

General

Profile

Actions
Copy link

Bug #14218

closed

Constraints on table nodecompliancelevels are not valid

Added by Nicolas CHARLES almost 6 years ago. Updated almost 6 years ago.

Status:
Released
Priority:
N/A
Assignee:
François ARMAND
Category:
Web - Maintenance
Target version:
4.3.9
Pull Request:
https://github.com/Normation/rudder/p...
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Fix check:
Regression:

Description

Table nodecompliancelevels have 3 time the constrains on column nodeid <> '' - it should have been ruleId and directiveId

it's not really important, but the checks are still ok

Actions
Copy link
 #1

Updated by Nicolas CHARLES almost 6 years ago

  • Status changed from New to In progress
  • Assignee set to Nicolas CHARLES
Actions
Copy link
 #2

Updated by Nicolas CHARLES almost 6 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Nicolas CHARLES to François ARMAND
  • Pull Request set to https://github.com/Normation/rudder/pull/2119
Actions
Copy link
 #3

Updated by Nicolas CHARLES almost 6 years ago

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

Updated by Alexis Mousset almost 6 years ago

  • Subject changed from Constraint on table nodecompliancelevels are not valid to Constraints on table nodecompliancelevels are not valid
Actions
Copy link
 #5

Updated by Alexis Mousset almost 6 years ago

  • Status changed from Pending release to Released
This bug has been fixed in Rudder 4.3.9 and 5.0.5 which were released today. 
Changelog
 Changelog
Actions
Copy link

Also available in: Atom PDF