Project

General

Profile

Bug #14218

Constraints on table nodecompliancelevels are not valid

Added by Nicolas CHARLES 7 months ago. Updated 7 months ago.

Status:
Released
Priority:
N/A
Category:
Web - Maintenance
Target version:
Severity:
User visibility:
Effort required:
Priority:
0

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

Associated revisions

Revision 35212245 (diff)
Added by Nicolas CHARLES 7 months ago

Fixes #14218: Constraint on table nodecompliancelevels are not valid

History

#1

Updated by Nicolas CHARLES 7 months ago

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

Updated by Nicolas CHARLES 7 months 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
#3

Updated by Nicolas CHARLES 7 months ago

  • Status changed from Pending technical review to Pending release
#4

Updated by Alexis MOUSSET 7 months ago

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

Updated by Alexis MOUSSET 7 months 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

Also available in: Atom PDF