Project

General

Profile

Actions
Copy link

Bug #3179

closed

The rule list doesn't complain when a rule refers to a non existing group

Added by Nicolas CHARLES over 11 years ago. Updated about 11 years ago.

Status:
Released
Priority:
2
Assignee:
François ARMAND
Category:
Web - Compliance & node report
Target version:
2.4.3
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

Somehow, after a rollback, a Rule refered to a non existing Group.

The deployement failed, but there was no way to find on the rule grid if a rule is broken or not, and no way to repair without clicking everywhere or fixing in the LDAP..
Happens on rudder 2.5, but probably also on 2.4

Actions
Copy link
 #1

Updated by Nicolas CHARLES over 11 years ago

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

I confirm that it happens also on 2.4

Actions
Copy link
 #2

Updated by Nicolas CHARLES over 11 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Nicolas CHARLES to François ARMAND
Actions
Copy link
 #3

Updated by Nicolas CHARLES over 11 years ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100
Actions
Copy link
 #4

Updated by Anonymous over 11 years ago

Actions
Copy link
 #5

Updated by Nicolas PERRON about 11 years ago

  • Status changed from Pending release to Released
Actions
Copy link

Also available in: Atom PDF